From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: gnus-article-decode-charset
Date: Wed, 25 Oct 2006 21:20:24 +0200 [thread overview]
Message-ID: <v9ejswxkw7.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87mz7kl2so.fsf@catnip.gol.com>
On Wed, Oct 25 2006, Miles Bader wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>> In the situation you describe, I use `<prefix> g' (<menu-bar>
>> <Article> <Display> <View as different encoding>):
>
> That sounds pretty inconvenient though -- it looks like you need to
> _predefine_ the available character sets, and map them to an integer key
> (which makes them hard to remember).
No, `gnus-summary-show-article-charset-alist' is only an abbreviation
for frequently encountered charset. If a number N is not present in
`gnus-summary-show-article-charset-alist' (or if it's nil), `N g'
prompts for a charset. (But that's what the doc string says. Didn't
you read it or is it unclear?)
E.g. I have ((12 . windows-1252) (0 . iso-8859-15) (8 . utf-8)) which
is easy to remember and sufficient for me. I rarely need other
charsets. (Of course, I mostly read articles with charsets typically
used in (Western) Europe.)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-10-25 19:20 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 ` gnus-article-decode-charset Reiner Steib
2006-10-25 17:32 ` gnus-article-decode-charset Miles Bader
2006-10-25 19:20 ` Reiner Steib [this message]
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=v9ejswxkw7.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).