Build: 032417c ja build. When forwarding a message inline, the Japanese words for Subject, Date, To and From in the header of the original message are corrupted. When forwarding a message as an attachment, those words are in English. Steps of reproduce: 1. Launch Mail. 2. Highlight a mail and select Message | Forward |Inline, on the forward mail compose page, you'll see the corrupted ja words. After receiving, the header of the forwarded mail is corrupted in the msg view pane. 3. Highlight a mail and select Message | Forward |as Attachment, send the mail to the testing account itself. After receiving, you'll the header of the forwarded mail is in English.
We have a workaround for Jab1.
The workaround is in ja 032417d build.
After tallking to mscott in detail (Thanks! Scott for taking the time to help us), I reverted the following strings in "chrome: messenger: locale: ja-JP: mime.properties" to English for JA Beta 1. String IDs: 1000 - 1023
Contact to ji.
Kat, have you filed a bug for Scott? This bug has the dependency on the core bug.
That's 34666 assigned to me.
Add dependency on 34666.
Putting on [nsbeta2+] radar for beta2 fix.
34666 have been fixed since 4/27. What is the status of THIS bug now ?
rchen said since 34666 is fixed we should mark this bug fix so IQA can verify it. momoi- please verify this against jab2. Thanks
mark it fixed
When forwarding a message inline, the header of the forwarded mail is in Japanese and is not corrupted. However, when forwarding a message as attachment, the header of the forwarded mail is in English. This bug is only partially fixed.
Above test results are done with Japanese 2000-07-21-09 build.
I wouldn't hold beta2 for this, this late in the beta2 cycle. i.e. I would not pull the beta off the wire for this problem. If it really isn't fixed, then I think we need to remove the beta2+ label and reschedule for beta3.
I suggest that we don't deal with the headers in attachments. Attachments should not be modified from what you received from the sender and that includes RFC 822 headers in ASCII. We forward msgs to different language users and we should not lock in headers in one language. If the inline headers can show in Japanese, then we should close this bug. By the way, I filed a separate bug to revert all inline headers from Japanese to English for JA build. Japanese users may forward inline msgs to non-Japanese users and may even use Western encoding. I don't think it is a good idea to keep quoted RFC 822 headers in Japanese.
That makes sense. Marked it as fixed.
Marked it as verified.