ubuntu-translations-coordinators team mailing list archive

[Gabor Kelemen <kelemeng@xxxxxxxx>]

Status update, as of Oneiric.

Just to recap, the basic workflow is the following in the upstream apt: 
- translators translate po/apt-all.pot
- the build system splits the translations into three smaller templates: apt, libapt-pkg4.11, libapt-inst1.3. The apt binaries use these, and apt-all is not used after this build time step at all.

At this point, enters Ubuntu packaging. Formerly, all three templates went into the apt package, recently this changed, and they go into the apt, libapt-pkg4.11 and libapt-inst1.3 packages. 
pkgbinarymangler does not know about this yet, so it strips away translations from the latter two packages: http://bazaar.launchpad.net/~ubuntu-core-dev/pkgbinarymangler/ubuntu/view/head:/striptranslations.blacklist
*Todo: file a bug about this (I volunteer :)).

In Launchpad Translations, we have currently all four templates enabled to import and translate, but only apt-all is set to export into langpacks, which is exactly the inverse of what should be done, if we want to provide updates in the langpacks: https://translations.launchpad.net/ubuntu/oneiric/+source/apt/+translations
* Todo: unset exporting apt-all, set exporting the derived templates. The versioned translation domains have to be updated too.

I think this is what we should do:
- encourage translators to translate apt-all.pot, then make sure it gets exported at non-langpack freeze time, and the apt package is rebuild with it, so folks can see its strings translated at install time too. I don't think that exporting the three derived templates to be used at build time would especially please the package maintainers, but I can be wrong :).
We can also encourage syncing this with upstream.
- ask translators to fill in only new translations into the three derived templates. Because .mo files in /usr/share/locale take precedence over those in /usr/share/locale-langpack (and rightly so), only newly translated strings will be visible via langpack updates, corrections of existing strings will have to wait until next export&rebuild.

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

Title:
  apt templates handling in Ubuntu

Status in Ubuntu Translations:
  In Progress

Bug description:
  The apt source package only contains the apt-all.po files  and no apt-
  all.POT.

  It look like durring the build time from apt-all, the build script creates 3 new templates:
  apt.pot
  libapt-pkg4.8.pot
  libapt-inst1.1.pot

  In Launchpad translations I have approved all 3 templates:
  https://translations.edge.launchpad.net/ubuntu/karmic/+source/apt

  I also did the transition from libapt-pkg4.7.pot (used in previous
  Ubuntu release) to libapt-pkg4.8.pot.

  
  Since the new source package does not contains any apt-all.pot file, the current apt-all template from Rosetta is not updated. Should we disable it ? 

  If we disable it, will be hard for Ubuntu translators to send translations upstream.
  But since there are no new apt-all template update, the current apt-all template from Rosetta is outdated.

  To avoid duplicate work and keep things in sync with upstream
  translation, Ubuntu translators shoul only translate the apt-all.po
  files and the manualy approve the required suggestions in the other 3
  templates.

  I think we should inform Ubuntu translators about this procedure and
  also modify the templates description.

  Michael Vogt, do you have any advice how we should best handle the apt
  translations in Ubuntu to make it easy for both Ubuntu translators but
  also for sending transltations upstream.

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