At last I realized the problem is due to my change:
2005-10-19 Katsumi Yamaoka <yamaoka(a)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(a)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))