ubuntu-packaging-guide-team team mailing list archive

[Andrew Starr-Bochicchio <a.starr.b@xxxxxxxxx>]

So, I added creation of the .doc and .doc-base files in my branch. I'm
going to try to finish this up tomorrow.

I guess the question I have about the final bits is how do we imagine
actually using it? Something that we run manually periodically, as some
a bzr-builddeb pre-build hook at source package build time, or during
the binary package build? I'll have to think about that a bit...

-- 
You received this bug notification because you are a member of Ubuntu
Packaging Guide Team, which is subscribed to Ubuntu Packaging Guide.
https://bugs.launchpad.net/bugs/961936

Title:
  Only ship translations which accomplish a certain level of completion

Status in Ubuntu Packaging Guide:
  In Progress

Bug description:
  We should only ship translations which accomplish a certain level of
  completion. There was code for this in the ubuntu-docs package at some
  stage.

  http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/hardy/ubuntu-
  docs/hardy/view/head:/debian/rules still has it

  ---

  UPDATE: I had a conversation with David Planella and we came up with the following 
  idea: 
   - we change translation settings in LP to auto-commit translations (done)
   - we get the Packaging Guide into the archive
   - we write a script using python-polib, which checks which translations are
     sufficiently complete and for them add binary package stanzas to debian/control
     and corresponding packaging bits. we will then run the script every now and 
     then and get more complete translations into Ubuntu this way (this is what 
     this bug should be about)
   - we mail ubuntu-docs and ubuntu-translators mailing lists and blog about the
     effort to translate our docs
   - we update and push the .pot file manually every now and then (make gettext)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-packaging-guide/+bug/961936/+subscriptions