-"tarball, or to add binary files that are not in it. If this is done by "
-"simply copying the files into the debianized source tree, "
-"<command>dpkg-source</command> will not be able to handle this. On the "
-"other hand, according to the guidelines given above, you cannot include such "
-"a changed binary file in a repackaged <filename>orig.tar.gz</filename>. "
-"Instead, include the file in the <filename>debian</filename> directory in "
-"<command>uuencode</command>d (or similar) form <footnote>"
-msgstr ""
-
-# type: Content of: <chapter><section><section><section><para><footnote><para>
-#: best-pkging-practices.dbk:1667
-msgid ""
-"The file should have a name that makes it clear which binary file it "
-"encodes. Usually, some postfix indicating the encoding should be appended "
-"to the original filename. Note that you don't need to depend on <systemitem "
-"role=\"package\">sharutils</systemitem> to get the "
-"<command>uudecode</command> program if you use <command>perl</command>'s "
-"<literal>pack</literal> function. The code could look like"
-msgstr ""
-
-# type: Content of: <chapter><section><section><section><para><footnote><screen>
-#: best-pkging-practices.dbk:1673
-#, no-wrap
-msgid ""
-"-file: perl -ne 'print(pack u, $$_);'\n"
-"$(file) > $(file).uuencoded uudecode-file: perl -ne 'print(unpack u, "
-"$$_);'\n"
-"$(file).uuencoded > $(file)"
-msgstr ""
-
-# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1675
-msgid ""
-"</footnote>. The file would then be decoded and copied to its place during "
-"the build process. Thus the change will be visible quite easy."
-msgstr ""
-
-# type: Content of: <chapter><section><section><section><para>
-#: best-pkging-practices.dbk:1680
-msgid ""
-"Some packages use <command>dbs</command> to manage patches to their upstream "
-"source, and always create a new <literal>orig.tar.gz</literal> file that "
-"contains the real <literal>orig.tar.gz</literal> in its toplevel directory. "
-"This is questionable with respect to the preference for pristine source. On "
-"the other hand, it is easy to modify or add binary files in this case: Just "
-"put them into the newly created <literal>orig.tar.gz</literal> file, besides "
-"the real one, and copy them to the right place during the build process."
-msgstr ""
-
-# type: Content of: <chapter><section><section><title>
-#: best-pkging-practices.dbk:1693
+"tarball, or to add binary files that are not in it. This is fully supported "
+"when using source packages in “3.0 (quilt)” format, see the "
+"<citerefentry><refentrytitle>dpkg-source</refentrytitle><manvolnum>1</manvolnum></citerefentry> "
+"manual page for details. When using the older format “1.0”, binary files "
+"can't be stored in the <filename>.diff.gz</filename> so you must store an "
+"<command>uuencode</command>d (or similar) version of the file(s) and decode "
+"it at build time in <filename>debian/rules</filename> (and move it in its "
+"official location)."
+msgstr ""
+
+#. type: Content of: <chapter><section><section><title>
+#: best-pkging-practices.dbk:1853