Re: [URN] Re: URL internationalization!

Masataka -

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

A very crude multilingual support is doable with the basic Latin
script only. And at some point, there were even people that claimed
that all languages would have to switch to it to keep up with
computer technology. But actually, computer technology has improved
a lot, and this is no longer necessary nor desirable.


> > 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.

Definitely not. I already mentionned several serious problems
with ISO-2022. I got reminded here of one I forgot, but which
is rather crucial:

- ISO-2022 interferes with URL reserved characters. ISO-2022-JP,
	for example, can contain, in stretches that encode
	Japanese characters, octets with the same values as
	"/" or "#" and so on.


> UTF8 is not a proper charset at all. Look at RFC 1815 on how
> to construct proper charsets from ISO 10646.

There is nothing in the relevant definitions of MIME "charset"s
that prescribes that a sender or receiver would be required
to display all of the characters that can be encoded with a
given "charset".


Regards,	Martin.