Gnus development mailing list
 help / color / mirror / Atom feed
From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: 5.8.2 bug: test тест téßt test
Date: 21 Apr 2000 13:26:05 -0400	[thread overview]
Message-ID: <5b7ldr9xhu.fsf@vermouth.cs.rochester.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "21 Apr 2000 19:25:40 +0200"

>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

LMI> Vladimir Volovich <vvv@vvv.vsu.ru> writes:
>> when sending a message with this subject, gnus encodes non-ascii text
>> as encoded-word, and as a result, the space between a cyrillic word
>> (koi8-r) and a latin-1 word is lost. This rule was already discussed
>> in this list (in a different thread):
>> 
>> 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.)
>> 
>> The subject contained a cyrillic word and a latin-1 word separated by
>> a real space. Gnus encoded both words as encoded-word, but not encoded
>> a space between them. As a result, this space is ignored when
>> displaying the subject.

LMI> Oh dear.

LMI> So should the rfc2047 algorithm be:

LMI> 1) find all words (or phrases) to encode
LMI> 2) encode all the words or phrases
LMI> 3) if there are now two encoded words after each other, we encode a
LMI>    space in between them?

I vaguely recall that I had fixed this bug. Please check the latest
version.

-- 
Shenghuo



  reply	other threads:[~2000-04-21 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-17  9:31 5.8.2 bug: test тестtéßt test Vladimir Volovich
2000-04-21 17:25 ` 5.8.2 bug: test тест téßt test Lars Magne Ingebrigtsen
2000-04-21 17:26   ` Shenghuo ZHU [this message]
2000-04-21 17:42     ` Lars Magne Ingebrigtsen

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=5b7ldr9xhu.fsf@vermouth.cs.rochester.edu \
    --to=zsh@cs.rochester.edu \
    /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).