On Fri, Jan 11, 2002 at 10:52:06PM +0900, Tomohiro KUBOTA wrote: > > Fixing the source code at the source is a lot cleaner than inflicting > > your "fix" on the rest of the world. It's as bad as Oracle's attempt > > to define a standard for its variant UTF-8 (CESU-8, which apparently > > should be pronounced 'sezyu' in English). Their stated reason is the > > same, that it's too much work to fix all of their databases, and > > their cure is to lay even more work off on the rest of the world. > > At first, this problem affect not only source codes but also > many texts of end users. You can easily imagine text files > of end users contain many "\" as currency sign AND many "\" > as a element of file names. Even if you may success to persuade > every Japanese Windows programmers to modify their source codes, > you won't be successful to persuade Japanese business users to > modify their files like accounts.xls .
A possibly more reasonable fix would be to change the fonts to the way they're supposed to be, and reverse the problem: they get backslashes instead of yen symbols for currency (and correctly get backslashes as delimiters.) Everything still works, except they end up with the problem, not the rest of the world. Then change \ to the correct Unicode yen symbol as appropriate (and most documents don't contain directory delimiters.) The problem with this is that I suspect most Japanese wouldn't be pleased to see backslashes instead of yen symbols. (It's easy enough to say "that's just as bad as the reverse; just do it", but that's not going to get any of them to go along with it.) -- Glenn Maynard -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
