Re: [URN] Re: URL internationalization!

YON

> > > > ASCII script is rich enough to denote French, Japanese, Thai,
> > > > Arabic, Hindi...
> > >
> > > This is just wrong!
> > 
> > Look at international airline tickets of people from France, Japan,
> > Thai, Arab and India and tell me what is wrong.
> 
> I was trying to decipher my airline ticket the other day. The first
> problem is that NO ONE can pronounce anyone's name.

Very good point. Still, anyone can transcribe your name.

Don't make NO ONE can pronouce nor transcibe anyone's URL.

> Living in the US
> with a name like Jan makes this a hot button for me.

Does "Jan" contain non-ASCII characters?

> > We are not interested in transcribing pronounciation of various
> > language to the accuracy of IPA, which is sometimes excessive
> > and somtimes insufficient.
> 
> Show me the way.

Of what?

> > Each language already has its own denotation system in basic 26
> > Latin alphabets, most, if not all, of them are unrelated to IPA.
> 
> Spec'd by whom?

In Japan, it's ministry of foreign affairs.

You should ask airline office.

> > Multi-language support is doable with ASCII only and is orthogonal
> > to multi-script support.
> 
> ???

Let's see the following Japanese translation of my sentence above:

	Maruchi ringaru sapohto ha asukii dakede dekirunode atte,
	maruchi sukuriputo sapohto toha chokkou suru gainen da.

which is a sentence of Japanese language with Latin script.

That is, this mail is a bi-lingual mail with ASCII only.

> > > Besides, all you ASCII lovers should be exceptionally excited by
> > > Martin's proposal because ASCII is a subset of utf8 (RFC 2044)
> > 
> > No, not at all. ISO-2022-{JP, KR, CN, JP-2} are all supersets
> > of ASCII and better than utf8 in all aspects.
> 
> Font management with ISO 2022 is intractable! 

Wrong. It is only that whether some font is available or not.

So is ISO 10646. Read RFC 1815.

And, it is usually the case that when someone does not have a font
of some character, that person can't read the character, anyway.

Still, I can type "Jan". Isn't it a great multilingual monoscript
internationalization accomplished by ASCII?

> > UTF8 is not a proper charset at all. Look at RFC 1815 on how
> > to construct proper charsets from ISO 10646.
> 
> Of course utf8 is not a charset. It is an encoding of ISO 10646.

Absolutely.

						Masataka Ohta