Fenix: [Bug] Firefox displays British English when the language of the device is set to English (Philippines)

Created on 25 Oct 2020  ·  5Comments  ·  Source: mozilla-mobile/fenix

Steps to reproduce

  1. Go to the Settings app of the phone.
  2. Set the device language to English (Philippines).

Expected behavior

Firefox should show American English instead of British English as we use American English here.

Actual behavior

It shows the British English as the language as the "z" on words like customize are replaced with "s".

Device information

  • Android device: Samsung Galaxy S9+ (Android 10, Build G965FXXSBETH2)
  • Fenix version: 82.0.0-beta.6
🌐 L10N 🐞 bug

All 5 comments

That’s reasonable to fix, Philippines have been ruled by Spain, then grabbed by the United States after the American-Spanish War (and by Japan during the WWII), finally gained independence one year after the WWII, so Philippines have heavily American influences, and they should perfering American English.

@Delphine do you know how our locale matching works?

Gecko can work with fallback chains, so if the user declares [en-PH, en-US, en-GB] then the chain will go from English (Philippines) to English (USA), not English (GB) first.

The question then is whether that's what Android is feeding to Fenix.

Older Androids only allow the user to set one locale, without any fallbacks, but newer Androids allow user to set a fallback locales in their preferred order.

@Burgercat can you verify which Android version are you on, and whether you were able to set fallback locales or just a single locale?

I am currently using Android 10 with the One UI skin. I am able to add other locales on the settings app. But currently, I use only a single locale which is English (Philippines).

This issue is marked as Won't fix here: https://issuetracker.google.com/issues/64429534.
All English locales (except US and US territories) fallback to British English for Android SDK versions 24+.

IMO handling this with a hack in the code will introduce more instability to an already "fragile" Locale API.
The only other fix I can think of would be importing the locale for Philippine English (either properly localized or just as a copy of the American English file).

Was this page helpful?
0 / 5 - 0 ratings