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

Re: mutt reply enconding problem

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday, January 25 at 01:20 PM, quoth Dimitris Mandalidis:
> However, mutt doesn't do the same with the message headers like 
> subject and probably from and to, when $edit_headers=yes, giving vim 
> the original subject line with iso-8859-7 encoding and forcing it to 
> fenc=iso-8859-7, after editing the reply it tries to iconv $charset 
> -t <one of $send_charset> but the file encoding is != $charset, so 
> the unreadable output.

I don't know whether your assumptions are correct, but I do know a 
little something about message headers: they're *REQUIRED* to be in 
US-ASCII. See RFC 2822, section 2.2, which says:

     Header fields are lines composed of a field name, followed by a
     colon (":"), followed by a field body, and terminated by CRLF. A
     field name MUST be composed of printable US-ASCII characters
     (i.e., characters that have values between 33 and 126, inclusive),
     except colon.

However, the MIME standard (RFC 2047) makes it possible to encode 
non-ASCII characters specifically for use in email headers, using the 
=?charset?e?string?= format.

Now, one of two things must be happening here: either you're receiving 
correctly encoded messages, mutt is decoding them, and then (for 
whatever reason, maybe a bug) sending the decoded version to your text 
editor OR you're receiving badly-encoded messages that do not use RFC 
2047 encoding, and mutt is doing its best to display them, but has 
difficulty formatting them for your text editor due to their 
brokenness.

You'd have to examine the raw form of the emails you're replying to in 
order to know which one is the case.

~Kyle
- -- 
Believe nothing, no matter where you read it or who has said it, 
unless it agrees with your own reason and your own common sense.
                                                              -- Buddha
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iEYEARECAAYFAkl82V0ACgkQBkIOoMqOI14MlACfQUWrIdPOShi6o3H8ixlwQJm9
OGQAoOXKdaNYB+yvrISXwa7+elSl1pVD
=uqOS
-----END PGP SIGNATURE-----