Re: Character set validation (with patch)
Sorry, I'm busy elsewhere, and can take a look here only way too
rarely. Noticed this thread only now, no time to test the patches.
On Tuesday, November 13, 2007 at 13:48:25 +0100, Rocco Rutte wrote:
> there're some bugs open where trouble could have been avoided if mutt
> did validate character sets
If I understand correctly, this would prohibit setting $*charset
variables to names that are unknown to iconv and to Mutt's internal
hardcoded list. But there are cases where one rightly wants to set such
unknown charset name.
One such case was described in bug #1269. The user wanted to send
mails labelled "iso-8859-8-i". This -i name is unknown to iconv and
Mutt, but the "iso-8859-8" variant is known. This user can set:
| set send_charset="...:iso-8859-8-i:..."
| iconv-hook ^iso-8859-8-i$ iso-8859-8
And today everything works as expected. But with charset validation,
the first line would be rejected.
OTOS validation would accept $send_charset=MacRoman, because it is
known to iconv. But it is not a IANA approved charset name for MIME
labels. Mutt should probably still accept it (for some specific usages),
but not seem to suggest it's approved in any way.
Libiconv 1.12 is released.