Quelques stats, et appel a volontaires pour les bascules
La periode de gel approchant, les mainteneurs se depechent de tous faire une
derniere mise a jour de leur paquet. Le cote positif des choses, c'est que
du coup, les stats de traduction font un joli bon en avant.
Pour po-debconf:
fr 96%
nl 78%
de 73%
pt_BR 69%
ja 52%
da 50%
es 58%
Sur le front des bascules, il reste 118 paquets utilisant debconf sans
po-debconf, et 80 bugs sont ouverts.
Malgre les nouveaux paquets apparaissant ou passant a debconf sans faire les
choses proprement (cf #208445), je me tiens a flot, et le nombre s'erode au
cours du temps. Depuis fevrier, le nombre de paquets fautifs est une
fonction monotone (meme si pas strictement decroissante). Le nombre de bugs
tend a decroitre un peu en ce moment. Mais on a eu une pointe a 121 bugs le
11 mars, et il ne reste plus que 118 paquets a bugger...
Si quelqu'un veut aider pour les 38 paquets restants, qu'il se manifeste.
Attention tout de meme, on est proche de la release, il est possible qu'on
ait pas le droit a l'erreur dans ce genre de manoeuvre.
Voici la liste des paquets:
acl-installer (coquin car templates generees)
ccc
cfal
cfalrtl
cxx
debian-edu-config (sans doute un faux positif?)
discover (faux positif, les templates ne sont pas utilisees)
filterproxy
ftape
ftape-tools
ftpwatch
gdm (faux positif, templates pompees de xdm avec les trad)
hybserv
ipvsadm
ispell-fi (les champs a traduire sont pas ASCII, ce qui embette
gettext)
kerberos-configs
lapack3 (bug soumis a lapack hier, je pense que Camm fera celui la)
libsafe
lids-2.4
lowmem (faux positif, l'absence de trad est une fonctionnalite)
lukemftpd
lw-per-installer (memes templates que acl-installer, grosso modo)
lw-pro-installer (memes templates que acl-installer, grosso modo)
lw-pro-installer-43 (memes templates que acl-installer, grosso modo)
mdnkit
mod-mono (templates a chier debout, a reecrire avant la bascule)
moviemate (faudrait re-expliquer au mainteneur que y'a pas besoin de
templates dans un paquet dummy charge simplement de
permettre la mise a jour. En attendant, faux positif)
mped
ntop (templates en mauvais etat, pleins de bugs sur les
fonctionnalitees liees a debconf, mainteneur ouvert aux
NMU)
nttcp
php4-pecl-ps (ca sent la question classique "Apache ou Apache-ssl?"
php4-ps |Christian, t'en es ou pour le partage de templates?)
prelude-nids
samba-doc-ja
usb-discover (d-i, il me semble. don't act si oui)
zope-cmfforum (il me semble me souvenir que l'un des combats de Denis,
zope-loginmanager|c'est d'obtenir la supression pure et simple des
zope-zwiki |templates zope, mais je suis plus sur)
La marche a suivre est la suivante:
- telecharger le source, faire une copie
- verifier que les templates sont utilisees (dh_installdebconf dans
debian/rules ou install a la main)
- regarder si les templates sont generees ou non, et chercher un autre
paquet si oui. Je ne me souviens plus du beau paquet qui genere ses
templates et qui utilise po-debconf. C'est un beau cas d'ecole, et
j'aurais aime le retrouver hier en passant lapack a la moulinette.
- reecrire les templates qui en ont besoin
- faire tout ce qui est dit dans le changelog en attachement. C'est le corps
du rapport de bug a soumettre ensuite.
- virer les *~ qui poluent les diff
- faire un diff -ruN des de vos changements et de la copie
- lire le diff avec attention pour voir si vous en avez trop fait ou pas
assez.
- Editer le dit rapport de bug pour l'adapter a vos modifications. Si
y'avait pas de trads dans le paquet, faut virer le paragraphe adequat. Si
le paquet depend pas de debhelper, faut build-depend sur po-debconf
directement et adapter le texte. Il faut choisir entre le paragraphe qui
dit "les templates ont ete modifiees" et celui qui dit "les templates sont
pas mal, bravo".
- adaptez le "Bye, Mt" ;) et tout ce que vous voulez en fait. Si vous faites
le boulot, vous etes libre de le faire comme vous voulez (c'est meme dans
la constitution debian)
- ouvrir un rapport de bug avec le texte en corps et le diff en attachement.
Bien sur, si vous meme ou l'un de vos agents venait a se faire prendre en
train de faire des conneries et produire des patches casses en periode de
release, le gouvernement de dlf nirait toute implication dans l'operation.
Ce message sera archive ad vitam eternam.
Mt.
--
Ce que nous vendons à Coca-Cola, c'est du temps de cerveau humain disponible.
-- Patrick Le Lay, PDG de TF1 (L'Expansion, 09/07/2004).
Using the "new" gettext format for debconf templates helps for templates
translations. For instance, detecting outdated or untranslated strings
becomes considerably easier. It also keeps track of who did which
translation.
Patch description:
------------------
The attached patch does the required modifications:
- debian/control modification for dependencies:
build-dep: debhelper (>= 4.1.16) which depends on po-debconf
depend: debconf (>= 1.2.0) since old versions have problems with templates
specifying the encoding of their content
- Add 'debconf-updatepo' to the clean target of your debian/rules
(to make sure that the relevant files are ready for translation in the
distributed source packages, and thus help translators)
- execute "debconf-gettextize debian/*templates*". This does:
- generate po/ directory containing all the translation mecanism
- change the template file to mark some strings as translatable by putting
a _ before the field name.
- mark the right strings as translatable in the templates. This is a manual
check to make sure that fields containing stuff which cannot be
translated such as kernel module name, and the one not shown to the users
are not marked as translatable.
- removed files left by debconf-gettextize (*.templates.XX which are the
old-style translations and now live in debian/po/XX.po)
The previously existing translation were not lost in the process, but
automatically converted to po files. You may however want to ask your
previous translator to review them and update them if needed. Also ask
them to add their name in the header of the po files, to ease future
maintainance and update of the file.
- update the style to the best current practice (see below)
For more details, see po-debconf documentation, especially "man 7
po-debconf"
This patch also document the most important modifications in the changelog.
Use this as a sample, and please feel free to change it to fit your taste.
If you want to give me credit for this, write my name but avoid to publish
my email address there since I already get enough spam.
About backports:
----------------
Please note that the suggested modifications will make your
package a little bit harder to backport to earlier Debian releases. If
this is a concern to you, you may try to adopt the method used by the
openssh package and detailed by Colin Watson in
http://lists.debian.org/debian-i18n/2003/debian-i18n-200307/msg00026.html
This patch does not includes this method as this would make it too
invasive, IMHO. So, preserving backportability is up to you...
Stylistic considerations:
-------------------------
<<<<<<
While I was working on the convertion to po-debconf, I noticed that the
templates of your package may be easily improved by applying the advices
contained at the following address:
http://people.debian.org/~bubulle/dtsg.txt
I applied the advices from this document concerning the short descriptions,
but you may want to change the long descriptions accordingly as well, for
example to make them clearer even to newbies. Don't get me wrong, I don't
want to criticize, I just want the template to reach a translatable state
(ie quite stable) rather soon.
======
While I was working on the convertion to po-debconf, I noticed that the
templates of your package are in a rather good shape. I did provide such
a conversion for a bunch of packages, and I saw a bunch of broken
templates very hard to understand for newbies. Yours are not that way,
and I want to congratulate you for that.
In case of future doubt, please note that the current best practices
concerning templates are available from:
http://people.debian.org/~bubulle/dtsg.txt
>>>>>>>
Future:
-------
Once the switch is achieved, and style improvements are done (if any), I
guess that you will receive translations of your templates rather soon. They
will consist in XX.po files where XX is the code of the language they
contain. Simply put them to debian/po, add a changelog entry, and your
package is ready for rebuilding and uploading after the usual checks.
If you modify your templates in the future, no action is absolutely
mandatory from you to take care of the translations (outdated translations
will be automatically discarded). But it is nicer to your translators and
your not english speaking users to include the updated translations in the
same upload. For that, run debconf-updatepo, and mail each translator the
XX.po file they provided you. Their adress can be found in the headers of
the po file. Wait a few days so that they can do their work, and put the new
version of the po file back in position in debian/po before upload.
Thanks for helping the translators, and thus your non english speaker
end-users.
Bye, Mt.
Reply to: