From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: XEmacs, Gnus and mm-coding-system priorities.
Date: Tue, 07 Dec 2004 10:04:08 +0900 [thread overview]
Message-ID: <b9yy8ga7wc7.fsf@jpl.org> (raw)
In-Reply-To: <16820.62708.663703.64580.z25zdq@parhasard.net>
>>>>> In <16820.62708.663703.64580.z25zdq@parhasard.net> Aidan Kehoe wrote:
> 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))))
> I was wrong, I can work around this. Since latin-unity knows the list of
> coding systems it can map into, we can check each entry in
> mm-coding-system-priorities for validity before trying to remap with it. So,
> for example, if shift_jis is in mm-coding-system-priorities, the latin unity
> code should just give up, and mm-find-mime-charset falls back to the code
> you had written.
That's good. I also vaguely thought it might be possible.
> I've a revised patch and test set (including your tests from the last mail)
> attached that addresses this. I'm also going to post this to gnu.emacs.gnus
> because ding@gnus evidently doesn't like me :-) .
Too bad. Maybe the administrator is taking a winter vacation?
Anyway, thank you for the new patch. I wish we could merge it
by the time Gnus v5.10.7 is released.
> In terms of usability, I'm starting to feel strongly that
> mm-coding-systems-priorities should be initialised to '(iso-8859-1
> iso-8859-15 iso-8859-2 iso-8859-16 utf-8) for non-East-Asian
> locales. Americans don't care, but for non-English speaking Europeans the
> Mule breakage just another reason not to use an Emacs.
Currently the default value for `mm-coding-systems-priorities'
is non-nil only in the Japanese language environments, which is
done by examining the value for `current-language-environment'.
Is it able to set `(iso-8859-1 iso-8859-15 ...)' by the same
way? If so, do you know those language names?
next prev parent reply other threads:[~2004-12-07 1:04 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
2004-12-07 1:03 ` Katsumi Yamaoka
2004-12-07 0:10 ` Aidan Kehoe
2004-12-07 1:04 ` Katsumi Yamaoka [this message]
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=b9yy8ga7wc7.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).