Reply misinterprets Commas in encoded-words (Gnus violates RFC 2047)

[Reiner Steib <reinersteib+gmane@imap.cc>]

Hi,

back in September 2004, Stefan Wiens reported the following bug in
gnus.gnus-bug but there was no response or fix yet:

,----
| From: =?iso-8859-1?q?Wiens=2C_Stef=AAn?= <s.wi@gmx.net>
| Subject: Reply misinterprets Commas in encoded-words
| Newsgroups: gnus.gnus-bug
| Date: Sat, 18 Sep 2004 03:34:06 +0200
| Message-ID: <87pt4kbbsh.fsf@xenon.eswe.dyndns.org>
| 
| To reproduce, please try to "reply" or "wide reply" to this message
| and have a look at the "To" and "Cc" headers in your Message buffer.
`----

The problem is that Gnus decodes »=?iso-8859-1?q?Wiens=2C_Stef=AAn?=«
to »Wiens, Stefªn <s.wi@gmx.net>« in the article buffer and when doing
a (wide) reply, this leads to:

| To: Wiens
| Cc: Stefªn <s.wi@gmx.net>,  bugs@gnus.org

Note that this problem is not artifical (as the »ª« might suggest):
Many people in Germany or other countries have non-ascii in their
names.  If the mail software of the sender writes the full name in the
From/Cc header in the form »Lastname, Fírstname« the user cannot reply
correctly without manual correction.

In the German Gnus newsgroup this has been discussed several times:
(a) http://www.google.de/groups?as_umsgid=uoek8x11f.fsf@M.web.de&hl=en
(b) http://www.google.de/groups?as_umsgid=87brbdhc4d.fsf@ABG3595C.abg.fsc.net&hl=en

According to Stefan Wiens and Dirk Nimmich (tin developer), Gnus'
behavior violates RFC 2047 (see thread (a)).  Could somebody look at
this problem, please?  Stefan, maybe you could summarize this and the
other problems with Gnus RFC-2047 en/decoder again if necessary.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/