From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-pretest-bug@gnu.org, Ding List <ding@gnus.org>
Subject: Re: gnus: incorrect conversion of Subject and From field from utf-8 to koi8-r
Date: Thu, 13 Oct 2005 20:26:54 +0200 [thread overview]
Message-ID: <v9ek6pw9w1.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <E1EQ6NU-000GJF-2s@bsam.ru> (Boris B. Samorodov's message of "Thu, 13 Oct 2005 20:56:24 +0400")
On Thu, Oct 13 2005, Boris B. Samorodov wrote:
[ On emacs-pretest. Cc-ing Ding ]
> Symptoms:
>
> I do have a letter with the next Subject:
> -----
> Subject: =?UTF-8?B?W2lwdC5ydSAjMTYzXSDQkNCy0YLQvtCe0YLQstC10YI6INCc0KHQmjog0KHQ?= =?UTF-8?B?nyDRgtC10YHRgg==?=
> -----
>
> In command-line mode I can do...
>
> $ echo "W2lwdC5ydSAjMTYzXSDQkNCy0YLQvtCe0YLQstC10YI6INCc0KHQmjog0KHQnyDRgtC10YHRgg==" | base64 -d | iconv -f utf-8
>
> ...and receive the answer:
>
> [ipt.ru #163] АвтоОтвет: МСК: СП тест
>
> But gnus (from cvs as emacs) shows the next line...
>
> Subject: [ipt.ru #163] АвтоОтвет: МСК: СП тест
>
> ...which is wrong.
I don't see any difference. Maybe I'm misunderstanding what you mean.
> The bug appeared to be at illegal concatenation of
> =?UTF-8?<foo> =?UTF-8?<bar> parts of the Subject.
Whitespace between adjacent encoded words have to be ignored according
to RFC 2047:
,----[ rfc2047.txt ]
| (=?ISO-8859-1?Q?a?= =?ISO-8859-1?Q?b?=) (ab)
|
| White space between adjacent 'encoded-word's is not
| displayed.
|
| (=?ISO-8859-1?Q?a?= =?ISO-8859-1?Q?b?=) (ab)
|
| Even multiple SPACEs between 'encoded-word's are ignored
| for the purpose of display.
|
| (=?ISO-8859-1?Q?a?= (ab)
| =?ISO-8859-1?Q?b?=)
|
| Any amount of linear-space-white between 'encoded-word's,
| even if it includes a CRLF followed by one or more SPACEs,
| is ignored for the purposes of display.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2005-10-13 18:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EQ6NU-000GJF-2s@bsam.ru>
2005-10-13 18:26 ` Reiner Steib [this message]
[not found] <E1EQHq4-0002rQ-EC@fencepost.gnu.org>
[not found] ` <E1EQPSa-0006iC-00@etlken>
2005-10-14 16:51 ` Katsumi Yamaoka
2005-10-15 0:46 ` Kenichi Handa
2005-10-15 8:28 ` Katsumi Yamaoka
2005-10-15 8:50 ` Kenichi Handa
2005-10-15 10:06 ` Katsumi Yamaoka
2005-10-16 0:25 ` Kenichi Handa
2005-10-18 18:20 ` Boris Samorodov
2005-10-19 4:12 ` Katsumi Yamaoka
2005-10-19 20:16 ` Richard M. Stallman
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=v9ek6pw9w1.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-pretest-bug@gnu.org \
/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).