ubuntu-packaging-guide-team team mailing list archive
-
ubuntu-packaging-guide-team team
-
Mailing list archive
-
Message #00611
[Bug 943154] Re: Make Packaging Guide translatable
I thought about this too and every single solution I could think of was
inherently dirty. I was thinking of doing a regular build of everything,
then cleaning up and applying some magic to be able to do the gettext
build (or the other way around). I don't know how feasible this is
though.
--
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
References