Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Learn More

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

  • 1 wotmołwa
  • 4 maja tutón problem
  • 2 napohladaj
  • Poslednja wotmołwa wot cor-el

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.

Wšě wotmołwy (1)

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

Wot cor-el změnjeny