Hi lists

Now after the release of version 1.0 of the toolkit and of Pootle, we
are looking ahead at some of the important things that need to be done.
This e-mail is mostly about underlying development work, so those of you
that are not interested in the development, can probably skip over this
thread :-)

If people feel up to the challenge of addressing one or more of these
issues, we would be very happy to collaborate. For some of the issues I
mention, some people are already working on them.

For the things mentioned here the basic plan is to move some of
functionality from Pootle to the toolkit so that it is easier to
maintain, to test and available to more tools. This is why we call it
the Pootle diet.

An issue that was discussed a few times on the list in the last year, is
the issue of the platform that Pootle is built on. Gasper Zejn has been
busy since November last year porting Pootle to Django, and we would
really now want to look at moving forward with a move to a more familiar
platform. To some extent we are trying to limit GUI work on Pootle while
we expect a platform change. Most of these tasks are meant to make the
porting easier and to be able to simplify testing of various functions.

So these are the current tasks we have identified. The order roughly
indicates the order in which we would like to attempt them. The details
for each are in a separate bug in Bugzilla:

* 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

* 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

* 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

* goals and work assignment
This is currently only a function of Pootle. If we move statistics
functionality to the toolkit, this should go as well, and it will expose
the functionality to more tools.

* string markup
Some current and planned functionalities will need a way to indicate the
positions of certain "features" in a string. For example for the
highlighting of tags, variables, escapes, or for indicating differences
between strings (to compare suggestions, to compare the current and
previous source strings, to compare a TM suggestion, etc.) This is not
so much current functionality of Pootle, but is something we want to
keep in our aim for the medium term.


I would like to hear everybody's thoughts.

Keep well
Friedel


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Translate-pootle mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/translate-pootle

Reply via email to