On 2/16/21, Dominik Pantůček <[email protected]> wrote: > > On 16. 02. 21 22:27, Matthew Flatt wrote: >> At Tue, 16 Feb 2021 16:03:29 -0500, Ben Greenman wrote: >>> Sadly, I've already compressed a few files using >>> `call-with-output-string` ... is there an easy way to decompress those >>> / undo the UTF-8 encoding? >> >> Unfortunately, the underlying `get-output-string` conversion is lossy, >> because bytes that don't form a UTF-8 encoding are converted to U+FFFD. >> >> (I see that the docs say #\? instead of #\uFFFD, and I'll fix the docs.) >> > > #\uFFFD is #\� (bytes EF BF BD in UTF-8) > > For those who do not see it (I suspect encoding issues) it is a white > question mark on black vertically elongated hexagon. > > And actually Racket REPL in my terminal displays it like this (7.9 BC, > 8.0 CS, both on Ubuntu 20.04 in GNOME terminal).
Alas, I see lots of those question mark hexagons in my data. Good to know. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/CAFUu9R5b5Y1kFQ0JuTtrTO-L14xFndABn-cSm44VB5s6H9wDRA%40mail.gmail.com.
