From: Toby Speight <Toby.Speight@streapadair.freeserve.co.uk>
Subject: Re: missing spaces in encoded-word displaying
Date: 15 Nov 1999 15:42:33 +0000 [thread overview]
Message-ID: <uaeofiwwm.fsf@lanber.cam.citrix.com> (raw)
In-Reply-To: Vladimir Volovich's message of "12 Nov 1999 14:42:39 +0300"
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.
next prev parent reply other threads:[~1999-11-15 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-12 11:42 Vladimir Volovich
1999-11-15 15:42 ` Toby Speight [this message]
1999-11-15 20:31 ` Vladimir Volovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uaeofiwwm.fsf@lanber.cam.citrix.com \
--to=toby.speight@streapadair.freeserve.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).