Re: [Nmh-workers] mhshow: unable to convert character set to utf-8, continuing...

[Ken Hornstein]

>This happens for many messages -- several every day. An example, from today,
>is your "mhstore RFE: add facility to manipulate the original filename" of
>Tue, 03 Jun 2014 09:00:32 -0400.

It seems like I misread that error message ... it implies that's what
it's trying to convert it TO, but really, UTF-8 is the source character set.
That particular message was UTF-8 because I was including the accented
character in Jon's name.

>For almost all of those messages, including the example, mhstore produces a
>file which is almost all ASCII; less, or even cat, does a quite credible job
>of rendering it. I would ask why mhshow can't do that. Except then, you might
>spend two hours telling me.

Sigh.  So, I told you the wrong thing earlier.  If a character conversion
fails, you'll get that error.  I personally think that's not the best
idea, but others disagree.  I'm curious: what do the following commands
return?

% mhparam iconv
% locale LC_CTYPE

--Ken