528227 - Determine mapping of locales for Maemo multi-locale builds, specifically for nb-NO (Norwegian bokmål)

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect, P1)

Description

[Seth Bindernagel]

We need to make sure that the locale codes in Mozilla's multi-locale build map directly to the Nokia device locale codes.  For instance, "no_NO" (Nokia notation) is a deprecated locale code.  90% of Firefox users use "nb-NO" (Mozilla notation), which is Norwegian bokmål

From the device, the locale codes are the folloowing

/usr/share/locale $ ls */LC_MESSAGES/hildon-common-strings.mo |awk -F / '{print $1;}'
da_DK
de_DE
en_GB
en_US
es_ES
es_MX
fi_FI
fr_CA
fr_FR
it_IT
nl_NL
no_NO
pt_BR
pt_PT
ru_RU
sv_SE

That would yield as base set for maemo-locales 

da
de
es-ES
fr
it
nl
pt-BR
ru

Non-optimal matches are left for
en_GB
es_MX
fi_FI
fr_CA
no_NO
pt_PT
sv_SE

It leaves "lengthy list of other locales" at non-optimal UE. That includes locales that are traditionally high in Firefox, Polish, Japanese, and a good list of locales with "pretty high" (tier 2), cs, es-AR, hu, ko, tr, zh-CN, zh-TW.

Does that list of device locales look right? And what it is on the n900?

Comment 1

[Seth Bindernagel]

I filed this bug by cloning an earlier bug.  The latter half of the initial message may not be as relevant.  I have edited comment #0 here to reflect what I wanted to file.  Sorry.

(In reply to comment #0)
> We need to make sure that the locale codes in Mozilla's multi-locale build map
> directly to the Nokia device locale codes.  For instance, "no_NO" (Nokia
> notation) is a deprecated locale code.  90% of Firefox users use "nb-NO"
> (Mozilla notation), which is Norwegian bokmål
> 
> From the device, the locale codes are the folloowing
> 
> /usr/share/locale $ ls */LC_MESSAGES/hildon-common-strings.mo |awk -F / '{print
> $1;}'
> da_DK
> de_DE
> en_GB
> en_US
> es_ES
> es_MX
> fi_FI
> fr_CA
> fr_FR
> it_IT
> nl_NL
> no_NO
> pt_BR
> pt_PT
> ru_RU
> sv_SE

Comment 2

[Axel Hecht [:Pike]]

Resolving this bug as INCOMPLETE.

We're not going to tweak the mapping of locale codes in any way. Doing so would basically mean that we're undoing matchOS and replacing it with something different, and I don't think that's in scope.

no_NO, if wanted in the multi-locale build is a different bug, and not fennec, but Core-Internationalization.

Comment 3

[Seth Bindernagel]

(In reply to comment #2)
> Resolving this bug as INCOMPLETE.
> 
> We're not going to tweak the mapping of locale codes in any way. Doing so would
> basically mean that we're undoing matchOS and replacing it with something
> different, and I don't think that's in scope.
> 
> no_NO, if wanted in the multi-locale build is a different bug, and not fennec,
> but Core-Internationalization.

Thanks, Axel!  Helpful explanation.  Can you file that bug please?  I'd like to see it on file ASAP so we can solve the no_NO issue.

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

is there a link to the no_NO bug that we can put in here?  I would like to mark this as verified, but want to make sure all loose ends are tied up.

Comment 5

[:Gavin Sharp [email: [e-mail]]]

Joel: bug 533814