Firefox 4 beta 2 will code freeze on July 19, 2010 (11:59 PM PDT). We
invite all localizers to participate, even though on short notice. We
will need to get your sign off on an "l10n-merged" build by mid-day
Monday PDT. We will ship localized betas using the l10n-merge tool from
mozilla-central, with your localizations on l10n-central. Firefox 4
beta 2 will release on July 22, 2010. Some website l10n (First Run,
Download, Feedback page) will also accompany this work.
If your team has not started working on l10n-central, you will certainly
want to read the details below. If your team has started, there is still
good information about exactly what is happening for this beta.
Since our Firefox 4 beta outreach session at the Mozilla summit, we have
had a chance to discuss with the Firefox product release team to
understand the upcoming release l10n strategy. The dev team is not eager
to branch because there are major platform enhancements that need to
land like electrolysis and layers. We will eventually branch to a
"Mozilla 2.0", but not before the end of July 2010. As you can see, we
will have to change the actual Mercurial repositories in order to ship
Firefox 4, but for now l10n-central is the temporary home for Firefox 4
work. You'll have enough time to get into Firefox 4 if you wait for
those details to settle. For now, we're just opening up the beta to the
teams that are fine with yet another repository.
Until then, we will use Axel's l10n-merge code to ship directly from
Mozilla Central. This tool will replace any untranslated strings on
Mozilla Central with English at build time. We will not have a real
string freeze for the betas.
You will need to sign off on your l10n work via the normal sign off
process. Get as much done as you can. When you are ready, you may sign
off on your locale by following this link:
We will definitely review search and other productization, we haven't
yet finalized on criteria on l10n coverage to be part of beta.
Throughout the beta process, we will continue to run l10-merge until
product string freeze.
Other last minute work to consider:
Pascal will be filing bugs to get the First Run and Download pages
localized. Laura Mesa and her team will work on finishing the feedback
website that people will see from the XPI.
Not right now. I did file
https://bugzilla.mozilla.org/show_bug.cgi?id=576234, but talking to
beltzner he said that it wasn't easy, as the code does special UI tricks
depending on whether it's running in a beta build or not. We're still
Which hg commands could I use to copy my 1.9.2 commits to
l10n-central? I remember you made something like this for Firefox 3.6,
it was a time saver.
It depends on what state you're in. It wasn't really a time saver for me
back then, fwiw, thus my attempt to get a good deal of locales onto the
2.0 branch directly from 1.9.2.
*If* you're lucky and didn't work on l10n-central at all, a
hg pull -r default http://hg.mozilla.org/releases/l10n-mozilla-1.9.2/...
can do the trick, and if you landed something, you might be able to
easily merge the two.
If not, there's no easy way.
Thanks, it worked! :)
>>> remote: added 33 changesets with 214 changes to 164 files
BTW, do you recommend hg transplant?
There are various locale/en-US directories in mozilla-central. Which
ones should be translated?
$ find -name en-US
Whatever compare-locales says,
https://developer.mozilla.org/En/Compare-locales, i.e., that's subject
At this point in time, extensions/reporter, browser, dom, toolkit,
other-licenses/branding/firefox, security/manager, netwerk.
services/sync is gonna come soon, you could start with that, even though
it's not yet switched on in the builds.
So basically the same directories as 1.9.3 with keeping in mind that
compare-locales may add sth in the near future, so it should be kept
Right, assuming the 1.9.3 is actually a 1.9.2 ;-)
This is a rather unorthodox answer, but the easiest - and correct for
sure - is to localize the contents of the en_US.jar in chrome. Of
course you need to stick the contents back where they belong in
locales. The localized jar can be used to test the localization
without doing the repository & nightly build loop. I am not sure if
you can simply replace the en_US.jar. I do know it works on localized
That's not a good suggestion, and we're making no attempt whatsoever to
keep this working, even to the extent that is may right now.
thanks to all that made it, we're at 18 locales now, that's pretty great
for such a short timeframe and a moving target.
I guess that more tried and didn't make it, I'm sorry for that, you'll
be in good shape for B3, though.
Keep your sign-offs coming, too. I'm not sure if we'll cancel them for
B3, that will depend on what's landing in the meantime. If we do, I'll
open a new thread here in the group.
For those that did make it into B2, please focus the attention of your
community to the webpages for B2? In particular, we'd like to see you
have the firstrun page translated, and the feedback page once it's out
there. Pascal is working on the latter. (Not to be confused with the
input web app on verbatim, different things.)
Thanks to all of you, on to some user and feedback gathering for fx4
around the globe.
I can't even see them on
BTW, I pushed a changeset that should make Italian green, but the
dashboard doesn't seem to cooperate.
Seems that things settled by now,
shows the posts in this thread allright.
Not sure about the mailing list.
thanks again for jumping in on such short notice, and for continuing to
do so while things were officially closed.
Beta 2 build 1 just went to build, with 23 locales. Great job everyone.
We'll update once the builds are becoming available for non-public
testing, and for public testing.
For the record, compare-locales uses branch's .ini file with list of
directories so there's no need for updating the tool itself. (And yes, I
meant 1.9.2 ;-) )