254868 - [meta] Character Encoding bugs

Status: NEW

(MailNews Core :: Internationalization, defect)

Description

[Prognathous]

This bug tracks issues with the Character Encoding menu, related prefs,
auto-detection and any suggested changes to the design of this (rather
confusing) UI.

Prog.

Comment 1

[Eyal Rozenberg]

*** Bug 260706 has been marked as a duplicate of this bug. ***

Comment 2

[Eyal Rozenberg]

splitting relevant parts of dupe bug into separate bugs.

Comment 3

[André Pirard]

Please add Bug 608609.

Side notes:

It is a bad idea to specify the character code of a Web page in the envelope (SMTP or HTTP MIME), because it puts the burden of modifying the page to someone who stores it to a file instead of to whoever wrote the page in the first place.

Any feature allowing the user to correctly display the bad character set of a bad page is not only inciting the Web authors to continue writing more bad pages but also towards the users displaying good pages the wrong way.  The Web is full of horror stories by people not having understood character sets explaining other people how to make mistakes.

Comment 4

[rinaldo rui]

Hello. With Seamonkey 2.6.1 when opening a file it keeps the character encoding specified in the file itself as <meta>...
With Seamonkey 2.21 all of a sudden the character encoding is forced to Western (Windows-1252)" even though it is not specified in the "customized list".
I haven't changed anything, just installed the new version and all of a sudden this has happened. I have gone back to the previous version and it works fine (that is: it does not change the character encoding).
can anyone help?
thanks

Comment 5

[Masatoshi Kimura [:emk]]

Please file a new bug and block this bug instead of adding a comment to a meta-bug.

Comment 6

[Henri Sivonen (:hsivonen)]

The remaining open dependencies seem to be outside Core. For Core we have bug 746911.