Fetch Firefox locales from l10n-central

We should switch to packaged locales.

It seems they fix the branding problems we have with language-packs (see tor-browser#41293 (closed)).

Additional information are also in comments of tor-browser#17400 (closed).

marked this issue as related to tor-browser#40612 (closed)

mentioned in issue tor-browser#17400 (closed)

I can do the part about fetching from hg the revisions listed in browser/locales/l10n-changesets.json.

The previous comments about this are in tor-browser#17400 (comment 2836300).

That'd be great, thanks!

I can help with the Firefox build part, if needed.

I've already managed to do so locally, basically we need to add the few steps listed here, hoping we can without having the mercurial data - I haven't tried that yet.

marked this issue as related to tor-browser#41293 (closed)

added Localization Next Sponsor 131 labels

added Task label

changed milestone to %Sponsor 131 - Phase 3 - Major ESR 102 Migration

marked this issue as related to tor-browser#17400 (closed)

marked this issue as related to tor-browser#41370 (closed)

mentioned in issue tor-browser#41370 (closed)

removed Next label

added Backlog label

mentioned in issue tpo/tpa/team#40953 (closed)

We are currently missing mercurial on the tb-build-* machines. I opened tpo/tpa/team#40953 (closed) to fix that.

assigned to @boklm

added Doing label

marked this issue as related to rbm#40047 (closed)

mentioned in issue rbm#40048 (closed)

marked this issue as related to rbm#40048 (closed)

mentioned in merge request rbm!42 (merged)

mentioned in merge request !572 (merged)

@intrigeri after this (possibly merged for Tor Browser 12.0a5) we won't use langpacks for Tor Browser anymore (and so we won't publish them anymore).

Does this affect Tails in any way?

@intrigeri after this (possibly merged for Tor Browser 12.0a5) we won't use langpacks for Tor Browser anymore (and so we won't publish them anymore).

Does this affect Tails in any way?

We currently use the langpack-$LOCALE@firefox.mozilla.org.xpi langpacks that are included in Tor Browser multi-lingual tarball.

When we start or Browser, we set intl.locale.requested based on the system locale chosen by the user, depending on which such XPI is available.

I suppose we can adjust to something else. What matters to us is the ability to:

1. Tell which locale is supported by Tor Browser
2. Set the Tor Browser locale depending on the system locale

This being said, if multi-lingual Tor Browser magically did that guesswork itself, I guess we would simply drop all that custom code and enjoy.

When we start or Browser, we set intl.locale.requested based on the system locale chosen by the user, depending on which such XPI is available.

Yes, we set it empty and Firefox should do some magic

Tell which locale is supported by Tor Browser

This might become a little bit more difficult. We keep the list in rbm.conf, otherwise you can find the languages we support in omni.ja.

Set the Tor Browser locale depending on the system locale

This being said, if multi-lingual Tor Browser magically did that guesswork itself, I guess we would simply drop all that custom code and enjoy.

This is what we'd like to have, too .

OK, great!

If it's not too much of a hassle, could you please ping me once a nightly build that includes these changes is available?

Thanks in advance :)

@intrigeri I think we will have one in the next days.

Nightly builds often take a pair of days now .

However, I already have a testbuild that is basically the same as a nightly with these changes, and that should have also the branding problems solved.

marked this issue as related to #40668 (closed)

mentioned in issue tor-browser#41378 (closed)

mentioned in merge request !576 (merged)

removed Backlog label

removed Doing label

Merged with !572 (merged) and with !576 (merged).

closed

marked this issue as related to tor-browser#41435 (closed)

marked this issue as related to #40685 (closed)

marked this issue as related to #40687 (closed)