fallback to english when user locale is not explicitly listed/supported in i18n configuration section

[goncalopolido]

I believe the status page should only display translated content when the user's browser locale matches a locale explicitly defined in the i18n configuration section. If the user’s locale isn’t supported or explicitly listed there, the page should automatically fall back to English.

This approach avoids showing incomplete or inaccurate translations, ensuring a consistent and reliable experience by defaulting to English.

[AnandChowdhary]

What happens currently? :O

[goncalopolido]

What happens currently? :O

What is happening?
Users whose locale doesn’t match pt-PT are still seeing the page in Portuguese, because the site is falling back to the first configured locale in i18n.

What did I do?
I configured the i18n section with only pt-PT as the supported locale.

What is supposed to happen?
Only users whose system/browser locale is set to pt-PT should see the translated content in Portuguese. All other users (e.g., with es, fr, etc.) should see the page in English as a fallback.

And you’re probably thinking:

“Oh, but what if a user has their system or browser set to a language that isn't listed in your i18n config? Then they’ll see the site in English, even though that’s not their language?”

Yes, exactly! That’s the intended behavior. If their language isn’t explicitly supported, they should see English. It’s better to show a complete, intentional English version than to risk showing partial or unrelated translations from a different language.

[goncalopolido]

Keep in mind this is just my opinion on how it should work.