Ah, Ohta-san. We can always count on him.
(His point is that if you have kanji in an IDN you can't tell whether to
draw it the Japanese way or the Chinese way, of course, and since
civilization as we know it depends on Japanese people never being
confronted with Chinese writing styles, even when being used for Chinese,
this obviously means that Unicode is Satan incarnate. Or something like
that.)
On Wednesday, March 20, 2002, at 01:01 AM, Doug Ewell wrote:
> The "experts" are out in force over on the Internationalized Domain Name
> (IDN) mailing list. Here's Mr. RFC 1815 with his thoughts on Unicode.
>
> -Doug Ewell
> Fullerton, California
>
>
> ----- Original Message -----
> From: "Masataka Ohta" <mohta@necom830.hpcl.titech.ac.jp>
> To: <idn-data@psg.com>
> Sent: Tuesday, March 19, 2002 11:22 pm
>
>
> D. J. Bernstein;
>
>> Paul Robinson writes:
>>> You tell him that although it's gobbledygook to people without greek
>>> alphabet support, it will still work. It's not convenient, but it
> WILL
>>> work. Guaranteed.
>>
>> False. IDNA does _not_ work. IDNA causes interoperability failures.
>
> IDNA does _not_ work, because Unicode does not work in International
> context.
>
>> People who say that IDN is purely a DNS issue are confused.
>
> It's purely a cultural issue.
>
>> In fact, the cost of fixing UTF-8 displays is much _smaller_ than the
>> cost of fixing IDNA displays. UTF-8 has been around for many years,
> has
>> built up incredible momentum (as illustrated by RFC 2277), and already
>> works in a huge number of programs.
>
> In international context, it is technically impossible to properly
> display Unicode characters.
>
> There is no implementation exist.
>
> While some implementations work in some localized context, local
> character set serves better for the context.
>
> Masataka Ohta
>
>
>
>
==========
John H. Jenkins
jenkins@apple.com
jenkins@mac.com
http://homepage.mac.com/jenkins/
This archive was generated by hypermail 2.1.2 : Wed Mar 20 2002 - 10:34:52 EST