Once the strings in /browser/metro are reviewed and stable, we should back out bug 844068 and let localization of the Metro UI begin. We've just finished reviewing our strings, and have finished nearly all of our planned string changes. The only planned change I'm aware of to existing strings is replacing the download manager with a download bar (bug 831942). We should probably wait for that change to land, then turn localization back on. (Of course we will continue to add new strings as we add features, and existing strings might occasionally change here or there, but hopefully no more than in other parts of mozilla-central.) Note to localizers: We disabled the Metro UI on for Aurora 21, and plan to disable it again for Aurora 22. We will not enable Metro Firefox on our release branches until its feature-completeness and quality are at the appropriate level for each branch. I'll make sure the l10n community is aware as early as possible of any plans to enable Metro on Aurora or any additional branches. I'll also try to prioritize changes like bug 831942 so that we can turn on localization as soon as possible and give you as much time as possible to start translating strings on mozilla-central.

(In reply to Matt Brubeck (:mbrubeck) from comment #0) > Of course we will continue to add new strings as we > add features, and existing strings might occasionally change here or there, > but hopefully no more than in other parts of mozilla-central.) That's supposed to happen. Just keep in mind that, once a string has landed on mozilla-central, if you want to change it you need to use a new ID for that entity, unless you're just fixing a typo or similar. > I'll also try to prioritize changes like bug 831942 so > that we can turn on localization as soon as possible and give you as much > time as possible to start translating strings on mozilla-central. Thanks ;-) The longer you leave Metro UI enabled on central, the easier is to catch problems before they move to Aurora and require to break the string freeze. >We've just finished reviewing our strings, and have finished nearly all of our planned string changes. Some of the questions I asked in bug 840888 are still unanswered. For example do you really need all those empty accesskeys in passwordmgr.properties?

I don't think we should switch on l10n of metro until we expect to switch it on in aurora. The reason being is that for those teams working on central, the infrastructure on aurora is going to bitch about strings they should remove.

Also as long as we hard-code accesskeys in Metro localizers will not be able to localize the keyboard shortcuts as known in their locale for Firefox desktop. See bug 882074.

We expect to enable Metro Firefox in Aurora and Beta for Firefox 26 (or Firefox 27 if we miss that deadline for some reason). I would like to re-enable localization on mozilla-central early in the Firefox 26 cycle (i.e. very soon). I'll also prioritize bug 882074 and any other bugs that are important for localization. Any comments/objections?

Backs out bug 844068.

Comment on attachment 790771 [details] [diff] [review] patch Review of attachment 790771 [details] [diff] [review]: ----------------------------------------------------------------- This looks good technically. Asking flod for feedback on the content this will switch on, are there any unknown left overs?

Comment on attachment 790771 [details] [diff] [review] patch Review of attachment 790771 [details] [diff] [review]: ----------------------------------------------------------------- The only one that I'm aware of is bug 882074, but it's almost fixed.

Thanks! Looking forward to more feedback from the l10n community once this is on central and later aurora. https://hg.mozilla.org/integration/fx-team/rev/7c4e4b3afb0d

Could anyone please give any guidelines that can help the QA in verifying this issue? Thanks!

(In reply to Manuela Muntean [:Manuela] [QA] from comment #10) > Could anyone please give any guidelines that can help the QA in verifying > this issue? Thanks! This change mainly affects localizers; it is not visible in the English-language build. Depending on whether any localizers have finished translating Metro strings on mozilla-central, you may be able to test their work using the builds here (perhaps the ".it" build?): http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central-l10n/

"it" is completely localized, usually updated with missing strings in 24/48 hours, so it's definitely good for testing. De, fr and es-ES are generally in good shape too.

Verified as fixed for iteration #14, with the "it" build from: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013/09/2013-09-18-03-02-02-mozilla-central-l10n/ , build ID: 20130918030202. Italian Metro seems to work properly.