Add a comment

Any way to "URI safe" a UTF16 compression? Comment from jugglervr on February 12, 2016 1:29:49 AM PST # I'm trying to store some data in the URI and I want to compress it to ensure that I don't run into problems with IE's 2k limit. UTF16 gives good ratios but has problems with some characters: "Uncaught SyntaxError: Failed to execute 'querySelectorAll' on 'Document':" Is there a good way to escape these strings or am I stuck with Base64?
Any way to "URI safe" a UTF16 compression? Comment from Anonymous on April 24, 2024 1:23:10 AM PDT #
Title
Body	HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
OpenID Login	(Not me?)
Name
E-mail address
Website
Remember me	Yes No
E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).

Home

All that is in there is just stuff I made up for the most part. However, the chances that some truth found its way in it are non negligible so this possibility should not be discarded. After all, I usually link to my sources. That said, those sources are most likely probably completely made up as well. You want to make sure it's going to work? Try it out for yourself. Ah, as well, those parts that are not blatantly stolen to others are © Pieroxy. Obviously. And last, but not least, thanks to David Vignoni for his icon set nuvola, to Manfred Klein for his font Stampede and to George Herriman for the work of his life, Krazy Kat.

Add a comment

Any way to "URI safe" a UTF16 compression?

Any way to "URI safe" a UTF16 compression?