Hi,
At 15 May 2001 20:10:11 +0200,
Juliusz Chroboczek <[EMAIL PROTECTED]> wrote:
> This is an issue which is currently of concern to me. Which of the
> non-ISO 2022 encodings do we want to support? Do they all preserve at
> least C0?
Note that ISO 2022 is a scheme to switch _character sets_
(JIS X 0208, ...), not _encodings_ (EUC-JP, ...). Thus,
ISO 2022 parser will not support any _encodings_.
> - UTF-8;
> - ???.
>
> What escape sequences do you suggest they should use?
For ISO-2022-compliant and non-ISO-2022-compliant "encodings"
such as ISO-8859-*, EUC-*, KOI8-*, Shift_JIS, Big5, UTF-8, and
so on (other than stateful ISO-2022-*), XTerm itself will support
these encodings via "-lc" mode. In other words, XTerm will
work as a Big5 terminal under Big5 locale. I think Big5 people
will be happy with this and they don't need ISO 2022 parser.
Those who use ISO-2022-* encodings (full ISO 2022,
ISO-2022-JP{,-1,-2,-3}, ISO-2022-CN{,-EXT}, ISO-2022-KR,
ISO-2022-INT-{1,2}, and so on) will need ISO 2022 parser.
Thus, I don't understand why it is important for the ISO 2022
parser to support UTF-8, Big5, and so on, because these encodings
will be supported by -lc mode of XTerm. ISO 2022 parser is
important only for encodings which are not supported by iconv()
or libiconv.
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://www.debian.or.jp/~kubota/
"Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
