On 2008-03-21 16:46:51 +0100, Vincent Lefevre wrote: >> I frankly wouldn't bother adding code to mutt to work properly >> in another inconsistent specification edge case, where the user >> actually runs several locales in parallel.
> The problem occurs even when using only *one* locale. If the user > is assumed to run under UTF-8, how about removing the $charset > variable? The user isn't assumed to run under UTF-8. The user is assumed to run in a consistent environment in which the terminal, the file system, and local files share a single character set which is inferred from the user's locale settings. Mutt works perfectly well in a fully iso-8859-1 environment, in a fully iso-8859-15 environment, and in a fully utf-8 environment -- to just enumerate those that I've used over the last few years. Where mutt "fails" is in an environment that is kind of utf-8, except for the terminal, and many of the local fils. I'd say "tough" for that one. -- Thomas Roessler <[EMAIL PROTECTED]>
