Re: 5.8.2 bug#1: test тестtéßt test

[Vladimir Volovich <vvv@vvv.vsu.ru>]

"VV" == Vladimir Volovich writes:

RFC-2047> When displaying a particular header field that contains
RFC-2047> multiple 'encoded-word's, any 'linear-white-space' that
RFC-2047> separates a pair of adjacent 'encoded-word's is ignored.
RFC-2047> (This is to allow the use of multiple 'encoded-word's to
RFC-2047> represent long strings of unencoded text, without having to
RFC-2047> separate 'encoded-word's where spaces occur in the unencoded
RFC-2047> text.)

 VV> The subject contained a cyrillic word and a latin-1 word
 VV> separated by a real space. Gnus encoded both words as
 VV> encoded-word, but not encoded a space between them. As a result,
 VV> this space is ignored when displaying the subject.

Here is an encoded subject:

Subject: 5.8.2 bug#1: test =?koi8-r?b?1MXT1A==?= =?iso-8859-1?q?t=E9=DFt?= test
                                                ^
                                                |
The question is: is this space -----------------+ a 'linear-white-space'?

If yes (and thus it should be ignored when displaying), then gnus'
encoded-word *encoder* is broken. Otherwise (if this is not a
'linear-white-space'), gnus' encoded-word *decoder* (i.e. function
which decodes subject and displays it in summary and article buffers)
is broken. In each case, this is a bug in gnus which should be fixed.

Best,
v.