1436856 - Enable Pontoon for Firefox for FireTV

Status: RESOLVED FIXED

(Localization Infrastructure and Tools :: Administration / Setup, task)

Description

[__oldboek]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20180128191252

Steps to reproduce:

Following the guide at: https://developer.mozilla.org/en-US/docs/Mozilla/Implementing_Pontoon_in_a_Mozilla_website

Project name: Firefox for Fire TV
Repository URL: https://github.com/mozilla-mobile/firefox-tv/
List of requested locales:

    English (U.S.)
    English (U.K.)
    French
    German
    Italian
    Spanish
    Japanese
    Portuguese (Brazil)
    English (India)
    English (Australia)
    Chinese (Simplified)

Comment 1

[Francesco Lodolo [:flod]]

Assigning to Delphine for now. 

I would expect localization to happen in a separate repository like other projects. Isn't that the case?

@Jeff
Please put a name that helps finding you in your prefs ;-)

Comment 2

[Francesco Lodolo [:flod]]

(In reply to Francesco Lodolo [:flod] from comment #1)
> I would expect localization to happen in a separate repository like other
> projects. Isn't that the case?

To clarify.

a) We should have a localization repository, e.g. firefoxtv-l10n (name is up to you, as long as it ends with -l10n), in the mozilla-l10n org. That would be used by Pontoon to store localizations.

Basically the equivalent of https://github.com/mozilla-l10n/focus-android-l10n/

Creation of that repository would be on me, I just need green light on the name.

b) You need to provide the en-US reference file (locales/templates/app.pot), and update all the scripts in the repository to point to this repository (right now they point at focus-android-l10n).

c) You need to provide the list of locales to localize in, checking with Delphine which ones we actually support (en-IN and en-AU are not).

This bug can be fixed (i.e. Pontoon can be enabled) only after these 3 points are done.

Comment 3

[__oldboek]

@flod: Sorry about that! I signed in with Github, surprised it didn't pull my name off of that.

a) firefoxtv-l10n sounds great to me.
b) Where should I put that file initially? Creating a PR to update the scripts now
c) Getting this list now.

Thanks again!

Comment 4

[Francesco Lodolo [:flod]]

(In reply to Jeff Boek from comment #3)
> @flod: Sorry about that! I signed in with Github, surprised it didn't pull
> my name off of that.
> 
> a) firefoxtv-l10n sounds great to me.

https://github.com/mozilla-l10n/firefoxtv-l10n/

> b) Where should I put that file initially?

Likely a PR with the other supported languages, given that we already have localizations.

en-US should be locales/templates/app.pot

Other locales should be locales/XX-XX/app.po

P.S. the repository is up, but Pontoon doesn't have write access here. That's for when we're ready with all the rest.
After that, I also need to reinstate the links in README.md to Pontoon and Webstatus (and add the project there)

Comment 5

[Delphine Lebédel [:delphine - OOO]]

(Also, continuing the conversation that was going on here: https://github.com/mozilla-mobile/firefox-tv/issues/408)

Thanks for setting up the l10n repo Flod!

Here is the list of locales I suggest we enable until the language switcher is in place:
* AMAZON TV LANGUAGE PREFERENCES:

    English (U.S.)
    English (U.K.)
    French
    German
    Italian
    Spanish
    Japanese
    Portuguese (Brazil)
    English (India)
    English (Australia)
    Chinese (Simplified)

* MOZILLA LOCALES AVAILABLE:
    English (en-US)
    English U.K. (en-GB)
    French (fr)
    German (de)
    Italian (it)
    Spanish (es)  --> Note this is our "generic" international Spanish
    Japanese (ja)
    Portuguese from Brazil (pt-BR)
    Simplified Chinese (zh-CN)

So to summarize, we do not have: English (India), English (Australia). We've never had localizers or projects localized in these locales, so I suggest we do not try and recruit for those at this point.

Susheel: are you OK going forwards with this proposed plan? i.e. enabling the Mozilla locales available for now - and adding all the other Mozilla locales available once the locale switcher is enabled?

Comment 6

[:sdaswani]

That sounds great Delphine but to be clear we would use the current English translation for those two other Australia and India?

Comment 7

[Delphine Lebédel [:delphine - OOO]]

That's a good question. Jeff checked on the TV (I just moved, Amazon TV somewhere in a box...) and it seems that right now if one chooses "English (Indian)" it just falls back to our en-US (since we don't have en-GB yet). I can test this further once I find the Amazon TV kit, but I would say that if a user chooses Australia or India English, then it will just use our current English (en-US) version.

Comment 9

[Delphine Lebédel [:delphine - OOO]]

To further complicate things, I'm wondering if it wouldn't make more sense to have India/Australia English fall back to our upcoming British English (en-GB) localization, vs falling back to our en-US one (given history and language).

I have no idea however how that works, and how Amazon TV identifies how to link the locales we distribute to their own language preferences. Maybe worth looking into...

Comment 10

[:sdaswani]

Delphine will en-GB be ready for 2.0? Meaning do we have to look into this for 2.0?

Comment 11

[Francesco Lodolo [:flod]]

(In reply to Delphine Lebédel [:delphine - use Need Info] from comment #5)
>     Spanish (es)  --> Note this is our "generic" international Spanish

Worth noting that we're using es-ES for Focus for Android, and support all other variants. If the long term plan is to have a language switcher, using 'es' could become a problem.

Comment 12

[Delphine Lebédel [:delphine - OOO]]

(In reply to Susheel Daswani from comment #10)
> Delphine will en-GB be ready for 2.0? Meaning do we have to look into this
> for 2.0?

I don't think we've discussed a specific timeline for l10n in 2.0 yet, so I can't really tell. But I suspect that if we enable en-GB for 2.0, then it will get localized on time. I can reach out to the team and make sure they are interested in taking on the project, once we decide on what we're doing in regards to the points below.

I think we basically have three options at the time:
1. we don't do en-GB for 2.0 (we wait for the locale switcher) and it will therefore use the American English (en-US) version
2. we enable en-GB but don't look into mapping it to the Australian and Indian English version on Amazon side. Once we have the locale switcher we won't really care about that
3. we enable en-GB for 2.0 and figure out how to make it correspond to the Australian and Indian English

I guess that decision is more of a product call.

Comment 13

[:sdaswani]

In my opinion Option 1 is acceptable and lowest cost. Up to Barbara though.

Comment 14

[Delphine Lebédel [:delphine - OOO]]

(In reply to Francesco Lodolo [:flod] from comment #11)
> (In reply to Delphine Lebédel [:delphine - use Need Info] from comment #5)
> >     Spanish (es)  --> Note this is our "generic" international Spanish
> 
> Worth noting that we're using es-ES for Focus for Android, and support all
> other variants. If the long term plan is to have a language switcher, using
> 'es' could become a problem.

Forgot to answer this part. Thanks for catching this flod, you're right!
Let's make sure we use es-ES for this, then.

Comment 15

[Barbara Bermes [:barbara] - NI please!]

Let's work iterative and with the lowest cost, so option 1 seems reasonable for now.

Comment 16

[Delphine Lebédel [:delphine - OOO]]

Thanks Barbara! we'll continue working through this then.

Comment 17

[Delphine Lebédel [:delphine - OOO]]

Project enabled on Pontoon here: https://pontoon.mozilla.org/projects/firefox-for-fire-tv/
Thanks Flod and Jeff for your help with all this!