We need to add support for two languages in Gaia for our launch: Portugues (Br) and Spanish (LatAm neutral).

User Stories L10N-002 and L10N-001

We're marking this bug with the C1 milestone since it follows the criteria of "unfinished feature work" (see https://etherpad.mozilla.org/b2g-convergence-schedule). If this work is not finished by Nov19, this bug will need an exception and will be called out at the upcoming Exec Review.

Leaving it to Staś to close this as RESOLVED/INVALID. The Spanish and Portuguese locales have been removed from the Gaia repo but they are on the Mozilla one in order to make sure they’ll be ready for v1, precisely.

What does Mozilla repo means? We need to have a way to test by default with the languages that are going to be used in the target markets...

To make it clear, there are two ways to solve this issue: • make it easier to build Gaia with locales hosted by the Mozilla l10n team [1] • add [pt-BR] and [es] to the list of the default locales in the github repo [2] As Staś is in charge of this, my opinion doesn’t matter much and I’ll trust him to deploy the best solution to ensure the targeted locales (en-US, pt-BR and es) are ready on time. [1] https://hg.mozilla.org/gaia-l10n [2] https://github.com/mozilla-b2g/gaia

What does B2G C1 milestone really mean here? The deadline for completing the localization work is December 17, so clearly long after November 19. Also, I don't think we actually want to have the localization files in the git repository. Instead, we want to include the desired localization files in the build during the build time. That's the first approach that Kazé outlined above. I'm working on filing specific release engineering bugs to make this happen. I'll update (and probably close) this bug when I'm done.

Any estimation about when this can be tested? Language selection affects to other device parts (e.g. Time Format) in order to test those combinations it would be good to have those languages supported soon. (In reply to Staś Małolepszy :stas from comment #7) > What does B2G C1 milestone really mean here? The deadline for completing > the localization work is December 17, so clearly long after November 19. > > Also, I don't think we actually want to have the localization files in the > git repository. Instead, we want to include the desired localization files > in the build during the build time. That's the first approach that Kazé > outlined above. > > I'm working on filing specific release engineering bugs to make this happen. > I'll update (and probably close) this bug when I'm done.

Note: First Run Experience also needs this.

Stas, can you answer the question in comment #8? Even though the translations aren't done yet, we need to be able to communicate to partners how to get their infrastructure ready for testing them when available.

Sorry, I followed up with Daniel over email, but I'm happy to comment here as well. Bug 817170 is the last fix to the build config that started out as bug 812829. I'm looking for a reviewer for it. Ben and I have tested this fix on releng's build machines and we were able to get working builds for all platforms. When the fix from bug 817170 lands, Ben will turn on multilocale nightly builds. This could happen as soon as tonight, or tomorrow.

This bug should be close since we have support of both languages (and more, if defined on languages.json and cloned) on Gaia. I don't have instructions for enabling Spanish and Portuguese in Gecko, but I know it's landed (I need to ping bhearsum). Ben could confirm if the builds for dogfooders are correct (we do not have access to them).

I don't think the most recently published dogfood build has spanish or portuguese enabled, but the next one should. Does that answer the question?

I just verified that the nightly device builds come with Spanish and Portuguese Gecko localizations enabled. You need to restart the device if you want to change the Gecko locale, but it works.

Appears to be working properly in Unagi build 20130103070201. Spanish and Portuguese can both be selected from the languages menu and appropriate fields are translated. Verifying as fixed.