From: Katsumi Yamaoka <yamaoka@jpl.org>
To: emacs-devel@gnu.org
Subject: [Unicode-2] euro sign disappears
Date: Fri, 16 Nov 2007 15:17:46 +0900 [thread overview]
Message-ID: <b4mmyte1zp1.fsf@jpl.org> (raw)
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.
next reply other threads:[~2007-11-16 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 6:17 Katsumi Yamaoka [this message]
2007-11-16 7:10 ` [Unicode-2] euro sign disappears Kenichi Handa
2007-11-16 7:27 ` Katsumi Yamaoka
2007-11-16 10:24 ` Kenichi Handa
2007-11-16 11:06 ` Katsumi Yamaoka
2007-11-16 15:39 ` Stefan Monnier
2007-11-16 12:41 ` Robert J. Chassell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4mmyte1zp1.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.