[Please CC me on replies. I am not subscribed. M-F-T set.]
Hi all,
I recently switched my systems to Unicode, which is lovely. However,
I can't quite get mutt configured correctly. I am using these
settings:
set charset = "utf-8"
set config_charset = "utf-8"
set assumed_charset = "utf-8:iso-8859-15:iso-8859-1:latin1:us-ascii"
set file_charset = "us-ascii:latin1:iso-8859-1:iso-8859-15:utf-8"
set send_charset = "us-ascii:latin1:iso-8859-1:iso-8859-15:utf-8"
which produces exactly the desired results for attachments, but not
for normal mail. If I send the message as an attachment,
$send_charset is properly used and the message will be sent with the
"lowest" possible charset specified in the MIME part header:
us-ascii, unless I use latin1 stuff, unless I use iso-8859-1 stuff,
unless...
However, when I send a message as a plain RFC822 message without
MIME, then the charset will always be set to utf-8, which is
suboptimal.
How can I get the same behaviour as with the attachments.
Please CC me on replies. I am not subscribed. M-F-T set.
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
spamtraps: madduck.bogus@xxxxxxxxxxx
"to me, vi is zen. to use vi is to practice zen. every command is
a koan. profound to the user, unintelligible to the uninitiated.
you discover truth everytime you use it."
-- reddy@xxxxxxxxxxxxxxxxxxx
Attachment:
signature.asc
Description: Digital signature