[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Unicode-2] euro sign disappears
From: |
Katsumi Yamaoka |
Subject: |
[Unicode-2] euro sign disappears |
Date: |
Fri, 16 Nov 2007 15:17:46 +0900 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.60 (gnu/linux) |
Hi,
I found strange behaviors of Emacs Unicode-2 when displaying the
euro sign. After starting Emacs as `LC_ALL=C emacs-23.0.60 -Q',
even if I run `set-language-environment' for the language of some
country belonging to EU, the following Lisp form doesn't display
the euro sign.
(insert (make-char 'latin-iso8859-15 164))
AFAIK, only the Japanese language environment displays it.
Europeans might have to run (set-language-environment 'Japanese)
before setting those native language environment. ;-)
Even in the Japanese language environment, a mail that is encoded
with `iso-2022-jp-2'[1] doesn't show the euro sign in it. For
example:
(insert (decode-coding-string "\e$(C\"f\e(B" 'iso-2022-jp-2))
I guess the cause of this problem is that the decoded string has
a charset property as follows:
(text-properties-at
0
(decode-coding-string "\e$(C\"f\e(B" 'iso-2022-jp-2))
=> (charset korean-ksc5601)
Aren't all concerned with a lack of charsets in
`charset-priority-list'? Or are they only to me?
In addition, is it right that Emacs uses a wide character for
displaying the euro sign? (It doesn't look suitable in English
text.)
[1] Gnus uses `iso-2022-jp-2' when encoding a mail containing
the euro sign because of the default value of
`mm-coding-system-priorities' that is set in the Japanese
language environment.
mm-coding-system-priorities
=> (iso-8859-1 iso-2022-jp iso-2022-jp-2 shift_jis utf-8)
It might be better to prefer `utf-8' than `iso-2022-jp-2' or
`shift_jis' nowadays.