[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: "James Seng" <jseng@pobox.org.sg>,"Simon Josefsson" <simon+idn@josefsson.org>
Subject: Re: [idn] Re: Legacy charset conversion in draft-ietf-idn-idna-08.txt
From: "James Seng" <jseng@pobox.org.sg>
Date: Tue, 28 May 2002 01:56:19 +0800
Cc: "IETF/IDN WG" <idn@ops.ietf.org>
References: <200205231129.HAA04661@ietf.org><iluk7pp67u3.fsf@latte.josefsson.org><001701c20586$5eae4130$5b00a8c0@JAMESSONYVAIO> <iluvg998x2i.fsf@latte.josefsson.org> <005601c2059f$7e12b790$5b00a8c0@JAMESSONYVAIO>

Let me clarify myself:

If you looking for a 1-to-1 code point mapping between ISO-2022 and ISO
10646, then there is no such table. ISO-2022 is design quite differently,
depending on the set of reportairs you operate upon.

-James Seng

> No. ISO-2022 specify a mechanism for encoding reportairs using code
> switching. The transcoding varies depending on the reportairs (up to 4)
you
> select. And it is not a 1-to-1 mapping with Unicode.

References:
- [idn] I-D ACTION:draft-ietf-idn-idna-08.txt
  - From: Internet-Drafts@ietf.org
- [idn] Legacy charset conversion in draft-ietf-idn-idna-08.txt
  - From: Simon Josefsson <simon+idn@josefsson.org>
- Re: [idn] Legacy charset conversion in draft-ietf-idn-idna-08.txt
  - From: "James Seng" <jseng@pobox.org.sg>
- [idn] Re: Legacy charset conversion in draft-ietf-idn-idna-08.txt
  - From: Simon Josefsson <simon+idn@josefsson.org>
- Re: [idn] Re: Legacy charset conversion in draft-ietf-idn-idna-08.txt
  - From: "James Seng" <jseng@pobox.org.sg>

Prev by Date: [idn] Re: FTP history
Next by Date: [idn] Re: FTP history
Previous by thread: Re: [idn] Re: Legacy charset conversion in draft-ietf-idn-idna-08.txt
Next by thread: [idn] Re: Legacy charset conversion in draft-ietf-idn-idna-08.txt
Index(es):
- Date
- Thread