Using Mozilla 1.1. Original mail in Japanese (ISO-2022-JP) codeset. Displays OK in viewer. Displays OK in composition window when "Reply"ing, but not when "Forward"ing. To be precise, ISO-2022-JP displays properly in header, but not in body of quoted message.
Roger, please see bug # # 162593, if deleting component registry file cures your problem, mark this as a dup. Thanks.
Deleting compreg.dat did not resolve this problem. Some mail contents display properly, but others are either partly munged or the entire text is treated as 7-bit characters. Mail content as simple as: これは、漢字のテストです。 Is seen in the Compose window (when forwarding) as: $B$3$l$O!"4A;z$N%F%9%H$G$9!#(B Is there something I can supply that can help you reproduce the problem?
Could you please attach a problematic message before forwarding? Thanks.
Created attachment 101216 [details] mail folder-file containing sample data place this file in your Mozilla mail directory. start up Mozilla Mail. select the folder. select the message. click Forward. The message body text will not display properly, though the Japanese in the Header displays correctly.
yes, i can confirm that in case of Forwarding the body in japanese encodings: iso-2022-jp and Shift-JIS don't work, EUC-Jp somehow doesn't seem to be affected. Chinese encodings work also. I tested with Roger's sample mail and with a test folder BodyMime (all mail in this folder display body correctly except the two mentionned above)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: forwarded mail won't display properly in composition window → Japanese message body (iso-2022-jp and Shift-Jis) doesn't display correctly in case of Forward
it looks like the JIS that is not working is with Hankaku Kana allowed.
broken on the trunk, branch is OK, nominating
I think we should fix this asap. P2 bug. Estimate 4-7 days of debugging
i18n triage team: nsbeta1+/adt1
Keywords: nsbeta1 → nsbeta1+
I do not see the problem using my local trunk build (pulled this morning). I tried forward inline for plain and html using the attached message. Marina, could you try latested trunk?
I think this was probably fixed by bug 120728.
so mark as fixed
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
verifying as fixed using 20030602 build
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.