Hi,
At Mon, 25 Jun 2001 12:01:45 +0100,
Markus Kuhn <[EMAIL PROTECTED]> wrote:
> What Emacs cannot yet do reliably is to automatically determine the
> system's default encoding by looking at the output of
> nl_langinfo(CODESET).
Emacs's encoding-related functionality is more than locale mechanism
can supply. For example, in Japanese "language environment", Emacs
can guess the encoding of the reading file, ISO-2022-JP, EUC-JP, or
Shift_JIS. Such "priority list" for encoding guessing is declared
for each "language environment". And more, the "language environment"
includes input methods. This idea is much more than locale mechanism.
However, I guess your idea is nice. In "ja_JP.eucJP" locale, the
priority list would be EUC-JP -> Shift_JIS -> ISO-2022-JP, while in
"ja_JP.SJIS" locale, it would be Shift_JIS -> EUC-JP -> ISO-2022-JP.
UTF-8 can be inserted in the list when Emacs 21 is released.
BTW, I am surprised you suggested such an idea because I feel
you don't like XTerm to have nl_langinfo(CODESET). Am I wrong?
> What Emacs cannot yet do reliably is to automatically determine the
> system's default encoding by looking at the output of
> nl_langinfo(CODESET).
What XTerm cannot yet do reliably is to automatically determine the
system's default encoding by looking at the output of
nl_langinfo(CODESET).
---
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/linux-utf8/
