Tomohiro KUBOTA wrote on 2001-02-01 17:03 UTC:
> I don't understand why you hate the statefulness, while terminals
> have other statefulness (thus we sometimes need 'stty sane' or
> 'Do Full Reset') after crash of curses-based software. I think
> you are guessing how escape sequences are annoying by your imagination,
> not by your daily usage of Kterm (or other ISO-2022-enabled terminals).
>
> Though I use ISO-2022-JP (has escape sequences)-enabled terminal
> (say, Rxvt with kanji enabled) everyday for real purpose, I don't
> feel any inconvenience.
Can we please go back to discussing how to make UTF-8 the only/primary/
main character encoding for Linux. This is the only purpose of this
mailing list. This is *NOT* a generic-localization-please-support-
my-favourite-encoding-too mailing list. ISO 2022 is dead. It has not the
slightest chance of ever becoming globally used outside CJK countries.
What kterm users find practical causes nothing but sheer horror for
non-CJK developers. Adding ISO 2022 support to an existing applications
is one to two orders of magnitude more expensive than adding UTF-8
support. That is why ISO 2022 never got supported by any of the standard
Unix packages (MULE being the only noteworthy exception). ISO 2022 has
not even the slightest chance to be of any help for a transition to
UTF-8. ISO 2022 is what ISO 10646 was designed to *replace* completely.
Recommended bedtime horror literature for tonight:
http://www.ecma.ch/ecma1/STAND/ECMA-035.HTM (= ISO 2022)
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/
