I liked UTF-8 more before I started to think hard about efficient RISC-V BitManip code for encoding/decoding it.
-
-
Replying to @oe1cxw
UTF is quite mad, and UTF-8 actually made it worse because it mostly is interchangeable with ASCII so mostly appears to work - except when it doesn’t.
1 reply 0 retweets 2 likes -
Replying to @kentindell @oe1cxw
The range of surrogate pairs is forbidden as code point forever because people thought 16 bits had to be enough for everyone but now the range of all code points ever is like a few millions again because the surrogate pairs can't encode beyond. Haha you say UTF-8 is crazy...
1 reply 0 retweets 0 likes -
Replying to @ledave123 @kentindell
But windows allows UTF-16 filenames that contain single surrogate code points (not as part of pairs) so now we also have WTF-8, that can contain such things so we can handle windows file names "properly"..
2 replies 0 retweets 1 like -
-
Replying to @ledave123 @kentindell
It's even on Wikipedia :Dpic.twitter.com/yFGyN136xA
1 reply 0 retweets 1 like
And I also found this that I wasn't aware of before.pic.twitter.com/dlbKH6iwpU
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.