-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, March 19 at 03:02 PM, quoth Chris G:
> On Wed, Mar 19, 2008 at 02:57:19PM +0000, Chris G wrote:
>> If you look in the header of this message I *fear* you will see that
>> the charset is set to iso-8859-1. It's not my muttrc that's doing
>> that, so what is setting it to that, incorrectly! I suspect that it's
>> probably this that is the fundamental problem (apart from getting my
>> editor to enter the correct utf-8 encoding).
>>
> Not even that, something has set the charset to us-ascii.
>
> Does something, somewhere *guess* the character set from the stream of
> characters it sees?
Yes; mutt does.
It uses $send_charset to figure that out. Here's the man-page entry on
that setting:
send_charset
Type: string
Default: "us-ascii:iso-8859-1:utf-8"
A colon-delimited list of character sets for outgoing
messages. Mutt will use the first character set into which
text can be converted exactly. If your "$charset" is not
iso-8859-1 and recipients may not understand UTF-8, it is
advisable to include in the list an appropriate widely used
standard character set (such as iso-8859-2, koi8-r or
iso-2022-jp) either instead of or after "iso-8859-1".
In case the text cannot be converted into one of these
exactly, mutt uses "$charset" as a fallback.
~Kyle
- --
The effect of liberty to individuals is, that they may do what they
please; we ought to see what it will please them to do, before we risk
congratulations.
-- Edmund Burke
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkfhMQoACgkQBkIOoMqOI14gmACeKaa7F/5WHbQKMyDFDKoxe05Y
QOoAoK/ORiJthL1axpxbiKXtUmeDs6aT
=kr6n
-----END PGP SIGNATURE-----
