We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

UTF-8 for legacy content no longer exists, how to solve?

  • 1 èsì
  • 4 ní àwọn ìṣòro yìí
  • 2 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ cor-el

Frederick888
Frederick888
more options

Firefox has deleted the selection of UTF-8 for legacy contents in the latest version. Now it's causing the garbled problem when I'm using FTP with file names which contain Japanese or Chinese.

I tried to modify the preference of intl.charset.fallback.override to UTF-8 but it didn't work.

How can I solve the problem? Do I have to go back to Firefox 27?

Thanks.

Firefox has deleted the selection of UTF-8 for legacy contents in the latest version. Now it's causing the garbled problem when I'm using FTP with file names which contain Japanese or Chinese. I tried to modify the preference of intl.charset.fallback.override to UTF-8 but it didn't work. How can I solve the problem? Do I have to go back to Firefox 27? Thanks.

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

See this thread:

  • bug 910192 - Get rid of intl.charset.default as a localizable pref and deduce the fallback from the locale
  • bug 967981 - Provide some way for addons/prefs to control the default fallback character set

Please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html

Ti ṣàtúnṣe nípa cor-el