msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2008-08-08 11:34-0300\n"
+"POT-Creation-Date: 2011-03-03 11:18-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
+"Language: \n"
"MIME-Version: 1.0\n"
-"Content-Type: text/plain; charset=utf-8\n"
-"Content-Transfer-Encoding: ENCODING"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
-# type: Content of: <appendix><title>
+#. type: Content of: <appendix><title>
#: tools.dbk:7
msgid "Overview of Debian Maintainer Tools"
msgstr ""
-# type: Content of: <appendix><para>
+#. type: Content of: <appendix><para>
#: tools.dbk:9
msgid ""
"This section contains a rough overview of the tools available to "
"a guide to some of the more popular tools."
msgstr ""
-# type: Content of: <appendix><para>
+#. type: Content of: <appendix><para>
#: tools.dbk:14
msgid ""
"Debian maintainer tools are meant to aid developers and free their time for "
"critical tasks. As Larry Wall says, there's more than one way to do it."
msgstr ""
-# type: Content of: <appendix><para>
+#. type: Content of: <appendix><para>
#: tools.dbk:18
msgid ""
"Some people prefer to use high-level package maintenance tools and some do "
"exclusion of a competing tool."
msgstr ""
-# type: Content of: <appendix><para>
+#. type: Content of: <appendix><para>
#: tools.dbk:26
msgid ""
"Most of the descriptions of these packages come from the actual package "
"descriptions themselves. Further information can be found in the package "
"documentation itself. You can also see more info with the command "
-"<command>apt-cache show <package-name></command>."
+"<command>apt-cache show <replaceable>package-name</replaceable></command>."
msgstr ""
-# type: Content of: <appendix><section><title>
+#. type: Content of: <appendix><section><title>
#: tools.dbk:32
msgid "Core tools"
msgstr ""
-# type: Content of: <appendix><section><para>
+#. type: Content of: <appendix><section><para>
#: tools.dbk:34
msgid "The following tools are pretty much required for any maintainer."
msgstr ""
-# type: Content of: <appendix><section><section><title>
+#. type: Content of: <appendix><section><section><title>
#: tools.dbk:37
msgid "<systemitem role=\"package\">dpkg-dev</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:39
msgid ""
"<systemitem role=\"package\">dpkg-dev</systemitem> contains the tools "
"(including <command>dpkg-source</command>) required to unpack, build, and "
-"upload Debian source packages. These utilities contain the fundamental, "
-"low-level functionality required to create and manipulate packages; as such, "
+"upload Debian source packages. These utilities contain the fundamental, low-"
+"level functionality required to create and manipulate packages; as such, "
"they are essential for any Debian maintainer."
msgstr ""
-# type: Content of: <appendix><section><section><title>
+#. type: Content of: <appendix><section><section><title>
#: tools.dbk:48
msgid "<systemitem role=\"package\">debconf</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:50
msgid ""
"<systemitem role=\"package\">debconf</systemitem> provides a consistent "
"added as modules."
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:56
msgid ""
-"You can find documentation for this package in the <systemitem "
-"role=\"package\">debconf-doc</systemitem> package."
+"You can find documentation for this package in the <systemitem role=\"package"
+"\">debconf-doc</systemitem> package."
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:60
msgid ""
"Many feel that this system should be used for all packages which require "
-"interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/> . "
+"interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/>. "
"<systemitem role=\"package\">debconf</systemitem> is not currently required "
"by Debian Policy, but that may change in the future."
msgstr ""
-# type: Content of: <appendix><section><section><title>
+#. type: Content of: <appendix><section><section><title>
#: tools.dbk:68
msgid "<systemitem role=\"package\">fakeroot</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:70
msgid ""
"<systemitem role=\"package\">fakeroot</systemitem> simulates root "
"a regular user: <literal>dpkg-buildpackage -rfakeroot</literal>."
msgstr ""
-# type: Content of: <appendix><section><title>
+#. type: Content of: <appendix><section><title>
#: tools.dbk:81
msgid "Package lint tools"
msgstr ""
-# type: Content of: <appendix><section><para>
+#. type: Content of: <appendix><section><para>
#: tools.dbk:83
msgid ""
"According to the Free On-line Dictionary of Computing (FOLDOC), `lint' is a "
"packages."
msgstr ""
-# type: Content of: <appendix><section><section><title>
+#. type: Content of: <appendix><section><section><title>
#: tools.dbk:89
msgid "<systemitem role=\"package\">lintian</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:91
msgid ""
"<systemitem role=\"package\">lintian</systemitem> dissects Debian packages "
"for common errors."
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:97
msgid ""
-"You should periodically get the newest <systemitem "
-"role=\"package\">lintian</systemitem> from <literal>unstable</literal> and "
-"check over all your packages. Notice that the <literal>-i</literal> option "
-"provides detailed explanations of what each error or warning means, what its "
-"basis in Policy is, and commonly how you can fix the problem."
+"You should periodically get the newest <systemitem role=\"package\">lintian</"
+"systemitem> from <literal>unstable</literal> and check over all your "
+"packages. Notice that the <literal>-i</literal> option provides detailed "
+"explanations of what each error or warning means, what its basis in Policy "
+"is, and commonly how you can fix the problem."
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:104
msgid ""
"Refer to <xref linkend=\"sanitycheck\"/> for more information on how and "
"when to use Lintian."
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:108
msgid ""
"You can also see a summary of all problems reported by Lintian on your "
"distribution (<literal>unstable</literal>)."
msgstr ""
-# type: Content of: <appendix><section><section><title>
+#. type: Content of: <appendix><section><section><title>
#: tools.dbk:116
-msgid "<systemitem role=\"package\">debdiff</systemitem>"
+msgid "<command>debdiff</command>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:118
msgid ""
-"<command>debdiff</command> (from the <systemitem "
-"role=\"package\">devscripts</systemitem> package, <xref "
-"linkend=\"devscripts\"/> ) compares file lists and control files of two "
-"packages. It is a simple regression test, as it will help you notice if the "
-"number of binary packages has changed since the last upload, or if something "
-"has changed in the control file. Of course, some of the changes it reports "
-"will be all right, but it can help you prevent various accidents."
+"<command>debdiff</command> (from the <systemitem role=\"package"
+"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/>) "
+"compares file lists and control files of two packages. It is a simple "
+"regression test, as it will help you notice if the number of binary packages "
+"has changed since the last upload, or if something has changed in the "
+"control file. Of course, some of the changes it reports will be all right, "
+"but it can help you prevent various accidents."
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:127
msgid "You can run it over a pair of binary packages:"
msgstr ""
-# type: Content of: <appendix><section><section><screen>
-#: tools.dbk:129
+#. type: Content of: <appendix><section><section><screen>
+#: tools.dbk:130
#, no-wrap
-msgid ""
-"\n"
-"debdiff package_1-1_arch.deb package_2-1_arch.deb\n"
+msgid "debdiff package_1-1_arch.deb package_2-1_arch.deb\n"
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:133
msgid "Or even a pair of changes files:"
msgstr ""
-# type: Content of: <appendix><section><section><screen>
-#: tools.dbk:135
+#. type: Content of: <appendix><section><section><screen>
+#: tools.dbk:136
#, no-wrap
-msgid ""
-"\n"
-"debdiff package_1-1_arch.changes package_2-1_arch.changes\n"
+msgid "debdiff package_1-1_arch.changes package_2-1_arch.changes\n"
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:139
msgid ""
-"For more information please see <citerefentry> "
-"<refentrytitle>debdiff</refentrytitle> <manvolnum>1</manvolnum> "
-"</citerefentry>."
+"For more information please see <citerefentry> <refentrytitle>debdiff</"
+"refentrytitle> <manvolnum>1</manvolnum> </citerefentry>."
msgstr ""
-# type: Content of: <appendix><section><title>
+#. type: Content of: <appendix><section><title>
#: tools.dbk:148
msgid "Helpers for <filename>debian/rules</filename>"
msgstr ""
-# type: Content of: <appendix><section><para>
+#. type: Content of: <appendix><section><para>
#: tools.dbk:150
msgid ""
-"Package building tools make the process of writing "
-"<filename>debian/rules</filename> files easier. See <xref "
-"linkend=\"helper-scripts\"/> for more information about why these might or "
-"might not be desired."
+"Package building tools make the process of writing <filename>debian/rules</"
+"filename> files easier. See <xref linkend=\"helper-scripts\"/> for more "
+"information about why these might or might not be desired."
msgstr ""
-# type: Content of: <appendix><section><section><title>
+#. type: Content of: <appendix><section><section><title>
#: tools.dbk:156
msgid "<systemitem role=\"package\">debhelper</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:158
msgid ""
"<systemitem role=\"package\">debhelper</systemitem> is a collection of "
"programs which can be used in <filename>debian/rules</filename> to automate "
-"common tasks related to building binary Debian packages. <systemitem "
-"role=\"package\">debhelper</systemitem> includes programs to install various "
+"common tasks related to building binary Debian packages. <systemitem role="
+"\"package\">debhelper</systemitem> includes programs to install various "
"files into your package, compress files, fix file permissions, and integrate "
"your package with the Debian menu system."
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:166
msgid ""
"Unlike some approaches, <systemitem role=\"package\">debhelper</systemitem> "
"debian/rules tools."
msgstr ""
-# type: Content of: <appendix><section><section><para>
+#. type: Content of: <appendix><section><section><para>
#: tools.dbk:172
msgid ""
-"There are a number of little <systemitem "
-"role=\"package\">debhelper</systemitem> add-on packages, too transient to "
-"document. You can see the list of most of them by doing <literal>apt-cache "
-"search ^dh-</literal>."
+"There are a number of little <systemitem role=\"package\">debhelper</"
+"systemitem> add-on packages, too transient to document. You can see the "
+"list of most of them by doing <literal>apt-cache search ^dh-</literal>."
msgstr ""
-# type: Content of: <appendix><section><section><title>
+#. type: Content of: <appendix><section><section><title>
#: tools.dbk:179
-msgid "<systemitem role=\"package\">debmake</systemitem>"
-msgstr ""
-
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:181
-msgid ""
-"<systemitem role=\"package\">debmake</systemitem>, a precursor to "
-"<systemitem role=\"package\">debhelper</systemitem>, is a more "
-"coarse-grained <filename>debian/rules</filename> assistant. It includes two "
-"main programs: <command>deb-make</command>, which can be used to help a "
-"maintainer convert a regular (non-Debian) source archive into a Debian "
-"source package; and <command>debstd</command>, which incorporates in one big "
-"shot the same sort of automated functions that one finds in <systemitem "
-"role=\"package\">debhelper</systemitem>."
-msgstr ""
-
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:191
-msgid ""
-"The consensus is that <systemitem role=\"package\">debmake</systemitem> is "
-"now deprecated in favor of <systemitem "
-"role=\"package\">debhelper</systemitem>. It is a bug to use <systemitem "
-"role=\"package\">debmake</systemitem> in new packages. New packages using "
-"<systemitem role=\"package\">debmake</systemitem> will be rejected from the "
-"archive."
-msgstr ""
-
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:200
msgid "<systemitem role=\"package\">dh-make</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:202
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:181
msgid ""
"The <systemitem role=\"package\">dh-make</systemitem> package contains "
"<command>dh_make</command>, a program that creates a skeleton of files "
"necessary to build a Debian package out of a source tree. As the name "
-"suggests, <command>dh_make</command> is a rewrite of <systemitem "
-"role=\"package\">debmake</systemitem> and its template files use dh_* "
-"programs from <systemitem role=\"package\">debhelper</systemitem>."
+"suggests, <command>dh_make</command> is a rewrite of <systemitem role="
+"\"package\">debmake</systemitem> and its template files use <command>dh_*</"
+"command> programs from <systemitem role=\"package\">debhelper</systemitem>."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:210
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:189
msgid ""
"While the rules files generated by <command>dh_make</command> are in general "
"a sufficient basis for a working package, they are still just the "
"groundwork: the burden still lies on the maintainer to finely tune the "
-"generated files and make the package entirely functional and "
-"Policy-compliant."
+"generated files and make the package entirely functional and Policy-"
+"compliant."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:218
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:197
msgid "<systemitem role=\"package\">yada</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:220
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:199
msgid ""
"<systemitem role=\"package\">yada</systemitem> is another packaging helper "
"tool. It uses a <filename>debian/packages</filename> file to auto-generate "
"<filename>debian/rules</filename> and other necessary files in the "
-"<filename>debian/</filename> subdirectory. The "
-"<filename>debian/packages</filename> file contains instruction to build "
-"packages and there is no need to create any <filename>Makefile</filename> "
-"files. There is possibility to use macro engine similar to the one used in "
-"SPECS files from RPM source packages."
+"<filename>debian/</filename> subdirectory. The <filename>debian/packages</"
+"filename> file contains instruction to build packages and there is no need "
+"to create any <filename>Makefile</filename> files. There is possibility to "
+"use macro engine similar to the one used in SPECS files from RPM source "
+"packages."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:230
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:209
msgid ""
-"For more informations see <literal><ulink "
-"url=\"http://yada.alioth.debian.org/\">YADA site</ulink></literal>."
+"For more informations see <ulink url=\"http://yada.alioth.debian.org/"
+"\"><literal>YADA</literal> site</ulink>."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:236
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:215
msgid "<systemitem role=\"package\">equivs</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:238
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:217
msgid ""
"<systemitem role=\"package\">equivs</systemitem> is another package for "
"making packages. It is often suggested for local use if you need to make a "
"on other packages."
msgstr ""
-# type: Content of: <appendix><section><title>
-#: tools.dbk:249
+#. type: Content of: <appendix><section><title>
+#: tools.dbk:228
msgid "Package builders"
msgstr ""
-# type: Content of: <appendix><section><para>
-#: tools.dbk:251
+#. type: Content of: <appendix><section><para>
+#: tools.dbk:230
msgid ""
"The following packages help with the package building process, general "
"driving <command>dpkg-buildpackage</command> as well as handling supporting "
"tasks."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:255
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:234
msgid "<systemitem role=\"package\">cvs-buildpackage</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:257
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:236
msgid ""
"<systemitem role=\"package\">cvs-buildpackage</systemitem> provides the "
"capability to inject or import Debian source packages into a CVS repository, "
"upstream changes into the repository."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:263
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:242
msgid ""
"These utilities provide an infrastructure to facilitate the use of CVS by "
"Debian maintainers. This allows one to keep separate CVS branches of a "
"benefits of a version control system."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:272
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:251
msgid "<systemitem role=\"package\">debootstrap</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:274
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:253
msgid ""
"The <systemitem role=\"package\">debootstrap</systemitem> package and script "
"allows you to bootstrap a Debian base system into any part of your "
"to operate and install the rest of the system."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:280
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:259
msgid ""
"Having a system like this can be useful in many ways. For instance, you can "
"<command>chroot</command> into it if you want to test your build "
"a bare base system. Chroot builders use this package; see below."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:288
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:267
msgid "<systemitem role=\"package\">pbuilder</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:290
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:269
msgid ""
"<systemitem role=\"package\">pbuilder</systemitem> constructs a chrooted "
"system, and builds a package inside the chroot. It is very useful to check "
"package."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:296
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:275
msgid ""
"A related package is <systemitem role=\"package\">pbuilder-uml</systemitem>, "
"which goes even further by doing the build within a User Mode Linux "
"environment."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:303
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:282
msgid "<systemitem role=\"package\">sbuild</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:305
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:284
msgid ""
"<systemitem role=\"package\">sbuild</systemitem> is another automated "
-"builder. It can use chrooted environments as well. It can be used "
-"stand-alone, or as part of a networked, distributed build environment. As "
-"the latter, it is part of the system used by porters to build binary "
-"packages for all the available architectures. See <xref "
-"linkend=\"wanna-build\"/> for more information, and <ulink "
-"url=\"&url-buildd;\"></ulink> to see the system in action."
+"builder. It can use chrooted environments as well. It can be used stand-"
+"alone, or as part of a networked, distributed build environment. As the "
+"latter, it is part of the system used by porters to build binary packages "
+"for all the available architectures. See <xref linkend=\"wanna-build\"/> "
+"for more information, and <ulink url=\"&url-buildd;\"></ulink> to see the "
+"system in action."
msgstr ""
-# type: Content of: <appendix><section><title>
-#: tools.dbk:317
+#. type: Content of: <appendix><section><title>
+#: tools.dbk:296
msgid "Package uploaders"
msgstr ""
-# type: Content of: <appendix><section><para>
-#: tools.dbk:319
+#. type: Content of: <appendix><section><para>
+#: tools.dbk:298
msgid ""
"The following packages help automate or simplify the process of uploading "
"packages into the official archive."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:323
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:302
msgid "<systemitem role=\"package\">dupload</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:325
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:304
msgid ""
"<systemitem role=\"package\">dupload</systemitem> is a package and a script "
"to automatically upload Debian packages to the Debian archive, to log the "
"it for new upload locations or methods."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:333
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:312
msgid "<systemitem role=\"package\">dput</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:335
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:314
msgid ""
"The <systemitem role=\"package\">dput</systemitem> package and script does "
"much the same thing as <systemitem role=\"package\">dupload</systemitem>, "
-"but in a different way. It has some features over <systemitem "
-"role=\"package\">dupload</systemitem>, such as the ability to check the "
-"GnuPG signature and checksums before uploading, and the possibility of "
-"running <command>dinstall</command> in dry-run mode after the upload."
+"but in a different way. It has some features over <systemitem role=\"package"
+"\">dupload</systemitem>, such as the ability to check the GnuPG signature "
+"and checksums before uploading, and the possibility of running "
+"<command>dinstall</command> in dry-run mode after the upload."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:345
-msgid "<systemitem role=\"package\">dcut</systemitem>"
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:324
+msgid "<command>dcut</command>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:347
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:326
msgid ""
-"The <systemitem role=\"package\">dcut</systemitem> script (part of the "
-"package <xref linkend=\"dput\"/> ) helps in removing files from the ftp "
-"upload directory."
+"The <command>dcut</command> script (part of the package <systemitem role="
+"\"package\">dput</systemitem>, <xref linkend=\"dput\"/>) helps in removing "
+"files from the ftp upload directory."
msgstr ""
-# type: Content of: <appendix><section><title>
-#: tools.dbk:355
+#. type: Content of: <appendix><section><title>
+#: tools.dbk:334
msgid "Maintenance automation"
msgstr ""
-# type: Content of: <appendix><section><para>
-#: tools.dbk:357
+#. type: Content of: <appendix><section><para>
+#: tools.dbk:336
msgid ""
"The following tools help automate different maintenance tasks, from adding "
"changelog entries or signature lines and looking up bugs in Emacs to making "
"use of the newest and official <filename>config.sub</filename>."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:362
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:341
msgid "<systemitem role=\"package\">devscripts</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:364
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:343
msgid ""
"<systemitem role=\"package\">devscripts</systemitem> is a package containing "
"wrappers and tools which are very helpful for maintaining your Debian "
"packages. Example scripts include <command>debchange</command> and "
-"<command>dch</command>, which manipulate your "
-"<filename>debian/changelog</filename> file from the command-line, and "
-"<command>debuild</command>, which is a wrapper around "
-"<command>dpkg-buildpackage</command>. The <command>bts</command> utility is "
-"also very helpful to update the state of bug reports on the command line. "
-"<command>uscan</command> can be used to watch for new upstream versions of "
-"your packages. <command>debrsign</command> can be used to remotely sign a "
-"package prior to upload, which is nice when the machine you build the "
-"package on is different from where your GPG keys are."
+"<command>dch</command>, which manipulate your <filename>debian/changelog</"
+"filename> file from the command-line, and <command>debuild</command>, which "
+"is a wrapper around <command>dpkg-buildpackage</command>. The <command>bts</"
+"command> utility is also very helpful to update the state of bug reports on "
+"the command line. <command>uscan</command> can be used to watch for new "
+"upstream versions of your packages. <command>debrsign</command> can be used "
+"to remotely sign a package prior to upload, which is nice when the machine "
+"you build the package on is different from where your GPG keys are."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:378
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:357
msgid ""
"See the <citerefentry> <refentrytitle>devscripts</refentrytitle> "
"<manvolnum>1</manvolnum> </citerefentry> manual page for a complete list of "
"available scripts."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:385
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:364
msgid "<systemitem role=\"package\">autotools-dev</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:387
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:366
msgid ""
"<systemitem role=\"package\">autotools-dev</systemitem> contains best "
-"practices for people who maintain packages which use "
-"<command>autoconf</command> and/or <command>automake</command>. Also "
-"contains canonical <filename>config.sub</filename> and "
-"<filename>config.guess</filename> files which are known to work on all "
-"Debian ports."
+"practices for people who maintain packages which use <command>autoconf</"
+"command> and/or <command>automake</command>. Also contains canonical "
+"<filename>config.sub</filename> and <filename>config.guess</filename> files "
+"which are known to work on all Debian ports."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:396
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:375
msgid "<systemitem role=\"package\">dpkg-repack</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:398
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:377
msgid ""
"<command>dpkg-repack</command> creates Debian package file out of a package "
"that has already been installed. If any changes have been made to the "
"modified), the new package will inherit the changes."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:404
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:383
msgid ""
"This utility can make it easy to copy packages from one computer to another, "
"or to recreate packages which are installed on your system but no longer "
"upgrade it."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:411
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:390
msgid "<systemitem role=\"package\">alien</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:413
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:392
msgid ""
"<command>alien</command> converts binary packages between various packaging "
"formats, including Debian, RPM (RedHat), LSB (Linux Standard Base), Solaris, "
"and Slackware packages."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:420
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:399
msgid "<systemitem role=\"package\">debsums</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:422
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:401
msgid ""
"<command>debsums</command> checks installed packages against their MD5 "
"sums. Note that not all packages have MD5 sums, since they aren't required "
"by Policy."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:428
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:407
msgid "<systemitem role=\"package\">dpkg-dev-el</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:430
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:409
msgid ""
"<systemitem role=\"package\">dpkg-dev-el</systemitem> is an Emacs lisp "
"package which provides assistance when editing some of the files in the "
"the latest entry in a <filename>debian/changelog</filename> file."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:439
-msgid "<systemitem role=\"package\">dpkg-depcheck</systemitem>"
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:418
+msgid "<command>dpkg-depcheck</command>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:441
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:420
msgid ""
-"<command>dpkg-depcheck</command> (from the <systemitem "
-"role=\"package\">devscripts</systemitem> package, <xref "
-"linkend=\"devscripts\"/> ) runs a command under <command>strace</command> "
-"to determine all the packages that were used by the said command."
+"<command>dpkg-depcheck</command> (from the <systemitem role=\"package"
+"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/>) runs a "
+"command under <command>strace</command> to determine all the packages that "
+"were used by the said command."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:447
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:426
msgid ""
"For Debian packages, this is useful when you have to compose a "
"<literal>Build-Depends</literal> line for your new package: running the "
"a good first approximation of the build-dependencies. For example:"
msgstr ""
-# type: Content of: <appendix><section><section><screen>
-#: tools.dbk:452
+#. type: Content of: <appendix><section><section><screen>
+#: tools.dbk:432
#, no-wrap
-msgid ""
-"\n"
-"dpkg-depcheck -b debian/rules build\n"
+msgid "dpkg-depcheck -b debian/rules build\n"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:456
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:435
msgid ""
"<command>dpkg-depcheck</command> can also be used to check for run-time "
-"dependencies, especially if your package uses exec(2) to run other programs."
+"dependencies, especially if your package uses <citerefentry> "
+"<refentrytitle>exec</refentrytitle> <manvolnum>2</manvolnum> </citerefentry> "
+"to run other programs."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:460
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:441
msgid ""
-"For more information please see <citerefentry> "
-"<refentrytitle>dpkg-depcheck</refentrytitle> <manvolnum>1</manvolnum> "
-"</citerefentry>."
+"For more information please see <citerefentry> <refentrytitle>dpkg-depcheck</"
+"refentrytitle> <manvolnum>1</manvolnum> </citerefentry>."
msgstr ""
-# type: Content of: <appendix><section><title>
-#: tools.dbk:469
+#. type: Content of: <appendix><section><title>
+#: tools.dbk:450
msgid "Porting tools"
msgstr ""
-# type: Content of: <appendix><section><para>
-#: tools.dbk:471
+#. type: Content of: <appendix><section><para>
+#: tools.dbk:452
msgid "The following tools are helpful for porters and for cross-compilation."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:474
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:455
msgid "<systemitem role=\"package\">quinn-diff</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:476
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:457
msgid ""
"<systemitem role=\"package\">quinn-diff</systemitem> is used to locate the "
"differences from one architecture to another. For instance, it could tell "
-"you which packages need to be ported for architecture "
-"<replaceable>Y</replaceable>, based on architecture "
-"<replaceable>X</replaceable>."
+"you which packages need to be ported for architecture <replaceable>Y</"
+"replaceable>, based on architecture <replaceable>X</replaceable>."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:484
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:465
msgid "<systemitem role=\"package\">dpkg-cross</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:486
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:467
msgid ""
"<systemitem role=\"package\">dpkg-cross</systemitem> is a tool for "
"installing libraries and headers for cross-compiling in a way similar to "
"<systemitem role=\"package\">dpkg</systemitem>. Furthermore, the "
-"functionality of <command>dpkg-buildpackage</command> and "
-"<command>dpkg-shlibdeps</command> is enhanced to support cross-compiling."
+"functionality of <command>dpkg-buildpackage</command> and <command>dpkg-"
+"shlibdeps</command> is enhanced to support cross-compiling."
msgstr ""
-# type: Content of: <appendix><section><title>
-#: tools.dbk:497
+#. type: Content of: <appendix><section><title>
+#: tools.dbk:478
msgid "Documentation and information"
msgstr ""
-# type: Content of: <appendix><section><para>
-#: tools.dbk:499
+#. type: Content of: <appendix><section><para>
+#: tools.dbk:480
msgid ""
"The following packages provide information for maintainers or help with "
"building documentation."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:503
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:485
+msgid "<systemitem role=\"package\">docbook-xml</systemitem>"
+msgstr ""
+
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:487
+msgid ""
+"<systemitem role=\"package\">docbook-xml</systemitem> provides the DocBook "
+"XML DTDs, which are commonly used for Debian documentation (as is the older "
+"debiandoc SGML DTD). This manual, for instance, is written in DocBook XML."
+msgstr ""
+
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:493
+msgid ""
+"The <systemitem role=\"package\">docbook-xsl</systemitem> package provides "
+"the XSL files for building and styling the source to various output formats. "
+"You will need an XSLT processor, such as <systemitem role=\"package"
+"\">xsltproc</systemitem>, to use the XSL stylesheets. Documentation for the "
+"stylesheets can be found in the various <systemitem role=\"package\">docbook-"
+"xsl-doc-*</systemitem> packages."
+msgstr ""
+
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:501
+msgid ""
+"To produce PDF from FO, you need an FO processor, such as <systemitem role="
+"\"package\">xmlroff</systemitem> or <systemitem role=\"package\">fop</"
+"systemitem>. Another tool to generate PDF from DocBook XML is <systemitem "
+"role=\"package\">dblatex</systemitem>."
+msgstr ""
+
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:509
msgid "<systemitem role=\"package\">debiandoc-sgml</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:505
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:511
msgid ""
"<systemitem role=\"package\">debiandoc-sgml</systemitem> provides the "
-"DebianDoc SGML DTD, which is commonly used for Debian documentation. This "
-"manual, for instance, is written in DebianDoc. It also provides scripts for "
-"building and styling the source to various output formats."
+"DebianDoc SGML DTD, which is commonly used for Debian documentation, but is "
+"now deprecated (<systemitem role=\"package\">docbook-xml</systemitem> should "
+"be used instead). It also provides scripts for building and styling the "
+"source to various output formats."
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:511
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:520
msgid ""
-"Documentation for the DTD can be found in the <systemitem "
-"role=\"package\">debiandoc-sgml-doc</systemitem> package."
+"Documentation for the DTD can be found in the <systemitem role=\"package"
+"\">debiandoc-sgml-doc</systemitem> package."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:533
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:526
msgid "<systemitem role=\"package\">debian-keyring</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:535
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:528
msgid ""
"Contains the public GPG and PGP keys of Debian developers. See <xref "
"linkend=\"key-maint\"/> and the package documentation for more information."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:541
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:534
msgid "<systemitem role=\"package\">debian-maintainers</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:543
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:536
msgid ""
-"Contains the public GPG keys of Debian Maintainers. See <ulink "
-"url=\"&url-wiki-dm;\"></ulink> for more information."
+"Contains the public GPG keys of Debian Maintainers. See <ulink url=\"&url-"
+"wiki-dm;\"></ulink> for more information."
msgstr ""
-# type: Content of: <appendix><section><section><title>
-#: tools.dbk:549
+#. type: Content of: <appendix><section><section><title>
+#: tools.dbk:542
msgid "<systemitem role=\"package\">debview</systemitem>"
msgstr ""
-# type: Content of: <appendix><section><section><para>
-#: tools.dbk:551
+#. type: Content of: <appendix><section><section><para>
+#: tools.dbk:544
msgid ""
"<systemitem role=\"package\">debview</systemitem> provides an Emacs mode for "
"viewing Debian binary packages. This lets you examine a package without "