-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday, August 3 at 04:55 PM, quoth Kai Grossjohann:
> 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).
Ahh, interesting. Well, the latter is easily remedied; windows-1252 is
*also* a superset of us-ascii (so this hook won't harm anything):
charset-hook us-ascii windows-1252
The other one is... well, downright malicious! Out of curiosity, what
mail client is composing messages mislabelled utf8 like that?
>> 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.
Hmm, that's a badly worded man-page entry. I think it means one of two
things (both of which are, I think, true): either it's saying that
only the first charset that is valid for the message will be used
(i.e. if windows-1252 is a valid way of interpreting the message,
utf-8 will not be tried---this is especially important for asian
charsets, where in most cases there's no way to tell if the charset
produced random garbage or not), OR it's saying that if your message
comes in multiple parts, the charset that is found to be acceptable
for the first part will be used for all subsequent parts.
But this won't work at all for you, I think, because it only applies
to parts of the message without any charset indication, and your
problem is incorrect charset labelling.
~Kyle
- --
Only a mediocre person is always at his best.
-- Somerset Maugham
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFGs0gQBkIOoMqOI14RAmIXAKCujQfpfwPWKXzODG/7V8kUbHAM8QCg/zBz
ixwYbLdNZC2xjwFT6zCQeIE=
=ivnQ
-----END PGP SIGNATURE-----
