<<< Date Index >>>     <<< Thread Index >>>

1.5.7 BUG: character set in traditional PGP



Greetings,

I am receiving mail from a PGP 2.6.x user in traditional PGP inline
format, with GnuPG 1.4, on a system that uses a de_DE.UTF-8 default
locale (SuSE Linux 9.2). Typing <Esc>P makes mutt ask for the
passphrase, but it gets the character set wrong, *all* umlauts received
come out as a EF BF BD sequence (mutt from CVS, checked out an hour or
two ago).

I saved the mail to a file, decoded the quoted-printable decoding and
ran my pgp_decrypt_command manually, it came out as proper ISO-8859-1,
so the incoming mail appears to come out of GnuPG in good shape.

Something inside mutt appears to trash the characters on the inbound
path.

Outbound appears to be fine, the receiver sees proper utf-8 after
decoding.

It would nice to see this fixed before 1.5.8.

The relevant mail headers and start of body are:

MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
Lines: 84

-----BEGIN PGP MESSAGE-----
Version: 2.6.3in

hIwDJ0SgHSa/XKkBBACOPfRjoXObBT/OZZLURjPFvKHfODuCHMEKAeqvEiNks1Wq
sCIFDG2IYVgB85zBB52pIjh3Gcyafh7kSS1kcFeyEN19DukFtcz+bAw8QpNx1Hik
...

-- 
Matthias Andree