At Tue, 16 Feb 2021 15:44:54 -0500, Ben Greenman wrote: > But in my compressed string, the second > byte is #o357 for some reason. I'm not sure how that could have > happened ... some kind of encoding issue with string ports?
Yes. You want `call-with-output-bytes` on the compress size and `call-with-input-bytes` on the decompress side. Otherwise, you'll get a UTF-8 decoding of compressed bytes (which is unlikely to be meaningful). -- 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/20210216135644.203%40sirmail.smtps.cs.utah.edu.
