Re: Q: View as Windows-1252?

[Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>]

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

On Monday, August 20 at 06:49 PM, quoth Alain Bench:
> -4) Kyle: You listed "charset-hook none windows-1252". I don't 
> recall having ever seen a charset=none label. Does it really happen?

I did actually see it in the wild. I think it was a misconfigured 
webmail client (<shudder> webmail clients are some of the worse 
abusers of charsets).

> -7) $assumed_charset takes a list of charsets, right. For raw 
> headers, Mutt scans the list and takes the first charset in which 
> the header is fully valid. However for bodies, Mutt takes... item #1 
> in list, period.
> There is *no* charset auto-sensing for bodies.

Oho! Interesting. How come?

> -10) Due to points #7 and #8, the optimal generic $assumed_charset 
> for westerners (ie for all Latin-1 centered languages) is the 
> mono-charset $assumed_charset=windows-1252
>
> Appending anything is (practically) useless. Prepending "utf-8" 
> would be good to headers, but would harm bodies.

Huh.

You know, it seems to me that something like that might benefit from 
matching all characters, in the guessed charset, against [:print:] 
(however that is determined for that charset). Is that even possible, 
or so ridiculously hard so as to never be implemented?

~Kyle
- -- 
A fanatic is one who can't change his mind and won't change the 
subject.
                                     -- Winston Churchill, July 5, 1954
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iD8DBQFGyd7JBkIOoMqOI14RAsdEAKDFUSF+o/ea2/I9HBZUdV8Hw275PgCfQUJB
vlJFTOCeEycNkR5NoRcREQE=
=Al1V
-----END PGP SIGNATURE-----