From: Vladimir Volovich <vvv@vsu.ru>
Subject: Re: bug in v5.10.2: gnus-group-charset-alist is ignored for some
Date: Sun, 04 May 2003 16:49:31 +0400 [thread overview]
Message-ID: <m34r4ayizo.fsf@vvv.vsu.ru> (raw)
In-Reply-To: <87he8c9dzi.fsf@unix.home>
"VK" == Vasily Korytov writes:
VK> On Sat, 03 May 2003 19:27:12 +0400, Vladimir Volovich wrote:
>> (eval-after-load "gnus-sum" '(setq gnus-group-charset-alist
>> (append (delete '(".*" iso-8859-1) gnus-group-charset-alist)
>> '((".*" koi8-r)))))
VK> FYI, there's no ".*" value in gnus-group-charset-alist as of Oort
VK> (IMHO, you should'n touch it at all in your case). There is
VK> gnus-default-charset, and it's much more easier to tweak. =))
>> i think that gnus somehow tries to detect the charset of the
>> message body
VK> Gnus, not Emacs? Are you sure?
VK> (Anyway, I'm unable to reproduce this problem on XEmacs/non-MULE
VK> -- you can guess, why. =)
>> (and the body contains some character unencodable in koi8-r which
>> makes it think that this is iso-8859-1)
VK> The message is correct KOI-8, BTW.
there was indeed a bug in gnus - ant it was fixed by Jesper Harder:
2003-05-03 Jesper Harder <harder@ifa.au.dk>
* gnus.el: Don't test for `mm-guess-mime-charset'.
* mm-util.el (mm-guess-mime-charset): Remove. Not used any more.
* gnus.el (gnus-default-charset): Set default value to
`undecided'.
* gnus-art.el (article-decode-charset): Don't supply 4th arg to
mm-decode-body.
* mm-bodies.el (mm-decode-coding-region-safely): Remove.
(mm-decode-body): Don't use mm-decode-coding-region-safely.
Best,
v.
next prev parent reply other threads:[~2003-05-04 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 15:27 bug in v5.10.2: gnus-group-charset-alist is ignored for some messages Vladimir Volovich
2003-05-03 16:44 ` bug in v5.10.2: gnus-group-charset-alist is ignored for some Vasily Korytov
2003-05-04 12:49 ` Vladimir Volovich [this message]
2003-05-04 12:54 ` Vladimir Volovich
[not found] <b90q8u$7o6$1@quimby.gnus.org>
2003-05-13 17:20 ` Lars Magne Ingebrigtsen
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=m34r4ayizo.fsf@vvv.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).