Hi,
* Antonio Radici wrote:
> 1) Klaus is reporting that mutt doesn't honor the body charset while sending
> a mail
> signed inline with pgp/gnupg, infact there is code in pgp.c to check if the
> send_charset is different from us-ascii, in that case it will be set to utf-8.
> This code is still there (checked the latest testing version 1.5.18-4).
For good reason I'd say, compare section 6.2 of RFC4880 and there the
Charset: armor header part. It reads:
- "Charset", a description of the character set that the plaintext is
in. Please note that OpenPGP defines text to be in UTF-8. An
implementation will get best results by translating into and out
of UTF-8. [...]
For encyption, mutt supports reading it in latest tip. Following the
above suggestion, the sending side is not touched. For some more
arguments, see http://dev.mutt.org/trac/ticket/3039 which is fixed by a
a modified version of Tamo's patch.
In PGP/MIME-times there won't be a better solution I'm afraid.
Rocco
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
