On Wed, Mar 19, 2008 at 12:13:39PM +0000, Chris G wrote:
> On Wed, Mar 19, 2008 at 11:03:14AM +0000, Michael Kjorling wrote:
> > On 19 Mar 2008 10:40 +0000, by [EMAIL PROTECTED] (Chris G):
> > > in mutt I have "set charset=utf-8".
> > >
> > > What am I doing wrong?
> >
> > There was a discussion about this just recently, starting with
> > message-ID <[EMAIL PROTECTED]>. In short, first off, try
> > to avoid setting $charset and see what that does.
> >
> Removing "set charset" from both ends has no effect at all.
>
> In my case it was all working perfectly when I had iso-8859-1
> settings, it was only when I have tried moving to utf-8 that things
> have gone awry.
>
It seems to me that mutt is actually *encoding* the characters wrong
(or it's using a library that's doing that) as even if I save the
sentmail copy of a message with (for example) pounds signs in it and
look at the saved copy the pounds signs don't display correctly
whereas every other program seems to be able to load and save pound
signs correctly.
I have no charset set in my muttrc now.
Mutt is putting the following in mail headers:-
Content-Type: text/plain; charset=utf-8
'locale' reports:-
LANG=en_GB.utf8
LC_CTYPE=en_GB.utf8
LC_NUMERIC="en_GB.utf8"
LC_TIME="en_GB.utf8"
LC_COLLATE=C
LC_MONETARY="en_GB.utf8"
LC_MESSAGES="en_GB.utf8"
LC_PAPER="en_GB.utf8"
LC_NAME="en_GB.utf8"
LC_ADDRESS="en_GB.utf8"
LC_TELEPHONE="en_GB.utf8"
LC_MEASUREMENT="en_GB.utf8"
LC_IDENTIFICATION="en_GB.utf8"
LC_ALL=
--
Chris Green
