Nuno Silva
2017-10-12 17:02:20 UTC
Hello,
Recently, I have tried to use mutt on a non-utf8 terminal. Everything
works as expected in an utf8 environment, but when I compose new e-mails
in a latin1/ISO-8859-1 terminal, mutt will expect the file to be in the
same encoding as the terminal, while my text editor will save the file
in utf8. The result is that non-ASCII characters get misinterpreted,
which can affect the message headers as well (e.g. real names in To: and
Cc:).
When replying to messages, this has not been an issue so far, as mutt
includes the quoted copy of the message I'm replying to and the editor
can use that to guess the encoding.
Is there some way to configure mutt so that it always uses utf8 to read
the new message after I exit the editor? Or a way to enable some
encoding autodetection that can tell utf8 apart from latin1?
Recently, I have tried to use mutt on a non-utf8 terminal. Everything
works as expected in an utf8 environment, but when I compose new e-mails
in a latin1/ISO-8859-1 terminal, mutt will expect the file to be in the
same encoding as the terminal, while my text editor will save the file
in utf8. The result is that non-ASCII characters get misinterpreted,
which can affect the message headers as well (e.g. real names in To: and
Cc:).
When replying to messages, this has not been an issue so far, as mutt
includes the quoted copy of the message I'm replying to and the editor
can use that to guess the encoding.
Is there some way to configure mutt so that it always uses utf8 to read
the new message after I exit the editor? Or a way to enable some
encoding autodetection that can tell utf8 apart from latin1?
--
Thanks in advance,
Nuno Silva
Thanks in advance,
Nuno Silva