Re: URL internationalization!
Masataka Ohta <[email protected]> Tue, 25 Feb 97 16:34:56 JST
| Newsgroups | gmane.ietf.url |
|---|---|
| Message-ID | <[email protected]> |
Martin; > > And, ISO 10646 can't handle multiple scripts of Hanzi and Kanji. > > This issue has been mentionned before. Of course, ISO 10646 > can handle CJK(V) ideographs What we, Japanese, daily use is not "CJK(V) ideograph" script but Kanji-Kana-majiri script. As ISO 2022 based encoding already supports Kanji-Kana-majiri script in fully internationalized way but ISO 10646 can't, there is no further discussion possible that ISO 10646 is internationalized. > URLs are identifiers, Sure. So, we need nothing more than ASCII. > Fortunately, this is less than 1% of the cases that > would be created if each of the typographic traditions > had separate codepoints. In too many cases, the error rate of 1% is unacceptable. > Having an artificial distinction between Chinese (which comes > in two variants, traditional and simplified), Japanese, > Korean, and Vietnamese CJKV ideographs in identifiers such > as URLs would lead to a multiplication of the problems > that Masataka rightfully hinted at in the case of Latin > and Greek A/Alpha. What we, Japanese, daily use is not "CJK(V) ideograph" script but Kanji-Kana-majiri script. Just remove artificial "CJK(V) ideograph" and no artificial distinction necessary. BTW, JIS X 0208 itself already contains too many similar characters that exact match of code points is useless for real world search. Masataka Ohta