[Dctrl-tools-devel] Splitting out upstream, perhaps?

[David Prévot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

Le 19/06/2012 16:15, Antti-Juhani Kaijanaho a écrit :
> I've
> always hoped dctrl-tools had wider applicability (and I'm currently using it in
> my doctoral work for something totally unrelated to Debian).

Great to see your hopes became a reality!

> And a question: how do translation updates work in upstream development,
> generally?  I've never had to deal with that so far.

Translations within Debian are usually limited to debconf templates,
while runtime and documentation translations are handled upstream
(upstream being Debian again for dctrl-tools).

If the current translation workflow is not a burden, I'd propose to keep
it that way: allowing translators to commit directly, and handling
(currently most of the) other translations with the BTS or via direct
mail. I can't speak for other teams, but as a French translator, I can
assure you I don't mind contributing upstream (quite the contrary), and
the team should continue its reviews in order to offer quality translations.

If you wish to propose another translation workflow, you may be
interested in the Translation Project [0]. I also participate to some
upstream translations that way, both approaches may have pros and cons,
I'm willing to discuss them if you consider another approach.

	0: http://translationproject.org

On a technical point of view, I guess there will be some (translatable)
upstream part and some additional (translatable) Debian part. The
translations (PO files) could either be split, or simply kept in one
block (for example, packages.d.o master branch includes every strings,
including Debian specific ones, so translators only need to work on one
(set of) PO file(s), and those translations are available in all
flavors: Debian, Ubuntu, or archive.d.n).

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJP4OjVAAoJELgqIXr9/gnyMJIQAKHoHuSQdX0Ig6t7vnKTZYRV
ZwinFBr7xm1h3KyvrThiHyqOmDCnNWiCs5ExQNMte224S3ZpDFF0h6/+SbsgxoyO
zn6M0IqGJK4aCZmoj5KGlB9P+DGsKA7lZVdI9Yb0+DG8Cv9+m7jofajO+UAPXHde
ZT3y2HYTPx8nQy2nadkDKtD3LISES/kdtekJ7F8GXf2IOJw6XMPtC6NTlDBZV0CZ
G7k5wHeBEmTgEyaaYxMQ+eNmdh47BXgPIumWPb8EMH5PGQgEg/7Glu2+KQz7f8dK
SZq6WbV6HBqb43xdARAGZcfpmcycUEMakYW4AvYe4qZQlaH2T3ZpjlUg79QXuPAP
HqhgZ5KZMS11hAf1qYU2B66SNxayDW8czGVeh5pLYX2dL2Vis5JT9JxTzeZxnaZI
ikzWREWQUwn9d+nZ6X3zAnxU/dTUItY616DswJhVdnzKygFJj9tUhTHWr987nmNV
SR01iaE6DKrhoabgZ8pR9Uy4+YIAQqOJpU/FssBwli6wijKcv5WH9HqBnKxLGniz
5K2g15tw7FocKWHAIfgvQ5PB99+Oona8EnzkU7DYqFSI5cu1a/WdtydHVbZdfqWO
ZK06E14sRkUhrTD80wfpSdJmCiTs4ErWSlNiXOPtAiNqw2M54HPRleIzH/h+OPOb
7Fm6VzZ0ukqFWodX96dZ
=6nin
-----END PGP SIGNATURE-----