From: Miles Bader <miles@gnu.org>
Subject: gnus-article-decode-charset
Date: Wed, 25 Oct 2006 23:17:29 +0900 [thread overview]
Message-ID: <877iyomqdi.fsf@catnip.gol.com> (raw)
Aka `(C-u) W M C' in summary buffer.
I often try to use this command when a message I get is apparently
mis-decoded (due to faulty header info or whatever), but it rarely seems to
work like I expect it to, and often doesn't give useful results at all.
I'm wondering if I'm using it incorrectly, or whether it's broken.
The main problem is: What version of the message does W M C operate on?
What I _expect_ is that it would
(1) fetch the original message,
(2) remove any mime wrapping like base-64, resulting in a unibyte buffer
full of raw message bytes, and then
(3) just call (decode-coding-region ... 'whatever)
Sometimes it appears to be trying to operate on whatever the currently
_displayed_ contents are, which is usually completely wrong. If I try to
work around this by manually fetching the "original" message using `C-u g',
that usually fails to work too, either because the original is base-64
encoded, or even when that's not true, apparently because the way it
displays the raw bytes isn't what W M C is expecting.
Also, since I often need to guess and try several different encodings
before I find the proper one, it's generally more convenient if it starts
from the beginning each time (applying decoding X to the failed results of
decoding Y usually doesn't work very well :-).
Anyway, any comments on how this command does/should work?
Thanks,
-Miles
--
I'd rather be consing.
next reply other threads:[~2006-10-25 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 14:17 Miles Bader [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2000-04-23 12:43 gnus-article-decode-charset Roman Belenov
2000-04-23 13:45 ` gnus-article-decode-charset Shenghuo ZHU
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
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=877iyomqdi.fsf@catnip.gol.com \
--to=miles@gnu.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).