Re: Reply misinterprets Commas in encoded-words (Gnus violates RFC

[Katsumi Yamaoka <yamaoka@jpl.org>]

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

>>>>> In <b9yis4ql3wu.fsf@jpl.org> Katsumi Yamaoka wrote:

> I agree.  Today I found a better way to fix the problem without
> modifying the rfc2047 encoder.  It doesn't require to modify the
> way to build the reply headers either.  The solution is to quote
> decoded words in the " *gnus article copy*" buffer (in which the
> reply headers are extracted) if there are special characters.
> The new patch for the trunk is below.

Please apply the following additional patch.  It is needed so as
not to quote words in the Subject header, etc.


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 937 bytes --]

--- rfc2047.el~	2005-02-18 07:31:04 +0000
+++ rfc2047.el	2005-02-18 08:40:05 +0000
@@ -830,9 +830,19 @@
 	    ;; things essentially must not be there.
 	    (while (re-search-forward "[\n\r]+" nil t)
 	      (replace-match " "))
-	    (when rfc2047-quote-decoded-words-containing-tspecials
-	      ;; Quote decoded words if there are special characters
-	      ;; which might violate RFC2822.
+	    ;; Quote decoded words if there are special characters
+	    ;; which might violate RFC2822.
+	    (when (and rfc2047-quote-decoded-words-containing-tspecials
+		       (let ((regexp (car (rassq
+					   'address-mime
+					   rfc2047-header-encoding-alist))))
+			 (when regexp
+			   (save-restriction
+			     (widen)
+			     (beginning-of-line)
+			     (while (and (memq (char-after) '(?  ?\t))
+					 (zerop (forward-line -1))))
+			     (looking-at regexp)))))
 	      (let (quoted)
 		(goto-char e)
 		(skip-chars-forward " \t")