[TAF] po-debconf://diald/fr.po
Le paquet mentionné dans le sujet va bientôt utiliser po-debconf (je
viens de lancer un rapport de bogue, avec patch, pour cela).
Merci au volontaire de répondre à ce courriel avec un sujet
"[ITT] po-debconf://<paquet>/fr.po""
Comment procéder pour traduire :
-utiliser le fichier fr.po attaché à ce mail
-le mettre dans un répertoire chez vous, par exemple
~/traducs/po-debconf/TODO/[paquet]
-le copier sous le nom templates.pot (IMPORTANT, cela permet de garder
l'original)
-l'éditer et traduire, de préférence avec un outil dédié genre kbabel
ou poedit (ou emacs et son po-mode s'il ne vous enquiquine pas trop)
-ne pas oublier de remplir les champs :
Project-Id-Version: --> mettre ici le nom du paquet et sa version au
moment de la traduc est une bonne idée
Last-Translator: --> le plus souvent votre outil mettra tout seul
VOTRE adresse
Language-Team: --> mettez "French <debian-l10n-french@lists.debian.org>\n"
-envoyer le fichier ici pour relecture avec le sujet "[DDR] po-debconf ://<paquet>/fr.po
-une fois "suffisamment" de relectures envoyées et la synthèse faite,
postez un "[RELU] po-debconf ://<paquet>/fr.po" de préférence en
"réponse" à votre DDR
-envoyez alors un rapport de bogue à l'auteur du paquet. Ci-dessous
mon script "bug-switch-tr" à moi, à utiliser "bug-switch-tr <paquet>"
#!/bin/sh
reportbug --attach=fr.po --include="/home/bubulle/src/debian/translation/po/patch-trswitch.txt" --offline -s "$1: French translation of gettext debconf templates" --severity=wishlist --tags=patch --no-config-files --package-version="N/A" $1
Le contenu du fichier patch-trswitch.txt :
========================================================================
Please find attached the french debconf templates translation, proofread by the
debian-l10n-french mailing list contributors.
This file should be put as debian/po/fr.po in your package build tree
after applying the "please switch to gettext templates" patch which
was sent some time ago.
This patch assumes that you applied the previous patch without
modifications, particularly to the templates file. If you did not do so,
especially if the former patch suggested modifications to the *original*
templates files (fixed spelling, minor changes for respecting some
conventions, etc.) please notify me and send me the new templates.pot file
so that I may adapt my fr.po file.
========================================================================
--
#
# 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.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2003-08-30 06:47+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=CHARSET\n"
"Content-Transfer-Encoding: 8bit\n"
#. Description
#: ../templates:4
msgid "Should the ethertap devices be created?"
msgstr ""
#. Description
#: ../templates:4
msgid ""
"Diald needs a \"fake\" interface for the system to use when the dialup link "
"is down. The \"ethertap\" device is preferred for this, as it was designed "
"for this purpose. If ethertap is not available, the system sets up a fake "
"SLIP connection (the precursor to PPP) to accomplish this."
msgstr ""
#. Description
#: ../templates:4
msgid ""
"Ethertap devices, however, are not shipped with Debian by default. They can "
"be created for you as part of this package installation. It is optional, "
"but highly recommended."
msgstr ""
#. Description
#: ../templates:18
msgid "Which PPP configuration do you want to use?"
msgstr ""
#. Description
#: ../templates:18
msgid ""
"It seems you have configured several different dial-up providers on your "
"system. Diald can be configured to use any one of them at a time."
msgstr ""
#. Description
#: ../templates:18
msgid ""
"(If you see one labeled \"old-config\", it represents your old manual "
"configuration from an older diald package. You can select this option to "
"configure your system to use the old configuration.)"
msgstr ""
#. Description
#: ../templates:29
msgid "Should diald use the standard default IP addresses?"
msgstr ""
#. Description
#: ../templates:29
msgid ""
"When setting up a connection, diald requires that an IP address be "
"configured for both the local and remote sides, even if they aren't "
"initially known. If a pppconfig entry assumes that they will be "
"autoconfigured, diald will set these to the default IP addresses 192.168.0.1 "
"(local) and 192.168.0.2 (remote) initially, and pick up the proper values "
"after the first connection is made."
msgstr ""
#. Description
#: ../templates:29
msgid ""
"If you use the 192.168.0.x network, however, this could cause this network "
"to be unreachable for a short time after diald is started. If this is the "
"case, you should pick two other IP addresses that aren't in use. Ranges "
"from the private IP address ranges (192.168.x.x, 172.16.x.x, and 10.x.x.x) "
"are good candidates."
msgstr ""
#. Description
#: ../templates:45
msgid "Please enter the IP address to use as the local default."
msgstr ""
#. Description
#: ../templates:49
msgid "Please enter the IP address to use as the remote default."
msgstr ""
Reply to: