From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: multiple charsets handling in gnus
Date: Sat, 08 Sep 2001 01:17:17 +0200 [thread overview]
Message-ID: <vaf1ylitwua.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87ae06zmtw.fsf@pale.local> (Alexander Kotelnikov's message of "Sat, 08 Sep 2001 01:56:59 +0400")
Alexander Kotelnikov <sacha@softjoys.ru> writes:
>>>>>> On Fri, 07 Sep 2001 23:47:40 +0200
>>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> wrote:
> Kai>
> Kai> Alexander Kotelnikov <sacha@softjoys.ru> writes:
> >> Most of mail I get is in koi8-r and I read it without any
>>> troubles. But when I get a mail with
>>> Content-Type: text/plain; charset=windows-1251
>>> or
>>> Content-Type: text/plain; charset=cp1251
>>> I see undecoded subject, like =?windows-1251?B?4vLu8O7l?= and body.
> Kai>
> Kai> Does the variable mm-charset-synonym-alist help?
>
> How can it help, if recoding from cp1251 to koi8-r does not work even
> when charset is not an alias (Windows-1251) but the original (cp1251)?
Hm. The content-type header has no bearing whatsoever on what Gnus
does with headers.
You could have charset=gb-2312 and the handling of
=?windows-1251?... in the header wouldn't change at all.
Does Gnus display the body correctly?
kai
--
Symbol's function definition is void: signature
next prev parent reply other threads:[~2001-09-07 23:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-07 17:39 Alexander Kotelnikov
2001-09-07 19:19 ` Kai Großjohann
2001-09-07 21:00 ` Alexander Kotelnikov
2001-09-07 21:47 ` Kai Großjohann
2001-09-07 21:56 ` Alexander Kotelnikov
2001-09-07 23:17 ` Kai Großjohann [this message]
2001-09-07 23:30 ` Alexander Kotelnikov
2001-09-08 10:59 ` Kai Großjohann
2001-09-08 11:06 ` Kai Großjohann
2001-09-08 21:04 ` Alexander Kotelnikov
2001-09-10 7:27 Pavel Janík
2001-09-12 19:13 ` Pavel Janík
2001-09-13 0:14 ` 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=vaf1ylitwua.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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).