Request localization for Firefox Translations utilizing Pontoon
Categories
(Mozilla Localizations :: Other, task)
Tracking
(Not tracked)
People
(Reporter: anatal, Assigned: flod)
Details
- Name of the product, brief description.
Firefox Translations, allows client side page translation for Firefox.
* Where the code lives and what kind of localization format it uses.
https://github.com/mozilla/firefox-translations. We currently don't have any localization implement, and would like guidance on the best approach.
* The desired repository structure.
Separate l10n repository
* Information about locales.
We are targeting: Spanish, German, Bulgarian, French, Polish, Estonian, English, Italian, Portuguese, Russian, Czech, Norwegian, Farsi, Icelandic
* Testing strategy.
We can automatically import newly available content from the pontoon hosted repo daily and then build a public facing XPI utilizing GH Actions so localizers could test it.
* Update frequency, schedule and deadlines.
We expect to release the extension for QA in one month, and to the public and 6-7 weeks, and after that we don't expect new languages to be added for few months.
* Main point of contact for the project.
André Natal
|
Assignee | |
Comment 1•3 years ago
|
||
Thanks for filing the request. I'll reach out next week for the next steps, since I'm out of office until Monday.
Leaving the NI open so it doesn't fall off the radar.
|
|
Assignee | |
Comment 2•3 years ago
|
||
(In reply to André Natal from comment #0)
* Where the code lives and what kind of localization format it uses.https://github.com/mozilla/firefox-translations. We currently don't have any localization implement, and would like guidance on the best approach.
Actually, there is nothing that I can do at the moment.
In order to localize the add-on, strings need to be exposed and not in the code. I don't see any trace of JSON files in the repo?
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Internationalization
You can also find examples around in Mozilla's projects (Facebook Container, Firefox Relay, Multi-Accounts Container). Unfortunately my team can't help with that part of the work.
Once strings are extracted, we'll need to review them to make sure they're clear, and then start the actual process.
|
Reporter | |
Comment 3•3 years ago
|
||
That's what I meant by guidance. I didn't know how to we should extract that and the actual format. Thanks for pointing out, I'll make sure we have those next week.
Hey Flod. We have updated the extension to provide the strings. They are in extension/_locales folder. The English strings are in en folder.
We have followed the documentation in https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Internationalization. But, if we still missed something that blocks this task from moving forward then please feel free to let us know and we will make those changes asap (adding NI just for this reason).
Thanks again.
|
|
Assignee | |
Comment 5•3 years ago
|
||
A few notes on the locales:
- Please remove the other folders and only keep
en(which should probably be renamed toen-US?). Those will be created as part of the translation process. - Locale codes don't match the ones we use internally at Mozilla, and there are a few that are unclear.
es-> Do we want this to bees-ES, or more variants?pt-> We differentiatept-PTandpt-BR, which one would you need?
I left a few comments in the PR introducing the English file.
|
|
Reporter | |
Comment 6•3 years ago
|
||
:flod is there a reference document where we can find the locale codes used internally at Mozilla so we could provide you with the list we are intending to use?
|
|
Assignee | |
Comment 7•3 years ago
|
||
In this specific case we want the same locale codes that we use in Firefox, so this is a good start (ignore ja-JP-mac)
https://hg.mozilla.org/mozilla-central/file/tip/browser/locales/all-locales
You can also see the locale codes enabled in Pontoon here
https://pontoon.mozilla.org/teams/
|
|
Assignee | |
Comment 8•3 years ago
|
||
I've opened a pull request to fix a few more things in the source file
https://github.com/mozilla/firefox-translations/pull/120/files
See also the note about adding me as a contributor to the repo, no need for write access.
Translations will live here. There's already Italian, so you can verify that everything works and start thinking about the import process
https://github.com/mozilla-l10n/firefox-translations-l10n/
Ideally, we should have at least one import+build a day for localizers to test. Once that's set up, I can add more languages and make the project in Pontoon public.
One important note on "Firefox Translations" (translate it or not). You mentioned that there's no product support at the moment, but this is one of the choices that we need to make once, and then enforce. Changing our minds later is going to create problems.
|
|
Assignee | |
Comment 9•3 years ago
|
||
(In reply to André Natal from comment #0)
We are targeting: Spanish, German, Bulgarian, French, Polish, Estonian, English, Italian, Portuguese, Russian, Czech, Norwegian, Farsi, Icelandic
This would be my list, based on the languages listed here.
bg
cs
de
en-CA
en-GB
es-AR
es-CL
es-ES
es-MX
et
fa
fr
is
it
nb-NO
nn-NO
pl
pt-BR
ru
|
|
Reporter | |
Comment 10•3 years ago
•
|
||
Hi Flod, this list looks reasonable for us. We can start with that. Thanks for narrowing it up. Is there anything else we need to do to have the project set on pontoon to start receiving contributions?
|
|
Assignee | |
Comment 11•3 years ago
|
||
I plan to open it up on Monday.
I think we still need to clarify the testing instructions (add-on disabled when you restart the browser), but the rest should be OK.
|
|
Assignee | |
Comment 12•3 years ago
|
||
Added pt-PT to the list above.
https://pontoon.mozilla.org/projects/firefox-translations-add-on/
Description
•