From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: documentation of gnus-article-treat-dumbquotes outdated?
Date: Wed, 13 Aug 2003 18:46:57 +0200 [thread overview]
Message-ID: <v9isp1h5dq.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3fzk5fuic.fsf@seneca.benny.turtle-trading.net>
On Wed, Aug 13 2003, Benjamin Riefenstahl wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>> - I guess most (or all?) chars from `gnus-article-dumbquotes-map' are
>> `windows-1252' characters, not present in Latin-1. `windows-1252'
>> is a registered[1] charset. So the real problem is that some
>> Windows clients send `windows-1252' labeled as `iso-8859-1'.
[ http://mail.gnu.org/archive/html/emacs-devel/2003-04/msg00177.html ]
> I than wrote:
[...]
>> (setq gnus-newsgroup-ignored-charsets
>> '(unknown-8bit x-unknown us-ascii iso-8859-1))
>> (setq gnus-default-charset 'cp1252)
>>
>> I.e. I disable using the MIME parameters for us-ascii and iso-8859-1
>> and set the default to cp1252 instead. This has worked fine so far
>> for me. Real us-ascii or iso-8859-1 messages don't have a problem
>> with this, as cp1252 is a proper superset of iso-8859-1.
I understand that this works (as long as "un-/mis-labeled" doesn't
include other charsets). Could you elaborate what you suggest WRT the
documentation of gnus-article-treat-dumbquotes?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2003-08-13 16:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87znigdhpa.fsf@jidanni.org>
[not found] ` <v98yq07afl.fsf@marauder.physik.uni-ulm.de>
2003-08-12 20:09 ` Reiner Steib
2003-08-12 21:12 ` Matthias Andree
2003-08-13 15:27 ` Benjamin Riefenstahl
2003-08-13 16:46 ` Reiner Steib [this message]
2003-08-13 18:12 ` Benjamin Riefenstahl
2003-08-18 2:00 ` James H. Cloos Jr.
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=v9isp1h5dq.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--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).