#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 gahr2):
Thanks for your comments Kevin!
I'd argue that the odds of receiving an iso-8859-1 mail with chars in
range 0x80-0x9f and wanting to "use" them as control characters is close
to zero. Am I missing any use case?
I really think a trade-off must be chosen between purity and user
friendliness. Just to figure out that a charset-hook is needed, and which
one, takes time and requires a fair grasp of the problem. Without a proper
understanding of charsets and overlaps thereof, a typical user will just
think that mutt can't properly display some characters. Anyway, this is
not about right or wrong, but it's a decision: does mutt require this
level of understanding from the typical user?
Perhaps the approach taken by the patch is too invasive. I would be happy
to have `charset-hook ^iso-8859-1$ cp1252` in the default muttrc.
For the record, other popular clients do this as well:
https://github.com/roundcube/roundcubemail/blob/master/program/lib/Roundcube/rcube_charset.php#L121-L126
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3925#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
