Hello,
Paul Prescod <[EMAIL PROTECTED]> wrote:
> I've never heard of a Japanese competitor to XML nor even Japanse
> complaints about it. I know many Japanese people who use.
Because Japanese have already had many and many problems about
character set and character encoding.
Some problems are caused by legacy character sets and encodings
(yes, Japanese legacy encodings aren't good, too).
Some are caused by Unicode. Some are in XML, some are in HTML
and CGI, some are in DB, some are in ordinary text.
Unicode problem in XML is just one of these problems. So,
Japanese may not complaint about it. In a sense, it is similar
to problems we have struggled to solve in many years
(with very ugly and ad-hoc way...).
# Do you know numeric character reference in i-mode HTML?
# They don't use Unicode, but Shift-JIS as character number(?!).
# (It's crazy, isn't it?)
# They don't complaint about Unicode. They just don't use it.
> "This technical report and [XML] treat Shift-JIS, an ordinary Japanese
> charset in Japan, as a CES that represents Japanese characters and
> [US-ASCII] characters in [ISO/IEC10646] or [Unicode 3.0]. For full
> interoperability in the Internet, migration from Shift-JIS to
> UTF-8/UTF-16 is highly recommended. "
>
> They suggest (surprisingly!) not only use of the Unicode character set
> but even the standard Unicode encodings.
Do you understand why they recommend to use UTF-8/UTF-16?
Because they think we cannot solved character conversion
problem. If there is an solution, they allowed to use
Shift-JIS, and convert into Unicode when we need. But they
don't think so, so they suggest for us never to use Shift_JIS
(and other japanese character encodings) in XML.
If we follow this suggestion when we design Parrot,
we should not use Shift_JIS and EUC-JP to write Parrot-based
language's script and data, to avoid conversion problems.
It may be the only way to avoid this problem, but it's not
useful for Japanese, at least today.
Best Regards,
TAKAHASHI 'Maki' Masayoshi E-mail: [EMAIL PROTECTED]
