Hi Adeodato!
On Saturday, August 20, 2005 at 2:59:34 PM +0200, Adeodato Simó wrote:
> * Sven Luther [Sat, 20 Aug 2005 14:12:21 +0200]:
>> even if my encoding settings where fubar, mutt should be copying the
>> line verbatim
An invalid byte would have perturbated later operations.
> it's not mutt who truncates, but your terminal.
More exactly truncation seems in enter.c:my_mbstowcs(), relying on
platform's mbrtowc(), itself relying on the current LC_CTYPE locale.
On a correctly configured Mutt and system, this works OK. And an
incoming invalid byte is already masked upstream when it reaches
my_mbstowcs(). Just check with:
| From: Joe =?utf-8?q?Trunc=E4te?= <[EMAIL PROTECTED]>
On reply this displays: Joe Trunc?te. The invalid is masked, either
by a question mark, or by an UTF-8 replacement char U+FFFD.
On a misconfigured system, I'm not sure something sensible in all
cases can be done. What if the locale was wrong but $charset right? What
if both are wrong? What if the name doesn't go thru the prompts because
of $fast_reply? And what happens when an invalid come in? Is it worth
the hassle?
Bye! Alain.
--
How to Report Bugs Effectively
<URL:http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
