Re: [Nmh-workers] Second release candidate for nmh 1.6 now available

[David Levine]

> As for alias conversion ... well, currently it only supports a small
> subset of the supported aliases for character sets.  In the case of
> US-ASCII, I'm not actually sure any other name for it is allowed in
> the RFCs.
>
> If you're sending out an email with charset="ANSI_X3.4-1968" ... well,
> I don't think that a call to iconv() is unreasonable here.

Looking at the other side, this is what gets reported (by
nl_langinfo(CODESET), too) for US-ASCII:

    $ LANG=C locale charmap
    ANSI_X3.4-1968

So users with a similar locale would (and will now, see below) pay
the price of iconv() for US-ASCII content.

> I guess I think it's more reasonable to handle this stuff in iconv()
> rather than maintain our own charset aliases; the worst case is
> stuff gets run through iconv when it isn't necessary, but I do not
> consider that a huge problem.

I agree.  I just removed the norm_charmap() calls from mhshow
and mhfixmsg and replaced with str(n)casecmp().

David