Re: mutt/2560: Mutt chokes on invalid charset in UTF environment
The following reply was made to PR mutt/2560; it has been noted by GNATS.
From: Christian Ebert <blacktrash@xxxxxxx>
To: bug-any@xxxxxxxxxxxxx
Cc:
Subject: Re: mutt/2560: Mutt chokes on invalid charset in UTF environment
Date: Tue, 21 Nov 2006 12:55:57 +0000
Hi,
* On Tuesday, November 21, 2006, Rocco Rutte wrote:
> What iconv are you using?
libiconv-1.10
> The message displays just fine here (with and without the -F
> switch)...
Good for you.
> I don't know if it helps resolving the issue, but can you convert via
> command line? What happens if you try to decode the mail like this:
>
> iconv -f iso-8859-i -t utf-8 < ... > ...
iconv: conversion from iso-8859-i unsupported
iconv: try 'iconv -l' to get the list of supported encodings
So, is "iso-8859-i" a valid encoding, or a spammer's phantasy?
I'm not keen on displaying it, I'd just like to delete it from
inside Mutt, without hassle. But in the end it's not that big a
problem for me, but less patient users might be put off because
there is no error message or something similar.
Also for someone with my setup, the assumed-charset patch is a
definite *must*, because the freeze would as well happen on
unclean but otherwise harmless messages (mutt/2425).
c