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

Roozbeh Pournader <[email protected]> Tue, 28 May 2002 19:54:26 +0430 (IRST)

Newsgroups	gmane.ietf.idn
Message-ID	<[email protected]>

On Tue, 28 May 2002, Simon Josefsson wrote:

> You are right.  What about other examples?
> 
> ISO-8859-1 0xB5:   U+00B5 / U+03BC: Mapped to U+03BC as you indicate
> ISO-8859-1 0xC5:   U+00C5 / U+212B: Mapped to U+00C5
> CP437 0xEA:        U+03A9 / U+2126: Mapped to U+03A9

These three won't cause any problem as you noted.

> JIS-X-0208 0x2140: U+005C / U+FF3C: ?

FF3C is compatibilitily mapped to 005C. So everything is fine.

> CP437 0xE1:        U+03B2 / U+00DF: ?
> CP437 0xEE:        U+03B5 / U+2208: ?

As far as I know, all existing CP437 tables map those to SMALL SHARP S
(U+00DF) and SMALL EPSILON (U+03B5) and not SMALL BETA or ELEMENT OF.
I just checked everywhere I could, this is the list:

	http://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/PC/CP437.TXT
	http://microsoft.com/globaldev/reference/oem/437.htm
	http://www.kostis.net/charsets/cp437.htm

Can you point me to anywhere disagreeing?

So you are suggesting that if one wants to use CP437 as the underlying
encoding, conform to IDNA RFCs, and then dives into Unicode charts for
finding the characters of CP437 instead of using tables he can find on the
net, he is in a real mess. I agree! The only thing we are disagreeing on 
is the real source of the mess. :-)

roozbeh