Make Packaging Guide translatable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Packaging Guide |
Fix Released
|
High
|
Andrew Starr-Bochicchio |
Bug Description
With https:/
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://
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.
Related branches
- Daniel Holbach (community): Approve
-
Diff: 6926 lines (+6536/-77)18 files modified.bzrignore (+3/-0)
Makefile (+122/-46)
conf.py (+13/-11)
debian/control (+2/-1)
debian/copyright (+1/-1)
debian/rules (+14/-1)
debian/ubuntu-packaging-guide.doc-base.single (+1/-1)
debian/ubuntu-packaging-guide.docs (+1/-1)
po/de.po (+3182/-0)
po/ubuntu-packaging-guide.pot (+3182/-0)
ubuntu-packaging-guide/debian-dir-overview.rst (+1/-1)
ubuntu-packaging-guide/fixing-a-bug.rst (+2/-2)
ubuntu-packaging-guide/index.rst (+2/-2)
ubuntu-packaging-guide/introduction-to-ubuntu-development.rst (+3/-3)
ubuntu-packaging-guide/packaging-new-software.rst (+1/-1)
ubuntu-packaging-guide/patches-to-packages.rst (+1/-1)
ubuntu-packaging-guide/security-and-stable-release-updates.rst (+3/-3)
ubuntu-packaging-guide/udd-intro.rst (+2/-2)
Changed in ubuntu-packaging-guide: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Starr-Bochicchio (andrewsomething) |
Changed in ubuntu-packaging-guide: | |
status: | In Progress → Fix Released |
I've got the basics working, but it's not really ready to land yet.
One thing that I'm not sure how to handle is that in order to build the translated files you seem to need to have the sphinx.mo files for the languages you want. As sphinx is in main, we strip out the .mo files and put them in language-pack-* packages instead. Build-depending on the needed language-packs doesn't really seem right.
We're going to need to figure out the workflow after this lands. As this project is all documentation, we're going to be breaking the translations on nearly every commit. Also, as we'll want the .pot file in version control so it's available to Rosetta, "make gettext" will probably have to be run before every push to trunk to keep it up to date. I wonder if there is some way we can automate that. I don't think bzr has per-branch pre-commit hooks though.
Also, how is this deployed to the website? This is going to change the installed location slightly, so landing it will probably need to be coordinated so as to not break the website.