Re: Q: View as Windows-1252?
On Fri, Aug 03, 2007 at 08:56:57AM -0500, Kyle Wheeler wrote:
> On Friday, August 3 at 03:37 PM, quoth Kai Grossjohann:
> > I find that I (fairly) often get messages with no charset specified, or
> > with the wrong charset specified, so I do Ctrl-E on them and edit the
> > charset parameter to windows-1252, which seems to work well for most
> > cases.
>
> What you probably want to do is set up some charset-hooks. For
> example:
>
> charset-hook none windows-1252
> charset-hook unknown windows-1252
> charset-hook x-unknown windows-1252
> charset-hook unknown-8bit windows-1252
> charset-hook windows-1251 windows-1252
I think this applies to bad charset specifications. But in my case I
notice that Ctrl-E either shows me charset=utf-8 (where the message is
in Windows-1252), or charset=us-ascii (msg also in Windows-1252).
> I have a bunch of hooks like this to fix known bad charsets. The
> 'assumed_charset' feature is also really really useful:
>
> set assumed_charset=us-ascii:windows-1252:utf-8
I didn't use this because it says "only the first content is valid for
the message body". But I guess it doesn't hurt to try.
Thanks,
Kai