Hi,
At Thu, 01 Feb 2001 19:30:50 +0000,
Markus Kuhn <[EMAIL PROTECTED]> wrote:
> 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.
Then please discuss about _removing_ support for 8bit encodings from
all softwares. :-p
Though I joined this mailing list very recently, I am glad to find that
many members are interested in supporting locale encodings. Note that
'locale encodings' include not only EUC-* but also ISO-8859-*. Only
few members, like you, are thinking about inhibiting all encodings
(maybe including ISO-8859-*) other than UTF-8.
> ISO 2022 is dead. It has not the
> slightest chance of ever becoming globally used outside CJK countries.
It is _your_ opinion. You don't have to use ISO-2022. I never force
you using ISO-2022. (While you seem to want to force all of us using
UTF-8...)
> 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).
I agree. I understand I cannot want _every_ softwares will support
ISO-2022 because it is too heavy duty for almost developers in the world.
(Many of them even don't know about LANG environmental variable!)
I want a few infrastructure softwares such as XTerm to support it
(so that ISO-2022-enabled software can run on them), and also, I need
it with low priority. (We can use Japanese without ISO-2022 support,
while we are really annoyed by tremendous amount of softwares which
can use 8bit encodings only.)
---
Tomohiro KUBOTA <[EMAIL PROTECTED]>
http://surfchem0.riken.go.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/
