Translate Toolkit on Fedora. Status of Virtaal and Pootle
Well not really :)
The Translate Toolkit has been packaged for Fedora for a while now, what I've done is update to v1.2 (with v1.2.1 in the pipeline) for both Fedora 10, 9, RHEL 5 and OLPC. This is the groundwork needed to get first Virtaal and then Pootle into Fedora.
Virtaal is awaiting review for inclusion in Fedora. I expect that to happen quite soon. Of course I'll need to package it quite soon again once the Virtaal MVC changes have landed on trunk. Check out the amazing work happening on the MVC branch.
Pootle is going to take a bit longer. I don't want to package a Pootle that relies on jToolkit so I'm waiting for the Django migration (there is probably a better page to link to) to be complete. I think it will be well worth the wait and does prevent me having to package jToolkit for Fedora.
- dwayne's blog
- Login or register to post comments
How about bundling jToolkit
Can't we consider just bundling jToolkit with Pootle for 1.2? If no other package is using jToolkit it doesn't really make a difference to anybody. It might mean a bit of work to include jToolkit in Pootle's setup script, but shouldn't only need a little bit of testing. This should be quite valuable while we wait for the Django Port of Pootle to finish and stabilise.
jToolkit packaged in Pootle
I have thought of that as a possibility and haven't ruled it out completely. But getting that past a reviewer might be rather hard.
With the speed of things happening on Django Pootle and the slow pace of getting my packages approved in Fedora we might see both a new Pootle release and my packaging happening at the same time.
By skipping the jToolkit stage I also get to ignore any migration issues from text based prefs files to DB.