From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: Mike Kupfer <kupfer@athyra.sfbay.sun.com>, xemacs-beta@xemacs.org
Subject: Re: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers
Date: Mon, 20 Feb 2006 20:30:05 +0900 [thread overview]
Message-ID: <b4mslqel136.fsf@jpl.org> (raw)
In-Reply-To: <b4moe12mkql.fsf@jpl.org>
At last I realized the problem is due to my change:
2005-10-19 Katsumi Yamaoka <yamaoka@jpl.org>
* rfc2047.el (rfc2047-allow-incomplete-encoded-text): New variable.
(rfc2047-charset-to-coding-system): New function.
(rfc2047-decode-encoded-words): New function.
(rfc2047-decode-region): Use them.
(rfc2047-decode-cte): Remove.
(rfc2047-parse-and-decode): Remove.
(rfc2047-decode): Remove.
Formerly `rfc2047-decode' didn't verify whether a given charset
is valid, while `rfc2047-charset-to-coding-system' (which merged
the feature of `rfc2047-decode' partially) does it now using
`mm-coding-system-p'. However, it should be left to
`mm-charset-to-coding-system' even if it is incomplete[1] now.
Therefore, I've made a change in both the trunk and the v5-10
branch.
[1] The form (mm-charset-to-coding-system 'foo-bar-baz) returns
foo-bar-baz in non-Mule XEmacs 21.4.
The following diff is for the latest Gnus XEmacs package:
2006-02-20 Katsumi Yamaoka <yamaoka@jpl.org>
* rfc2047.el (rfc2047-charset-to-coding-system): Don't check the
coding system which mm-charset-to-coding-system returns for a
given charset is valid.
--- rfc2047.el~ 2005-12-19 22:31:44 +0000
+++ rfc2047.el 2006-02-20 11:29:44 +0000
@@ -835,7 +835,7 @@
(cond ((eq cs 'ascii)
(setq cs (or (mm-charset-to-coding-system mail-parse-charset)
'raw-text)))
- ((setq cs (mm-coding-system-p cs)))
+ ((mm-coding-system-p cs))
((and charset
(listp mail-parse-ignored-charsets)
(memq 'gnus-unknown mail-parse-ignored-charsets))
next prev parent reply other threads:[~2006-02-20 11:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601280127.k0S1RqD7007468@athyra.sfbay.sun.com>
[not found] ` <87irs44xm9.fsf@tleepslib.sk.tsukuba.ac.jp>
2006-01-29 20:05 ` Reiner Steib
2006-01-29 22:24 ` Steve Youngs
2006-01-29 22:40 ` Reiner Steib
2006-01-30 1:16 ` Stephen J. Turnbull
2006-02-17 22:13 ` Date of XEmacs' Gnus (5.10.7) package (was: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers) Reiner Steib
2006-01-30 23:24 ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-01-30 23:39 ` where does package-get-info get its info from? (was: gnus 5.10.7 not rendering Latin-1 headers) Mike Kupfer
2006-01-31 1:11 ` where does package-get-info get its info from? Steve Youngs
2006-02-18 0:34 ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-02-18 14:55 ` Stephen J. Turnbull
2006-02-19 12:48 ` Reiner Steib
2006-02-19 22:11 ` Mike Kupfer
2006-02-19 23:22 ` Reiner Steib
2006-02-20 7:41 ` Katsumi Yamaoka
2006-02-20 9:40 ` Katsumi Yamaoka
2006-02-20 11:30 ` Katsumi Yamaoka [this message]
2006-02-20 19:20 ` Mike Kupfer
2006-02-21 18:29 ` Mike Kupfer
2006-02-20 8:46 ` Stephen J. Turnbull
2006-02-20 9:41 ` Reiner Steib
2006-02-20 15:52 ` Stephen J. Turnbull
2006-02-20 21:26 ` Miles Bader
2006-04-09 8:14 ` Aidan Kehoe
2006-04-11 18:35 ` Reiner Steib
2006-04-13 22:34 ` Mike Kupfer
2006-04-14 8:14 ` Stephen J. Turnbull
[not found] <17990.13620.262943.353149@parhasard.net>
2007-05-13 9:20 ` Gnus: Autoloads for parse-time.el variables (was: [PATCH] package building problems.) Reiner Steib
2007-05-13 12:45 ` Aidan Kehoe
2007-05-14 17:21 ` Mike Kupfer
[not found] <m33awph096.fsf@Overgaard.mail.dk>
[not found] ` <878x6g6yz7.fsf@uwakimon.sk.tsukuba.ac.jp>
2007-10-06 16:09 ` [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages Reiner Steib
2007-10-07 13:47 ` Thomas Overgaard
2007-10-09 21:13 ` gnus 5.10.8 for XEmacs (was [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages) Mike Kupfer
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=b4mslqel136.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=kupfer@athyra.sfbay.sun.com \
--cc=xemacs-beta@xemacs.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).