Hi,
At Thu, 10 Jan 2002 13:40:09 -0800,
Edward Cherlin wrote:
> > (Unfortunately, Microsoft Japanese fonts don't *have* a
> > single-width backslash *at all*, which means terminal
> > emulators--which typically don't want to deal with multiple
> > fonts--are hard pressed to do anything like this at all. Grrr.)
>
> These broken fonts must be replaced. That is the only way to get
> proper display of Japanese using Japanese fonts in Unicode under
> Windows. Unfortunately, they exist because some Japanese claim that
> they are *necessary* for proper display of Japanese in Unicode, which
> is nonsense.
Yes, I think this is a mess. However, Microsoft cannot change it.
For example, I can write
"the cost is \100 and the file is C:\text\abc.txt" or,
printf("The cost is \\100.\n");
Here, "\" in "\100" or "\\100" means yen sign (and you may think
it should be mapped into U+00A5), while the codepoint of U+005C
is proper for "\" in file name or "\n". We cannot transcode such
strings in automatic way. Thus, Microsoft chose a way that
"\" is mapped into U+005C and the glyph for U+005C is yen sign.
I heard that Java also have such mapping table.
I agree this is a severe violation of Unicode standard but I don't
know any clean solution.
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://www.debian.or.jp/~kubota/
"Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/
--
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
