+"Some debhelper commands will automatically generate parts of Debian "
+"maintainer scripts. If you want these automatically generated things "
+"included in your existing Debian maintainer scripts, then you need to add "
+"B<#DEBHELPER#> to your scripts, in the place the code should be added. "
+"B<#DEBHELPER#> will be replaced by any auto-generated code when you run "
+"B<dh_installdeb>."
+msgstr ""
+
+#. type: textblock
+#: debhelper.pod:571
+msgid ""
+"If a script does not exist at all and debhelper needs to add something to "
+"it, then debhelper will create the complete script."
+msgstr ""
+
+#. type: textblock
+#: debhelper.pod:574
+msgid ""
+"All debhelper commands that automatically generate code in this way let it "
+"be disabled by the -n parameter (see above)."
+msgstr ""
+
+#. type: textblock
+#: debhelper.pod:577
+msgid ""
+"Note that the inserted code will be shell code, so you cannot directly use "
+"it in a Perl script. If you would like to embed it into a Perl script, here "
+"is one way to do that (note that I made sure that $1, $2, etc are set with "
+"the set command):"
+msgstr ""
+
+#. type: verbatim
+#: debhelper.pod:582
+#, no-wrap
+msgid ""
+" my $temp=\"set -e\\nset -- @ARGV\\n\" . << 'EOF';\n"
+" #DEBHELPER#\n"
+" EOF\n"
+" system ($temp) / 256 == 0\n"
+" \tor die \"Problem with debhelper scripts: $!\";\n"
+"\n"
+msgstr ""
+
+#. type: =head2
+#: debhelper.pod:588
+msgid "Automatic generation of miscellaneous dependencies."
+msgstr ""
+
+#. type: textblock
+#: debhelper.pod:590
+msgid ""
+"Some debhelper commands may make the generated package need to depend on "
+"some other packages. For example, if you use L<dh_installdebconf(1)>, your "
+"package will generally need to depend on debconf. Or if you use "
+"L<dh_installxfonts(1)>, your package will generally need to depend on a "
+"particular version of xutils. Keeping track of these miscellaneous "
+"dependencies can be annoying since they are dependent on how debhelper does "
+"things, so debhelper offers a way to automate it."
+msgstr ""
+
+#. type: textblock
+#: debhelper.pod:598
+msgid ""
+"All commands of this type, besides documenting what dependencies may be "
+"needed on their man pages, will automatically generate a substvar called "
+"B<${misc:Depends}>. If you put that token into your F<debian/control> file, "
+"it will be expanded to the dependencies debhelper figures you need."
+msgstr ""
+
+#. type: textblock
+#: debhelper.pod:603
+msgid ""
+"This is entirely independent of the standard B<${shlibs:Depends}> generated "
+"by L<dh_makeshlibs(1)>, and the B<${perl:Depends}> generated by "
+"L<dh_perl(1)>. You can choose not to use any of these, if debhelper's "
+"guesses don't match reality."
+msgstr ""
+
+#. type: =head2
+#: debhelper.pod:608
+msgid "Package build directories"
+msgstr ""
+
+#. type: textblock
+#: debhelper.pod:610
+msgid ""
+"By default, all debhelper programs assume that the temporary directory used "
+"for assembling the tree of files in a package is debian/I<package>."
+msgstr ""
+
+#. type: textblock
+#: debhelper.pod:613
+msgid ""
+"Sometimes, you might want to use some other temporary directory. This is "
+"supported by the B<-P> flag. For example, \"B<dh_installdocs "
+"-Pdebian/tmp>\", will use B<debian/tmp> as the temporary directory. Note "
+"that if you use B<-P>, the debhelper programs can only be acting on a single "
+"package at a time. So if you have a package that builds many binary "
+"packages, you will need to also use the B<-p> flag to specify which binary "
+"package the debhelper program will act on."