News for hackers. Stuff that matters.
Re:The Tragedy of UCS-2 by gumby on Saturday August 03, 2019 @12:23PM (#20601163)
I remember the politics of this well. It was all about legacy encodings (similar to the UCS-2 issue in the article). There were many encodings (“code pages” in MS land) for each language or character set, even Latin-derived ones. Just getting a single one for Cyrillic or Greek was a hurdle, with the most common in use as the “default”. True character unification would have been great, but was too much of a hurdle because you couldn’t just use an 8-bit character space plus a single offset. This was in the days of 16-bit machines, remember.

This legacy support is why there are precomposed characters.

It’s not quite the same for Han unification (people using those alphabets were already used to complex gyration was ao e). In that case the linguists, historians and other scientists were in agreement but they neglected politics. In Latin unification nobody cares that J sounds different in every language, but because Hanzi embody semantics, Japan may have a loancharacter because it once sounded the same as a word in use at the time OR because it had the same meaning as a word in use at the time so the sense of “unified” can be contentious, even though they are simply code points.

There are no comments on this comment yet.