Re: Adjusting terminal via ISO 2022 to locale encoding

[Markus Kuhn]

Juliusz Chroboczek wrote on 2001-05-15 18:10 UTC:
> JS> However, there are people like me who want to switch between fully
> JS> ISO-2022 compliant encodings (which are not ISO-8859-x) and UTF-8
> JS> depending on the locale.
> 
> This is an issue which is currently of concern to me.  Which of the
> non-ISO 2022 encodings do we want to support?

I'd suggest KOI8-R (as defined by the RFC) and those code pages for
which Microsoft submitted a conversion table to the Unicode consortium.

They should all go under ESC % ... as they all leave C0 and would be
used with standard return.

Better even would be to rewrite ISO 2022 to add support for 128
character large graphic sets in the CR/GR area.

> Do they all preserve at
> least C0?
> 
>  - UTF-8;
>  - ???.
> 
> What escape sequences do you suggest they should use?

We could put together a proper list (in the format required by ISO 2375)
and then ask [EMAIL PROTECTED] to register them as a "coding
system different from that of ISO 2022, with standard return".

We'd just need a sponsoring national standards body sponsoring the
proposal. Keld?

Markus

-- 
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org,  WWW: <http://www.cl.cam.ac.uk/~mgk25/>

-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/