GNOME Bugzilla – Bug 212631
should autorecognize broken windows charsets
Last modified: 2013-09-10 14:02:43 UTC
Evolution should automatically figure out when a message you received claims to be iso-8859-1 (or whatever), but is really Windows crap. No iso-8859 charsets have characters in the 128 to 159 range, but the windows ones do. We may not want to check every message for this though. Perhaps we could just check X-Mailer/User-Agent and only do it for Outlook+OE.
We already scan all message content to convert it to utf8, the check would be relatively easy.
ok, so I've started hacking this - but what should I do if I find a message that uses a Windows fake-charset?
note to self: http://czyborra.com/ has a list of charsets and stuff.
okay, so according to his page it seems that this only affects iso-8859-* charsets and all of them should be able to be mapped to windows-cp1252 so it was pretty simple. Does anyone have any messages of this type so I can test?
okay...so I misread... here's the real mapping: iso-8859-1 maps to windows-cp1252 iso-8859-2 maps to windows-cp1250 iso-8859-5 maps to windows-cp1251 iso-8859-6 maps to windows-cp1256 iso-8859-7 maps to windows-cp1253 iso-8859-8 maps to windows-cp1255 iso-8859-9 maps to windows-cp1254 iso-8859-13 maps to windows-cp1257
Well, as you saw, I tried sending you some messages, but it didn't work. Perhaps it only works on old versions of windows/ outlook/oe?
I know our admin/marketing people have sent such broken messages before.
Btw, this is still open because I haven't yet been able to test this functionality, although I suspect that it should work.
marking as 1.1.0 since mostly this just needs to be tested and maybe slight cleanups but other than that it is already "there"
seems to work...