Hello. The question is what to serve to users with "pt" as the "Accept-Language" header, if no other value match - should we serve pt-PT content, pt-BR or some default language (like en-US). How is this situation handled for the "en" value?
Cláudio 2015-11-04 14:45 GMT+00:00 Matjaz Horvat <[email protected]>: > Hi Shane, > > I agree simply copying region specific variants to generic ones is a bad > idea. > > The request to serve pt-PT content to pt users came from our pt-PT > community. Adding Cláudio. > > Before we proceed, it would be valuable if we could get data on how many > pt visitors we get in comparison to pt-PT and pt-BR. > > -Matjaž > > On Tue, Nov 3, 2015 at 6:17 PM, Richard Newman <[email protected]> > wrote: > >> 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 platform. >> >> On Tue, Nov 3, 2015 at 7:19 AM, Shane Tomlinson <[email protected]> >> wrote: >> >>> > 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 somewhere. >>> >>> Shane >>> >>> >>> On Tue, Nov 3, 2015 at 3:00 PM, Richard Newman <[email protected]> >>> wrote: >>> >>>> 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 the pt-BR build sends will perhaps (I >>>> haven't checked) be something like >>>> >>>> pt-BR,pt,en-US >>>> >>>> Firefox for Android is very likely to send the OS locale as part of >>>> that, as well as being naturally multilocale. You can try it out with the >>>> app's built-in locale switcher. >>>> >>>> Firefox for iOS is a different matter entirely, and the Accept-Language >>>> header will be based on both locale and region as defined by iOS. >>>> >>>> >>>> >>>> >>>>> John Morrison is concerned that copying from a region specific variant >>>>> to the generic variant is bad practice and is gently nudging us to do >>>>> better. >>>>> >>>> >>>> … but that's true :) >>>> >>>> >>> >> >
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
