On Sun, 27 Jun 2004, Matthew Palmer wrote: > On Sun, Jun 27, 2004 at 01:05:13PM +0200, Nicolas Bertolissio wrote: > > Le dimanche 27 juin 2004, Marco d'Itri ?crit : > > > On Jun 27, Christian Perrier <[EMAIL PROTECTED]> wrote: > > > > > > > Some of you guys take care of them...and after a few days upload a new > > > > version with the updated templates. Thanks to you, you're by chance > > > > the majority. > > > I do not think this is a good thing. Packages with updated templates > > > should be uploaded in time for the release, but IMO doing a new upload > > > only because of the translations wastes bandwith and buildds time. > > > > This is because you do this the wrong way, you should ask translators > > from your templates to update their translations _before_ uploading, > > this can be done winthin 3 / 4 days with translation being proofread by > > the translation team. > > If I've got twelve languages translated in my package (not that I do, I > think I've maxed two, I just picked the number at semi-random), it starts to > get rather annoying to look in twelve .po files for the Language-Team and > send the new version of my POT (and, if I recall correctly, the old .po) to > them all. A script (maybe in devscripts or something), well-publicised (ie > mentioning it prominently in the initial bug report e-mails), which will do > this work automatically, would encourage maintainers to report updated > translations.
I think you shouldn't only mail the teams that already have a translation, IMO you should mail debian-i18n to ask for new translations and translation updates. That way the translator teams also know they don't translate the file to sit a long time in BTS. Some may think this is suboptimal, but for teams with less translations it may be a good way to prioritize the huge list... Just my 2c Luk
