3 ms·

> Japanese localization Shift-JIS or whatever 0x5c shenanigans were immediately brought back to mind. https://web.archive.org/web/20061208222907/http://blogs.

by lloeki 3y ago

> Japanese localization Shift-JIS or whatever 0x5c shenanigans were immediately brought back to mind. https://web.archive.org/web/20061208222907/http://blogs.msdn.com/michkap/archive/2005/09/17/469941.aspx https://web.archive.org/web/20061208222907/http://blogs.msdn... Still makes ripples to this day: https://superuser.com/questions/1167662/why-is-windows-10-displaying-as-¥-on-the-command-line https://superuser.com/questions/1167662/why-is-windows-10-di...

pezezin 3y ago
Shift-JIS is still a pain in the ass. I recently encountered two applications that only work properly in Japanese Windows, and in any other locale will just display mojibake. And these are modern applications, made in the last year. How is that even possible in 2023?
- ranger_danger 3y ago
  Because most (esp. Japanese) people don't know how to use Unicode properly, or don't care. They just build without defining UNICODE and naively assume your local codepage to be CP932 because 99% of their target audience is exactly this (and hence seemingly unaffected).
  - KingMob 3y ago
    Well, Unicode's Han unification process kind of screwed Japan, so that's somewhat understandable. It makes it hard to use Unicode for historical documents with older variants, documents using more than one CJK language (like talking about Chinese in Japanese), and worst of all, a lot of theoretically-compatible CJK fonts look wrong because they chose Chinese glyphs. There's many ways Unicode is an improvement over what came before, but they screwed up with Han unification.