Le paquet openldap2 utilise po-debconf et sa traduction est
devenue incomplète.
#####################################
Utiliser le fichier attaché, les templates ont été modifiés sans inclure
la traduction dans #237100
#####################################
Ce message (non automatique) est destiné à avertir le dernier traducteur
qu'une petite mise à jour est nécessaire.
En effet, les statistiques de traduction de ce fichier sont désormais:
3f20u
où:
-t : nombre de chaînes traduites
-f : nombre de chaînes floues (fuzzy), donc traduites par analogie
mais à contrôler
-u : nombre de chaînes non traduites
Si aucun message [ITT] n'est publié par ce dernier traducteur dans un délai
d'une semaine, un autre traducteur peut prendre en charge la mise à jour.
Dans ce dernier cas, merci de bien veiller à garder le traducteur d'origine
mentionné dans le fichier corrigé.
Comment procéder pour mettre à jour :
-récupérer le fichier incomplet depuis
http://www.debian.org/intl/l10n/po-debconf/fr
-le mettre à jour
-envoyer le fichier ici pour relecture avec le sujet
[RFR] po-debconf://openldap2/fr.po
Si vous jugez que les modifications étaient triviales, vous pouvez vous
dispenser de la relecture
-une fois "suffisamment" de relectures envoyées et la synthèse faite,
postez un
[LCFC] po-debconf://openldap2/fr.po
de préférence en réponse à votre RFR
-envoyez alors un rapport de bogue à l'auteur du paquet. Ci-dessous
le script "bug-update" à bubulle, à utiliser "bug-update openldap2"
#!/bin/sh
reportbug --attach=fr.po \
--include="/home/bubulle/src/debian/translation/podeb/patch-update.txt" \
--offline -s "$1: French debconf templates translation update" \
--severity=wishlist --tag=patch --tag=l10n --no-config-files \
--package-version="N/A" $1
Le contenu du fichier patch-update.txt :
========================================================================
Please find attached the French debconf templates translation update,
proofread by the debian-l10n-french mailing list contributors.
========================================================================
Une fois reçu le numéro du bogue postez une dernière fois dans
debian-l10n-french un mail avec le sujet
[BTS] po-debconf://openldap2/fr.po #xxxxxx
où xxxxxx est le numéro du bogue.
Ces informations sont destinées à renseigner le suivi automatique de
l'avancement des traductions :
http://haydn.debian.org/~thuriaux-guest/dlf/
--
Thomas Huriaux
# # Translators, if you are not familiar with the PO format, gettext # documentation is worth reading, especially sections dedicated to # this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # # Some information specific to po-debconf are available at # /usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans # # Developers do not need to manually edit POT or PO files. # msgid "" msgstr "" "Project-Id-Version: openldap2\n" "Report-Msgid-Bugs-To: torsten@debian.org\n" "POT-Creation-Date: 2006-04-30 13:25+0200\n" "PO-Revision-Date: 2004-03-09 18:51+0100\n" "Last-Translator: Christian Perrier <bubulle@debian.org>\n" "Language-Team: French <debian-l10n-french@lists.debian.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ISO-8859-15\n" "Content-Transfer-Encoding: 8bit\n" #. Type: boolean #. Description #: ../slapd.templates:4 msgid "Do you want to omit the configuration of slapd?" msgstr "" #. Type: boolean #. Description #: ../slapd.templates:4 msgid "" "If you choose yes here, no default configuration or database will be created." msgstr "" #. Type: boolean #. Description #: ../slapd.templates:11 msgid "Move old database" msgstr "" #. Type: boolean #. Description #: ../slapd.templates:11 msgid "" "There are still files in /var/lib/ldap which will probably break the " "configuration process. With this option enabled the maintainer scripts will " "move the old database files out of the way before creating a new database." msgstr "" #. Type: boolean #. Description #: ../slapd.templates:20 msgid "Retry configuration" msgstr "" #. Type: boolean #. Description #: ../slapd.templates:20 msgid "" "The configuration you entered is invalid. Make sure that the DNS domain name " "has a valid syntax, the organization is not left empty and that the admin " "passwords match. If you decide not to retry the configuration the LDAP " "server will not be set up. Run dpkg-reconfigure if you want to retry later." msgstr "" #. Type: string #. Description #: ../slapd.templates:28 #, fuzzy msgid "Enter your DNS domain name" msgstr "Nom de domaine :" #. Type: string #. Description #: ../slapd.templates:28 #, fuzzy msgid "" "The DNS domain name is used to construct the base DN of your LDAP directory. " "Entering foo.bar.org will give you the base DN dc=foo, dc=bar, dc=org." msgstr "" "Le nom de domaine sert à construire le nom de répertoire de base (« base " "DN ») de votre serveur LDAP. Par exemple, « foo.bar.org » génère le nom de " "répertoire de base « dc=foo, dc=bar, dc=org »." #. Type: string #. Description #: ../slapd.templates:34 msgid "Enter the name of your organization" msgstr "Nom de votre organisation :" #. Type: string #. Description #: ../slapd.templates:34 msgid "" "Whatever you enter here will be stored as the name of your organization in " "the base DN of your LDAP directory." msgstr "" "Ce que vous indiquez ici deviendra le nom de votre organisation dans le " "répertoire de base de votre serveur LDAP." #. Type: string #. Description #: ../slapd.templates:40 msgid "Admin entry" msgstr "Entrée d'administration :" #. Type: string #. Description #: ../slapd.templates:40 msgid "" "The admin entry is the entry in the directory which has full read and write " "access." msgstr "" "L'entrée d'administration est l'entrée possédant les droits de lire et " "écrire dans le répertoire." #. Type: password #. Description #: ../slapd.templates:46 msgid "Admin password" msgstr "Mot de passe de l'administrateur :" #. Type: password #. Description #: ../slapd.templates:46 msgid " Please enter the password for the admin entry in your LDAP directory." msgstr "" "Veuillez indiquer le mot de passe de l'administrateur du répertoire LDAP." #. Type: password #. Description #: ../slapd.templates:51 msgid "Verify password" msgstr "Vérification du mot de passe :" #. Type: password #. Description #: ../slapd.templates:51 msgid "" "Please reenter the admin password for your LDAP directory for verification." msgstr "" "Veuillez indiquer à nouveau, pour vérification, le mot de passe de " "l'administrateur du répertoire LDAP." #. Type: note #. Description #: ../slapd.templates:57 msgid "passwords do not match" msgstr "Les mots de passe ne sont pas les mêmes" #. Type: note #. Description #: ../slapd.templates:57 msgid "" "You need to enter the admin password twice. Please note that differences " "such as uppercase/lowercase and added whitespace matter." msgstr "" "Vous devez indiquer le mot de passe deux fois. Veuillez noter que les " "différences de casse (majuscule/minuscule) et les espaces importent." #. Type: boolean #. Description #: ../slapd.templates:64 msgid "Do you want your database to be removed when slapd is purged?" msgstr "Faut-il supprimer la base de données quand le paquet slapd est purgé ?" #. Type: password #. Description #: ../slapd.templates:68 msgid "encrypted admin password" msgstr "Mot de passe chiffré de l'administrateur :" #. Type: boolean #. Description #: ../slapd.templates:73 msgid "Change configuration to load backend modules" msgstr "" "Faut-il changer la configuration du chargement de modules d'interfaces ?" #. Type: boolean #. Description #: ../slapd.templates:73 #, fuzzy msgid "" "With OpenLDAP 2.1 backends are not longer built into the server but are " "instead dynamically loaded at startup. This means that the slapd " "configuration has to be changed to load the modules for the backends you are " "using. If you select this option I'll try to fix the configuration for you. " "If you don't select this then you *must* fix your configuration file " "yourself or slapd (and slapcat if you are upgrading from an older version) " "will fail and the package will not be installed. For more information " "read /usr/share/doc/slapd/README.Debian." msgstr "" "À partir d'OpenLDAP 2.1, les interfaces (« backends ») ne sont plus " "présentes dans le serveur mais chargées dynamiquement au démarrage. Cela " "signifie que la configuration de slapd doit être modifiée pour charger les " "modules des interfaces que vous utilisez. Si vous choisissez cette option, " "la configuration sera corrigée automatiquement. Dans le cas contraire, vous " "*devrez* la corriger vous-même sinon slapd ne fonctionnera pas (ainsi que " "slapcat si vous effectuez une mise à jour depuis une ancienne version) et le " "paquet ne sera pas installé. Pour plus d'informations, veuillez consulter /" "usr/share/doc/slapd/README.Debian." #. Type: boolean #. Description #: ../slapd.templates:86 msgid "Allow LDAPv2 protocol" msgstr "" #. Type: boolean #. Description #: ../slapd.templates:86 msgid "" "slapd now defaults to having the old LDAPv2 protocol not allowed. Programs " "and users are generally expected to be upgraded to LDAPv3. If you have old " "programs which have not been moved to use LDAPv3 and you still need LDAPv2 " "support then select this option and 'allow bind_v2' will be added to your " "slapd.conf to tell slapd to accept LDAPv2 connections." msgstr "" #. Type: boolean #. Description #: ../slapd.templates:97 msgid "Fix LDAP directory on upgrade" msgstr "Faut-il corriger le répertoire LDAP lors de la mise à jour ?" #. Type: boolean #. Description #: ../slapd.templates:97 msgid "" "The installation scripts of the old OpenLDAP 2.0 packages create a directory " "that does not conform to the ldap schema. The new version is more strict " "about this and you won't be able to access your directory after the upgrade " "without fixing it. If you select this option I'll try to fix it for you " "automagically." msgstr "" "Les scripts d'installation des anciens paquets d'OpenLDAP 2.0 créaient un " "répertoire non conforme au schéma LDAP. La nouvelle version ne tolère plus " "cela et vous ne pourrez plus accéder à votre répertoire après la mise à jour " "si cela n'est pas corrigé. Si vous choisissez cette option, une correction " "automatique sera tentée." #. Type: boolean #. Description #: ../slapd.templates:107 msgid "Move aside current database and create a new one?" msgstr "" #. Type: boolean #. Description #: ../slapd.templates:107 msgid "" "You have specified a directory suffix (domain) that doesn't match the one " "currently in /etc/ldap/slapd.conf. Changing the directory suffix requires " "moving aside the current LDAP database and creating a new one. Are you sure " "you want to abandon the current database? (A backup will be made.)" msgstr "" #. Type: note #. Description #: ../slapd.templates:116 msgid "slapcat failed during upgrade" msgstr "" #. Type: note #. Description #: ../slapd.templates:116 msgid "" "When attempting to upgrade your LDAP directory there was an error. This " "error occured when performing the 'slapcat' which attempts to extract your " "LDAP directory. This failure could be because of an incorrect config file. " "For example, if the appropriate moduleload lines for your backend database " "type are missing. This failure will cause 'slapadd' later to fail too. The " "old database files are about to be moved to /var/backups. If you want to " "try this upgrade again then move the old database files back into place, fix " "whatever caused slapcat to fail, and run: slapcat | /usr/share/slapd/" "fix_ldif -w -o \"$organization\" > $location Move the database files back to " "a backup area and then try and slapadd from $location." msgstr "" #. Type: note #. Description #: ../slapd.templates:132 msgid "slapadd failed during upgrade" msgstr "" #. Type: note #. Description #: ../slapd.templates:132 msgid "" "When attempting to upgrade your LDAP directory there was an error. This " "error occured when performing the 'slapadd' which attempts to populate an " "empty new LDAP directory using the information from your original LDAP " "directory. Your original LDAP directory files have been saved in /var/" "backups. The results of the attempted upgrade is the ldif file in /var/" "backups. slapadd may have failed due to a configuration problem (in which " "case slapcat would have failed too) or due to a problem in the ldif. If the " "problem was with the ldif then you may be able to fix it and attempt the " "slapadd again." msgstr "" #. Type: note #. Description #: ../slapd.templates:145 msgid "Slave databases require updateref option" msgstr "" #. Type: note #. Description #: ../slapd.templates:145 msgid "" "In your slapd configuration file at least one database is configured as " "slave, and the updateref option is not set. The updateref option specifies " "the referral(s) to pass back when slapd is asked to modify a replicated " "local database. See slapd.conf(5) for more details." msgstr "" #. Type: note #. Description #: ../slapd.templates:145 msgid "" "Starting with version 2.1.23, slapd requires the updateref option to be set " "on slaves. You should make sure to fix your slapd.conf configuration file." msgstr "" #. Type: select #. Description #: ../slapd.templates:160 msgid "Which database backend would you like to use?" msgstr "" #. Type: select #. Description #: ../slapd.templates:160 msgid "" "While the BDB backend is the recommended choice of the OpenLDAP developers, " "the LDBM backend has proven to be more reliable for some Debian users, " "especially when the BDB database wasn't properly configured. When using the " "BDB backend, make sure to do so. For information on how to tune BDB, see " "http://www.openldap.org/faq/data/cache/893.html."; msgstr "" #. Type: select #. Description #: ../slapd.templates:160 msgid "" "The BDB backend (back-bdb) and LDBM backend (back-ldbm) are comparable in " "purpose and back-bdb evolved from experience gained from back-ldbm, but the " "two are quite distinct today. They both store entries based on a 32-bit " "entry ID key, and they use a dn2id table to map from DNs to entry IDs. They " "both perform attribute indexing using the same code, and store index data as " "lists of entry IDs. As such, the LDAP-specific features they offer are " "nearly identical. The differences are in the APIs used to implement the " "databases. back-ldbm uses a generic database API that can plug into several " "different database packages. In Debian, it's built against BerkeleyDB (BDB). " "While BerkeleyDB supports this generic interface, it also offers a much " "richer API that has a lot more power and a lot more complexity. back-bdb is " "written specifically for the full BDB API, and uses some of BDB's more " "advanced features to offer transaction processing, fine grained locking, and " "other features that offer improved concurrency and reliability. For more " "information, see http://www.openldap.org/faq/data/cache/756.html."; msgstr ""
Attachment:
signature.asc
Description: Digital signature