On Tue, Feb 17, 2009 at 11:37:36PM +0100, Christian Ebert wrote:
> I am also sure that libiconv 1.11 has other bugs, only not those
> that triggered the problem.
>
> It's more a question of which bugs in the software Mutt depends
> on are deemed worthy to work around.
No, I think it's more a ques
* Derek Martin on Tuesday, February 17, 2009 at 15:22:02 -0600
> On Tue, Feb 17, 2009 at 08:47:13AM +0100, Christian Ebert wrote:
>> iconv -l would have saved me for the iso-8859-i case of that bug,
>> because it worked with the old version (1.10) of iconv I had then
>> on my machine.
>
> The que
On Tue, Feb 17, 2009 at 08:47:13AM +0100, Christian Ebert wrote:
> iconv -l would have saved me for the iso-8859-i case of that bug,
> because it worked with the old version (1.10) of iconv I had then
> on my machine.
The question is, is it generally available in iconv implementations
(i.e. those
Hi Rocco and Derek,
* Derek Martin on Monday, February 16, 2009 at 23:11:42 -0600
> On Tue, Feb 10, 2009 at 01:17:36PM +0100, Rocco Rutte wrote:
>> * Derek Martin wrote:
>>> I have a thought about the approach to fix #2560:
>>>
>>> http://dev.mutt.org/trac/ticket/2560
> [...]
>> Yes: there's no p
Hi Rocco,
On Tue, Feb 10, 2009 at 01:17:36PM +0100, Rocco Rutte wrote:
> * Derek Martin wrote:
>> I have a thought about the approach to fix #2560:
>>
>> http://dev.mutt.org/trac/ticket/2560
[...]
> Yes: there's no portable iconv way to obtain the list of supported
> charsets, at least as far as
Hi,
* Derek Martin wrote:
I have a thought about the approach to fix #2560:
http://dev.mutt.org/trac/ticket/2560
The first time Mutt needs to call iconv, it should get (and cache) the
list of available encodings (the equivalent of iconv -l from the
command line). If the message's encoding i
t; > a celebration? ;-)
>
> A party sounds like a great idea. How about a bug hunting party?
>
> http://dev.mutt.org/trac/query?status=infoneeded&status=started&status=assigned&status=infoneeded_new&status=new&status=accepted&group=status&milestone=1.6
I have a th
