|
|
35.
|
|
|
The configuration file consists of several sections, general, XML/XSL support, POD support and HTML support.
|
|
|
type: Content of: <refentry><refsect1><refsect2><para>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:129
|
|
|
36.
|
|
|
General includes the name and location of the po4a config file (probably best to leave this as <filename>po4a.config</filename>), the po directory containing the documentation PO files (often <filename>doc/po</filename>), 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.
|
|
|
type: Content of: <refentry><refsect1><refsect2><para>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:132
|
|
|
37.
|
|
|
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 <command>xsltproc</command> and the location of the XML or DocBook files. The XSLFILE can be overridden, if necessary.
|
|
|
type: Content of: <refentry><refsect1><refsect2><para>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:141
|
|
|
38.
|
|
|
POD support includes specifying which of the binary packages use POD support in the PODPACKAGES variable and the full name of the POD file.
|
|
|
type: Content of: <refentry><refsect1><refsect2><para>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:146
|
|
|
39.
|
|
|
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.
|
|
|
type: Content of: <refentry><refsect1><refsect2><para>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:150
|
|
|
40.
|
|
|
COMMANDS
|
|
|
type: Content of: <refentry><refsect1><title>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:158
|
|
|
41.
|
|
|
<option>--pot-only</option>
|
|
|
type: Content of: <refentry><refsect1><variablelist><varlistentry><term>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:162
|
|
|
42.
|
|
|
Only updates the POT file(s). <option>--pot-only</option> 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, <command>po4a-build</command> can update the POT file(s) at the start of the build, so that <command>dpkg-source</command> includes them into the source tarball.
|
|
|
type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:165
|
|
|
43.
|
|
|
svn-buildpackage example
|
|
|
type: Content of: <refentry><refsect1><variablelist><varlistentry><example><title>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:178
|
|
|
44.
|
|
|
<command>svn-buildpackage</command> has explicit support for this kind of addition, using the <option>useNativeDist</option> SVN property and the <option>native-dist</option> Make target.
|
|
|
type: Content of: <refentry><refsect1><variablelist><varlistentry><example><para>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
share/doc//po4a-build.xml:179
|
