Hello again list, It's been a month since we released the first Alpha release of Pootle 2.1.0, it didn't get much testing (I'm heartbroken :-( but that didn't stop us from working hard so here comes Pootle 2.1.0 Alpha 2, another snapshot release to give you a taste of things to come.
No new features where introduced in this release, but we rewrote the implementation of the translate page for better performance. much better performance in fact in our benchmarks apache was able to serve 3 times as many requests per second because of this optimization. it also brings down memory use considerably. Now you have no excuse, if you've complained about memory use, performance under a large number of users or high concurrency you must test this release and send us many many wonderful patches, bug reports, patches, feature requests and patches. (did I say patches? please send patches) We also introduced two new ./manage.py (or django-admin.py) commands: * (sync_stores) for mass saving new translations to disk * (update_stores) for mass updating database with new strings from file system You can download the snapshot from http://translate.sourceforge.net/snapshots/Pootle-2.1.0-alpha2/ some features depend on an unreleased version of Translate Toolkit, you'll find a snapshot release of toolkit on the same url. 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-alpha2/ directory This should be our last alpha release, we hope to release a beta by the end of this month. remember Alpha release means anything could happen, do not use this snapshot for real work we don't know of any case where you'll loose data but we won't be surprised if it happens, some things might not work and the database structure is sure to change between now and release day. we have upgrade scripts for 2.0 users, but there will be no upgrade path from 2.1.0 alpha to 2.1.0 stable. I'm pasting information from the 2.1.0 Alpha1 announcement for those who missed it and don't know what Pootle 2.1.0 is about: New features: * 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). 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. * 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" cheers, Alaa ------------------------------------------------------------------------------ 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
