I think that the first thing for Character Encoding Autodetect to be less confusing is ti say what it does. Assuming that it means that any indication of a character set is ignored ans that it is guessed by the contents... Character Encoding Autodetect is normally not needed because a page MUST specify the encoding it uses. Using it instead of reporting an error to a webmaster is causing the webmaster to continue to make the same errors. Also, picking the character code from the HTTP request is an error because the contents of the page MUST specify the encoding, it knows better than an Apache server and the browser won't update the page when it's written to a file. The only case where character encoding mangling is necessary is when, for example, displaying a text file of which the character set is specified nowhere and, of course, displaying the page correctly before reporting to the webmaster.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/206884 Title: fuzzy/confusing firefox View -> Character encoding menu semantics To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/206884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
