Package: tiger Version: N/A Severity: wishlist Tags: patch l10n Please find attached the french debconf templates update, proofread by the debian-l10n-french mailing list contributors.
If you do not already use it, you might consider using the "podebconf-report-po" utility, which helps warning translators about changes when you modify some debconf templates in your packages. The usual policy when using it is sending a warning to translators when you plan to upload a version of your package with debconf templates changes (even typo corrections). Then leave about one week for them to update their files (several translation teams have a QA process which requires time). podebconf-report-po will take care of sending the translators the needed material as well as getting the translators adresses from the PO files. All you have to do is just using the utility..:-) Example use (from your package build tree): $ podebconf-report-po This will go through debian/po/*.po files, find those needing an update, extract the translators data from these files and prepare a mail to send to these translators (you can also use the "--languageteam" switch to also mail the mail addresses listed in "Language-Team" field). You can also use this utility to request for new translations: $ podebconf-report-po --call This will send a mail to [email protected] with all the needed information and material for new translators to add new languages to your supported languages. If you apply this policy, please forget about these remarks, of course....This message is generic..:-) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
# Translation of tiger debconf templates to French # Copyright (C) 2003 Debian french l10n team <[email protected]> # This file is distributed under the same license as the tiger package. # # Contributors to this translation work: # Nicolas Bertolissio <[email protected]>, 2003 msgid "" msgstr "" "Project-Id-Version: tiger 1:3.2.1-2\n" "Report-Msgid-Bugs-To: [email protected]\n" "POT-Creation-Date: 2010-01-02 01:05+0100\n" "PO-Revision-Date: 2003-10-31 15:51+0100\n" "Last-Translator: Nicolas Bertolissio <[email protected]>\n" "Language-Team: French <[email protected]>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" #. Type: string #. Description #: ../templates:1001 msgid "Recipient of the daily mails:" msgstr "Destinataire des courriels quotidiens :" #. Type: string #. Description #: ../templates:1001 msgid "" "The user you enter below will receive all the emails that 'tiger' sends " "during the day when running the cron jobs. This does not mean that when " "executing the 'tiger' program standalone this user will receive the reports. " "Also note that any administrator will be able to access the reports since " "they are available in the /var/log/tiger/ directory." msgstr "" "L'utilisateur que vous indiquerez recevra tous les courriels envoyés par " "« tiger » lors de l'exécution des tâches périodiques. Cet utilisateur ne " "recevra pas les rapports lors de l'exécution directe du programme « tiger ». " "Veuillez aussi noter que tout administrateur pourra accéder aux rapports " "puisqu'ils seront disponibles dans le répertoire /var/log/tiger/." #. Type: note #. Description #: ../templates:2001 msgid "Take a minute to customize 'tiger'" msgstr "Prenez le temps de personnaliser « tiger »" #. Type: note #. Description #: ../templates:2001 msgid "" "You should customize the files at /etc/tiger/ to adapt to your local " "security policy. Firstly, customizing the kind of checks that will be made " "in this system, as well as the information needed for tests in order to " "reduce false positives (in /etc/tiger/tigerrc). Secondly, customizing at " "what times these tests will be executed (in /etc/tiger/cronrc). And thirdly, " "since some modules warnings might not be problems regarding your current " "security policy, define a given template file at /etc/tiger/templates/ using " "runs from each of the modules. Once defined, all the runs will be checked " "against each one of the templates available (one per module) and only new " "warnings will be issued." msgstr "" "Vous devriez personnaliser les fichiers dans /etc/tiger/ pour les adapter à " "votre politique de sécurité locale. Commencez par personnaliser (dans /etc/" "tiger/tigerrc) les vérifications qui sont faites sur le système, ainsi que " "les informations nécessaires aux tests. Cela permettra de réduire le nombre " "de faux positifs. Ensuite, personnalisez (dans /etc/tiger/cronrc) l'heure à " "laquelle ces tests sont exécutés. Puis, si les avertissements de certains " "modules peuvent être ignorés au regard de votre politique de sécurité " "actuelle, définissez un fichier de modèle dans /etc/tiger/templates/ après " "avoir utilisé chaque module. Par la suite, après chaque exécution, le " "résultat sera comparé à ces fichiers de modèles et seuls les nouveaux " "avertissements seront signalés." #~ msgid "Remove templates in buggy 'tiger' versions" #~ msgstr "Supprimer les modèles des versions boguées de « tiger » ?" #~ msgid "" #~ "Initially Debian's 3.1 tiger versions were distributed with a bug that " #~ "would cause templates to be created under /var/log/ instead of /var/log/" #~ "tiger/. Normal operation assumes templates are under /var/log/tiger/ and " #~ "these templates will not be useful in newer Tiger versions. You might " #~ "want to preserve a copy of them (to use as templates) and move them " #~ "manually under their proper location. The package will not do this " #~ "automatically in order to avoid removing previous templates. Should we " #~ "remove these files if any are found?" #~ msgstr "" #~ "Les versions 3.1 de Tiger initialement distribuées dans Debian créaient " #~ "les modèles dans /var/log/ au lieu de /var/log/tiger/. Le fonctionnement " #~ "normal suppose que les modèles sont dans /var/log/tiger/. Les modèles " #~ "situés dans /var/log ne seront pas utilisés par les versions de Tiger " #~ "plus récentes. Vous pouvez souhaiter en conserver une copie (pour servir " #~ "de référence) et les déplacer manuellement au bon endroit. Cela ne sera " #~ "pas effectué automatiquement pour éviter de supprimer les modèles " #~ "précédents. Cette option permet de supprimer ces anciens fichiers s'ils " #~ "existent."
