Hi Peter, У нед, 31. 01 2010. у 12:20 +0000, Peter Clifton пише: > Having to wait hours (for the automatic review), or days - if it > requires manual approval is a real strain on my productivity, and > motivates me to stop using Rosetta for translations all together. Using Bazaar integration (importing templates directly from your bzr code branches) should avoid the need for manual template approval. If you are not introducing new templates, keeping the same directory and filename structure should help get them all through automatic approval every time. > I'd appreciate some insight into the issues which translations are > reviewed for, and why I can't do it myself. It's basically historical: we've never had time to develop tools to clean up after something is messed up. And it's easy to mess up. Few of the main reasons why we did it from the start: * English should be the base language, because our DB is designed around this * Multiple translatable templates should be in appropriate directory structure * A project which has translations happening elsewhere shouldn't be registered in Launchpad as well (or people would be confused) At the moment, we feel that everybody would be better off with the approach of "letting everything in, clean-up later if needed". And, some of these things should be detected automatically (eg. heuristically for non-English in base messages). However, the approval process is still confusing enough that even experienced i18n people get it wrong sometimes. And the tools to clean up afterwards are non-existent. We've made a small step forward with bzr-integration, so I suggest you use that for a faster turnaround time. Auto-approver is also slow because it has to go over all files that need reviewing over and over again until they are either approved or removed from the queue. And it's a two-stage process (first it tries to auto-approve a template, and when that's done, it auto-approves translations against that template in the next run). Again, this is historical. These are all things that we'd love to improve and/or see improved. However, our time is severely limited. But, Launchpad is open source so if you want to take on any of these issues, come talk to us on #launchpad-dev on FreeNode IRC or start by visiting https://dev.launchpad.net/. Cheers, Danilo
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)