[TAF] po-debconf://lirc/fr.po
Le paquet lirc utilise po-debconf mais les écrans
debconf ne sont pas encore traduits en français.
Merci au volontaire de répondre à ce courriel avec un sujet
"[ITT] po-debconf://lirc/fr.po""
Comment procéder pour traduire :
-récupérer le fichier templates.pot depuis
http://people.debian.org/~pmachard/intl/l10n/po-debconf/pot#lirc
(il sera disponible demain), utilisez le fichier joint à ce message en
attendant.
-le mettre dans un répertoire chez vous, par exemple
~/traducs/po-debconf/TODO/lirc
-le copier sous le nom fr.po (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 "[RFR] po-debconf ://lirc/fr.po
-une fois "suffisamment" de relectures envoyées et la synthèse faite,
postez un "[LCFC] po-debconf ://lirc/fr.po" de préférence en
"réponse" à votre RFR
-envoyez alors un rapport de bogue à l'auteur du paquet. Ci-dessous
mon script "bug-trad" à moi, à utiliser "bug-trad lirc"
#!/bin/sh
reportbug --attach=fr.po --include="/home/bubulle/src/debian/translation/po/patch-translate.txt" --offline -s "$1: French debconf templates translation" --severity=wishlist --tag=patch --tag=l10n --no-config-files --package-version="N/A" $1
Le contenu du fichier patch-translate.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.
========================================================================
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://lirc/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://people.debian.org/~bertol/
Signification des abréviations utilisées sur debian-l10n-french:
[TAF] : « Traduction A Faire ». Ce message indique que tel ou tel
document est à traduire
[ITT] : « Intent To Translate » ou Intention de Traduire
Le document mentionné va etre traduit par l'émetteur de ce
courriel
Il devient « propriétaire » de la traduction
[RFR] : « Request For Review » ou Demande de relecture (DDR)
Le traducteur demande à qui le veut bien de relire ce document
Merci de fournir ensuite un fichier diff unifié de préférence
et de placer votre relecture en réponse au RFR, dans la liste
[LCFC]: « Last Chance For Comments » ou Derniers Commentaires (RELU)
Le traducteur va bientot envoyer ou "commiter" cette traduction
Depechez-vous si vous avez des modifications a suggérer
[BTS] : « Bug Tracking System » ou Système de Gestion des bogues
C'est un message purement technique pour les robots de tenue de
statistiques : le traducteur a créé un bogue avec cette traduction
La traduction n'est en général pas jointe au message
[DONE]: Travail terminé sur ce document
C'est un message purement technique pour les robots de tenue de
statistiques : la traduction a en fait été intégrée. Pas la peine de
le faire quand un BTS existe car le robot d'analyse le fera lui-meme
Ce marqueur est utilisé dans des cas particuliers où il est
nécessaire de "fermer" un travail en cours.
Les pseudo-URLs:
On désigne les documents sous forme de pseudo-URL:
type://document/lang.po
type:
po : traduction des messages d'un programme
po-debconf : traduction des écrans debconf d'un paquet Debian
man : traduction d'une page de manuel
document:
c'est souvent le nom du paquet ou celui de la page WWW
lang:
c'est la langue...donc en général "fr" pour le français
#
# 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: 2004-02-11 10:27-0800\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"
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid "Select drivers to build."
msgstr ""
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid ""
"i2c: TV cards from Hauppauge and PixelView. Needs the new I2C stack (present "
"on 2.4 kernels). You can get it at:"
msgstr ""
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid "http://www2.lm-sensors.nu/~lm78/.";
msgstr ""
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid ""
"gpio: TV cards from FlyVideo98, Avermedia, MiRO and many others. Needs bttv "
"version 0.7.45 or higher (present on 2.4 kernels). If you are using the "
"bttv tarball, copy it to the kernel."
msgstr ""
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid "parallel: Custom parallel-port receiver."
msgstr ""
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid "serial: Serial-port driver."
msgstr ""
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid "sir: Serial InfraRed (IRDA)."
msgstr ""
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid "it87: ITE IT8705 and IT8712 CIR ports (e.g. on the ECS K7S5A)."
msgstr ""
#. Type: multiselect
#. Description
#: ../lirc-modules-source.templates:5
msgid "bt829: Tekram M230 Mach64"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc-modules-source.templates:28
msgid "Should I try to automagically select support for your hardware?"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc-modules-source.templates:28
msgid ""
"You have installed and configured LIRC. I can try to guess what kernel "
"modules are needed and their parameters from your previous answers."
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:34
msgid "You don't need any aditional kernel modules."
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:34
msgid ""
"Unless you want to build LIRC kernel modules for some other system, you can "
"probably remove this package."
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:40
msgid "How to build the binary modules package."
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:40
msgid ""
"For instruction on how to build the binary modules debian package read: /usr/"
"share/doc/lirc-modules-source/README.Debian"
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:40
msgid "Quick walktrough:"
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:40
msgid "cd /usr/src/"
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:40
msgid "tar -xzf lirc-modules.tar.gz"
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:40
msgid "cd modules/lirc"
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:40
msgid "debian/rules binary-modules KSRC=/path/of/my/kernel/source/"
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:40
msgid "dpkg -i ../lirc-modules-*.deb"
msgstr ""
#. Type: select
#. Choices
#: ../lirc-modules-source.templates:58
msgid "ANIMAX, IRDEO, Other"
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:60
msgid "What type of serial device should be supported?"
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:60
msgid ""
"The following list includes short descriptions of the different options "
"available:"
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:60
msgid "ANIMAX: Anir Multimedia Magic"
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:60
msgid "IRDEO: IRdeo"
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:60
msgid ""
"If you don't know what the other devices are, you should probably choose "
"\"Other\"."
msgstr ""
#. Type: boolean
#. Description
#: ../lirc-modules-source.templates:76
msgid "Is your serial IR device a transmitter?"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc-modules-source.templates:81
msgid "Should the carrier signal be generated by software?"
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:86
msgid "Which IO port is your IR serial device using?"
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:91
msgid "Which IRQ is your IR serial device using?"
msgstr ""
#. Type: select
#. Choices
#: ../lirc-modules-source.templates:95
msgid "ACTISYS_ACT200L, TEKRAM, Other"
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:97
msgid "What type of SIR device should be supported?"
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:97
msgid ""
"The following lists are short descriptions of the options to show what they "
"mean."
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:97
msgid "ACTISYS_ACT200L: Actisys Act200L dongle."
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:97
msgid "TEKRAM: Tekram Irmate 210 (16x50 UART compatible serial port)"
msgstr ""
#. Type: select
#. Description
#: ../lirc-modules-source.templates:97
msgid "Other: Any other supported device."
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:110
msgid "Which IO port is your SIR device using?"
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:115
msgid "Which IRQ is your SIR device using?"
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:120
msgid "Which IO port is your parallel IR device using?"
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:125
msgid "Which IRQ is your parallel IR device using?"
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:130
msgid "What timer should be used for your parallel IR device?"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc-modules-source.templates:135
msgid "Should I try to automatically build the modules?"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc-modules-source.templates:135
msgid ""
"I can try to build and install your lirc kernel modules, as long as your "
"current kernel's source (and gcc) are present on your computer."
msgstr ""
#. Type: boolean
#. Description
#: ../lirc-modules-source.templates:135
msgid ""
"Even if you select \"yes\", you should build and install a binary 'kernel "
"modules' package so that the package manager can keep track of the files."
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:145
msgid "Where is your kernel source?"
msgstr ""
#. Type: string
#. Description
#: ../lirc-modules-source.templates:145
msgid ""
"To build lirc kernel modules, I need the sources of the kernel you plan to "
"use them with."
msgstr ""
#. Type: note
#. Description
#: ../lirc-modules-source.templates:151
msgid "${ksrc} is not a valid kernel source tree."
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:4
msgid "Should I create LIRC device nodes if they are not there?"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:4
msgid "LIRC needs some files under /dev/ for it to work:"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:4
msgid "/dev/lirc /dev/lircd and /dev/lircm"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:12
msgid "Do you want to reconfigure LIRC?"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:12
msgid ""
"LIRC is already configured, reconfiguring it may spoil some of your "
"handcrafted configuration in /etc/lirc/hardware.conf."
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:12
msgid "However comments, LIRC_ARGS and other unknown code will be preserved."
msgstr ""
#. Type: note
#. Description
#: ../lirc.templates:20
msgid "You should take care of old configuration files."
msgstr ""
#. Type: note
#. Description
#: ../lirc.templates:20
msgid ""
"Previous versions of this package didn't include any configuration file and "
"expected the user to put his own /etc/lircd.conf and /etc/lircmd.conf"
msgstr ""
#. Type: note
#. Description
#: ../lirc.templates:20
msgid "The new location for this files is /etc/lirc/."
msgstr ""
#. Type: note
#. Description
#: ../lirc.templates:20
msgid ""
"I will try to arrange things properly but, in case I can't, please make sure "
"that non of LIRC configuration files are left directly under /etc/."
msgstr ""
#. Type: string
#. Description
#: ../lirc.templates:85
msgid "lircmd should use IntelliMouse protocol instead of IMPS/2"
msgstr ""
#. Type: string
#. Description
#: ../lirc.templates:85
msgid ""
"The method lircmd uses to simulate a mouse is not compatible with IMPS/2 "
"protocol so IntelliMouse support has been added and is now the prefered "
"protocol."
msgstr ""
#. Type: string
#. Description
#: ../lirc.templates:85
msgid ""
"You ARE currently using lircmd with IMPS/2 protocol and are encouraged to "
"update /etc/lirc/lircmd.conf and the configuration of any program which uses "
"lircmd as a mouse to use IntelliMouse protocol."
msgstr ""
#. Type: string
#. Description
#: ../lirc.templates:85
msgid "NOTE: gpm will refuse to use lircmd as a mouse with IMPS/2 protocol."
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:99
msgid "Should I delete /var/log/lircd?"
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:99
msgid ""
"LIRC now uses syslog as a logging mechanism. This means that /var/log/lircd "
"is not anymore pertinent."
msgstr ""
#. Type: boolean
#. Description
#: ../lirc.templates:99
msgid ""
"If you answer 'no' to this question /var/log/lircd will be left there and "
"you will have to take care of it yourself."
msgstr ""
Reply to: