From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: detecting encoding for Japanese
Date: Tue, 03 Sep 2002 07:38:34 +0900 [thread overview]
Message-ID: <yotlwuq4585x.fsf@jpl.org> (raw)
In-Reply-To: <vaf8z2k8fj0.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
>>>>> In <vaf8z2k8fj0.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
>>>>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
[...]
Kai> Okay. So it seems that Japanese users always want what you are
Kai> saying.
Kai> What do you think about changing the default value to the
Kai> following expression?
Kai> (when (string= current-language-environment "Japanese")
Kai> '(iso-2022-jp iso-2022-jp-2 japanese-shift-jis utf-8))
Kai> We could add a comment saying that we still need to investigate
Kai> which values are good for other language environments.
That's good.
Kai> But I wonder if there is a right way to do this? The right way,
Kai> IMHO, would be to use the standard coding system priorities in
Kai> principle, except that they are slightly modified to prefer
Kai> iso-2022-jp over euc-jp. Hm. "emacs -q -no-site-file", then
Kai> setting the Japanese language environment, tells me:
Kai>| Priority order for recognizing coding systems when reading
Kai>| files: 1. iso-2022-jp (alias: junet)
Kai>| 2. japanese-iso-8bit (alias: euc-japan-1990 euc-japan euc-jp)
Kai>| 3. japanese-shift-jis (alias: shift_jis sjis)
Kai>| 4. iso-2022-jp-2
Kai>| 5. iso-latin-1 (alias: iso-8859-1 latin-1)
[...]
Although surely it becomes so in almost systems, please see the
function `setup-japanese-environment-internal' doing:
(defun setup-japanese-environment-internal ()
(cond ((eq system-type 'ms-dos)
(prefer-coding-system 'japanese-shift-jis))
((eq system-type 'usg-unix-v)
(prefer-coding-system 'japanese-iso-8bit)))
[...])
This is defined in language/japan-util.el and which will be
called from `(set-language-environment "Japanese")'. Because of
this, the coding priority in Solaris will be the order of:
(mapcar 'symbol-value coding-category-list)
=> (japanese-iso-8bit iso-2022-jp japanese-shift-jis
iso-2022-jp-2 iso-latin-1 iso-2022-7bit iso-2022-8bit-ss2
emacs-mule raw-text chinese-big5 nil no-conversion ...)
I do not know whether only `usg-unix-v' is special, though.
--
Katsumi Yamaoka <yamaoka@jpl.org>
next prev parent reply other threads:[~2002-09-02 22:38 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 5:48 Hal Snyder
2002-08-29 10:00 ` Kai Großjohann
2002-08-29 12:04 ` Simon Josefsson
2002-08-29 14:08 ` Hal Snyder
2002-08-29 16:01 ` Simon Josefsson
2002-08-29 16:24 ` Hal Snyder
2002-08-29 16:59 ` Kai Großjohann
2002-08-30 0:05 ` Katsumi Yamaoka
2002-08-30 12:23 ` Kai Großjohann
2002-09-02 12:16 ` Katsumi Yamaoka
2002-09-02 17:31 ` Kai Großjohann
2002-09-02 22:38 ` Katsumi Yamaoka [this message]
2002-09-03 1:52 ` Katsumi Yamaoka
2002-09-03 2:03 ` Katsumi Yamaoka
2002-09-03 6:19 ` Katsumi Yamaoka
2002-09-03 6:43 ` Katsumi Yamaoka
2002-09-03 21:43 ` Hal Snyder
2002-09-03 22:09 ` Kai Großjohann
2002-08-30 10:43 ` Simon Josefsson
2002-08-30 12:25 ` Kai Großjohann
2002-08-30 22:58 ` Hal Snyder
2002-09-11 10:40 ` Yoshiki Hayashi
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=yotlwuq4585x.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).