Re: Reply misinterprets Commas in quoted encoded-words

[Katsumi Yamaoka <yamaoka@jpl.org>]

>>>>> Katsumi Yamaoka wrote:
>>>>>> Reiner Steib wrote:
>> I got the following report in the German Gnus newsgroup [1]: When
>> replying to a mail with this from header ...

>>| From: "=?iso-8859-1?Q?Fghijkl,_Wolf-J=F6rg?=" <schnuerpel@example.com>

>> ... you get the following:

>>| To: ""Fghijkl
>>| Cc: Wolf-Jörg"" <schnuerpel@example.com>

>> On reply Gnus seems to double the quotes.

> Confirmed.  I'm going to make shift to fix this bug.  Thanks.

Fixed in the Gnus trunk.  I've improved the rfc2047 code so as not
to quote decoded words containing special characters (`,' is it in
this case) if there are the quotation marks around the words already.
It is effective only when the quotation marks are adjacent to words,
doesn't check whether the quotation marks are not the ones used for
the neighboring words.  So, the following ones might cause a similar
(or another) problem:

From: " =?iso-8859-1?Q?Fghijkl,_Wolf-J=F6rg?= "
From: "FOO"=?iso-8859-1?Q?Fghijkl,_Wolf-J=F6rg?="BAR"

(It's very hard to distinguish which word is quoted by `"'s)

BTW, please keep in mind that quoted-encoded-words are all illegal.
RFC2047 says:

   + An 'encoded-word' MUST NOT appear within a 'quoted-string'.

Though Gnus decodes even such things for users' convenience.
The person's name should have been encoded as it is done by Gnus as
follows:

(rfc2047-encode-string "\"Fghijkl, Wolf-Jörg\"")
 => "=?iso-8859-1?Q?Fghijkl=2C_Wolf-J=F6rg?="

Note that `, ' is encoded into `=2C_'.

Regards,