Hello,
Marc Haber already asked for a small document that could give best
practice for maintainers.
Today, Denis and Thomas also pointed that we should define a common
hierarchy to help the l10n robot to detect POs used for translation.
This robot is used by some translation teams (at least the French one) to
inform the translators that the PO needs to be updated.
Detecting po4a's PO will permit to check that the POT are up-to-date and
the POs also.
(Denis and Thomas, correct me if I'm wrong)
Can you check if the attached file is clear enough? (is it too verbose?)
Do you agree of the proposed file hierarchy?
Does it represent your opinion?
BTW, there are currently 17 packages which build-depend on po4a:
adduser, apt-build, apt-proxy, apt-show-versions, base-passwd,
belocs-locales-bin, debarchiver, debhelper, deborphan, debsums,
devscripts, fakeroot, glibc, mailliststat, pppconfig, smb2www, squashfs
dpkg (soon in experimental)
apt, aptitude and debianutils may also switch
Kind Regards,
--
Nekral