Re: Message-hook problem
Hi Henry!
On Wednesday, August 22, 2007 at 6:48:32 +0900, Henry Nelson wrote:
[superscript one]
> In Alain's post it was a wide character, in Breen's, single width.
There is a problem: You're supposed to see question mark(s). You
have an EUC-JP-MS terminal, and its subset EUC-JP locale and $charset.
This U+00B9 character does not exist in EUC-JP (nor EUC-JP-MS). When
stepping on such an unconvertable character, Mutt replaces it by as many
question marks as there are bytes encoding the character. This should
look so in the pager, and in the $editor when composing a reply. This is
what I see myself in Japanese PuTTY.
What you see looks like raw UTF-8 (and Latin-1) displayed as-is on
an EUC-JP-MS terminal, unconverted. This should not happen, and may be
due to:
- some evil procmail rule munging Content-Type
- some charset-hook matching UTF-8 and aliasing it either to EUC-JP, or
to an unknown charset (this activates pass-thru mode)
- some iconv-hook (with libiconv you don't need any iconv-hooks)
- an unknown $charset
- Mutt fails to make use of libiconv
The 2 last are "for the record". They are *not* your problem,
because there are sure proofs that your libiconv setup works enough to
properly convert your EUC $charset to 2022.
Bye! Alain.
--
Give your computer's unused idle processor cycles to a scientific goal:
The Folding@home project at <URL:http://folding.stanford.edu/>.