ubuntu-packaging-guide-team team mailing list archive

[David Planella <david.planella@xxxxxxxxxx>]

If you want the translations to be out of the language packs, I believe
there is an option on pkgbinarymangler (or perhaps it can be specified
in the same package, on the control file?) to blacklist a package from
getting its translations. I'd recommend having a word with pitti about
it, as he knows the exact details.

In terms of exposing it to translators, if you're not using language
packs but rather ship the translations in the package (watch out for it
not becoming too big, though), I'd recommend enabling translations in
the upstream project, with the following settings:

For the overall project:
- Restricted permissions
- Assigned to Ubuntu translators

Then on the relevant series:
- Enable automatic imports (import only templates)
- Enable automatic exports (for a full automated experience, use the same branch for exports and imports)

In terms of workflow, if you don't want to break translations on every
commit, I'd recommend doing .pot file updates only on milestones where
you think the documentation is stable, and announce these milestones on
the ubuntu-translators mailing list.

And regarding deployment, we've got write access to the directory where
the html is published, so if translations can live in the same place and
we can write them there, it shouldn't be much of an issue, I think.
We'll probably only have to adjust the script that publishes the HTML
(and other formats, probably) to ensure translations are pulled too.

Thanks for making the Packaging Guide translatable!

-- 
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/943154

Title:
  Make Packaging Guide translatable

Status in Ubuntu Packaging Guide:
  In Progress

Bug description:
  With https://bitbucket.org/birkenfeld/sphinx/issue/561/configuration-
  option-store-translations-in fixed in Sphinx 1.1 (which is in precise
  and which we could backport into our PPA), we could enable
  translations.

  One requirement we have is: one .pot file for the whole package as
  opposed to one .pot file per article. To do this we need to set
  gettext_compact and move all articles in one directory.
  (http://sphinx.pocoo.org/config.html#confval-gettext_compact)

  I prepared a couple of things in a branch at lp:~dholbach/ubuntu-
  packaging-guide/i18n which makes "make gettext" work, but
  unfortunately this will break paths for "make html", etc.

  Any help with this is appreciated, as I'm going to be too busy to
  finish the work in the next few weeks.

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