From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Subject: Re: quoted-printable no-go in news?
Date: Thu, 10 Apr 2003 21:06:11 +0200 [thread overview]
Message-ID: <m3llyiyxy4.fsf@merlin.emma.line.org> (raw)
In-Reply-To: <m3istpb46j.fsf@defun.localdomain> (Jesper Harder's message of "Tue, 08 Apr 2003 13:48:36 +0200")
Jesper Harder <harder@myrealbox.com> writes:
> FWIW, the umlauts are displayed correctly for me. That's because I'm
> using a Latin-1 locale, while you're probably using UTF-8.
My locale is
LANG=de_DE@euro
Which looks pretty much like Latin-9 (iso-8859-15).
> Here's what happens:
>
> * Gnus detects that the message can't possibly be encoded in Latin-1 as
> advertised in the header (because \200 is not a valid character in
> Latin-1).
This would also apply to Latin-9.
> * It then uses Emacs' charset detection functions to determine the
> charset. By default, Emacs doesn't know about windows-1252, so it
> isn't detected correctly, and the text is decoded as something else.
It must have guessed some other charset that doesn't map \200 then. How
do I ask it which character set it thinks it is again?
> The real way to solve it is to teach Emacs about windows-1252. That's
> possible with `code-pages.el' in CVS Emacs. With this package loaded
> and configured, the €'s are displayed correctly and converted to a
> proper charset when you reply.
can I just steal that from CVS and stuff it into my 21.3 emacs? Or
should I go for CVS? (BTW, is CVS emacs fast enough? 21.2/21.3 are _way_
slower than 21.1 was).
> If you're not using code-pages.el, then it's probably better to use the
> declared charset unconditionally, since the most common case of wrong
> charset declaration is presumeably windows-125x vs. iso-8859-x.
>
> I've changed the code to skip the auto detection if a charset was
> declared in the headers and `code-pages' hasn't been loaded.
Thanks.
--
Matthias Andree
next prev parent reply other threads:[~2003-04-10 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 19:43 Matthias Andree
2003-04-07 22:29 ` Randal L. Schwartz
2003-04-08 5:59 ` Graham Murray
2003-04-10 17:44 ` Matthias Andree
2003-04-08 11:48 ` Jesper Harder
2003-04-10 19:06 ` Matthias Andree [this message]
2003-04-10 19:39 ` Matthias Andree
2003-04-10 23:25 ` Reiner Steib
2003-04-10 20:26 ` Jesper Harder
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=m3llyiyxy4.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.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).