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

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Ce sujet de discussion a été archivé. Veuillez poser une nouvelle question si vous avez besoin d’aide.

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

  • 1 réponse
  • 4 ont ce problème
  • 2 vues
  • Dernière réponse par 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.

Toutes les réponses (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

Modifié le par cor-el