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.

Confirm the bug.

Reassign to mscott.

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.

marking nsbeta1+ and moving to mozilla0.8

QA contact to marina.

moving to mozilla0.9

reassigning to chuang.

moving to mozilla0.9.1

reassigning to putterman. I've been working on this a bit and have a partial solution. Need to work on the rest.

moving to 0.9.2

marking nsbeta1- and moving to future milestone

added nsbeta1 keyword, it's a good feature to have and it's a common situation for users to open a stanalone message window.

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.

reassigning to ssu.

take out Future and nsbeta1-. Change it to --- and nsbeta1 to ask for consideration of nsbeta1+ for m1.2final

we think this is a low priority bug, changed to nsbeta1-

i18n triage team: nsbeta1-

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.