This, of course, means that a ton of Japanese Windows users don't actually know how to type their own currency sign, because they keep typing \ and Microsoft helpfully displays it as ¥. Except, you know, no other OS does that.
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
...to be fair Microsoft tends to have a TON of software issues related to legacy stuff.

-
imagine all dropping legacy conventions, it won't be windows anymore.
End of conversation
New conversation -
-
-
tbh, lain won't care about that shit, she uses operating systems from apple. or did those do the same shit?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
In DOS, codepage 437 or 850 was used. Both have the ¥ in it. And since Windows, codepage 1252 is usually used, which also has it. Since NT, Microsoft is using Unicode-16 internally, with even less issues. Why should this be MS‘s fault? International coding is hard.
-
Because Windows is doing this as a hack on *Unicode* systems. They are literally displaying the wrong glyph for a particular Unicode code point, on purpose. Only on Japanese locales. That's a violation of the Unicode standard.
- Show replies
New conversation -
-
-
Same in Korea with the ₩, it's always fun trying to navigate to C:₩Users₩Sky₩My Documents.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
it can't be entirely blamed on Microsoft. ISO 646 was the original sin.
-
Korea has the same thing for ₩
End of conversation
New conversation -
-
-
But this could be handy! I was helping a friend of mine to program the software which uses small character LCD display. We needed any currency sign other than $. I tried to output "\" to the display and it worked: ¥ was shown!
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.