Re: URL internationalization!

> >> >ASCII script is rich enough to denote French, Japanese, Thai,
> >> >Arabic, Hindi...
> 
> ROTFLOL. ASCII dosn't work properly for English, never mind all those others.

OK. Your mail in ASCII is not English.

> Can you pronounce "ghoti" in English orthography? Use "gh" as in "laugh",
> "o" as in "women", and "ti" as in "nation". (Example due to George Bernard
> Shaw)[1]

Sure.

> There is no standard for representing Arabic or any other non-Latin script
> in English, much less in international ASCII.

.....

It is of course, impossible to represent Arabic language in
English, because Arabic language and English are different
languages.

Instead, there are formal and/or informal ways to represent
English in Latin script, Arabic language in Latin script,
English in Arabic script or Arabic language in Arabic script.

> Anyway, this is a non-issue.

Of course.

> Anyone who wishes to can use ASCII URLs, and
> the question is whether and how to accommodate those who wish to use their
> own scripts.

There is no need to represent URL in non-ASCII.

> The key issue is that regardless of anyone's preferences, Unicode is the
> only international standard for handling multiple scripts that the major
> software vendors are willing to implement and use as the basis for
> internationalizing their operating systems and applications.

Major software vendors has already implemented, say, ISO-2022-JP,
to handle multiple scripts.

And, ISO 10646 can't handle multiple scripts of Hanzi and Kanji.

> I vote yes, yes, permitted but discouraged for future use, [sigh], don't be
> silly, I hope so, and Hooray!

Just repeating your opinion without any reasoning is nothing.

							Masataka Ohta