164784 - Japanese message body (iso-2022-jp and Shift-Jis) doesn't display correctly in case of Forward

Status: VERIFIED FIXED

(MailNews Core :: Internationalization, defect)

Description

[Roger Meunier]

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.

Comment 1

[marina]

Roger, please see bug # # 162593, if deleting component registry file cures your
problem, mark this as a dup. Thanks.

Comment 2

[Roger Meunier]

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?

Comment 3

[marina]

Could you please attach a problematic message before forwarding? Thanks.

Comment 4

[Roger Meunier]

Attachment: 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.

Comment 5

[marina]

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)

Comment 6

[marina]

it looks like the JIS that is not working is with Hankaku Kana allowed.

Comment 7

[marina]

broken on the trunk, branch is OK, nominating

Comment 8

[Frank Tang]

I think we should fix this asap. P2 bug. Estimate 4-7 days of debugging

Comment 9

[Samir Gehani]

i18n triage team: nsbeta1+/adt1

Comment 10

[nhottanscp]

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?

Comment 11

[nhottanscp]

I think this was probably fixed by bug 120728.

Comment 12

[nhottanscp]

so mark as fixed

Comment 13

[marina]

verifying as fixed using 20030602 build