Gnus development mailing list
 help / color / mirror / Atom feed
* gnus-article-decode-charset
@ 2000-04-23 12:43 Roman Belenov
  2000-04-23 13:45 ` gnus-article-decode-charset Shenghuo ZHU
  0 siblings, 1 reply; 11+ messages in thread
From: Roman Belenov @ 2000-04-23 12:43 UTC (permalink / raw)


What is gnus-article-decode-charset intended for ? It seems that Gnus
automatically decodes text according to Content-type header; calling
this function seems to decode already decoded text making it
unreadable.

Is it possible to make this function always use original mail text as
the source for decoding, disregarding any transformations done before?
Sometimes I receive letters with wrong charset in Content-type;
Gnus misdecodes message text and trying to decode it with other coding
systems doesn't help.

-- 
 							With regards, Roman.




^ permalink raw reply	[flat|nested] 11+ messages in thread
* gnus-article-decode-charset
@ 2006-10-25 14:17 Miles Bader
  2006-10-25 14:58 ` gnus-article-decode-charset Reiner Steib
  0 siblings, 1 reply; 11+ messages in thread
From: Miles Bader @ 2006-10-25 14:17 UTC (permalink / 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.




^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2006-10-25 22:01 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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

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).