I liked UTF-8 more before I started to think hard about efficient RISC-V BitManip code for encoding/decoding it.
-
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...
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"..
-
-
*weeps* Perhaps we should just go over to using emoji as our only form of writing.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
And surely the accompanying WTF-16
-
- Show replies
New conversation -
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.