JS> Well, soemtimes there's a need to change the encoding of the
JS> terminal during the lifetime of the terminal.
JS> Korean xterm "Hanterm" [...] its support of UTF-8 is limited to
JS> [...] KS X 1001
That's a red herring. In an ideal world, you'd be running a single
UTF-8 terminal emulator with support for a large subset of Unicode,
and you'd never need to switch encodings.
The only reason to support ISO 2022 is for compatibility with legacy
applications.
Juliusz
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
- Re: Adjusting terminal via ISO 2022 to locale encoding Jungshik Shin
- Re: Adjusting terminal via ISO 2022 to locale encoding Markus Kuhn
- Re: Adjusting terminal via ISO 2022 to locale encoding Frank da Cruz
- Re: Adjusting terminal via ISO 2022 to locale encoding Jungshik Shin
- Re: Adjusting terminal via ISO 2022 to locale encoding Keld J�rn Simonsen
- Re: Adjusting terminal via ISO 2022 to locale encoding Tomohiro KUBOTA
- Re: Adjusting terminal via ISO 2022 to locale encoding Jungshik Shin
- Re: Adjusting terminal via ISO 2022 to locale encoding Kiyokazu SUTO
- Re: Adjusting terminal via ISO 2022 to locale encoding Bruno Haible
- Re: Adjusting terminal via ISO 2022 to locale encoding Bruno Haible
- Juliusz Chroboczek
