I bet when they created NSString, they thought that a simple 16-bit-per-character encoding ought-to-be-enough-for-everybody, and later they hacked this into UTF-16. I would've preferred ASCII hacked into UTF-8 instead ;)
-
To HarfBuzz I send the full substring (icu's ubidi separates ltr from rtl). I need code unit access for caret navigation in a basic editbox
Admittedly that works for the most basic cases, but even if you use a sane canonicalization, you still have to contend with the fact that Codepoints Aren’t Characters, and there are many instances where you don’t want an insertion point between them.
-
-
At least for games, where localization is done on demand and market size you can usually get away with assuming that one UTF-32 code point is one character, and can be rendered as such. Only exception in >20 languages we had was Arabic (and that was a marketing experiment)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.