From: "Владимир Волович" <vvv@vvv.vsu.ru>
Subject: Re: bug(s) in moving messages.
Date: 14 Sep 1998 22:39:04 +0400 [thread overview]
Message-ID: <m37lz6mtdj.fsf@vvv.vsu.ru> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "14 Sep 1998 08:26:00 +0200"
"LMI" == Lars Magne Ingebrigtsen writes:
LMI> " шптьэьЮ
LMI> чшчрьГ" <vvv@vvv.vsu.ru> writes:
>> But for the nnmbox backend, russian letters in the " *Original
>> Article*" buffer look already decoded, i.e. like perfect russian
>> letters! But in the article buffer they instead look like a mess
>> with \214<8-bit_char>. So yes, it seems that the error is that the
>> article gets decoded twice: the first time in the " *Original
>> Article*" buffer, and the second time in the Article buffer. :-(
LMI> I think I've located and fixed this bug. Could you check after
LMI> Pterodactyl Gnus v0.31 has been released to see whether things
LMI> start working?
Unfortunately, no. Things seem to work like previously (including
buffers " *Original Article*"). Some more details follow.
1) Some messages in russian display in nnmbox groups well. For
example, the message with
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0010_01BDDFDF.5FBF1020"
and the text part was
Content-Type: text/plain;
charset="koi8-r"
Content-Transfer-Encoding: quoted-printable
This message displayed perfectly well. (and i suppose that all qp
messages will be ok). problems are with 8-bit messages.
2) subjects and "from" addresses of the messages which are in
encoded-word format, are displayed in a summary buffer and in an
article buffer; the _body_ is still displayed broken.
3) if the message is text/plain charset=koi8-r, and c-t-e=8-bit, then
these messages are looking well in an " *Original Article*" buffer
(i.e., russian letters are looking Ok).
4) if the message is text/plain charset=iso-8859-5, and c-t-e=8-bit,
then russian letters in an " *Original Article*" buffer look like
russian letters, but encoded brokenly (as if they were iso-8859-5
text displayed on a koi-r terminal).
my setup:
(set-default-font "fontset-standard")
(set-language-environment "Cyrillic-KOI8")
(setq rfc2047-default-charset 'koi8-r)
;(setq mm-default-coding-system 'koi8) ; this problem is independent of this setting
(setq gnus-secondary-select-methods '((nnmbox "")))
Best regards, -- Vladimir.
prev parent reply other threads:[~1998-09-14 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-11 22:42 Vladimir Volovich
1998-09-12 7:15 ` Lars Magne Ingebrigtsen
1998-09-12 9:51 ` Vladimir Volovich
1998-09-12 12:04 ` Lars Magne Ingebrigtsen
1998-09-12 13:29 ` Vladimir Volovich
1998-09-13 5:32 ` Lars Magne Ingebrigtsen
1998-09-13 10:39 ` Владимир Волович
1998-09-14 6:26 ` Lars Magne Ingebrigtsen
1998-09-14 18:39 ` Владимир Волович [this message]
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=m37lz6mtdj.fsf@vvv.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).