Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Aidan Kehoe <kehoea@parhasard.net>
Subject: Re: XEmacs, Gnus and mm-coding-system priorities.
Date: Tue, 07 Dec 2004 07:30:27 +0900	[thread overview]
Message-ID: <b9ypt1n83gc.fsf@jpl.org> (raw)
In-Reply-To: <b9yeki45fb4.fsf@jpl.org>

[-- Attachment #1: Type: text/plain, Size: 121 bytes --]

It is strange that Aidan Kehoe's message replying to me and the
ding list didn't appear in the list again.  Here it is:


[-- Attachment #2: Type: message/rfc822, Size: 2591 bytes --]

From: Aidan Kehoe <kehoea@parhasard.net>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: XEmacs, Gnus and mm-coding-system priorities.
Date: Mon, 6 Dec 2004 13:35:46 +0000
Message-ID: <16820.24626.23607.206081.dm0@vm.parhasard.net>

 Ar an séiú lá de mí na Nollaig, scríobh Katsumi Yamaoka: 

 > [...] I tried your patch with the old mm-util.el and confirmed it works.
 > However, it doesn't work with non-Latin characters:
 > 
 > (let ((mm-coding-system-priorities '(shift_jis)))
 >   (rfc2047-encode-string (string (make-char 'japanese-jisx0208 38 66))))
 > 
 > It returns "=?shift_jis?Q?=83=C0?=" for Emacs, but
 > "=?iso-2022-jp?B?GyRCJkIbKEI=?=" for XEmacs.

Yes, that does make sense, because Latin Unity doesn’t yet work with
non-ISO, non-Unicode character sets. (If it ever will.)

Right, given that, the patch can’t solve the general case. You should
probably leave it out of the trunk until Latin Unity gets support for the
East Asian character sets, if it ever does. (And it might need a name change
at that point :-) Shame, because it did eliminate the most annoying thing I
find about Gnus on Mule; I _never_ want to send messages as iso-2022-jp, nor
as multipart messages split by character set.  

 > Although the default order of `mm-mime-mule-charset-alist' is just
 > suitable for Japanese messages and we don't need to modify
 > `mm-coding-system-priorities' in Japan, we will need to much improve it.
 > I will study your patch and look for the way to incorporate the
 > latin-unity feature in the latest mm-util.el.

Okay. Note that in Western Europe, the right thing to do is probably to send
a message in iso-8859-1 if its contents fit into that character set,
iso-8859-15 if it has the Euro sign, and UTF-8 if it has anything more
obscure than that. The current behaviour doesn’t really allow us to tell
Gnus that in XEmacs. 

-- 
“As democracy is perfected, the office of president represents, more and
more closely, the inner soul of the people. On some great and glorious day
the plain folks of the land will reach their heart’s desire at last and the
White House will be adorned by a downright moron.” – H.L. Mencken 

  parent reply	other threads:[~2004-12-06 22:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 16:55 Aidan Kehoe
2004-12-06  2:30 ` Katsumi Yamaoka
2004-12-06 13:35   ` Aidan Kehoe
2004-12-06 15:19   ` Katsumi Yamaoka
2004-12-06 22:30   ` Katsumi Yamaoka [this message]
2004-12-07  1:03     ` Katsumi Yamaoka
2004-12-07  0:10   ` Aidan Kehoe
2004-12-07  1:04     ` Katsumi Yamaoka
2004-12-07 12:32       ` Katsumi Yamaoka
2004-12-17 12:21         ` Aidan Kehoe
2004-12-17 12:46           ` Katsumi Yamaoka
2004-12-17 16:09             ` Katsumi Yamaoka
2004-12-31  9:01         ` XEmacs hangs in rfc2047-encode-string (Was: XEmacs, Gnus and mm-coding-system priorities.) Steinar Bang
2004-12-31 11:47           ` XEmacs hangs in rfc2047-encode-string Reiner Steib
2004-12-31 14:41             ` Steinar Bang
2004-12-31 19:10               ` Andrey Slusar
2005-01-01  9:04                 ` Steinar Bang
2005-01-01 18:03                   ` Andrey Slusar
2005-01-01 19:25                     ` Steinar Bang
2005-01-01 22:05                       ` Andrey Slusar
2005-01-02  7:49                         ` Steinar Bang
2004-12-31 12:53           ` Steinar Bang
2004-12-31 13:42           ` Arnaud Giersch
2004-12-31 14:45             ` Steinar Bang
2004-12-07  1:03 ` XEmacs, Gnus and mm-coding-system priorities Katsumi Yamaoka

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=b9ypt1n83gc.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=kehoea@parhasard.net \
    /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).