3 ms·
> I would imagine things begin to improve around 2000 due to the broad adoption of unicode? Yes. I don't remember the exact timing, but it was the switchover t
by tkgally 2y ago
> I would imagine things begin to improve around 2000 due to the broad adoption of unicode?
Yes. I don't remember the exact timing, but it was the switchover to Unicode by Windows and Mac that finally resolved the character encoding conflicts (mostly).
I don't know how much attention this got outside Japan, but there was significant opposition here to Unicode for a while from some Japanese intellectuals. Handwritten and, sometimes, typeset Japanese has traditionally allowed for a lot of minor variations in the forms of kanji. A person might write their name with an extra stroke in one character, for example. Some of those variants are ignored in Unicode as well as in the Japanese encodings on which it is based, and some people kicked up a fuss about it in the Japanese press. I remember reading rants accusing Bill Gates of trying to suppress Japanese culture by imposing a homogenized character encoding through Windows.
The controversy has long since died down, though there have been efforts to develop more comprehensive character sets of Japanese and other Asian languages, such as TRON Code and Mojikyō:
https://en.m.wikipedia.org/wiki/TRON_(encoding) https://en.m.wikipedia.org/wiki/TRON_(encoding)
https://en.m.wikipedia.org/wiki/Mojiky%C5%8D https://en.m.wikipedia.org/wiki/Mojiky%C5%8D
- samatman 2y agoOh it gets attention on Hacker News to this day. Any time there's a thread about something Unicode one or another of our Japanese colleagues will show up to make a fuss about how Unicode is quite insufficient for Japanese, for this reason or that. In 2024 I'm out of sympathy for this. There's an entire tertiary plane for extended Hanzi/Kanji/ideographs, if there are still missing glyphs please take it up with the Unicode Consortium, because there's plenty of room and it is reasonable to support one (1) character encoding now. But it is in fact Microsoft's fault that the farcical attempt to squeeze "CJK" into a two-byte encoding was even attempted. They were firmly committed to the idea that UCS-2 could ever be viable and we're stuck with various consequences of this fatuous premise to this day.