>>>>> In Reiner Steib wrote: > On Thu, Feb 17 2005, Katsumi Yamaoka wrote: >> From: Wiens, Stefªn >> >> I wrote that it seems to be difficult to parse. > Would it be possible to build the (Reply) headers from the original > (undecoded) article? That is what I just wrote that it seems to be difficult. ;-) > My impression is that this would be necessary in order to fix the > problem. 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. > There are some problems with this patch. After applying your patch, I > see the *encoded* From in the Summary and Article buffer: >| From: =?iso-8859-1?q?Wiens=2C_Stef=AAn?= Eh?, that's strange. I've modified neither the decoder nor the core of the encoder, hmm..., but now, let's junk it anyway. I'm sorry to have waste your time. * gnus-msg.el (gnus-copy-article-buffer): Quote decoded words containing special characters. * rfc2047.el (rfc2047-encode-parameter): Use ietf-drums-tspecials. (rfc2047-quote-decoded-words-containing-tspecials): New variable. (rfc2047-decode-region): Quote decoded words containing special characters when rfc2047-quote-decoded-words-containing-tspecials is non-nil.