Closed Bug 86341 Opened 24 years ago Closed 24 years ago

mail headers become garbage

Categories

(Core :: Internationalization, defect, P1)

Product:
Core
Component:
Internationalization
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: masaki.katakai, Assigned: nhottanscp)

References

Details

(Keywords: intl, regression, smoketest)

Attachments

(2 files)

screenshot
11.87 KB, image/jpeg
Details
Patch, those C strings need UTF-8 to UCS2 conversion.
1.03 KB, patch
Details | Diff | Splinter Review
On today's nightly 20010617, mail headers on mail message view become garbage. Subject and Sender of japanese become garbage. I'll attach the snapshot. I checked 0615 build with the same machine and with the same profile, it worked file. So changes from 0615 might cause this problem.
Attached image screenshot —
I'm seeing this problem on Windows, Solaris too.
OS: Linux → All
Hardware: PC → All
Switching QA contact to ji@netscape.com.
Keywords: intl
QA Contact: andreasb → ji
Added regression,smoketest keywords.
Keywords: regression, smoketest
This started to happen from 2001-06-17-21-mtrunk build. The last good build was 2001-06-17-06-mtrunk build.
Priority to P1, Severity to blocker.
Severity: critical → blocker
Priority: -- → P1
this happens only with the subject in the message body and when you click Reply or Forward it displays correctly however you'll see garbage upon receiving for the subject in the body again
Adding scc to cc.
same is true for non-ascii recipient name that can not be displayed correctly in the message body , it'll be "G??nter Gr??se"
r=scc
checked in
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
The patch also fixed the recipient name problem reported by marina.
which build should this be fixed in? i was going to log a bug on this but i guess someone found it before me. i saw this with this mornings trunk builds 20010618xx during my smoketesting.
The check in time was 06/18/2001 11:05.
*** Bug 86491 has been marked as a duplicate of this bug. ***
*** Bug 86466 has been marked as a duplicate of this bug. ***
Masaki, please use a little more specific summary next time. ;)
*** Bug 86350 has been marked as a duplicate of this bug. ***
Verified both in the trunk and branch.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: