ubuntu-translations-coordinators team mailing list archive

[David Planella <david.planella@xxxxxxxxxx>]

I agree that having the .pot file in the source tree is not ideal, but
it's the easiest way to get translations automatically imported in
Launchpad. The other option is to manually upload the .pot template
every time it is updated.

Launchpad used to have support for automatically generating .pot files
for intltool-based projects, which we'd ideally use. It might well be
that it's still working, but I'm not sure about its maintenance status.

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1268939

Title:
  Needs translation support

Status in Ubuntu Translations:
  Triaged
Status in “unity-scope-click” package in Ubuntu:
  New

Bug description:
  The click scope needs to be set up for translations.

  In summary, to make translations happen, we need to:

  - Have a top-level po folder to contain translations
  - Have the build system generate a .pot template that is committed to the source tree
  - Have the .deb package create that .pot template on build
  - Have a build system rule to build translations (.po -> .mo conversion) via gettext tools
  - Have Launchpad set up for translations (I can take care of this one)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1268939/+subscriptions