Gnus development mailing list
 help / color / mirror / Atom feed
From: Hal Snyder <hal@vailsys.com>
Subject: Re: detecting encoding for Japanese
Date: Tue, 03 Sep 2002 16:43:52 -0500	[thread overview]
Message-ID: <87it1m21gn.fsf@ghidra.vail> (raw)
In-Reply-To: <vaf8z2k8fj0.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Mon, 02 Sep 2002 19:31:15 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

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

I don't think it's necessarily an issue of priorities. When there is
an incoming message without Content-type: properly set, it seems that
only iso-2022-jp is tried. The previously mentioned "AI" used when
opening a file, if applied to messages, should find the right encoding
- or at least distinguish iso/euc/sjis/utf8, regardless of priorities.



  parent reply	other threads:[~2002-09-03 21:43 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
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 [this message]
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=87it1m21gn.fsf@ghidra.vail \
    --to=hal@vailsys.com \
    /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).