#3773: piped text attachment is not converted to the local charset
----------------------+----------------------
Reporter: vinc17 | Owner: kevin8t8
Type: defect | Status: closed
Priority: major | Milestone:
Component: charset | Version:
Resolution: fixed | Keywords:
----------------------+----------------------
Changes (by Kevin McCarthy <kevin@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"f46ed1718cb4ac38f7c5d5f84b5ca4be576cbb72"
6831:f46ed1718cb4]:
{{{
#!CommitTicketReference repository=""
revision="f46ed1718cb4ac38f7c5d5f84b5ca4be576cbb72"
Perform charset conversion on text attachments when piping. (closes #3773)
(see #3886)
When piping a text attachment, there is no reliable way to know the
charset used.
Vincent Lefèvre says:
It was decided in the past that when there is no information on the
charset in a transmission to an external command (e.g. as for mail
composing), texts are expected to be transmitted in the local
charset.
Add a MUTT_CHARSET flag to enable charset conversion on text
attachments for both when $attach_split is set and unset.
}}}
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3773#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
