Relaxing the Thunderbird stable branch checkin rules for l10n changes?
[X-Post and F'up 2 set to mozilla.dev.planning]
Right now, every change in a translation of TB2 needs a separate bug
report and a specific approval from the relevant l10n coordinator. In the
past that was Axel Hecht, now it's me as I have taken over as TB l10n
coordinator. The reason for this rule was probably that the same rule
existed for Firefox l10n so it was applied to Thunderbird as well.
The underlying reason was, as Axel told me, that in the past people did
check in broken stuff, which borked their localization.
In my opinion, this mostly applies to Firefo...[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 Owner Sign Offs for Thunderbird 2
Now that the we've passed the localization deadline for Thunderbird 2, it's time to build a list of all of the locales that are ready to be released.
Can the l10n owners sign off on their locales for Thunderbird 2?
I've started a wiki page here:
Release will use the locales listed on that page.
Content-Type: text/plain; charset=ISO-8859-15
Is there any particular tests you'd like us to do?
Qui, ...l10n change in Aviary Branch (Firefox 1.0)
The new plugin finder service had a non-localizable string that was
brought to my attention today. I just checked in the patch to fix this
and am giving an heads up :)
Another localization change was made - bug 260803
Doron Rosenberg wrote:
> The new plugin finder service had a non-localizable string that was
> brought to my attention today. I just checked in the patch to fix this
> and am giving an heads up :)
Doron Rose...Landing l10n-impact security fixes on stable branches
we had the problem once or twice already, and we'll have it again.
We come up with a security problem, or a regression, and it needs an
error message or a tiny tad of UI.
As much as we hate it, it happens.
So, one way of solving this is to just not "fix" those bugs, like, to
silently fail on those errors. I'm not really fond of this, the user
experience would suffer.
The next way is to hard-code the en-US strings. Would anybody like that?
The way I'd suggest is to create the en-US patch as one would on trunk,
with minimal UI impact of cou...Sign off last l10n changes for Firefox 4.0
Recently I checked spelling of Belarusian localization and pushed the corrections to l10n-central.
I wanted to sign off them to Firefox 4.0, but unexpectedly I found the Firefox 4.0 and Firefox 4.0 Mobile trees are closed now.
Is there any chance to sign off the changes?
With best regards,
I'll open sign-offs again soon. Right now, I keep them closed to not
confuse people about the likelyhood of that shipping.
We're shipping the RC3 bits tomorrow, by all chances.
You changes should come to users in a .x release, though.
On 20.03.11 ...Re: Landing l10n-impact security fixes on stable branches
> So, one way of solving this is to just
> not "fix" those bugs, like, to
> silently fail on those errors. I'm not
> really fond of this, the user
> experience would suffer.
Another solution would be to try and come up with a set of generic-enough warning and error statements such that any locale that doesn't submit a translated string by the deadline for the update will be modified to use one of these generic error messages. Then a subsequent update can change to the translated string.
Technically, this could even be accomplished with some sort of...[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...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....18.104.22.168 and other no-l10n-impact releases and sign-offs
there has been a general consensus that the sign-off process we were
following on the 1.0.x branch was a bit wasteful and time-intensive.
I was internally proposing something more streamlined for releases
without l10n impact, and that is, that we drop the sign-off requirement
for those releases and just go for a QA commitment. This includes that
l10n-teams and their communities feel invited to the regular Firefox QA
testing days (next one will be tomorrow).
I want to ping you on this, and though this is on short notice, I guess
we'll go for it, unless you raise...RE: 22.214.171.124 and other no-l10n-impact releases and sign-offs
I checked the tinderbox for Mozilla1.8-l10n-zh-CN and found there are =
some string changes but for Mozilla1.8.0-l10n-zh-CN no change.
Will Mozilla1.8-l10n-zh-CN be used for any release ? Or just =
Mozilla1.8.0-l10n-zh-CN is used for next 1.5.0.x releases?
From: email@example.com =
[mailto:firstname.lastname@example.org] On Behalf Of Axel Hecht
Sent: 2006=C4=EA1=D4=C226=C8=D5 1:54
Subject: Re: 126.96.36.199 and other no-l10n-impact releases and sign-offs
as there is no...l10n.m.o update: cancel sign-offs, and Locale:ab-CD bugs on your team page
I just pushed a few enhancements to l10n.m.o:
Bugs that have your locale as Locale flag are now shown on your team
page and the l10n.mozilla.org/bugs overview
That's mostly bugs on mozilla.org. You used to have to rely on the
webdashboard to be notified on those, and you can still keep on doing
that. But they're now also shown on the bug list for your Localization.
You can now cancel a sign-off. If you clicked on the sign-off link by
accident, or find out by testing that you really shouldn't have this
exposed to users, yo...[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...[SeaMonkey] Important L10n change without string ID change
Hi fellow localizers,
I just checked in bug 517596 to SeaMonkey, which changes URLs in
localized prefs from a .org to a .com URL with the effect of not
breaking with a certificate warning any more when trying to download
more themes or dictionaries from the relevant menus in the application.
As the ID is the pref name for such localized prefs, we can't change the
ID, but all SeaMonkey localizations need to look into this!
Fortunately we have just RCs upcoming as the next checkpoint, we'll
check for this on the changesets you opt in with - note that we don't