L10n:Bugogram: Difference between revisions

875 bytes removed ,  5 November 2019
no edit summary
No edit summary
Line 64: Line 64:


We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s
We also need to initialize the repository with content from this external repository https://bitbucket.org/mozilla-l10n/%(loc)s
Please make sure that dxr is updated to pick up the new repository.


PS: to be clear to the localization team, this bug is handled by Mozilla staff.
PS: to be clear to the localization team, this bug is handled by Mozilla staff.
Line 78: Line 76:


PS: to be clear to the localization team, this bug is handled by Mozilla staff.
PS: to be clear to the localization team, this bug is handled by Mozilla staff.
== product-details ==
; short_desc : Add '%(loc)s' to product-details
; product : Release Engineering
; component : Ship It
; blocked : fx-l10n-%(loc)s
; cc : l10n@mozilla.com,francesco.lodolo@gmail.com
We need to add '%(loc)s' to the Firefox Nightly l10n builds on mozilla.org:
* Locale needs to be added to the list of supported Nightly locales.
* If missing, add an entry in languages.json with both the English and localized name for this locale.
P.S. To be clear to the localization team, this bug is handled by Mozilla staff.


== Webservices ==
== Webservices ==
Line 114: Line 100:


Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.
Once we have a specification on what the search engines for %(language)s should look like, flod and the localization team will work on an implementation on that. flod will create and attach patches for the desired changes and get them reviewed. After a successful review, flod will land them. %(name)s, if you're interested, you could create the patches, too. You'd ask flod for review on those before landing.
Please don't commit any modifications in browser/searchplugins to the hg repository without a patch reviewed by flod, Stas, Axel or someone else appointed by flod. The data here is sensitive to users and our search partners, thus requiring extra care here.


The %(language)s team and flod will be driving this bug to completion.
The %(language)s team and flod will be driving this bug to completion.
Line 144: Line 128:
; blocked : fx-l10n-%(loc)s
; blocked : fx-l10n-%(loc)s


flod, Peiying, please add web pages to this locale's folder on mozilla.org.
Peiying, please add web pages to this locale's folder on mozilla.org.


Please notify in the actual translation bug when this is done.
Please notify in the actual translation bug when this is done.
Line 157: Line 141:
To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages.  
To release Firefox in %(language)s, we need a way to promote it. We do that via https://www.mozilla.org/firefox/ web pages.  


flod or Peying will follow up here when the initial setup work is done. After that, files will be added to GitHub, and will be available for localization in Pontoon at https://pontoon.mozilla.org/%(loc)s/mozillaorg/
Peying will follow up here when the initial setup work is done. After that, files will be added to GitHub, and will be available for localization in Pontoon at https://pontoon.mozilla.org/%(loc)s/mozillaorg/


All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.
All the translations you do will be available on the testing website, http://www-dev.allizom.org/%(loc)s/ , around 15-30 minutes after commit.
263

edits