Re: Choosing right character representation for i18n issues

[GOTO Masanori <gotom@debian.or.jp>]

From: Markus Kuhn <Markus.Kuhn@cl.cam.ac.uk>
Subject: Re: Choosing right character representation for i18n issues 
> It is not really a serious political issue, more an issue among a few
> vocal Japanese geeks (many of which have neither read JIS X 0221 nor
> studied the unihan database). UCS is now an official Japanese Industrial
> Standard (JIS X 0221) and it is widely used for Japanese word processing
> (MS-Word, etc.). ISO 2022 is a bit like EBCDIC: Not entirely dead yet,
> but definitely smelling funny already.

Unfortunately, it seems that almost Japanese do not
see unicode texts in fact. 
Texts created by such a MS-Word, or so, are only represented
binary data, and if user want to output in text file mode,
the software automatically select SJIS encoding in many cases.
On Un*x system, many software cannot handle UTF-8 currently,
so the user who use Un*x select EUC encoding.

From: "Hirotaka Yoshioka" <hyoshiok@jp.oracle.com>
Subject: Re: Choosing right character representation for i18n issues
> > (MS-Word, etc.). ISO 2022 is a bit like EBCDIC: Not entirely dead yet,
> > but definitely smelling funny already.
> 
> iso-2022-jp is the common encoding for an internet mail for Japanese
> text.

Yes. iso-2022-jp has been widely used for an mail or news or irc.
But I merely meet that a person uses iso-2022-jp text in quite
separated situation(=mail/news).

From: Otfried Cheong <otfried@cs.ust.hk>
Subject: Re: Choosing right character representation for i18n issues
> When visiting Todai, I asked some Japanese students why Japanese
> didn't like Unicode, and the answer was quite surprising:

Todai(it means The University of Tokyo?) do 
another m17n, Kanji project.
Almost Japanese does not think the same, I think.

Regards,
--
GOTO Masanori
Department of Computational Intelligence and Systems Science,
Tokyo Institute of Technology.
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/