[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] Prohibit CDN code points
It is possible if we assume the ccTLD implied the language used . So, they
can be treated with different way based on the ccTLD name implied language.
Now, only gTLD has this problems. If only ASCII ".com" is used, it can
not identify which language is used in hostname part. But if ML-gTLD is
available , the ML(com) can be classfied by the implied language characters
in ML(com). Especially , ML(gTLD) is very small and can be predefined .
L.M.Tseng
----- Original Message -----
From: "Paul Hoffman / IMC" <phoffman@imc.org>
To: "ben" <ben@cc-www.com>; "Kenny Huang" <huangk@alum.sinica.edu>;
"IETF-IDN" <idn@ops.ietf.org>
Sent: Monday, January 21, 2002 2:00 AM
Subject: Re: [idn] Prohibit CDN code points
> At 12:30 PM -0500 1/20/02, ben wrote:
> >Is it possible to let the
> >Japanese and Korean domains names go forward and prohibit Chinese
> >domain names?
>
> No, and that one of the main problems that the CDN community faces.
> In the ISO/IEC 10646 repertoire (which is the same as the Unicode
> repertoire), it is impossible to differentiate between Chinese
> characters and Korean characters and Japanese characters. Thus, any
> proposal to remove the characters for one language removes them for
> all.
>
> --Paul Hoffman, Director
> --Internet Mail Consortium
>