Needs translation setup

[David Planella]

Currently the indicator on the phone has got translatable messages that are not translatable since we don't expose them to translators.

What's needed is to add a rule to extract translatable messages from the source code with xgettext and put them into a .pot file under the po/ folder.

As an example, all system apps are also using CMake and internationalized with the same rules, so I assume they can just be reused for the indicator. Here's how the Web Browser does it:

http://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/po/CMakeLists.txt
http://bazaar.launchpad.net/~phablet-team/webbrowser-app/trunk/view/head:/CMakeLists.txt#L52

Once that's done, I can help setting up the project in Launchpad for translations.

[Sebastien Bacher (seb128)]

The touch and desktop indicators use the same sources, those should be translated in Ubuntu at the usual location.

The main issue there is launchpad bug https://bugs.launchpad.net/langpack-o-matic/+bug/1201485 leading to outdated templates.

I'm going to update manually the templates

[Sebastien Bacher (seb128)]

indicator-messages' template updated: https://translations.launchpad.net/ubuntu/saucy/+source/indicator-messages

[Sebastien Bacher (seb128)]

The power one is uptodate: https://translations.launchpad.net/ubuntu/saucy/+source/indicator-power/

[Sebastien Bacher (seb128)]

The sound one as well: https://translations.launchpad.net/ubuntu/saucy/+source/indicator-sound

[David Planella (dpm)]

After a chat with seb128 on IRC I've realized that the indicators will ship with converged source on 13.10 and that translations should appear in the source package namespace in Launchpad once bug 1201485 is fixed.

To bring some more context, translations will be stripped and imported only for those packages in the Unity daily builds PPA that are in main. Unity8 and other packages will not be promoted to main for 13.10, thus their translations will not be stripped, but those from indicators will be (they already are).

I've marked the bug tasks for the projects which have already got a translations set up as Invalid, but they might still need a manual update of the .pot file as it's been done for indicator-messages.

Indicator-location and indicator-power still need to be internationalized, though.

[Sebastien Bacher (seb128)]

https://translations.launchpad.net/ubuntu/saucy/+source/indicator-bluetooth

[Sebastien Bacher (seb128)]

indicator-session on https://translations.launchpad.net/ubuntu/saucy/+source/indicator-session

[Sebastien Bacher (seb128)]

https://translations.launchpad.net/ubuntu/saucy/+source/indicator-datetime

[Sebastien Bacher (seb128)]

Ok, with that all the desktop indicators have their template update. The other ones are in universe and need a different setup to be translatable (e.g have translations enabled on the upstream project for example)

[David Planella (dpm)]

Indicator-location is the last template that needs to be enabled for translations. We had a chat between seb128, charles and I yesterday, and to enable translators to do their work while waiting for the fix, I generated a .pot file locally and manually uploaded it to the upstream project. What is left to do is:

1) File a MIR for indicator-location to get the translations of the source package imported (universe package translations are not imported): https://wiki.ubuntu.com/MainInclusionProcess - Charles might be in the best position to do this as the developer
2) Generate and commit a .pot file in the upstream project source tree to enable translations there too (translations will be shared with the upstream project) - same as above, Charles, it'd be great if you could look into this as part of this bug
3) Enable automatic translations export to have translations auto-committed to the upstream project - I can do that.