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

Bad charset conversion with gpg-signed mime-forward.



Hi,

I've seen some talks about gpg handling in mutt recently so I thought
it might be appropriate to report a bug I encountered with
mime-forwarded message when I gpg-sign the forward.

Full report is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=295528

Summary: the charset declared in the header of the forwarded email are
changed from an original value of iso-8859-1 to utf-8 without actually
converting the message body. I don't know why this charset conversion
is necessary, but it does not seem to occur properly anyway.

In the original bugreport you can see an "latin small letter e with
grave" that gets converted from its 8bit iso-8859-1 representation to
its quoted-printable encoding (but still iso-8859-1 where the new
headers say utf-8).

I could reproduce the bug with latest CVS, but now my &eacute; letter
is encoded in quoted-printable by the folowing sequence: "=EF=BF=BD"
instead of "=E9" previously.

Attachment: signature.asc
Description: Digital signature