Re: mutt/1269: send_charset doesn't support charset-hook'd charsets

To: Mutt Developers <mutt-dev@xxxxxxxx>, Takahashi Tamotsu <ttakah@xxxxxxxxxxxxxxxxx>, Marco d'Itri <md@xxxxxxxx>, 152444@xxxxxxxxxxxxxxx
Subject: Re: mutt/1269: send_charset doesn't support charset-hook'd charsets
From: Takahashi Tamotsu <ttakah@xxxxxxxxxxxxxxxxx>
Date: Mon, 15 Aug 2005 14:50:47 +0200
List-unsubscribe: <mailto:mutt-dev-request@mutt.org?body=unsubscribe>
References: <mutt-pr-1269@xxxxxxxxxxxxx>
Reply-to: bug-any@xxxxxxxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

Synopsis: send_charset doesn't support charset-hook'd charsets

**** Comment added by tamo on Mon, 15 Aug 2005 14:50:47 +0200 ****
 FYI: Some discussion here:

For 1.5.9: iconv-hook patch by Moriyama-san
http://marc.theaimsgroup.com/?l=mutt-dev&m=110873560103951&w=2


And the conclusion:
http://marc.theaimsgroup.com/?l=mutt-dev&m=110934238023932&w=2


No side effect so far. The iconv-hook patch is well-tested.
Should this be marked as "need-eg"? I don't think so,
but I think we can apply this patch very safely.

Prev by Date: [PATCH] Re: Bug#316388: still prompts for passphrase with gpg-agent unless GPG_TTY is set
Next by Date: Re: mutt/1675: no filename when using _mutt -e 'set content_type=text/html' email_address_
Previous by thread: [PATCH] Re: Bug#316388: still prompts for passphrase with gpg-agent unless GPG_TTY is set
Next by thread: Re: mutt/1269: send_charset doesn't support charset-hook'd charsets
Index(es):
- Date
- Thread