Re: proposal for a "Standard-Exit" or "Namespace" character

• Previous message: Doug Ewell: "Re: proposal for a "Standard-Exit" or "Namespace" character"
• In reply to: Kenneth Whistler: "Re: proposal for a "Standard-Exit" or "Namespace" character"
• Next in thread: James Kass: "Re: proposal for a "Standard-Exit" or "Namespace" character"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

Kenneth Whistler <kenw at sybase dot com> wrote:

>> however, it should
>> provide a character to mark the position at which unicode is 'closed'
>> or 'left'.
>
> And that is defined by ISO/IEC 10646 itself:
>
> "When the escape sequences from ISO/IEC 2022 are used, the
> identification of a return, or transfer, from UCS to the
> coding system of ISO/IEC 2022 shall be by the escape sequence
> ESC 02/05 04/00. ..."

OK, time to test my understanding of ISO 2022. I think 2022 defines
<ESC 02/05 04/00> as the standard return from any character set, and it
was repeated in 10646 for convenience.

--
Doug Ewell  *  Thornton, Colorado, USA  *  RFC 4645  *  UTN #14
http://www.ewellic.org
http://www1.ietf.org/html.charters/ltru-charter.html
http://www.alvestrand.no/mailman/listinfo/ietf-languages  ˆ

• Next message: David Starner: "Re: proposal for a "Standard-Exit" or "Namespace" character"
• Previous message: Doug Ewell: "Re: proposal for a "Standard-Exit" or "Namespace" character"
• In reply to: Kenneth Whistler: "Re: proposal for a "Standard-Exit" or "Namespace" character"
• Next in thread: James Kass: "Re: proposal for a "Standard-Exit" or "Namespace" character"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2.1.5 : Mon Apr 13 2009 - 20:56:46 CDT