User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.2.1) Gecko/20021130 Most of the emails I receive use the charset ISO-8859-1, and several include 8bit characters (typically German umlauts). Usually, these are displayed correctly in the Mozilla's mail reader. However, opening an attachments that's handled by a plugin (as opposed to an external application) breaks the character encoding. This can't be corrected other than by re-starting the mail application. E.g., I've installed Acrobat Reader as Mozilla plugin. When I open a PDF attachment, Mozilla Mail replaces the mail text with the Acrobat plugin that displays the attached document. When changing back to a text view (by selecting another mail or a text attachment), the umlauts (and other special characters) in that mail are no longer displayed correctly. Instead of each umlaut, a sequence of two special characters is displayed. This effect can't be reverted, i.e. the only way to permanently get back the umlauts is re-starting the mail reader. When changing the display character encoding for such a mail to UTF-8, the umlauts can be read again. However, after switching to a different mail and back (and thereby restoring the original charset), the umlauts are broken again. The mail (view source) contains 8bit umlaut characters in ISO-8859-1 charset. It seems, that Mozilla Mail is converting them to UTF-8 (for internal operation, I guess), but never converts them back for display. The same effect appears with other plugins and also in windows that were opened for a specific mail (by double-click). Reproducible: Always Steps to Reproduce: 1. Install Acrobat plugin, prepare mailbox with mails with umlauts and PDF attachments 2. Open a mail, then open it's attachment (so that the plugin replaces the text window) 3. Switch to another mail with umlauts (so that the text area is restored) Actual Results: 8bit characters are no longer presented correctly, but (I suppose) in UTF-8. Expected Results: Mozilla should display the characters correctly, i.e. the same way it did, before the plugins temporarily replaced the text area. This bug's been there in previous versions, i.e. I had the same problem with 1.0, 1.0.1 and 1.1.

Please only repport bugs if you use the latest milestone (there is a big note in the bug report page : "2 weeks old build"). *** This bug has been marked as a duplicate of 110729 ***

v