Open
Bug 49230
Opened 24 years ago
Updated 2 years ago
standalone message window does not inherit character coding setting from main window
Categories
(MailNews Core :: Internationalization, defect)
Tracking
(Not tracked)
NEW
Future
People
(Reporter: guangyan, Unassigned)
References
Details
(Keywords: intl)
This bug is related to bug 45059. Specifically, when viewing a message with an incorrect MIME charset info in the main window (the 3-pane view), one can change the view->character coding setting so that the message will be displayed correctly. After making this change, when the message is opened up in a standalone window, it should be displayed correctly if the change has been inherited by the standalone window. However, the standalone window does not currently inherit the changes made in the main window. observed with 2000-08-16-08M18 build Steps to reproduce: 1. in the main window view a message with false/missing MIME charset info so that it's not displayed correctly. 2. go to View->Character Coding and select the correct language so that the message is displayed correctly. 3. double click on the message to open it in a standalone window. expected result: message should be displayed correctly in a standalone window using main window's new charset setting. actual result: message is not displayed correctly because standalone window fails to inherit the charset change made in the main window.
Comment 3•24 years ago
|
||
I don't think this meets our beta3 criteria. Moving to future. Feel free to take it up with mail triage team if we need to look at it more. You can always just change the charset in the standalone message pane and we display the message correctly.
Target Milestone: --- → Future
Comment 4•24 years ago
|
||
marking nsbeta1+ and moving to mozilla0.8
Whiteboard: [nsbeta1+]
Target Milestone: Future → mozilla0.8
Comment 9•24 years ago
|
||
reassigning to putterman. I've been working on this a bit and have a partial solution. Need to work on the rest.
Assignee: chuang → putterman
Comment 11•24 years ago
|
||
marking nsbeta1- and moving to future milestone
Comment 12•23 years ago
|
||
added nsbeta1 keyword, it's a good feature to have and it's a common situation for users to open a stanalone message window.
Keywords: nsbeta1
Comment 13•23 years ago
|
||
Charset override only has one time effect, not inherited to other window which is also true for browser. For the convenience to view non MIME, we have folder charset feature.
Updated•23 years ago
|
Comment 15•22 years ago
|
||
take out Future and nsbeta1-. Change it to --- and nsbeta1 to ask for consideration of nsbeta1+ for m1.2final
Comment 16•22 years ago
|
||
we think this is a low priority bug, changed to nsbeta1-
Updated•22 years ago
|
Target Milestone: --- → Future
Comment 17•22 years ago
|
||
i18n triage team: nsbeta1-
Comment 18•21 years ago
|
||
I face this problem frequently as I want to view all HTML with charset Big5 with Big5-HKSCS (to see some Hong Kong special characters, which are very common). I need to change the charset page by page, which is unconvenient. I hope that the charset can be inherited. Or, moreover, it is better than I can choose to override the MIME charset by my defualt charset.
Updated•20 years ago
|
Product: MailNews → Core
Assignee | ||
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•16 years ago
|
QA Contact: marina → i18n
Comment 19•5 years ago
|
||
surely this is no longer true?
Assignee: smontagu → nobody
Severity: major → normal
Flags: needinfo?(rsx11m.pub)
Priority: P3 → --
Updated•4 years ago
|
Flags: needinfo?(rsx11m.pub)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•