Tim Freedom wrote: > [snip snip] > > Once I invoke mutt and view my sample mbox with utf-8 characters in it > (which a friend is able to see without a problem on FreeBSD) I see some > correct glyphs and lots of octals, > > \207 > > \206\203 > > so in all, there are a few correct glyphs but the majority of them are > octals. > > Why is this happening ? and what can I do to correct it (or debug it) ?
I was able to resolve my own problem (thanks to the few people that replied and helped). It related to setting a correct locale value. Doing either of the following did the trick, % unsetenv LC_ALL % setenv LC_CTYPE en_US.UTF-8 -or- % setenv LC_ALL en_US.UTF-8 My problem was that I wasn't touching LC_ALL (which I'm guessing overrides individual settings - no mention of that in the 'man' page). Out of curiosity, why doesn't mutt enable utf-8 natively and by default ? Are there any adverse affects if that were to happen ? In the few cases where the terminal doesn't support UTF-8 (legacy systems), couldn't 'configure' probe/test for those and do the appropriate thing ? Or give the user a configure option to simple always enable it -- something akin to '--enable-utf8' ? Regards, .tf. __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com
