[Pkg-mutt-maintainers] Bug#671847: [Mutt] #3879: mutt: encoded-words are not decoded in mailto:

[Thomas Roessler]

You should do the RFC 2822 parse first, then the decode -- 2047 is
specifically written so it parses as one token.

Thomas Roessler  (@roessler)

On Tue, Sep 27, 2016 at 6:17 PM, Mutt <fleas at mutt.org> wrote:

> #3879: mutt: encoded-words are not decoded in mailto:
> ------------------------+----------------------
>   Reporter:  antonio@…  |      Owner:  mutt-dev
>       Type:  defect     |     Status:  closed
>   Priority:  major      |  Milestone:
>  Component:  charset    |    Version:  1.7.0
> Resolution:  fixed      |   Keywords:
> ------------------------+----------------------
> Changes (by Kevin McCarthy <kevin@…>):
>
>  * status:  new => closed
>  * resolution:   => fixed
>
>
> Comment:
>
>  In [changeset:"55819a7e61695bffea31646464183fcb2d54899d"
>  6802:55819a7e6169]:
>  {{{
>  #!CommitTicketReference repository=""
>  revision="55819a7e61695bffea31646464183fcb2d54899d"
>  RFC2047-decode mailto header values. (closes #3879)
>
>  RFC 6068 specifies that the header values (with the exception of body)
>  may contain RFC 2047-encoded values.
>  }}}
>
> --
> Ticket URL: <https://dev.mutt.org/trac/ticket/3879#comment:2>
> Mutt <http://www.mutt.org/>
> The Mutt mail user agent
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-mutt-maintainers/attachments/20160927/2f69998f/attachment.html>