That list is from
intl/locale/language.properties
where we've hard-coded which locales we'll expose for Accept-Language
headers. This is one of the differences between in-product locale and the
web, alas.
The default Accept-Language header will also differ between Gecko/desktop
and each mobile
> Firefox desktop is built for hi-IN, pt-PT, pt-BR. You can grab
single-locale builds for those locales:
If I open about:preferences#content, I can only add `hi` or `pt` under
languages. I see neither hi-IN nor pt-PT.
Perhaps that's an issue with the en-US build, obviously a discrepancy
exists so
>
> Firefox supports neither hi_IN nor pt_PT, only hi and pt.
>
I'm not sure this is a true statement.
Firefox desktop is built for hi-IN, pt-PT, pt-BR. You can grab
single-locale builds for those locales:
http://ftp.mozilla.org/pub/firefox/releases/42.0b9/mac/
The Accept-Language header that
Hi Matjaz, we are looking for a little guidance.
In the fxa-content-server-l10n repo, we currently copy hi_IN to hi and
pt_PT to pt. These region specific variants are maintained whereas the
generic language variant is not. Firefox supports neither hi_IN nor pt_PT,
only hi and pt. John Morrison is
4 matches
Mail list logo
