Package: newpki-server Severity: normal Tags: patch l10n
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.
For more details, see po-debconf documentation, especially "man 7
po-debconf"
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...
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.
Additional notes, specific to this package:
-------------------------------------------
As it seems that French is your own language and that you made the
translation by yourself, please _always_ ask for a review by the
debian-l10n-french contributors, by sending the appropriate [rfr] (see
http://www.debian.org/intl/french/ for the documentation and procedures
of the debian-l10n-french team). It will avoid you some obvious
mistakes, such as "doit il" or bad typography, as well as enabling a
consistency between all the translations within Debian. I haven't fixed
it in this patch, because I hope that you will ask us shortly for a
review.
Thanks for helping the translators, and thus your non-english speaking
end-users.
Cheers,
--
Thomas Huriaux
signature.asc
Description: Digital signature
