Closed
Bug 56275
Opened 24 years ago
Closed 7 years ago
After changing Themes mail body for non-ascii messages is garbled
Categories
(MailNews Core :: Internationalization, defect, P3)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: marina, Unassigned)
References
Details
(Keywords: intl, Whiteboard: [rtm-])
**** observed with 2000-10-12 build ****
Steps to reproduce:
- go to Preferences and change Themes from Modern to classic;
- come back to Messenger;
- select a message (any: JA, French, Cyrillic);
//note: header in the thread and header in the message body are fine but the
body itself is garbled
Comment 1•24 years ago
|
||
I can reproduce this with win32 branch build ID2000101108.
Work around is to create a new thread pane.
Status: NEW → ASSIGNED
Latin--2 languages are garbled in the thread as well (for Subject and sender
name)
adding rtm keyword, i think it's pretty serious
Keywords: rtm
*** Bug 56277 has been marked as a duplicate of this bug. ***
After switching Themes the Latin-2 entries in Address Book are garbled. Naoki,
do i leave as comments here or enter a new bug for AB?
Updated•24 years ago
|
Target Milestone: --- → M23
Updated•24 years ago
|
Whiteboard: [rtm-]
Comment 7•24 years ago
|
||
marina, can you re-test this for the current build?
Comment 8•24 years ago
|
||
Mass change to bugs filed by marina --> QA contact to marina.
thanks!
QA Contact: momoi → marina
Updated•24 years ago
|
Target Milestone: --- → mozilla0.8
Comment 9•24 years ago
|
||
Adding mscott to cc, do you know any possibility that libmime might be affected
by the theme change?
Comment 10•24 years ago
|
||
MIME sends UTF-8 to layout, so messenger notify it by setting a force charset.
But after the theme change, the force charset seems to be reset. So input to
layout is not recognized as UTF-8.
If I open a message as a stand alone, the message is shown correctly.
Also if I set 'mCharsetInitialized' false manually (in debuger) the message is
shown correctly because it forces a charset back to UTF-8.
Scott, please take a look at this.
void
nsMessenger::InitializeDisplayCharset()
{
if (mCharsetInitialized)
return;
// libmime always converts to UTF-8 (both HTML and XML)
if (mDocShell)
{
nsAutoString aForceCharacterSet;
aForceCharacterSet.AssignWithConversion("UTF-8");
nsCOMPtr<nsIContentViewer> cv;
mDocShell->GetContentViewer(getter_AddRefs(cv));
if (cv)
{
nsCOMPtr<nsIMarkupDocumentViewer> muDV = do_QueryInterface(cv);
if (muDV) {
muDV->SetForceCharacterSet(aForceCharacterSet.GetUnicode());
}
mCharsetInitialized = PR_TRUE;
}
}
}
Assignee: nhotta → mscott
Status: ASSIGNED → NEW
Target Milestone: mozilla0.8 → ---
Comment 11•24 years ago
|
||
marking nsbeta1-. Need to get theme switching for message pane to work first.
Comment 12•24 years ago
|
||
Scott, I don't know about getting theme switching to work first, but this
problem seems serious with any theme change. Marina, can you comment on the bug?
Comment 13•24 years ago
|
||
That's why we have a big warning when you switch themes which says "be sure to
close all mail windows". docshell's and such tend to become detached when you
switch themes. this bug should be marked a dup of that one.....we still have a
lot of theme switching work to do.
Updated•24 years ago
|
Severity: critical → normal
Comment 14•23 years ago
|
||
I think Scott is correct, the warning always shows up on-top for me. Please let
us know, if you see something different. Agree with the nsbeta1- for now.
Comment 15•23 years ago
|
||
Marina - If you and Jenn agree on MScott's message, that this is as designed, we
should close this as invalid.
Reporter | ||
Comment 16•23 years ago
|
||
the verification of this bug is blocked by bug 116038 though i don't think it is
happening in the latest builds
Updated•20 years ago
|
Product: MailNews → Core
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
Assignee: mscott → nobody
Updated•16 years ago
|
QA Contact: marina → i18n
Comment 17•7 years ago
|
||
Based on the last old comments, I think this should be closed, so closing..
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•