From: Vladimir Volovich <vvv@vsu.ru>
Subject: Re: one more bug in latest gnus
Date: Tue, 27 May 2003 18:01:30 +0400 [thread overview]
Message-ID: <eyy90s5w05.fsf@video.uic.vsu.ru> (raw)
In-Reply-To: <bavqsu$46t$1@quimby.gnus.org>
Hi!,
one more bug:
when you press RET on the message button (after previewing the
previous message in this thread) you'll see
Subject: йМХЦЮ йНРЕКЭМХЙНБЮ Х=?KOI8-R?Q?_=D7=E5=E1=EE=F2=E0=E5=E2=E0?=
I.e., gnus did not decode the whole subject - some encoded-words were
left undecoded.
It looks like gnus does not use consistent calls to decode headers:
sometimes it fails to decode multiline headers. It should use some
unified functions which will properly deal with headers, instead of
using special function in several places which appear to have bugs.
Best,
v.
next parent reply other threads:[~2003-05-27 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bavqsu$46t$1@quimby.gnus.org>
2003-05-27 14:01 ` Vladimir Volovich [this message]
2003-05-27 22:02 ` Simon Josefsson
2003-05-27 13:45 Vladimir Volovich
2003-05-27 21:57 ` Simon Josefsson
2003-05-28 22:26 ` Dave Love
2003-05-30 9:44 ` Dave Love
[not found] ` <bb7b07$99b$1@quimby.gnus.org>
2003-05-30 17:45 ` Vladimir Volovich
2003-06-02 2:20 ` Jesper Harder
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=eyy90s5w05.fsf@video.uic.vsu.ru \
--to=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).