Re: [Mutt] #3039: wrong/ignored character set for traditional PGP

To: matthias.andree@xxxxxx, pdmef@xxxxxxx
Subject: Re: [Mutt] #3039: wrong/ignored character set for traditional PGP
From: Mutt <fleas@xxxxxxxx>
Date: Thu, 12 Jun 2008 13:09:27 -0000
Cc: mutt-dev@xxxxxxxx
In-reply-to: <054.3358a23e8714f61b4b8ff1b0b9cb4199@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: <054.3358a23e8714f61b4b8ff1b0b9cb4199@xxxxxxxx>
Reply-to: fleas@xxxxxxxx
Sender: owner-mutt-dev@xxxxxxxx

#3039: wrong/ignored character set for traditional PGP

Changes (by pdmef):

  * component:  mutt => crypto
  * summary:  mutt-1.5.17: wrong character set for traditional PGP =>
              wrong/ignored character set for traditional PGP

Comment:

 As rfc2440 mentions Charset armor header, how about the modification to
 Tamo's pgp_charsethack.1 patch? It doesn't touch the sending part and
 doesn't add the option; it only makes mutt properly recognize the Charset:
 armor header. Note that the patch is untested.

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

References:
- [Mutt] #3039: mutt-1.5.17: wrong character set for traditional PGP
  - From: Mutt

Prev by Date: mutt: new changeset
Next by Date: Re: [Mutt] #3067: PGP/MIME signatures incorrectly assigned
Previous by thread: Re: [Mutt] #3039: mutt-1.5.17: wrong character set for traditional PGP
Next by thread: Re: [Mutt] #3039: wrong/ignored character set for traditional PGP
Index(es):
- Date
- Thread