[l10n] l10n process and documentation
As discussed in the last bi-weekly meeting, we at Mozilla Italia are
trying to formalize a process to coordinate the Italian MDN localization
In this regard, we started writing a document that we plan to publish on
the Italian localization of MDN. It has been suggested by jms that we
publish it under https://developer.mozilla.org/it/MDN/ .
Our problem is we have a somewhat cumbersome way of handling the review
process of localized articles. We have a single topic on our forum where
we ask for revision, our QA people suggests corrections and we
localizers correct our transl...[L10N] Few pebbles that grinds l10n-ability
Hello everyone :)
I am currently trying to translate (and update) the JS section as a whole.
Doing this=2C I encounter some problems=2C that I would say are particularl=
linked to l10n (localization).
Some things are going well :) and some other not that much. I would like=20
to discuss the following points:
- Template l10n: I am really grateful for Florian and Jean-Yves to be=20
there to add what's needed in the macro!!! Without them=2C it would be a=20
hard time getting these localized.
- Template l10n-ability: generated ToC are cool=2C auto-next/prev in=20
guides a...merging amo-l10n and l10n.web lists or not ?
We have a general purpose mailing list/newsgroup for general web
localization which is firstname.lastname@example.org
(mozilla.dev.l10n.web on usenet), we also have a mailing-list for AMO
localization only at email@example.com
Given that both lists are low traffic and there is some overlap, do you
think that we should merge them?
I would be particularily interested in knowing what users of both lists
think of it and why we should merge lists or not merge them.
> Hi people,
> We have a general purpose mai...[Calendar l10n] Status update after late-l10n changes
after the late-l10n checkin on Thursday where four strings were added
it's time for another status update.
Here's a short overview of the current situation:
1) The following locales have green tinderboxen on the
MOZILLA_1_8_BRANCH and should be okay for the RC1:
es-ES, fr, ga-IE, ja, ja-JP-mac, lt, mk, nb-NO, nl, pl,
pt-PT, sk, uk, zh-CN
2) The following locales have orange tinderboxen on the
ca, cs, da, de, es-AR, eu, hu, it, ka, pt-BR, ru, tr
3) The following locales have red tinderboxen on the
...l10n for services/sync going on in a few, check your weave-l10n
for those that have localized weave, the files in services/sync should
be the very same as those in services in your weave-l10n repos.
Copy and review should be fair enough.
On 30.07.10 10:08, Axel Hecht wrote:
> for those that have localized weave, the files in services/sync should
> be the very same as those in services in your weave-l10n repos.
> Copy and review should be fair enough.
landed, and PS: For B3, I'm not going to block on the services/sync
strings, but after that, we'll nag :-)
Il 3...l10n-merged linux firefox 3.1 builds on the l10n server
we've talked about it for ages, now we're at a point that I had picked
as a milestone, if I'd really plan on paper.
We have l10n-merged linux builds for all 60 firefox 3.1 localizations
we're currently building on the l10n server, with build on push. You
push a change, it builds, and the build should work.
I didn't go into details like specific branding for merged builds or
More details on
Axel Hecht wrote:
> Hi all,
> we...l10n dashboard defunct, no progress on product l10n, regression from hg update
in case you wonder, the l10n dashboard is not going to pick up any new
data, nor produce any builds, there's a regression from an hg update on
hg.mozilla.org that's breaking the infrastructure.
https://bugzilla.mozilla.org/show_bug.cgi?id=573285 is the culprit.
This basically stops any progress on l10n on any of our hg-based
Thanks to a sunday shift by Aravind, the l10n dashboard is up again.
On 21.06.10 02:08, Axel Hecht wrote:
> in case you wonder, the l10n dashboard is not going to pick up any new
> data, n...l10n-owner approval requested for Firefox 1.0.7 l10n builds
Collect and ship all ready l10n builds for Firefox 1.0.7. Use this bug
as a tracking bug for pending localizations, as well.
1. Test builds found at
2. Build sign offs in this bug should be of the form:
<locale> ready for staging
Example: for cs-CZ:
cs-CZ ready for staging
If the locale isn't ready to ship, then note so by saying:
<locale> not ready fo...Updating l10n-merge in production, switching on l10n-merge in general, all of Firefox, TB, SeaMonkey, whatnot
the version of compare-locales/l10n-merge we use in release production
is rather dated, and we should update. We should also switch on
l10n-merge across the board on all builds. This is a bit of a can of
worms. I'll try to untangle that, but you know me.
Features of the new code:
- catches more errors (yet more in the works right now, thanks android)
- *fixes* more errors by removing bad strings from existing files and
replacing them with en-US
- all release automations (moco, momo, seamonkey) refer to the same
http://hg...FYI: Firefox 1.0 l10n builds now uploading to latest-aviary1.0-l10n
Notice to all --
If you're tracking Firefox 1.0 builds off of the l10n build systems
please turn your attention from latest-0.11-l10n to
latest-aviary1.0-l10n. I've made this change for consistency's sake
with our other build systems and in preparing for future releases. Thanks!
Ysgrifennodd Chase Phillips:
> Notice to all --
> If you're tracking Firefox 1.0 builds off of the l10n build systems please turn your attention from latest-0.11-l10n to
> latest-aviary1.0-l10n. I've made this change for consistency's sake with our ot...FYI: Firefox 1.0 l10n build machines to shift to Firefox 1.0.1 l10n
As a heads up to all l10n contributors who were a part of the Firefox
1.0 release and those who are working to be a part of our 1.0.1 release,
we'll be transitioning our l10n build systems so they generate 1.0.1
builds this weekend. This will conclude our automated builds of Firefox
1.0. When the transition is complete, new nightly builds will begin
If your localization has a released Firefox 1.0, you should not need to
make any changes for the 1.0.1 release. At this time, ...Firefox OS 1.4 branched: 1.4: releases/gaia-l10n/v1_4, 2.0: /gaia-l10n
I've just branched the 1.4 efforts for Firefox OS.
The /gaia-l10n repos you worked on for the past 12 weeks are now aiming
at Firefox OS 2.0, for at least 6 weeks.
Your work and fixes for 1.4 shall go to /releases/gaia-l10n/v1_4/.
I've migrated your work for 1.4 onto those repositories, unless you're
petercg or civas, you guys landed stuff on those repos, you'll figure it
If you've pushed in the past hour, I might not have it.
I'll follow up when I have pushed the update to en-US.
.... and I just pushed 2.0 to /gaia-l10n/en-US....L10n Test day, Thursday, January 20 from 9:00
A gentle reminder, there will be an L10n Firefox 4 Test day this
*Thursday, January 20 from 9:00 - 17:00 (UTC -8)*.
Since most of you are on CET or earlier timezones, this should enable
you to test your Firefox 4 candidates during the evening with the
Mozilla QA team. Please join us on #testday.
For more information, please go here:
> Anthony Hughes <mailto:firstname.lastname@example.org>
> January 14, 2011 10:42 PM...Current status of Thunderbird l10n
My team didn't manage to stay up to date with Thunderbird since version 4,
but we might now be getting back to that.
I tried to look for documentation explaining what the current status is,
how to do things, etc. but currently I'm not even sure when what is
released. Are only long-term releases being made? If yes, do localisations
have an opportunity to enter through bug fix releases every 6 weeks? What
should we aim for right now?
Thank you for anybody that can shed some light on this.