On Wed, 16 May 2001, Tomohiro KUBOTA wrote:
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_.
You may be right, but I don't see any reason not to use ISO 2022
escape sequences for character set designation (put cha. set xxx in G0,
put char. set yyy in G1, put char. set zzz in G2 and invoke G0 on GL,
invoke G1 and G2 on GR alternatingly with single shift or locking shift)
as a way to "announce" what encoding is going to be in effect from that
point on.
> > - 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.
Well, soemtimes there's a need to change the encoding of the terminal
during the lifetime of the terminal. Think about this. Most of time
I invoke my mail client Pine under Korean xterm "Hanterm" (which can
support three encodings, EUC-KR, UTF-8, and JOHAB). However, its support
of UTF-8 is limited to all Hangul syllables along with Chinese characters
and symbols defined in KS X 1001. So, when I get an email in ISO 8859-1
(containing characters with acute/grave accent and so forth) or UTF-8
(with lots of characters outside the repertoire of 11,172 Hangul syllables
plus Chinese characters and symbols in KS X 1001), I need to open an
xterm to reat that email. If xterm can understand the announcement of
the encoding we're talking about, I can make Pine automatically switch
(with the conditional invocation of 'display filter') encodings depending
on MIME charset of email messages. I believe Mutt has a similar feature
and Lynx can be made (modified ) to make use of this feature. That way,
I never have to run multiple Pine sessions (running in multiple terminals
with different encodings ).
Jungshik Shin
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
