Hi,

At Tue, 23 Oct 2001 12:25:00 +0100 (BST),
Markus Kuhn wrote:

> Unfortunately, that doesn't work right out-of-the-box yet.
> 
> Elisp has at the moment no direct way of accessing the output of
> nl_langinfo(CODESET), therefore Emacs doesn't know about the current
> locale's character set and can't consider this information when deciding
> on the character set of a loaded file. Gerd Moellmann <[EMAIL PROTECTED]> said
> that fixing this would already be on the post-21 todo list.

Emacs 20 already had a mechanism to guess encoding of the file
with ordered candidate list of encodings.  The problem is, we have
to configure the list.  ("set-language-environment" set this list.)

For example, in Japanese environment, the encoding-guesser will
check the encoding of the file with the candidate of EUC-JP,
Shift_JIS, and ISO-2022-JP.  (UTF-8 should be added to this list).

Thus, what is configured using LC_CTYPE variable should the top
candidate for the guesser, not the unique candidate.


I think terminal-coding-system should also be set from LC_CTYPE.
I heard a few months ago that Emacs21 will be able to do this.
Now Emacs21 has been released.  Did someone tested?

Also, Emacs20 in X Window System could not display non-ISO-8859-1
characters without some settings in ~/.emacs or ~/.Xresources
(these characters were displayed by white box).  This is caused
by improper default font configuration.  Is this problem fixed
in Emacs21 ?

---
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/

Reply via email to