Op Vrydag 2007-07-13 skryf F Wolff: > Hi lists > I wanted to write about the progress with the restructuring work (the Pootle diet).
> > * Statistics > I have been working on the initial work of caching some statistics in a > simple database to avoid reading the files unnecessarily. Firstly we'll > port pocount, then pofilter, and then make use of the same > infrastructure in Pootle. I hope to commit a very rough initial version > with support in pocount later today or on Monday. > http://bugs.wordforge.org/show_bug.cgi?id=271 This work is mostly feature complete. The toolkit work is in SVN trunk and the Pootle work is in the branch called Pootle-diet. Testing is welcome. There is a small outstanding issue in Pootle with the word counts for translation assignments, but I believe the rest should all work now. Basic statistics as well as statistics about the quality checks are now cached in an sqlite database. Pocount is currently the only tool in the toolkit that accesses this database. The performance hasn't really been tuned yet, but the basic work is probably now in place to start improving it. Any help is most welcome. > * Version control > Lars has been doing some excellent work on improving the code that > enables Pootle to work with version control systems. We would like to > move this code to the toolkit and make it easier to add more systems > (thanks for the promised support for git :-) Lars, I would appreciate > your thoughts and participation on these (and review of the darcs patch > posted today :-) > http://bugs.wordforge.org/show_bug.cgi?id=272 Those on the Pootle list would have seen the progress on the version control code. Recently Lars submitted the work to move the version control functionality to the toolkit, so I expect this to be done reasonably soon. This only provides the basic version control access, not the merging and conflict handling code that is currently in Pootle - but hopefully this can get more attention later. > > * Indexing with Lucene > We should move indexing support from jToolkit to the toolkit to ensure > that we don't loose that functionality if we migrate away from jToolkit. > http://bugs.wordforge.org/show_bug.cgi?id=273 No work started yet. I have also read about Xapian, which we might want to support in addition to Lucene. If anybody is interested in this one, I think it is quite doable, since it is a fairly well isolated part of code. Basically it is about moving the code from jToolkit into the translate toolkit, and then we can work on improving it from there. This will make indexed search available to all programs using the translate toolkit. Keep well Friedel ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
