-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, January 26 at 01:07 AM, quoth Dimitris Mandalidis: > On Sun, Jan 25, 2009 at 03:28:02PM -0600, Kyle Wheeler wrote: > >> 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. > > Indeed, the iso-8859-7 characters in the subject line were shown as > escaped octal values.
AH! Perfect - so, mutt didn't know how to handle them at all! Largely because they're not encoded correctly. They're like sugar in the gas tank: not what the engine was expecting. Now, what mutt *should* do, I think, is mask those unprintable non-recognizable characters when it hands them to the editor, so that they don't confuse the editor (and to help avoid sending incorrect headers to other people)... you should probably submit a bug report (http://dev.mutt.org) so that this gets fixed. ~Kyle - -- The best way to know God is to love many things. -- Vincent Van Gogh -----BEGIN PGP SIGNATURE----- Comment: Thank you for using encryption! iEYEARECAAYFAkl89cMACgkQBkIOoMqOI17hqwCeOai1iiJaAak41nEYDYpS9CDq iRUAnRB1nXaEkh++M+4JquG1q5BLtDof =ow9r -----END PGP SIGNATURE-----
