(gnus-summary-supersede-article, gnus-summary-resend-message-edit):

 Bind mail-parse-charset to the value of gnus-newsgroup-charset to decode
 non-MIME encoded text in message header.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index f5f6377..bde885f 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,10 @@
+2008-08-08  Katsumi Yamaoka  <yamaoka@jpl.org>
+
+       * gnus-msg.el (gnus-summary-supersede-article)
+       (gnus-summary-resend-message-edit): Bind mail-parse-charset to the
+       value of gnus-newsgroup-charset to decode non-MIME encoded text in
+       message header.
+
 2008-07-30  Katsumi Yamaoka  <yamaoka@jpl.org>
 
        * rfc2104.el (rfc2104-string-make-unibyte): Define it as a compiler

diff --git a/lisp/gnus-msg.el b/lisp/gnus-msg.el
index 77210e9..555b6a0 100644 (file)
--- a/lisp/gnus-msg.el
+++ b/lisp/gnus-msg.el
@@ -812,7 +812,8 @@ post using the current select method."
 This is done simply by taking the old article and adding a Supersedes
 header line with the old Message-ID."
   (interactive)
-  (let ((article (gnus-summary-article-number)))
+  (let ((article (gnus-summary-article-number))
+       (mail-parse-charset gnus-newsgroup-charset))
     (gnus-setup-message 'reply-yank
       (gnus-summary-select-article t)
       (set-buffer gnus-original-article-buffer)
@@ -1274,7 +1275,7 @@ A new buffer will be created to allow the user to modify body and
 contents of the message, and then, everything will happen as when
 composing a new message."
   (interactive)
-  (let ((article (gnus-summary-article-number)))
+  (let ((mail-parse-charset gnus-newsgroup-charset))
     (gnus-setup-message 'reply-yank
       (gnus-summary-select-article t)
       (set-buffer gnus-original-article-buffer)