Closed
Bug 70525
Opened 23 years ago
Closed 23 years ago
Non ASCII mail body is garbled after switch from "Account Central"
Categories
(MailNews Core :: Internationalization, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9
People
(Reporter: marina, Assigned: nhottanscp)
References
Details
(Keywords: intl)
Attachments
(1 file)
1004 bytes,
patch
|
Details | Diff | Splinter Review |
**** observed with 2001-02-28 build **** go to the smoketest folder and look at 4 th message or send a message in UTF-8, get it and note that the body displays 8 bit as two single ones
Assignee | ||
Comment 2•23 years ago
|
||
I think this is caused by the force charset setting to "UTF-8" for the message body view is somehow cleared. The same problem when changing theme. Not sure if this is a regression or just randomly happening.
After utf-8 mails get this problem, all the Japanese mails in the mailboxes including those sent in ISO-2022-JP get garbled as well. Changed QA contact to marina.
Keywords: intl
Priority: -- → P1
There is one scenario which can always reproduce the problem on my machine with 03/06 win32 trunk build: 1. Launch Mail. 2. Confirm that the Japanese mails in your mailbox are displayed correctly. 3. Highlight Local Folders and select New | Folder 4. Enter some japanese characters for the local folder name and click on OK button. 5. Go back to the Japanese mail you just checked at step 2, you'll see the Japanese mail body are all garbled.
yes, this is one way to see the problem, i encountered it today while entering bug #71099
Nominating for nsbeta1. This is not only limited to utf8 mails.
Keywords: nsbeta1
Assignee | ||
Comment 7•23 years ago
|
||
Can you reproduce it with 6.0 or 6.01 (i.e. is this really a regression)?
Assignee | ||
Comment 9•23 years ago
|
||
>4. Enter some japanese characters for the local folder name and click on OK button.
Does it have to be a Japanese folder name? How about ASCII folder name?
Comment 10•23 years ago
|
||
Yes, creating an ascii folder in "Local Folders" can also make the problem happen.
Comment 11•23 years ago
|
||
This is reproducible with a new profile either with an IMAP or POP account.
Assignee | ||
Comment 12•23 years ago
|
||
Change the summary, this happens after coming back from "Account Central" view. Cc to racham, we always need to set message body view to UTF-8 (see the code in nsMessenger.cpp). I think something got broken after showing http://lxr.mozilla.org/seamonkey/source/mailnews/base/src/nsMessenger.cpp#328 Bhuvan, I have a related question. Is "Acount Central" view localizable?
Status: NEW → ASSIGNED
Summary: Regression:UTF-8 encoded mail body is garbled → Non Latin1 mail body is garbled after switch from "Account Central"
Target Milestone: --- → mozilla0.9
Comment 13•23 years ago
|
||
Naoki, AccountCentral view is localizable (msgAccountCentral.dtd) Also, I have patch that causes ContentViewer assertion when switched from AccountCentral to Inbox. When I land the patch for that bug, I will update this bug and we can verify to see if the problem reported here has gone.
Assignee | ||
Comment 14•23 years ago
|
||
Is there a bug for that assertion (so I can put that as depend)?
Assignee | ||
Updated•23 years ago
|
Summary: Non Latin1 mail body is garbled after switch from "Account Central" → Non ASCII mail body is garbled after switch from "Account Central"
Assignee | ||
Comment 15•23 years ago
|
||
*** Bug 70766 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 16•23 years ago
|
||
*** Bug 71819 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 17•23 years ago
|
||
*** Bug 66757 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 18•23 years ago
|
||
Assignee | ||
Comment 19•23 years ago
|
||
I changed nsMessenger.cpp to set force charset to UTF-8 per message. This makes sure that the view is always UTF-8, even after reset by switching from the account central or changine the theme (bug 56275) or whatever situations we might exist. On my machine PIII 500MHz, it takes 95.78 microseconds, so it won't take much time even executed per message. Scott, what do you think?
Assignee | ||
Comment 20•23 years ago
|
||
*** Bug 69340 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 21•23 years ago
|
||
This seems to be fixed by the performance landing.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 22•23 years ago
|
||
Naoki, mScott fixed the problem I referred to on the branch and the merge hence seemed to have fixed this one. thanks scott. bhuvan
Assignee | ||
Comment 23•23 years ago
|
||
*** Bug 73706 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 24•23 years ago
|
||
*** Bug 72641 has been marked as a duplicate of this bug. ***
Comment 26•23 years ago
|
||
*** Bug 74401 has been marked as a duplicate of this bug. ***
Reporter | ||
Comment 27•23 years ago
|
||
*** Bug 74795 has been marked as a duplicate of this bug. ***
Comment 28•21 years ago
|
||
*** Bug 198240 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•