On Mon, Oct 12, 2009 at 6:47 PM, Evan Prodromou <[email protected]> wrote:
> Brion Vibber wrote: > > Is Pootle good enough as an interface that we just need to jumpstart > maintenance on it, or would there be interest in migrating to TranslateWiki? > > > I've been really bad at maintaining Pootle. I would breathe a great sigh of > relief to have TranslateWiki do this instead. > > I like TranslateWiki and I think the organizers have the exactly the right > perspective. I love the idea of reaching a lot more translators, too. > I've gotten a couple other suggestions so far, which I'm adding at http://status.net/wiki/Translations#Alternate_editing_interfaces Please feel free to add comments or experiences anyone's had with those systems (good or bad). A couple of important questions: > > - How do we get new strings into the translation system? > - How do we get new translations out of the wiki and into our > repository? > > Current versions of Pootle have support for integration with source management systems; it should be possible to rig it up to pull updates from git and even commit directly back to it. For now I'm committing all the updates currently in the system, and I'll see if we can get an updated Pootle config in the next day or two so we've got something to work with; after a little shakedown we'll have a better idea whether we still want to pursue something else. For TranslateWiki we might need to work out the actual update/commit implementation, I'm not sure they've done a git project before so it might not be ready to roll yet. Transifex looks like it should also be possible to set up w/ git support; we'd need to contact the admins there for initial project setup but it should be more automated after that. -- brion vibber (brion @ pobox.com / brion @ status.net) StatusNet, Inc San Francisco
_______________________________________________ StatusNet-dev mailing list [email protected] http://lists.status.net/mailman/listinfo/statusnet-dev
