-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, Jun 30, 2015 at 11:20:42AM +0000, Virgo Pärna wrote:
[...] > It did not work in 4.4.9, because there I had not set UTF-8 > locale in confuguration. When I set it, then the attribute charset > started also working. But one of the changes alone was not enaugh. > So I guess there is some change in MIME library and some > change in default locale of services. Aigh. I feel your pain. My favourite anecdote here? Double-encoding-declaration: I get a HTML mail (correctly) declared 'windows-1252' [1] in the Mail (or MIME) headers. But the HTML within has a <meta http-equiv="blah"/> *also* (correctly but redundantly) declaring the content as 1252. My mail user agent (correctly) transforms the thing to UTF-8, because it's my friggin' policy. Now the html "header" is lying (no, the transcoder doesn't catch that -- how should it?) Pass that to html2text and this one gets the encoding wrong. Took me a while to chase that down. Duh. [1] Why does this scenario correlate nearly 100% with windows-1252? This is left as an exercise to the reader. - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlWSgQUACgkQBcgs9XrR2kbH1QCffS1I/wY7/pzquYSICOMUAY2Y oVYAnjOjt1Lm4yLeQobBDy9nvKkBn1Pg =gkS3 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150630114405.ga12...@tuxteam.de