I'm filing this bug at Jeff's suggestion, but I'm not sure if this is the right approach for my project. I've never done this before, so please tell me if I've made any mistakes :) There are two RSS add-ons that we're planning to feature with the Firefox 30 release, and we would like them to be localized. Right now the add-ons (and the locale files) live in github repos here: * https://github.com/leibovic/world-cup-feed/tree/master/content/locale * https://github.com/leibovic/fennec_rss/tree/master/content/locale Project owner: Margaret Leibovic Length of project (in number of source strings or words): currently 5 strings :) Description of target audience: Firefox for Android users Where the source project will live: currently in a github repo Target locales for first iteration: Firefox for Android locales (ideally, but could be fewer) Rate of adding new locales per quarter: same rate as Firefox of Android Resources available for L10n drivers and localizers (can include personnel): Margaret Identify project's life-cycle: aiming to release add-ons with Firefox 30 release, but maintain them for an undermined length of time afterwards Project's release schedule (URL preferred): same as Firefox 30 Project's target release date: June 10

For a project of this size, we could just ask people to send a pull request? I know that worked in the first few weeks of AMO after their recent migration. Kind-of depends on how many updates the strings will have, too. Alternatively, use translate-tools to convert the strings into a PO file (each?) and let's create a project on verbatim.

I would be fine with pull requests. I don't think there will be many (if any) updates to these strings. I also just realized there is also the issue of localizing the title/descriptions that we put on AMO. I was reading on MDN that you can add localization bits to your install.rdf for this, so I suppose localizers could also make PRs to that file, although I would want to make an example and test that out. There is also the AMO listing itself, which has a more detailed description. I'm not sure how add-ons currently localize those listings, or whether that's even something that AMO supports. So maybe we shouldn't worry about that, at least for now.

What's remaining here? Is it only a matter of announcing the github repo and that it's available for l10n on dev.l10n?

Just wanted to check in here give an update on these add-ons. At this point, the strings are stable and should be ready for localization. I rearranged the directories for these add-ons a bit, and the locale files are now located here: https://github.com/leibovic/world-cup-feed/tree/master/locale https://github.com/leibovic/fennec_rss/tree/master/locale The world cup add-on only has 2 strings, and the generic feed add-on only has 4 strings, so this should hopefully be pretty easy to localize. I think making pull requests on my repos would be the simplest way to add new locales. Should I just make a post to dev.l10n about this?

I am going to take this one.

We are going to expose that project to our web localizers since we are also asking them to translate promos for the worldcup add-on on mozilla.org and about:home. You have a dashboard here with a first set of locales (to refine): http://l10n.mozilla-community.org/webdashboard/?project=worldcup_addons Data is updated automatically (every 15mn). I'll work tomorrow on the export script to properties/rdf for the extensions on Github. I will run the export will provide translations and code updates as pull requests.

The 6 locales requested are done and Pull requests are done too. There is one question for Margaret regarding non breaking spaces syntax in properties files, should they be kept with an html entity, converted to a js Unicode non breaking space character or replaced by a blank space? We can add more locales for one or both add-ons, if you wish so, please tell me. Thanks

Thanks Pascal. Regarding additional locales, I have received a request from Tetsuya that Japanese is added to the mix. How do you usually work with the Mozilla Japan for localization? Do they use the same dashboard? Margaret, would it be possible to add the japanese feed before submitting to AMO? Posting it here: http://www.goal.com/jp/feeds/news?fmt=rss&ICID=HP

They use the same dashboard, for web pages some are on mozilla.org with our process, others are on mozilla.jp with theirs. I am going to add Japanese.

(In reply to Pascal Chevrel:pascalc from comment #7) > The 6 locales requested are done and Pull requests are done too. There is > one question for Margaret regarding non breaking spaces syntax in properties > files, should they be kept with an html entity, converted to a js Unicode > non breaking space character or replaced by a blank space? I think that they should use a JS Unicode character, since we're using them in JS, e.g.: https://github.com/leibovic/world-cup-feed/blob/master/bootstrap.js#L207 However, let's double check with flod about what Firefox localizers normally do, since they're used to localizing these properties file.

(In reply to :Margaret Leibovic from comment #10) > (In reply to Pascal Chevrel:pascalc from comment #7) > > The 6 locales requested are done and Pull requests are done too. There is > > one question for Margaret regarding non breaking spaces syntax in properties > > files, should they be kept with an html entity, converted to a js Unicode > > non breaking space character or replaced by a blank space? > > I think that they should use a JS Unicode character, since we're using them > in JS, e.g.: > https://github.com/leibovic/world-cup-feed/blob/master/bootstrap.js#L207 > > However, let's double check with flod about what Firefox localizers normally > do, since they're used to localizing these properties file. Yeah, this doesn't look right: https://dl.dropboxusercontent.com/u/3358452/2014-05-28%2017.37.16.png

I don't think localizers use much of non breaking space in .properties, it's much more common in web content (so entity). I'm sure I've seen the Unicode format around though http://hg.mozilla.org/mozilla-central/file/default/dom/locales/en-US/chrome/layout/MediaDocument.properties

Théo told me that for Firefox, he uses a real unicode space in .properties files, so I will do that as well.

Adding Japanese folks to this bug to speed things up a bit. Guys, could you translate the add-on strings for this bug? The strings are exposed on the Web Dashboard for your locale in the 'add-ons' section. Thanks! : http://l10n.mozilla-community.org/webdashboard/?locale=ja

Hey Margaret. Just wanted to check about comment 8. Were you able to add Japanese to the supported locales? Thanks!

(In reply to Gregory Jost from comment #15) > Hey Margaret. Just wanted to check about comment 8. Were you able to add > Japanese to the supported locales? Thanks! Yes, I was! (Well, Pascal and the Japanese folks are really the ones who did the work :) The XPI here is up to date with all the latest changes: http://people.mozilla.org/~mleibovic/worldcupfeed.xpi

You guys rock!

Marking fixed as we have the set of locales requested for the World Cup

We do! Thanks for your help!