> Hi Lübbe (and everyone else) :)
> After asking the LP guys about this 'n that, I think I've got an idea
> about how LP translations could be integrated into your workflow with
> aid from 2 relatively simply PHP (or similar) scripts.
> I don't know if we have any PHP wizards or the like around here who
> could give a hand? If not, I'll dig into it myself as soon as I get the
> time, though I will have learn as I go, as I haven't messed too much
> with PHP in the past.
> Script 1) When triggered, requests a TSVN translation export from
> Launchpad through an account reserved just for this "bot" (needs to
> attach a session cookie for automatic login).
> This script could be wget/cURL triggered 2-3 hours before the nightly
> Script 2) When triggered, checks the "bot" mail account for the latest
> export message from LP since last export, fetches the .tar.gz from the
> link in the mail and places it on the web server next to the scripts.
> Then either return "UPDATED"/"NOUPDATE"/"FAILED"/etc.
> Depending on the result of the script, the nightly build script could
> then fetch the .tar.gz, unpack it, and commit it back into SVN while
> building the nightly language packs.
Now, that's something I really don't like. Automatic commits are a bad
thing, and we'd loose the information *who* did the changes.
If we really want to use Launchpad for translations (which I'm not so
happy about either: yet another server for our project beside
sourceforge, tigris and tortoisesvn.net), then the translations would
have to be manually fetched from Launchpad and committed by translators
who supervise the changes.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-06-17 21:10:53 CEST