Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Legacy encoding: UTF-8 no longer available as of Firefox 28

  • 11 uphendule
  • 81 zinale nkinga
  • Igcine ukuphendulwa ngu wong369

more options

I'm using the development version of Kubuntu 14.04. I just did an 'aptitude update; aptitude full-upgrade' today, which updated my installation of Firefox to version 28. I noticed that the "Character Encoding for Legacy Content" option no longer has an option for UTF-8, which is what I had previously set it to. I would like to set this to UTF-8 but cannot find an associated option in about:config.

I would like this option to be restored.

All Replies (11)

more options

This setting is only meant for 8 bit encodings that are locale dependent.
The intl.charset.default pref is removed and intl.charset.fallback.override is now being used.


  • bug 910192 - Get rid of intl.charset.default as a localizable pref and deduce the fallback from the locale

Please do not comment in bug reports

more options

This was an intentional change to have the fallback encoding for legacy content be determined by the locale of your Firefox.

The old "intl.charset.default" preferences no longer exists.

There is a new preference named "intl.charset.fallback.override" but if you set it to UTF-8, that is ignored. The rationale for this is UTF-8 is not a legacy encoding.

What is the reason for using utf-8 as the fallback encoding for legacy content? Is this for content not delivered from a webserver (so there is no content type header)?

References to the bug tracking system:

About the bug tracking system:

It's generally not helpful to add comments to closed bugs, but you can register on the Bugzilla site and create a new bug making the case for having this option.

more options

It's true that UTF-8 is not a legacy encoding. However, legacy pages are those that do not declare their encoding. While dealing with sites (internal intranet and smaller internet) that do not declare an encoding, I want to assume UTF-8.

This gives me the option of notifying the authors that their pages/sites don't specify the encoding as they should. I want to see many occurrences of U+FFFD REPLACEMENT CHARACTER instead of junk in an inferred legacy encoding.

Okulungisiwe ngu mruffalo

more options

Sounds like time to file a new bug.

As a temporary workaround, maybe there's an extension which lets you override Firefox's normal encoding selection. (Unfortunately, a page reload might be required.)

more options

Thank you -- I think I'll file a new bug for this as per your suggestion.

I posted comments to the two bugs that you linked in your earlier message, but I don't think I was as constructive or respectful as I should have been with the tone of my messages. I was quite unhappy upon finding this change in Firefox 28 and shouldn't take it out on Mozilla developers who mean well.

more options

I have the same problem:

The pages served on intranet do not declare their encoding. With setting UTF-8 this was not a problem. Now, text is completely garbled. This is especially painful as we're working in a mixed language/script environment.

more options

Hi DKARSEM, I haven't looked up the bug to see what is planned for this issue.

Hopefully you can fix this in your intranet software. It could be as simple as one global change in your web server configuration. Usually your web server will announce its identity in the Response headers. To view those, open Firefox's web console (Mac: Command+Alt+k, Windows: Ctrl+Shift+k), load a page on your intranet, and click one of the links in the console to view the headers. With that knowledge, you probably can find the steps for your internal webmaster to set the default character set so that individual applications and pages do not need to be updated.

more options

Actually many web-interfaces of old devices made by english-speaking countries just output utf-8 characters without declaring a charset.

I don't understand why "UTF-8" is ignored in "intl.charset.fallback.override". That is unmeaning and only brings troubles to those developers who need it.

A default "UTF-8" encoding is very convenient for those non-english developers when they just want to do some little tests in a html file.

And most old local websites declared a local encoding for their users without any problems.

Just like google removes "http://" from address bar, which makes copying the domain name from an entire url become much troublesome, a useless small modification may make people choose another product.

more options

Hi wong369, I don't have an answer to the original problem, but you may have noticed that Firefox also removes http:// from the address bar. There is a preference in about:config to bring it back if you prefer (I prefer): switch browser.urlbar.trimURLs to false.

more options
more options

Thank jscher2000, I have already switched the browser.urlbar.trimURLs preference, and that's why I finally turn back to firefox after using chrome for several years. I mentioned that just because I hoped firefox could keep being customizable .