Quoting Guillem Jover (firstname.lastname@example.org): > master is currently up to date in relation to the lenny branch. But > it's not, against the current sources, as we have been trying to avoid > to update the pot files. OK. > Regarding switching the pointers for translators, we have been talking > about doing some major cleanup of strings, in the C and perl code, > to remove dupes, make them easier to translate, or more understandable, > so I think it would be best if translators didn't target master for a > while. But then we can always keep not updating the pot files until the > strings have settled down a bit. Yes. But I think this should be their choice. Some of them (/me included) prefer keeping up constantly mor ethan doing bug updates at rare moments. This malkes the work less frightening...:-) > So, Christian, I think it's fine to update the pointers from lenny to > master, as long as the translators themselves do not update the pot > files. Or do you see any problems with that? I think that, if we want to satisfy those translators who prefer working at their own pace, we should update POT files (and PO files from them) regularly, as soon as one of those "big cleanup" has happened. I suspect they will happen in batches when either Raphaël or you (or other ppl) merges something in the master branch. How about having a git branch for localization and use a "dpkg" project on pootle.debian.net for translators to work there (and there only)? This way you could sync PO files of the master branch with that branch and sync the new/modified strings back to it by updating the POT files in master and pushing this to the l10n branch? I think it should be feasible to ask translators to work and update their work in Pootle only. And, even if some still send bug reports, those could be picked by the l10n "master" and committed through Pootle. The only concern might be that Changelog files would become hard to maintain (they are already...).
Description: Digital signature