From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: gnus-article-decode-charset
Date: 23 Apr 2000 09:45:42 -0400 [thread overview]
Message-ID: <2nvh19q6bd.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Roman Belenov's message of "23 Apr 2000 16:43:13 +0400"
>>>>> "Roman" == Roman Belenov <roman@nstl.nnov.ru> writes:
Roman> What is gnus-article-decode-charset intended for ? It seems
Roman> that Gnus automatically decodes text according to Content-type
Roman> header; calling this function seems to decode already decoded
Roman> text making it unreadable.
Roman> Is it possible to make this function always use original mail
Roman> text as the source for decoding, disregarding any
Roman> transformations done before? Sometimes I receive letters with
Roman> wrong charset in Content-type; Gnus misdecodes message text and
Roman> trying to decode it with other coding systems doesn't help.
If Gnus calls gnus-article-decode-charset twice on the same text, the
text could be double decoded. This should not happen unless you type
`W M c' or click the menu item.
If Gnus mis-decodes the message, you can use `0 g CHARSET' in the
summary buffer to re-decode (not double decode).
--
Shenghuo
next prev parent reply other threads:[~2000-04-23 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-23 12:43 gnus-article-decode-charset Roman Belenov
2000-04-23 13:45 ` Shenghuo ZHU [this message]
2000-04-23 14:21 ` gnus-article-decode-charset Roman Belenov
2000-04-23 21:06 ` gnus-article-decode-charset Kai Großjohann
2000-04-23 21:29 ` gnus-article-decode-charset Shenghuo ZHU
2000-04-23 21:41 ` gnus-article-decode-charset Kai Großjohann
2006-10-25 14:17 gnus-article-decode-charset Miles Bader
2006-10-25 14:58 ` gnus-article-decode-charset Reiner Steib
2006-10-25 17:32 ` gnus-article-decode-charset Miles Bader
2006-10-25 19:20 ` gnus-article-decode-charset Reiner Steib
2006-10-25 22:01 ` gnus-article-decode-charset Miles Bader
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=2nvh19q6bd.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).