#3925: Always treat iso-8859-1 as cp1252
--------------------------+----------------------
Reporter: gahr2 | Owner: mutt-dev
Type: enhancement | Status: new
Priority: minor | Milestone:
Component: charset | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by kevin8t8):
I believe Vincent's argument is that if you received an iso-8859-1
message/attachment that was **intended** to have a 0x80 control character,
in a utf-8 environment it would end up being displayed and then possibly
saved as U+20AC (€).
Perhaps your argument back is "what are the odds of that?", but:
* Mutt already supplies the charset-hook to work around these kinds
issues.
* this is documented (albeit briefly) in
https://dev.mutt.org/trac/wiki/MuttFaq/Charset
* hardcoding this in for everyone, just to work around Outlook 12.0 bugs?
In 2017? Really?
If this were a rampant problem, it might merit a charset-hook in the
sample muttrc. But in this case I think the better question is "why", not
"why not". I don't feel "why" has a strong argument.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3925#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
