Re: [URN] Re: URL internationalization!
"YON - Jan C. Hardenbergh" <[email protected]>
| Newsgroups | gmane.ietf.url |
|---|---|
| Organization | Netscape Communications |
| Message-ID | <[email protected]> |
Masataka Ohta wrote:
>
> > > 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. Living in the US
with a name like Jan makes this a hot button for me.
> > Perhaps, if you used the ASCII hacking of the IPA, I could go along
> > with that.
>
> No, we don't.
>
> 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.
> 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?
> Multi-language support is doable with ASCII only and is orthogonal
> to multi-script support.
???
> > 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!
> 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.
YON