GNOME Bugzilla – Bug 101010
Bad headers in some articles
Last modified: 2006-06-18 05:25:09 UTC
When Pan decides itselvs that message body needs different encoding than set. (I.e. group has set ISO8859-2 encoding but sometimes -- ie. in reply to m$ outlook message -- it decides that message body is in utf-8). Why it does not change also message headers to match body encoding? Or force reencoding into iso8859-2 ?
Lukas: don't quite understand this bugreport. Can you give me a step by step recipe on how to reproduce this bug?
I have subscribed group cz.muni.test, in preferences I have defaultcharset iso8859-2. Someone post an article from M$ outlook that does not report any encoding. However real encoding was really iso8859-2 but not set, an article contained 8bit chars. --- X-Newsreader: Microsoft Outlook Express 5.00.2615.200 MIME-Version: 1.0 Content-Type: text/plain --- I follow up and wrote some reply. However pan reencode message body to utf-8 encoding and posted it with MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit however chars were encoded with utf-8. So pan should to not change encoding or when it changes encoding than should correct message headers. Is it now more clear? More over if I set defaultcharset to utf-8, pan does not display outlook messages with 8bit chars. (outlook messages do not have any encoding info as I showed).
Yes thanks, that's much clearer, even though I can't reproduce it. :) BTW: what locale are you using? *** This bug has been marked as a duplicate of 89453 ***
I have LANG unset and LC_CTYPE=cs_CZ. By the way can you control the change of message body encoding? If so change encoding in headers as well. And it reminded me, that if \t [tab] char is in subject and I follow up such message the pan posts corrupted headers. (at least it says that message has corrupted headers and does not display it).