L10n:Firefox in 2016: Difference between revisions

(→‎For Developers: rephrase recent nightly strings)
Line 6: Line 6:


== Engineering Changes ==
== Engineering Changes ==
Jumping right in to it.
Jumping right in to it. As everybodies head is wired slightly differently, here are three ways to look at it:


All English strings that we ship to any release channel are in the hg repository for aurora and central.
An English string exposed for l10n begins its life cycle in mozilla-central, and lives and dies until it merges to Aurora. At that point, it's frozen until the end of its lifetime, which comes when we stop shipping any version that has a code path using that string. As long as code on any of aurora/beta/release/esr use a particular string, it can't be removed.
 
''Or, in sets:''
 
All English strings that we use in any shipping version (aside Nightly)  on any release channel are in the hg repository for aurora and central.


* A string in ESR is also in aurora and central.
* A string in ESR is also in aurora and central.
Line 16: Line 20:


In reverse,
In reverse,
* central has all the strings from central, aurora, beta, release, esr;
* central has all the en-US strings from central, aurora, beta, release, esr;
* aurora has all the strings from aurora, beta, release, esr;
* aurora has all the en-US strings from aurora, beta, release, esr;
* beta has all the strings from beta, release;
* beta has all the en-US strings from beta, release;
* release has all the strings from release;
* release has all the en-US strings from release;
* esr has all the strings from esr.
* esr has all the en-US strings from esr.


''What do we win?''
''What do we win?''
Line 34: Line 38:


=== For Localizers ===
=== For Localizers ===
Localizers will work on one repository, with compare-locales giving results against ESR, release, beta, and aurora. Instead of landing strings in different repositories, the l10n work lands in one repository, with the different en-US repos giving information about the urgency of the strings in question.
Localizers will work on one repository per locale, with compare-locales giving results against ESR, release, beta, and aurora. Instead of landing strings in different repositories, the l10n work lands in one repository, with the different en-US repos giving information about the urgency of the strings in question.


== Localization Tool Changes ==
== Localization Tool Changes ==
Confirmed users, Bureaucrats and Sysops emeriti
2,976

edits