GNOME Bugzilla – Bug 206422
chars with 8th bit set in header fields (from, subject, etc) are converted to underscores
Last modified: 2013-09-10 13:59:49 UTC
Characters with 8th bit set in header fields (From, Subject) are converted to underscores. It's fatal feature in Evo. Yes, RFC prohibbits this, but AFAIK majority of mail with 8bit headers is being sent by OutLook express. Of course this makes headers (most importantly subject) unreadable. Use value of mail's charset from Content-Type header to interpret these characters. Please fix it ASAP!
the problem is that there's no way to get the Content-Type header (in fact, god only knows if it even exists) easily while parsing the headers since each header knows nothing about previously parsed headers (or, heaven forbid) headers yet-to-be parsed. Now, what I *have* done is to make Evolution use the user's locale charset if it finds the header to contain 8-bit text without being properly encoded. I'm not sure what else I can do...
Thanks for trying to fix this bug. Unfortunately the fix you made doesn't fix things for a lot of nations which use different charsets under unix and under windows (japanese and russians included). So the subject:and From: will be unreadable as before.. The only way to fix this bug is not to parse headers one by one in sequence, but first to peek value of Content-Type header, extract charset, and then parse each of the headers. Even a simple hack would be fine if you don't want to redesign headers parsing approach. Or the encoder that will convert all header's value on arrival to quoted-printable (Evo displays headers with quoted-printable in them just fine). This bug is extremely important, and with it Evo will be unusable for a lot of people. A lot of other popular MUAs show 8bit chars in headers just fine, using value of content-type header. So the Evo is just an exception unfortunately.
*** This bug has been marked as a duplicate of 201993 ***