4 ms·
Could also have issues with systems that have broken 16-bit-only Unicode support (Java, Windows, ...) in which code points beyond U+FFFF have to be encoded with
by kazinator 8y ago
Could also have issues with systems that have broken 16-bit-only Unicode support (Java, Windows, ...) in which code points beyond U+FFFF have to be encoded with some surrogate pair nonsense that is likely untested in many text-handling situations.
- planteen 8y agoThat's like saying UTF-8 requires "nonsense" pair, triplet, or quadruplet chars. UTF-16 handles all Unicode code points just fine. UCS-2 does not. Windows transitioned from UCS-2 to UTF-16 long ago.
- kazinator 8y agoThe problem is Windows programs, not Windows per se. The difference is that UTF-8 gets tested in this regard; multi-byte encoding situations actually occurring in UTF-8 are not rare occurrences that only trigger on funny characters that nobody uses. (For that matter, four-byte UTF-8 situations are in the same boat, of course, but not two- or three-.)
- loeg 8y ago> (For that matter, four-byte UTF-8 situations are in the same boat, of course, but not two- or three-.) Yeah. Notorious example here is MySQL's "utf8" column type only supporting 3-byte UTF-8 sequences.