# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
-#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: 2013-07-20 10:33+0000\n"
-"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"PO-Revision-Date: 2013-07-20 20:07+0900\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: 8bit\n"
+"X-Generator: Poedit 1.5.4\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta date=\"Sat, 20 Jul 2013 19:30:49 +0900\"]]\n"
-msgstr ""
+msgstr "[[!meta date=\"Sat, 20 Jul 2013 19:30:49 +0900\"]]\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta updated=\"Sat, 20 Jul 2013 19:30:49 +0900\"]]\n"
-msgstr ""
+msgstr "[[!meta updated=\"Sat, 20 Jul 2013 19:30:49 +0900\"]]\n"
#. type: Plain text
#, no-wrap
msgid "[[!tag Debian]]\n"
-msgstr ""
+msgstr "[[!tag Debian]]\n"
#. type: Plain text
#, no-wrap
msgid "[[!meta title=\"Les _triggers_ de Dpkg et RPM : comparaison.\"]]\n"
-msgstr ""
+msgstr "[[!meta title=\"_triggers_ in Dpkg and RPM: a comparaison.\"]]\n"
#. type: Plain text
msgid ""
"connais pas de traductions pour RPM, et la version française ne "
"s'appliquerait pas bien, pour les raisons qui suivent."
msgstr ""
+"Dpkg and RPM provide a mechanism called _[[triggers]]_. But is it doing the "
+"same thing?"
#. type: Plain text
msgid ""
"`desktop-file-utils`, qui fera le nécessaire pour ajouter une entrée dans le "
"système de menu de l'interface graphique."
msgstr ""
+"There are two different types of _triggers_ for Dpkg: _explicit_ and "
+"_file_. In the case of _explicit triggers_, the script of a package A will "
+"activate a package B. The _file_ type is more frequently used. In that "
+"case, the creation, modification or deletion of a file in a path declared by "
+"a package B will activate the package B. The _triggers_ are often used when "
+"a package _A_ has to register an information to a package B. For instance, "
+"when a graphical application is installed, its package will add its "
+"description in the `/usr/share/applications` directory, which will trigger "
+"the `desktop-file-utils` package, which will do what is necessary to add a "
+"new menu entry in the window manager."
#. type: Plain text
msgid ""
"jour ou le retrait d'un paquet A va activer un paquet B si le paquet B "
"déclare son intérêt pour le paquet A dans son fichier _SPEC_ (en mettant des "
"conditions sur la version du paquet A si nécessaire). Les documentations de "
-"[RPM](http://rpm.org/api/4.4.2.2/triggers.html) et de "
-"[Fedora](http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s02.html) "
-"donnent quelques exemples d'utilisation, comme la mise à jour de liens "
-"symboliques lors du remplacement d'un serveur de courriels par un autre."
+"[RPM](http://rpm.org/api/4.4.2.2/triggers.html) et de [Fedora](http://docs."
+"fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/"
+"ch10s02.html) donnent quelques exemples d'utilisation, comme la mise à jour "
+"de liens symboliques lors du remplacement d'un serveur de courriels par un "
+"autre."
msgstr ""
+"RPM's _triggers_ function differently. The installation, update or removal "
+"of a package A will activate a package B if this package B declares its "
+"interest for the package A in its _SPEC_ file (with possible restrictions on "
+"package A's version). The documentation of [RPM](http://rpm.org/api/4.4.2.2/"
+"triggers.html) and [Fedora](http://docs.fedoraproject.org/en-US/"
+"Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch10s02.html) gives a few "
+"examples of use, like the update of symbolic links when one mail server is "
+"replaced by aonther."
#. type: Plain text
msgid ""
"cas de RPM, les _triggers_ semblent plus spécialisées, puisqu'elles "
"concernent à chaque instance la relation entre deux paquets."
msgstr ""
+"Altogether, despite both mechanisms have the same name, they do not have the "
+"same goal. In the case of Dpkg, the _triggers_ are especially useful to "
+"group similar actions. For instance, to update the list of manual pages "
+"once after installing a hundred of packages, instead of a hundred of times, "
+"after installing each package. They are also useful to transfer commands "
+"from a large number of packages to a central one, thus easing the evolution "
+"of the system. In the case of RPM, the _triggers_ seem more specialised, as "
+"they always are about the relationship between a pair of packages."