1128546 - [META] Get the app l10n ready

Status: RESOLVED WONTFIX

(support.mozilla.org :: BuddyUp, defect)

Comment 1

[Kadir Topal [:atopal]]

Mike, can you please add the bugs this meta bug depends on? Please add about 3 points worth of bugs to sprint 2015.8 to get started and Anthony can finish it when he comes back from vacation. Feel free to remove this meta bug from the sprint once the blocker bugs are added.

Comment 2

[Michael Cooper [:mythmon]]

This is a technical overview for how BuddyUp is going to get localized, to provide context to the other bugs.

Generally, l10n has a few steps: 1. getting strings out of the app, 2. getting strings translated, and 3. getting strings back into the app. Here is how we will accomplish those steps with BuddyUp:

1. Strings will be extracted from BuddyUp templates and JS code by parsing it for calls to gettext and friends. The strings will be extracted in a format that Kitsune's localization tools can understand, and merged into Kitsune's strings.

2. Strings will be translated in Verbatim (https://localize.mozilla.org) like other Kitsune localization.

3. At build time for BuddyUp, JS translations files will be downloaded from https://support.mozilla.org and integrated into the package. All localizations will be included. The files will provide the implementation of the gettext functions, as well as the translations. If there are no language files available, a fallback set of gettext functions that simple return their arguments untranslated will be used.

I'll file bugs for this now.

Comment 3

[Michael Cooper [:mythmon]]

This process is similar to how Yaocho got translations last Summer. We should be able to take inspiration from it: https://github.com/mozilla/yaocho/

Comment 4

[Michael Cooper [:mythmon]]

Removing this from the sprint in favor of the implementation bugs, bug 1158909 and bug 1158912.

Comment 5

[Stefan Plewako [:stef]]

(In reply to Mike Cooper [:mythmon] from comment #2)
> 2. Strings will be translated in Verbatim (https://localize.mozilla.org)
> like other Kitsune localization.

Please avoid direct localize.mozilla.org dependency if possible and use something more open (like svn.mozilla.org).

Comment 6

[Adrian Kalla [:adriank]]

(In reply to Mike Cooper [:mythmon] from comment #2)
> 2. Strings will be translated in Verbatim (https://localize.mozilla.org)
> like other Kitsune localization.

Please stop *forcing* the localizers to use some crappy and laggy web tool, since many localizers will be pissed off about that and just not localize your stuff.

Please export it to an external repository on svn.mozilla.org or hg.mozilla.org so *any* tool can be used to translate - including, *but not only* localize.mozilla.org.

Comment 7

[Michael Cooper [:mythmon]]

Verbatim works by pushing and pulling to svn.mozilla.org. Any project on localize.mozilla.org is available on svn.mozilla.org. Here is where SUMO's strings are, which is where Buddyup's strings will be: http://svn.mozilla.org/projects/sumo/locales/ .

Comment 8

[Stefan Plewako [:stef]]

(In reply to Mike Cooper [:mythmon] from comment #7)
> Verbatim works by pushing and pulling to svn.mozilla.org. Any project on
> localize.mozilla.org is available on svn.mozilla.org.

Sorry, but that is not exactly true.

> Here is where SUMO's
> strings are, which is where Buddyup's strings will be:
> http://svn.mozilla.org/projects/sumo/locales/ .

We only want to be able to update them via svn.mozilla.org - if that will be true than great.

Comment 9

[Michael Cooper [:mythmon]]

This isn't something I can speak to. I don't do any localization. This bug is simply about adding BuddyUp to the pre-existing SUMO localization process, which uses Verbatim.  We don't have enough development time to implement a different system. Please feel free to file bugs against SUMO to change the localization process.

Comment 10

[Ben (:bensternthal)]

Triaging old SUMO bugs. AFAIK buddy up is no longer supported and not under active development, so closing these out as won't fix.