-#. type: Content of: <refentry><refsect1><refsect2><title>
-#: apt.conf.5.xml
-msgid "dpkg trigger usage (and related options)"
-msgstr ""
-
-#. type: Content of: <refentry><refsect1><refsect2><para>
-#: apt.conf.5.xml
-msgid ""
-"APT can call &dpkg; in such a way as to let it make aggressive use of "
-"triggers over multiple calls of &dpkg;. Without further options &dpkg; will "
-"use triggers once each time it runs. Activating these options can therefore "
-"decrease the time needed to perform the install or upgrade. Note that it is "
-"intended to activate these options per default in the future, but as it "
-"drastically changes the way APT calls &dpkg; it needs a lot more testing. "
-"<emphasis>These options are therefore currently experimental and should not "
-"be used in production environments.</emphasis> It also breaks progress "
-"reporting such that all front-ends will currently stay around half (or more) "
-"of the time in the 100% state while it actually configures all packages."
-msgstr ""
-
-#. type: Content of: <refentry><refsect1><refsect2><para><literallayout>
-#: apt.conf.5.xml
-#, no-wrap
-msgid ""
-"DPkg::NoTriggers \"true\";\n"
-"PackageManager::Configure \"smart\";\n"
-"DPkg::ConfigurePending \"true\";\n"
-"DPkg::TriggersPending \"true\";"
-msgstr ""
-
-#. type: Content of: <refentry><refsect1><refsect2><para>
-#: apt.conf.5.xml
-msgid ""
-"Note that it is not guaranteed that APT will support these options or that "
-"these options will not cause (big) trouble in the future. If you have "
-"understand the current risks and problems with these options, but are brave "
-"enough to help testing them, create a new configuration file and test a "
-"combination of options. Please report any bugs, problems and improvements "
-"you encounter and make sure to note which options you have used in your "
-"reports. Asking &dpkg; for help could also be useful for debugging proposes, "
-"see e.g. <command>dpkg --audit</command>. A defensive option combination "
-"would be <placeholder type=\"literallayout\" id=\"0\"/>"
-msgstr ""
-
-#. type: Content of: <refentry><refsect1><refsect2><variablelist><varlistentry><listitem><para>
-#: apt.conf.5.xml
-msgid ""
-"Add the no triggers flag to all &dpkg; calls (except the ConfigurePending "
-"call). See &dpkg; if you are interested in what this actually means. In "
-"short: &dpkg; will not run the triggers when this flag is present unless it "
-"is explicitly called to do so in an extra call. Note that this option "
-"exists (undocumented) also in older APT versions with a slightly different "
-"meaning: Previously these option only append --no-triggers to the configure "
-"calls to &dpkg; - now APT will also add this flag to the unpack and remove "
-"calls."
-msgstr ""
-
-#. type: Content of: <refentry><refsect1><refsect2><variablelist><varlistentry><listitem><para>
-#: apt.conf.5.xml
-msgid ""
-"Valid values are \"<literal>all</literal>\", \"<literal>smart</literal>\" "
-"and \"<literal>no</literal>\". The default value is \"<literal>all</literal>"
-"\", which causes APT to configure all packages. The \"<literal>smart</"
-"literal>\" way is to configure only packages which need to be configured "
-"before another package can be unpacked (Pre-Depends), and let the rest be "
-"configured by &dpkg; with a call generated by the ConfigurePending option "
-"(see below). On the other hand, \"<literal>no</literal>\" will not configure "
-"anything, and totally relies on &dpkg; for configuration (which at the "
-"moment will fail if a Pre-Depends is encountered). Setting this option to "
-"any value other than <literal>all</literal> will implicitly also activate "
-"the next option by default, as otherwise the system could end in an "
-"unconfigured and potentially unbootable state."
-msgstr ""
-
-#. type: Content of: <refentry><refsect1><refsect2><variablelist><varlistentry><listitem><para>