Re: URL internationalization!

Masataka Ohta <[email protected]> Tue, 11 Mar 97 19:14:28 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.
> 
> I never spoke about "CJK(V) ideograph *script*", I only spoke
> of individual characters.

What we are daily using is "script".

> Some people use the term "script" for
> CJK(V) ideographs, others, such as you, prefer not to do so.
> For the discussion here, it's largely irrelevant, because
> it is the individual characters that matter.

If it's individual characters, character sets containing Latin,
Greek and Cyrillic 'A's are ambiguous and is unusalble.

> You started the discussion with the terms "Hanzi script" and
> "Kanji script", but please note that the majority of Japanese
> will use the word "Kanji" also for the characters used in
> China,

Don't try to confuse terminologies. The majority of Japanese
use the word "Eiji" also for the Latin characters used for
Franch.

> > 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.
> 
> How come that you claim ISO 10646 can't? It can represent all
> the characters in the Kanji-Kana-majiri "script". What else
> would be needed?

Huh? Support of 'Kanji-Kana-majiri "script"' is perfectly possible
with ISO 10646, which I have shown in RFC1815.

But, it's a localization issue of Japanization of ISO 10646.

It is unrelated to the fact that ISO 10646 is no good for the
internationalization.

> > BTW, JIS X 0208 itself already contains too many similar
> > characters that exact match of code points is useless for real
> > world search.
> 
> Agreed. Search engines have to take this into account.

Sure.

> But current URLs allow case distinction, and search engines
> also have to take this into account, so it's not a problem.

Not a problem of what?

Do you want to say that ISO-2022-JP is fine?

But, URLs are not for search engines.

						Masataka Ohta