Subject in GB2312(MIME-encoded) is displayed as garbage on Linux. Body text has no problem.
Screenshot: http://bugzilla.mozilla.gr.jp/showattachment.cgi?attach_id=476 Original report in Bugzilla-jp: http://bugzilla.mozilla.gr.jp/show_bug.cgi?id=1751
With the attached testing mail, I did see the problem with the subject display. However, the testing mail is a mix of Simplied Chinese and Japanese characters. In this case, it is possible to have this problem: Japanese characters are mapped to gb2312 codepoints. And please note that the testing mail is a reply mail. I don't have any problems when viewing a gb2312 mail sent from mozilla. This testing mail is sent from Becky!, another possible cause of the problem.
The test case shows that the body is encoded in GB2312 but the real encoding used for the subject header is Shift_JIS. Try decoding the Base64 for the header and see which encoding makes sense. See the attached image below which was obtained when the encoding was swicthed to Shift_JIS from GB2312.
Created attachment 63833 [details] The header B64 string decoded as Shift_JIS The subeject seems to have been in Shift_JIS originally but was encoded usign BG 2312. How this happened exactly is a mystery but perhaps you can do this with Becky.
You can set the folder properties encoding to Shift_JIS and put a checkmark to force that encoding. You will see the subject header correctly also this way.
Yes, i can see the Japanese subject after forcing the folder charset to Shift-JIS, another good reason to have folder charset feature for this kind of mails. :-)
So the message is broken and the bug is invalid?
My guess is that this is a Becky-side bug. Most probably the original message had a Shift_JIS subject header and as the user replied to this message using GB2312, it encoded it without converting it to GB2312. If you use Mozilla from the beginning, the subject line in the image I attached can be encoded OK with BG2312 and you can read it under that encoding.
Marking it invalid for now unless there is additinal data to indicate otherwise.
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → INVALID
Verified as such.
Marked it as verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.