Re: Legacy charset conversion in draft-ietf-idn-idna-08.txt

Paul Hoffman / IMC <[email protected]> writes:

>>   When all systems use ASCII or Unicode, different
>>+interpretations are not allowed in this specification.
>
> I think that goes too far. A user system that "uses Unicode" could
> still make wrong judgements between the keyboard and the encoding. For
> example, on the Mac, typing Option-8 inserts a bullet character. There
> are many different bullet characters in the Unicode character
> repertoire, so entering a host name that includes one of those bullet
> symbols might get the wrong result. Thus, I'd rather not use that last
> sentence.

Yes, I agree.

>>+When involved systems use non-ASCII and non-Unicode characters (such
>>+as ISO-8859-1 and ISO-2022-JP, which are common on the Internet),
>
> We're not concerned with what is common on the Internet, but what is
> common in systems.

Make it "common in systems on the Internet" then.  I doubt you care
about how I handle IDN's in my own disconnected system?  Or just
"common".