Glenn Maynard writes: > The problem isn't the conversion costs, it's the fact that Windows will > continue to use the characters incorrectly, and will reintroduce the > problem continuously.
How can the Windows specific problem possibly affect us? In most cases, Japanese Windows users will send Shift_JIS encoded text for a while; Linux programs will continue to display Shift_JIS 0x5C as YEN SIGN. So there is no problem here. Later, when Japanese Windows users publish web pages in UTF-8, if they use U+005C for the YEN SIGN, and thus display salaries of "30000 \", then it's *their* problem because *their* software produces non-W3C compliant HTML or XML. In either case, there is no problem for Linux users. Bruno -- Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/linux-utf8/
