Hello,

Ola Lundqvist a écrit :
> In this case it is trivial. Just type make.

Yes, for your package this is very easy. But many translators dont work
with the source package (they never download them). They take a .pot
file in a web storage (like
http://www.fr.debian.org/international/l10n/po-debconf/pot ), translate
the .pot file and send the po to maintener.
Often, when a translator begin a work, he search the .pot file. If
there's not .pot file, he translate  an other thing.  A translator is
not a developper, he translate and that's all.
I'm not a good example : I'm more a developper than a translator.

> Isn't it better to search for .po files ?
No, because maintener may prepare his package for l10n and have no
translation. A package with a .po file has been translated at least one
time, a package with .pot file is "for translation" with or without
others translations.

> Or even search for packages that depend on po4a ?
No. po4a is used for other uses, programs package messages translation,
debconf translation, etc. It's not used only for manpages translation.

> I do not really understand this. The pot file will be recreated so patching
> that file do not help in this case.
Yes. pot file is never patched. but when a translator begin translation
he take the "xx.pot" file, just rename it "language.po", translate this
.po file and send this to maintener (only po file). If two translators
(or more) work (on differents languages) they need to do this with the
same .pot (maintener's .pot file). If they create their own pot file
with different options their translations will be not merged correctly.

Worse, if the maintener's options are not the same to the translator's
options, translation could be not correctly merged. (in the case of a
complex .pot build, not with this package of course)

To conclude this discussion, it's true than, for this package, "to hold
or not to hold" :-) the .pot file is not very critical because build the
.pot file is trivial and there's not many translations.

Best regards

Valéry Perrin

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to