Re: Choosing right character representation for i18n issues

["Hirotaka Yoshioka" <hyoshiok@jp.oracle.com>]

Hi,

Markus Kuhn wrote:
> > Still another point is that I have heard that not all problems that
> > the CJKV users have with UTF-8 are of a technical nature, some of them
> > are political.
> 
> As a Japanese friend of mine put it nicely recently: many of the
> Japanese "experts" who engage in anti-Unicode flame wars are usually
> hardcore geeks with imaginary requirements far away from every-day
> reality. We have such geeks on the Unicode mailing list for almost any
> common language, not just Japanese.
> 
> > And repairing all the technical problems does of
> > course not repair the political issues.  Where could I learn more
> > about the political and technical sides of this?
> 
> 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). 

I agree your comments (many of them don't read JIS X0221).

We had a BOF at Linux World Expo Tokyo regarding an internationalization
of open source software. I made a question to the floor if you have read
the Unicode standard. Very few people raised the hand.

But if the Unicode standard is translated into Japanese, I think
the situation could be changed and many misunderstanding will
be vanished.

> 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.

iso-2022-jp is the common encoding for an internet mail for Japanese
text.

Regards,
   Hiro
-- 
Hiro Yoshioka/Principal Engineer
mailto:hyoshiok@jp.oracle.com (office)
http://www.best.com/~yoshioka/d/98/
The statements, views and opinions expressed here are my own 
and do not necessarily represent those of Oracle Corporation
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/