Hi,
At Sun, 04 Feb 2001 15:15:02 +0000,
Markus Kuhn <[EMAIL PROTECTED]> wrote:
> I write in the same document (my thesis) English text in a Roman font,
> Latin insets in italic, and computer source code in a Courier font. I do
> this multi-linugal processing in ASCII and this is really *EXACTLY* just
> the same as a Japanese/Chinese multilingual text.
Again and again I have to say that difference between Chinese and
Japanese characters is not like difference Roman and Italic glyphs
but like difference between Latin and Greek characters.
And, it is not geeks but all average Japanese people who cannot read
Chinese version of U+76F4. CJK Han Unification is a problem for
average Japanese people, who don't know about encodings. They
just read Japanese or Chinese texts, just feel characters are funny
and just don't buy such products. It is also a problem for foreigners
who want to study Japanese language. They may remember wrong characters.
And more, complain about CJK Han Unification is NOT related to ISO-2022.
Unicode could be without unifying too many CJK Ideographs, just by
assigning larger code space when the initial Unicode was developed.
Yes, I insisted ISO-2022 is a solution for CJK Han Unification, but
it is a fact that we need a solution even if we don't use ISO-2022.
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://surfchem0.riken.go.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/lists/
