<B>po4a-buildB> [<B>-fB> | <B>--fileB> FILE] [<B>--pot-onlyB>]
<B>po4a-buildB> [<B>-?B> | <B>-hB> | <B>--helpB> | <B>--versionB>]
When <B>po4aB> prepares the translated content as POD or DocBook XML, the final documentation can then be built using <B>po4a-buildB>. Both the untranslated and translated content is built as a single process, updating the POT files at the same time.
Existing build instructions are replaced by a single call to <B>po4a-buildB> and a simple configuration file is used to tell <B>po4a-buildB> how to build each element and which binary packages will include the translated and untranslated content.
Once built, the content will be in package-specific directories beneath the <B>BASEDIRB> specified in the configuration file. For a binary package foo, with translations into German and French, this would result in:
BASEDIR/foo/man/man1/foo.1 BASEDIR/foo/man/de/man1/foo.1 BASEDIR/foo/man/fr/man1/foo.1
This makes it easy to include all the generated content into the binary package with a single install location:
doc/foo/man/* ./usr/share/man/ doc/foo/html/* ./usr/share/doc/foo/
This rule will not need to be updated when new translations are added and adding a second binary package (bar) allows the content for that package to kept separate.
1. DocBook XML for section 1.
2. DocBook XML for section 3.
3. DocBook XML for HTML.
4. POD for section 1.
5. POD for section 3.
6. POD for section 5.
7. POD for section 7.
<B>po4a-buildB> uses a default configuration file, po4a-build.conf which should be in the top level directory of your package VCS. (Use the <B>-fB> option to specify a different file.) See <B>po4a-build.confB>(5).
An example configuration file is available at:
The configuration file consists of several sections, general, XML/XSL support, POD support and HTML support.
General includes the name and location of the po4a config file (probably best to leave this as po4a.config), the po directory containing the documentation PO files (often doc/po), the full name of the POT file used to create the translations, the BASEDIR for the generated output, whether the package contains manpages in section 3 rather than just section 1 and the names of the binary packages which are to contain the generated output.
XML/XSL support includes specifying which of the binary packages use XSL support in the XMLPACKAGES variable, the top level DocBook file to pass to <B>xsltprocB> and the location of the XML or DocBook files. The XSLFILE can be overridden, if necessary.
POD support includes specifying which of the binary packages use POD support in the PODPACKAGES variable and the full name of the POD file.
HTML support specifies the subdirectory to create below BASEDIR for the untranslated and translated HTML content and the DocBook file to generate the HTML. The HTMLXSL file can be overridden, if necessary.
Only updates the POT file(s). <B>--pot-onlyB> is intended to support packages including all POT files in the package source. Packages using Autotools can easily add the POT file via EXTRA_DIST but packages just using a Makefile or certain VCS build helpers can find it awkward to add the POT file (which is a generated file) without putting the POT file into the VCS. To avoid this ugly and unnecessary work, <B>po4a-buildB> can update the POT file(s) at the start of the build, so that <B>dpkg-sourceB> includes them into the source tarball.
# adds the POT file to the source tarball native-dist: Makefile po4a-build --pot-only
$ svn propset useNativeDist 1 debianprint the usage message and exit.print the usage message and exit.
This manual page was written by Neil Williams email@example.com