Re: quoted-printable no-go in news?

[Jesper Harder <harder@myrealbox.com>]

Matthias Andree <ma@dt.e-technik.uni-dortmund.de> writes:

> Gnus displays wide hollow boxes instead of the umlauts in Message-ID:
> <etvq8vonajs2p1llpmfpnl8d0rehmsdu5u@4ax.com> (de.rec.fotografie) -- it
> is declared iso-8859-1 and quoted-printable; but Gnus nicely and
> correctly displays "\200" for a b0rken =80. 

It's not related to QP -- the same would happen if it wasn't QP-encoded.
The real problem is that the article is not in iso-8859-1 as declared,
but in Windows-1252.

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.

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).

* 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.

* If you're using a Latin-1 locale, then this happens to be displayed
  correctly.

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.

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.