<<< Date Index >>>     <<< Thread Index >>>

Re: Reading UTF-8 Mail (was Re: e-mail encoding/formatting)



On Thu, May 04, 2006 at 10:01:31PM +0200, Alain Bench wrote:
>  On Monday, May 1, 2006 at 14:06:13 -0400, Richard Cobbe wrote:
> 
> > unable to get mutt to display extended characters correctly
> 
>     Things like "?~@~Y" for Kyle?s nice curly apostrophs or such for
> semi-graphics are indeed generated by Ncurses. But perhaps only due to a
> broken locale. Here with Ncurses 5.5.20060416, LC_ALL=C and a forced
> $charset=utf-8 permits reproducing your symptoms.

Responding to both your posts:

I don't have any locale-related environment variables set; I get the
following:

[vetinari:~]$ locale
LANG=
LC_COLLATE="C"
LC_CTYPE="C"
LC_MESSAGES="C"
LC_MONETARY="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_ALL="C"

I also don't set the charset variable within .muttrc.  Querying the
charset variable (with :set ?charset) gives me "us-ascii" -- I'm not
sure quite where that's coming from, although it's what I want in most
cases.

I'm running with ncurses 5.4-20041023 *and* ncursesw 5.4-20041023.  It
seems as though mutt is linked against both:

    [vetinari:~]$ otool -L /sw/bin/mutt
    /sw/bin/mutt:
            /sw/lib/ncurses/libncurses.5.dylib (compatibility version 5.0.0, 
current version 5.0.0)
            /sw/lib/libncursesw.5.dylib (compatibility version 5.0.0, current 
version 5.0.0)
    <etc>

I've got a lot to do at school right now, but when things calm down in a
bit, I may try to play with some of these issues.  I'm using fink's
mutt; they've got a newer one (1.5.11) in the unstable tree that might
work better.  If that fails, I may also try to build from source to get
rid of that configure switch you mentioned.

Thanks,

Richard