Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: detecting encoding for Japanese
Date: Mon, 02 Sep 2002 19:31:15 +0200	[thread overview]
Message-ID: <vaf8z2k8fj0.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <yotld6rwmvrr.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 02 Sep 2002 21:16:40 +0900")

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> In <vaf1y8g5yck.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
>>>>>>	Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
>
> Kai> Another thought: Mule itself also has a priority list of
> Kai> encodings.  So I wonder why does Gnus need another priority list?
> Kai> Normally, I'd guess that Japanese would normally configure their
> Kai> Emacs for the right priorities, and then Gnus should do the right
> Kai> thing automatically.  There could be two reasons why this is not
> Kai> happening: (1) Japanese use a different encoding in email than in
> Kai> editing files, or (2) the priorities that Emacs sets up normally
> Kai> do not propagate properly to Gnus, or (3) Emacs does not set
> Kai> itself up for the right priorities at all when users setup a
> Kai> Japanese language environment.  Yes, I can't count...
>
> That's a good consideration.  (1) is the main reason.  Though
> iso-2022-jp is used for mail messages, euc-jp has mainly been
> used in UNIX and DOS has used shift_jis.  Although it will be
> different with the system-type, Emacs gives a priority to euc-jp
> or shift_jis in general and it is a right way for editing files.
> It seems to be a good way that Emacs offers the priority list
> for mails apart from the list for files for the specified
> language environment.

Okay.  So it seems that Japanese users always want what you are
saying.

What do you think about changing the default value to the following
expression?

    (when (string= current-language-environment "Japanese")
      '(iso-2022-jp iso-2022-jp-2 japanese-shift-jis utf-8))

We could add a comment saying that we still need to investigate which
values are good for other language environments.

But I wonder if there is a right way to do this?  The right way,
IMHO, would be to use the standard coding system priorities in
principle, except that they are slightly modified to prefer
iso-2022-jp over euc-jp.  Hm.  "emacs -q -no-site-file", then setting
the Japanese language environment, tells me:

/----
| Priority order for recognizing coding systems when reading files:
|   1. iso-2022-jp (alias: junet)
|   2. japanese-iso-8bit (alias: euc-japan-1990 euc-japan euc-jp)
|   3. japanese-shift-jis (alias: shift_jis sjis)
|   4. iso-2022-jp-2 
|   5. iso-latin-1 (alias: iso-8859-1 latin-1)
|   6. iso-2022-7bit 
|   7. iso-2022-8bit-ss2 
|   8. emacs-mule 
|   9. raw-text 
|   10. chinese-big5 (alias: big5 cn-big5)
|   11. no-conversion 
|   12. mule-utf-8 (alias: utf-8)
\----

So it seems that Emacs already prefers iso-2022-jp over euc-jp.  It's
not clear to me where the problem comes from.  Do you get a different
output from M-x describe-coding-system RET RET?

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)



  reply	other threads:[~2002-09-02 17:31 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 [this message]
2002-09-02 22:38                   ` Katsumi Yamaoka
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=vaf8z2k8fj0.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).