From: Vladimir Volovich <vvv@vvv.vsu.ru>
Subject: 5.8.2 bug#1: test тестtéßt test
Date: 15 Dec 1999 19:10:25 +0300 [thread overview]
Message-ID: <ey902wyyku.fsf@video.uic.vsu.ru> (raw)
Hi,
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.
Best regards, Vladimir.
next reply other threads:[~1999-12-15 16:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-15 16:10 Vladimir Volovich [this message]
1999-12-15 16:20 ` 5.8.2 bug#2: " Vladimir Volovich
1999-12-17 10:01 ` 5.8.2 bug#2: test ~~~~téßt test Shenghuo ZHU
1999-12-15 16:48 ` 5.8.2 bug#1: test тестtéßt test Vladimir Volovich
1999-12-17 15:43 ` 5.8.2 bug#1: test тестtéßt test тест téßt Shenghuo ZHU
1999-12-17 17:07 ` 5.8.2 bug#1: test ^[,LbUab^[(Btéßt test тестtéßt Vladimir Volovich
1999-12-17 18:24 ` 5.8.2 bug#1: test тестtéßt test тест téßt Shenghuo ZHU
1999-12-17 18:26 ` Shenghuo ZHU
1999-12-17 19:28 ` 5.8.2 bug#1 blah blah blah Florian Weimer
1999-12-18 13:32 ` Hrvoje Niksic
1999-12-17 21:58 ` 5.8.2 bug#1: test ^[,LbUab^[(Btéßt test тестtéßt Vladimir Volovich
1999-12-17 22:25 ` 5.8.2 bug#1: test Shenghuo ZHU
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=ey902wyyku.fsf@video.uic.vsu.ru \
--to=vvv@vvv.vsu.ru \
/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).