missing spaces in encoded-word displaying

missing spaces in encoded-word displaying

[Vladimir Volovich]

Hi,

with pgnus 0.83 (sorry, cannot test with newer version just now), i've
got a mail with the following subject:

Subject: Re: =?KOI8-R?Q?=CF=DE=C5=CE=D8_=CE=D5=C4=CE=CF_=D0=D2=CF_=DB=D2=C9=C6=D4=D9_(LH?=
  =?koi8-r?b?ySDsydTF0sHU1dLOwdE=?=)

Gnus shows this subject in Article buffer (and in the summary buffer)
in the following way:

Subject: Re: очень нудно про шрифты (LHи Литературная)

Note that there is no space between "LH" and "и". Imho, there should
be a space (i've tested how Outlook Express displays a subject, and
there is a space).

Is this a bug in Gnus?

Best,
v.

Re: missing spaces in encoded-word displaying

[Toby Speight]

Vladimir> Vladimir V. Volovich <URL:mailto:vvv@vvv.vsu.ru>

0> In article <eyg0ycaqc0.fsf@video.uic.vsu.ru>, Vladimir wrote:

Vladimir> with pgnus 0.83 (sorry, cannot test with newer version just
Vladimir> now), i've got a mail with the following subject:
Vladimir>
Vladimir> Subject: Re: =?KOI8-R?Q?=CF=DE=C5=CE=D8_=CE=D5=C4=CE=CF_=D0=D2=CF_=DB=D2=C9=C6=D4=D9_(LH?=
Vladimir>   =?koi8-r?b?ySDsydTF0sHU1dLOwdE=?=)
Vladimir>
Vladimir> Gnus shows this subject in Article buffer (and in the summary
Vladimir> buffer) in the following way:
Vladimir>
Vladimir> Subject: Re: очень нудно про шрифты (LHи Литературная)
Vladimir>
Vladimir> Note that there is no space between "LH" and "и". Imho,
Vladimir> there should be a space (i've tested how Outlook Express
Vladimir> displays a subject, and there is a space).
Vladimir>
Vladimir> Is this a bug in Gnus?

IINM, it's a bug in OE[1].  Space between adjacent encoded-words is
not significant, and should be elided.  One reason for this is so that
very long phrases with no spaces can be split over multiple lines.

The header you show is also broken by the first line being 90 characters
long (RFC 822 restricts header lines to 76 characters).

RFC 2047 says:

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.)


[1] Interestingly, MS Outlook likes to break lines mid-word when
    they're *not* encoded, leading to spurious spaces appearing when
    read with standards-based software like Gnus.

Re: missing spaces in encoded-word displaying

[Vladimir Volovich]

"TS" == Toby Speight writes:

 TS> Space between adjacent encoded-words is not significant, and
 TS> should be elided.

Thx for clarification! It's great to find gnus RFC-compliant once
again.

	Best regards, -- Vladimir.
-- 
When I was little, I went into a pet shop and they asked how big I'd get.
		-- Rodney Dangerfield