Mass-landing of accessible video controls to happen on Thursday, 6 AM UTC
Staś Małolepszy
SHORT VERSION: there will be a mass-landing to all locales' repositories
on Thursday, around 6 AM UTC. Please use |hg pull -u| more often than
usually.
LONG VERSION:
In his recent message to this newsgroup, Seth mentioned 6 strings to
translate for RC1, plus 5 additional ones that had not yet landed. And
they still haven't, but hopefully will land soon, once all necessary
reviews and approvals are granted.
These 5 strings are all in one *new* file:
/toolkit/chrome/global/videocontrols.dtd
They have been added by these two bugs:
* Bug 489549: Buttons of HTML5 audio and video element control set have
no accessible names https://bugzilla.mozilla.org/show_bug.cgi?id=489549
* Bug 490287: Slider of audio/video element hasn't accessible name
https://bugzilla.mozilla.org/show_bug.cgi?id=490287
The file looks something like this:
<!ENTITY playButton.playLabel "Play">
<!ENTITY playButton.pauseLabel "Pause">
<!ENTITY muteButton.muteLabel "Mute">
<!ENTITY muteButton.unmuteLabel "Unmute">
<!--
Localization note: the #1 string is the current media position, and the
#2 string is the total duration. For example, when at the 5 minute mark
in a 6 hour long video, #1 would be "5:00" and #2 would be "6:00:00",
result string would be "5:00 of 6:00:00 elapsed".
-->
<!ENTITY scrubberScale.nameFormat "#1 of #2 elapsed">
The good news is that play/pause/mute/unmute already exist in
/browser/chrome/browser/browser.dtd, so they don't require coming up
with new translations. And because this is happening all in a separate
file, we thought it would be a good idea to mass-land this file for all
locales. Our rationale is this: the risk of a conflict is minimal and
even if someone forgets to hg pull -u after the mass-landing, the merge
shouldn't cause any problems (because this is a new file). Mass-landing
should spare you the trouble of copying&pasting those 4 translations. We
can make it en masse with scripts (yay, silme!), which should be easier
for everybody.
As for scrubberScale.nameFormat, the string hasn't landed yet even on
central, but we will use this occasion and land it as well in this file
(in English) for all locales. Please translate it before the code
freeze. It's the 7th string to translate in this update.
Since videocontrols.dtd hasn't yet landed on 1.9.1, for some time it
will be reported as "obsolete" by compare-locales, but after the landing
on en-US, it will make the l10n builds not break. Which is probably a
good thing :)
This is a heads-up message to announce the mass-landing that will happen
in approximately 2 hours, at 6 AM UTC. Thanks for reading.
Best,
Staś
--
Staś Małolepszy
Mozilla L10n driver
+48 600462291
+33 643800452
Staś Małolepszy
> Hi all,
>
> SHORT VERSION: there will be a mass-landing to all locales' repositories
> on Thursday, around 6 AM UTC. Please use |hg pull -u| more often than
> usually.
Working on it right now... Stay tuned.
-stas
Staś Małolepszy
> Staś Małolepszy wrote:
>> Hi all,
>>
>> SHORT VERSION: there will be a mass-landing to all locales' repositories
>> on Thursday, around 6 AM UTC. Please use |hg pull -u| more often than
>> usually.
>
> Working on it right now... Stay tuned.
The mass-landing is over. Please |hg pull -u| in your locale clone.
For some time the l10n dashboard might report an obsolete file
(/toolkit/chrome/global/videocontrols.dtd). Please just ignore this for
now. The English strings will land on en-US soon (reviews already
granted, awaiting approvals) and when they do, dashboard will be happy
about this file already being in your repository :) Please remember to
translate the one additional string in this file:
<!ENTITY scrubberScale.nameFormat "#1 of #2 elapsed">
Please let me know if you have comments, questions or issues with hg.
I'll be happy to answer them or help.
Take care,
Stas
Mad Maks
greetings MM
Axel Hecht
I don't think we should do the mass landing on central. The policy on
who's doing what why when there differs too much between the different
locales.
If you have a working mozilla-central, your repos will have diverged in
their changeset history anyway by now, in particular for those that have
fennec landed, so you could just import stas' landing on 1.9.1 into your
central repo, and push. In case of nl, that would be
hg import
http://hg.mozilla.org/releases/l10n-mozilla-1.9.1/nl/raw-rev/083ce5d8e8a4
Note, this url is the "raw" diff, so if you go to the web interface, go
to the changeset (which has /rev/ in its url) and use the "raw" link
there. Or just edit /rev/ to /raw-rev/.
On a related note, fennec is eventually going to move to 1.9.1, too, but
there are still a few more bugs outstanding until we get that up.
Axel
Mad Maks
OK thanks