Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: gnus-article-decode-charset
Date: Wed, 25 Oct 2006 16:58:02 +0200	[thread overview]
Message-ID: <v9hcxszblx.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <877iyomqdi.fsf@catnip.gol.com>

On Wed, Oct 25 2006, Miles Bader wrote:

[ gnus-article-decode-charset ]
> 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.

I never use `gnus-article-decode-charset' so I don't know there's any
useful interactive use at all.  Anyone?

In the situation you describe, I use `<prefix> g' (<menu-bar>
<Article> <Display> <View as different encoding>):

,----[ (info "(gnus)Paging the Article") ]
| `A g'
| `g'
|      (Re)fetch the current article (`gnus-summary-show-article').  If
|      given a prefix, fetch the current article, but don't run any of the
|      article treatment functions.  This will give you a "raw" article,
|      just the way it came from the server.
| 
|      If given a numerical prefix, you can do semi-manual charset stuff.
|      `C-u 0 g cn-gb-2312 RET' will decode the message as if it were
|      encoded in the `cn-gb-2312' charset.  If you have
| 
|           (setq gnus-summary-show-article-charset-alist
|                 '((1 . cn-gb-2312)
|                   (2 . big5)))
| 
|      then you can say `C-u 1 g' to get the same effect.
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2006-10-25 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 14:17 gnus-article-decode-charset Miles Bader
2006-10-25 14:58 ` Reiner Steib [this message]
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=v9hcxszblx.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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).