HOW TO CHANGE TEXT ENCODING IN FIREFOX FOR ANDROID

Text copyright Mozilla Foundation licensed under Creative Commons Attribution-ShareAlike 3.0 United States or, at your option, any later version. Hopefully, there won’t be a Text Encoding menu in 2022. Obviously, that would involve renaming the item to something like “Override Text Encoding”. A long time ago in Firefox (like maybe before Firefox 30-50 not sure when exactly), I could switch the text encoding manually in the 'View' menu to fix this and view the part of the page that has mojibake correctly, even if something else in the page would look incorrect. The expectation is that the telemetry will show that the single menu item “Automatic” can replace the whole menu. This will eliminate a reason for Firefox to differ from Chrome and Safari on the encoding topic. The spec says not to do this, which is why Firefox does not do this at present, but the plan is to change the spec. Īdditionally, the intent is to start honoring the encoding declaration in an XML declaration in text/html soon. when 86 has spent its time on the release channel). If things go well, the telemetry can be analyzed when Firefox 87 is released (i.e.

HOW TO CHANGE TEXT ENCODING IN FIREFOX FOR ANDROID

After all, Chrome and Firefox for Android don’t have the menu at all.įor users who have telemetry enabled, we collect data about whether the item “Automatic” was used at least once in given Firefox subsession, whether an item other than “Automatic” was used at least once in a given Firefox subsession, and a characterization of how the encoding that is being overridden was determined (from HTTP, from meta, from chardetng running without the user triggering it, from chardetng as triggered by the user by having chosen “Automatic” previously, etc.). This item runs chardetng even for labeled pages with UTF-8 allowed as a possible outcome and with the top-level domain of the page ignored.ĭoes it make sense to have items other than “Automatic”? Probably not. There is a new first item called “Automatic”.Instead of there being three locale-specific detection modes, chardetng is now enabled for everyone without UI to turn it off. The three Japanese encodings have been replaced with a single item that autodetects among those three.The menu is now called “Text Encoding” (as in Safari) as opposed to “Character Encoding” on the assumption that the new name suggests the purpose better to users who are not familiar with the terminology.

There are four differences made as four distinct steps over time: In mid-January 2021, the Text Encoding menu in Firefox looks like this: To recap, at the end of 2014 the Character Encoding menu in Firefox looked like this: Still, I made it more usable in the case when it is used. Copypaste from the old intro still applies: This post is about a UI feature that I wish no one would have to use. Now seems like a good time to take a new snapshot for the record. Text Encoding Menu in 2021 Text Encoding Menu in 2021īack in December 2014, I wrote a post called Character Encoding Menu in 2014.

How to change text encoding in firefox