On Mon, 15 Mar 2010 22:35:12 +0200, Alaa Abd El Fattah <[email protected]> wrote: > Hello list, > > We've been working on the next major version of Pootle immediately > after releasing 2.0.1, in fact the new formats support introduced in > 2.0.3 was a side effect of work we've been doing for the upcoming 2.1. > > It is still early in the development cycle but we thought it's time to > let share some of the new features by making a snapshot Alpha release. > > You can download the snapshot from > http://translate.sourceforge.net/snapshots/Pootle-2.1.0-alpha1/ > > some features depend on an unreleased version of Translate Toolkit, > you'll find a snapshot release of toolkit on the same url. it might > work with toolkit 1.6.0. > > New features in Pootle 2.1.0 Alpha1: > > * Support monolingual formats: yes this means Pootle will directly > support Java properties, PHP arrays and Subtitle files directly > without having to use a converter (subtitles support depend on > Gaupol http://home.gna.org/gaupol/). > > * Automatic glossary extraction: Pootle can generate terminology > stores based on the most frequently used words in your project just > follow the manage glossary link in translate tab. If you don't like > some of the terms suggested you can delete them (by the time 2.1 is > released you'll be able to edit terms and even create new ones).
Yay. > > That's all the new features we introduced, but they required major > changes. Pootle now stores translations in the database. which has > many consequences: > > * Pootle no longer depends on statsdb, statsdb was a major bottleneck > for concurrency due to being tied to sqlite. I think change will > make many people happy. not that this alpha still depends on sqlite > and creates a stats.db but isn't really used except for testing, > we'll get rid of statsdb completely soon. > > * Translations files do not reflect current state of translations > automatically. Now that translations live mostly in the database the > translations files under the po/ directory do not get updated on > every translation. Translations get saved to file by demand when you > download them from the web only. there is an optional > localsettings.py variable AUTOSYNC that forces translations to be > saved immediately (same behavior as always) but it has a negative > effect on performance and should only be used if you have other > applications or scripts that need to access the files directly. > Possible problem for us. Is it possible to make the sync happen automatically at configurable intervals please? > * The main Django database is now much larger, in Pootle 2.0 the > database was quite small, its size depended on the number of > languages, projects and files. in 2.1 it's size depends on the > number of translation strings as well and even the smallest project > has thousands of these. This should have no negative impact on > performance but larger Pootle installations might find using sqlite3 > as the database engine impractical. using MySQL (or PostgreSQL) will > have a very measurable impact on performance. > > * If you want to test upgrading an existing installation of Pootle > 2.0.x you'll need to install South (http://south.aeracode.org/). it > might be packaged for your distro under the name django-south, if > not just run "easy_install South" > > We do not recommend installing this snapshot release, run directly > from checkout instead, you can avoid installing the snapshot release > of toolkit by copying or symlinking the > translate-toolkit-1.6.1-pre/translate/ directory into the > Pootle-2.1.0-alpha1/ directory > > We would love to hear your feedback on the new features and how > they can be improved. on what stopped working and on what other > features and fixes you'd like to see in the upcoming 2.1 version. but > we must warn you this release is for testing purposes only. it is very > very very far from ready, some things might not work at all and don't > expect the database structure to remain intact, there will be no > upgrade path from 2.1.0-alpha* and 2.1.0 stable. We don't know of > any cases where it will destroy your data but we wouldn't be > surprised. > > cheers, > Alaa > Amos ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
