Re: Q: View as Windows-1252?
* Kai Grossjohann on Sunday, August 12, 2007 at 23:36:40 +0200
> Thanks to Kyle's suggestions, I've now got
>
>| set assumed_charset=iso-8859-1:windows-1252
TFM says about assumed charset: "However, only the first content
is valid for the message body." So for "Westerners" simply using
the superset windows-1252 should be enough -- and work in your
case.
> in my muttrc file. However, it does not help for a message with the
> following headers:
>
>| Mime-Version: 1.0
>| Content-Type: text/plain; format=flowed
>| Content-Transfer-Encoding: 8bit
>
> Note that it does not indicate a charset. When I do Ctrl-E on this
> message, the prompt says "charset=us-ascii". Editing that to
> "charset=windows-1252" does the trick -- Mutt now shows umlauts as such
> instead of as question marks.
I have the following in muttrc (kudos to Alain Bench):
charset-hook ^unknown-8bit$ cp1252
charset-hook ^x-unknown$ cp1252
charset-hook ^x-user-defined$ cp1252
charset-hook ^us-ascii$ cp1252
charset-hook ^iso-8859-1$ cp1252
charset-hook ^iso-8859-8-i$ iso-8859-8
charset-hook ^gb2312$ gb18030
set assumed_charset="cp1252"
c
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting. [TOFU := text oben, followup unten]
Q: What is the most annoying thing in email and on usenet?