Transfer indicator needs internationalization

[David Planella]

As with the rest of indicators, the transfer indicator needs to mark all its visible messages for translations and generate a .pot file. This needs to happen with enough time before RTM for translators to be able to do their work and for the translations to land.

[Sebastien Bacher (seb128)]

One of the things dh_translations checks for, to know if a project is using intltool, is the presence of a po/POTFILES.in, adding one leads to have a template correctly generated during the package build. I'm adding a merge proposal doing that

[Víctor R. Ruiz (vrruiz)]

The .pot file must also be updated. Adding a merge proposal.

[Launchpad Janitor (janitor)]

This bug was fixed in the package indicator-transfer - 0.1+14.10.20140905-0ubuntu1

---------------
indicator-transfer (0.1+14.10.20140905-0ubuntu1) utopic; urgency=low

  [ Sebastien Bacher ]
  * Tweak translations setup to have a template generated (LP: #1348825)
 -- Ubuntu daily release <email address hidden> Fri, 05 Sep 2014 15:39:57 +0000

[Sebastien Bacher (seb128)]

@Victor, why do you need to update the pot? The translations can be done on https://translations.launchpad.net/ubuntu/utopic/+source/indicator-transfer

[Víctor R. Ruiz (vrruiz)]

Sebastien: While marking strings for localization in some projects, I was also requested to update the .pot file. I understood that translations.launchpad.net grabbed the pot file from the repo.

[Sebastien Bacher (seb128)]

Victor, some projects do their translation in trunk, some use the ubuntu translations

[Martin Pitt (pitti)]

Right, when projects use Launchpad to do upstream translations the .pot needs to live in bzr trunk to get imported. But most Ubuntu packages only build the POT during package build and thus get imported into Launchpad as *ubuntu package* (not upstream project) translations.

The langpacks that we build are always built from Ubuntu package translations. They usually sync with upstream's (called "message sharing").

The slight advantage of also translating strings in the upstream project is that LP can (and usually is) be configured to directly commit them to trunk, and thus the turnaround between doing translations and getting langpack updates from them is just minutes. With Ubuntu translations you need to release/upload the project first and wait for a new LP export of Ubuntu translations. (langpack-o-matic has the script "merge-touch-upstream-translations" for that, which is a hack intended to speed up translations and the move to langpacks, but isn't intended to be a long-term thing).

So in summary, it's fine to do like the indicators and translate in Ubuntu only as long as there is an up to date POT being built during package build.