<<< Date Index >>>     <<< Thread Index >>>

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: Sun, 25 Mar 2007 14:54:47 +0200

 * Christian Ebert on Tuesday, March 13, 2007 at 11:55:05 +0100:
 > * Vincent Lefevre on Tuesday, November 21, 2006 at 20:45:03 +0100:
 >>  On 2006-11-21 15:05:02 +0100, Christian Ebert wrote:
 >>>  libiconv-1.10
 >> 
 >>  You should try 1.11 (this is what I'm using, from MacPorts).
 > 
 > Upgraded in the meantime to 1.11:
 > 
 > $ mutt -v | grep libiconv
 > libiconv: 1.11
 > 
 >>>  So, is "iso-8859-i" a valid encoding, or a spammer's phantasy?
 >> 
 >>  iso-8859-8 exists, but iso-8859-8-i is a spammer's phantasy.
 > 
 > This was solved with a charset hook.
 > 
 > But the same freeze happens with attached message.
 
 After experimenting with
 
 set charset=utf-8//TRANSLIT
 
 which of course puts question-marks in the from-header, I now do
 
 charset-hook ^utf-8$ iso-8859-2
 
 which seems to do the trick. I hope it doesn't break other
 things.
 
 Anyway, I seem to be the only one to have this problem ;)
 
 c