Hacker, author, trainer
Technorati Profile [technorati.com]
This week I am mostly hating email programs that send out emails with the wrong charset listed in the Content-Type header.
The most common error I see is
Content-Type: text/plain; charset=iso-8859-1
When actually it should be
Content-Type: text/plain; charset=Windows-1252
If an email has the right charset then mutt will display it properly, but if it's wrong then I get a nasty mess and the mail is far harder to read.
It's therefore ironic that the worst offender is a regular email I get from a company who advises on small company PR
Sounds like a job for The Demorniser (Score:2)
Sounds like another job for The Demoroniser [fourmilab.ch]... Or an equivalent tool.
-- "It's not magic, it's work..."
Re:Sounds like a job for The Demorniser (Score:2)
It's probably a programmer somewhere who thinks that iso-8859-1 and Windows-1252 are the same thing.
Re:Sounds like a job for The Demorniser (Score:2)
Fair point. You can probably assume that the main problem is when Windows sends out a Windows encoding say cp-1252, but lies and calls is iso-8859-1.
One possible solution is to scan any iso-8859-1 files, looking for any diagnostic control-code points (Demoroniser has some suggestions for that), and then ask a recoding program convert this to a civilised scheme, or correctly set the Content-Type.
I have to deal with this all the time, users think that Windows is "correct", then the output a document, inco
-- "It's not magic, it's work..."
Re:Sounds like a job for The Demorniser (Score:2)
It's probably some programmer somewhere who has no idea what charsets are, or didn't bother caring enough to check the output, and just used someone else's code (either an existing library or copy/paste).
Re:Sounds like a job for The Demorniser (Score:2)