From: Karl Eichwalder <ke@gnu.franken.de>
Cc: ding@gnus.org
Subject: Re: charset="Windows-1252"
Date: 04 Nov 1999 07:31:59 +0100 [thread overview]
Message-ID: <shbt9ag42o.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: Janne Rinta-Manty's message of "Wed, 03 Nov 1999 08:54:28 GMT"
Thanks for all your hints and your encouragements!
Janne Rinta-Manty <jrm@iki.fi> writes:
| I just added windows-1252 to the list
| gnus-newsgroup-ignored-charsets, and the messages are now displayed
| OK. This probably requires that iso-8859-1 is the default charset.
Indeed, that's a very good work around -- strange enough, I only figured
out howto set the variable via customize. And then, gnus stopped
reading the active file. This setting seems to help for now:
(setq gnus-read-active-file nil)
I tried:
(eval-after-load "gnus-sum"
(setq gnus-newsgroup-ignored-charsets
(cons 'windows-1252 gnus-newsgroup-ignored-charsets)))
This leads to an error message; IIRC,
"... gnus-newsgroup-ignored-charsets ... not defined".
--
work : ke@suse.de |
: http://www.suse.de/~ke/ | ------ ,__o
personal: ke@gnu.franken.de | ------ _-\_<,
: http://www.franken.de/users/gnu/ke/ | ------ (*)/'(*)
prev parent reply other threads:[~1999-11-04 6:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-01 22:02 charset="Windows-1252" Karl Eichwalder
1999-11-02 9:21 ` charset="Windows-1252" Steinar Bang
1999-11-02 9:53 ` charset="Windows-1252" Hrvoje Niksic
1999-11-02 10:02 ` charset="Windows-1252" Steinar Bang
1999-11-02 11:14 ` charset="Windows-1252" Hrvoje Niksic
1999-11-02 12:28 ` charset="Windows-1252" Steinar Bang
1999-11-02 13:17 ` charset="Windows-1252" Florian Weimer
1999-11-02 13:02 ` charset="Windows-1252" Johan Kullstam
1999-11-02 14:53 ` charset="Windows-1252" Toby Speight
1999-11-04 16:42 ` charset="Windows-1252" Robert Bihlmeyer
1999-11-03 8:54 ` charset="Windows-1252" Janne Rinta-Manty
1999-11-04 6:31 ` Karl Eichwalder [this message]
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=shbt9ag42o.fsf@tux.gnu.franken.de \
--to=ke@gnu.franken.de \
--cc=ding@gnus.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).