<<< Date Index >>>     <<< Thread Index >>>

Re: Q: View as Windows-1252?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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 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

And finally, windows is a superset of this other, and this other is 
often incorrectly labelled by brain-dead webmail applications:

    charset-hook iso-8859-1 windows-1252

> Is it possble to automate this, so that I only have to press a 
> single key?

The way you'd have to do it is to pipe the message to a script that 
replaces that header.

~Kyle
- -- 
Families are like fudge... mostly sweet with a few nuts.
                                                            -- Unknown
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iD8DBQFGszQpBkIOoMqOI14RAiqsAJ9Ein01r4CakLLNW2RqM+nMx5DrtgCeKA5y
3iBNiIDhbmFFgBH+UMeOSp4=
=p9kd
-----END PGP SIGNATURE-----