bug in encoded-word encoding

[vvv@vsu.ru]

Hi,

i composed a mail in gnus (current cvs version), with the following
To: header:

To: Дмитрий И. Гусев <some@where>

gnus encoded it like this:

To: =?koi8-r?b?5M3J1NLJyiDp?=. =?koi8-r?b?59XTxdc=?= <some@where>

which is a bug according to RFC2047:

 RFC2047> IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's
 RFC2047> by an RFC 822 parser.  As a consequence, unencoded white space
 RFC2047> characters (such as SPACE and HTAB) are FORBIDDEN within an
 RFC2047> 'encoded-word'.  For example, the character sequence
 RFC2047>     =?iso-8859-1?q?this is some text?=
 RFC2047> would be parsed as four 'atom's, rather than as a single 'atom' (by
 RFC2047> an RFC 822 parser) or 'encoded-word' (by a parser which understands
 RFC2047> 'encoded-words').  The correct way to encode the string "this is some
 RFC2047> text" is to encode the SPACE characters as well, e.g.
 RFC2047>     =?iso-8859-1?q?this=20is=20some=20text?=
 RFC2047> The characters which may appear in 'encoded-text' are further
 RFC2047> restricted by the rules in section 5.

gnus should have included the dot into the encoded-word, instead of
putting int immediately after it.

i think that such a bug was once fixed, but somehow it is again
present. :-(( i wonder, why....

(it is not a good sign that fixed bugs are appearing again and again)

Best,
v.