Re: [Mutt] #2982: non-ascii sender names not decoded in gmail imap

To: shado23@xxxxxxxxx, brendan@xxxxxxxxxx, gregory.petrosyan+mutt@xxxxxxxxx
Subject: Re: [Mutt] #2982: non-ascii sender names not decoded in gmail imap
From: Mutt <fleas@xxxxxxxx>
Date: Sat, 17 May 2008 19:01:56 -0000
Cc: mutt-dev@xxxxxxxx
In-reply-to: <039.70e629b16d961bf91f1d65abe0b9516a@xxxxxxxx>
List-post: <mailto:mutt-dev@mutt.org>
List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-dev"
Mail-followup-to: fleas@xxxxxxxx
References: <039.70e629b16d961bf91f1d65abe0b9516a@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#2982: non-ascii sender names not decoded in gmail imap message index

Changes (by brendan):

  * status:  new => closed
  * resolution:  => wontfix

Comment:

 I'm afraid this particular bug is much easier for google to fix than me.
 It's very hard to attempt to decode improperly encoded strings without
 running the risk of mishandling proper strings. I'm not going to attempt
 it myself. I am willing to be proven wrong by a nice clean patch though :)

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2982#comment:2>

References:
- [Mutt] #2982: non-ascii sender names not decoded in imap message index
  - From: Mutt

Prev by Date: Re: [Mutt] #3023: hcache vs. switching charset
Next by Date: [ANNOUNCE] mutt-1.5.18 has been released
Previous by thread: Re: [Mutt] #2982: non-ascii sender names not decoded in gmail imap
Next by thread: [Mutt] #2983: mutt 1.5.17 fails to build on old Linux
Index(es):
- Date
- Thread