We are happy to announce the 4th and hopefully final beta of Pootle. This release brings vast improvements to the user interface, Pootle is not only looking much prettier but is also easier to use thanks to Julen's very hard work.
We've also introduced a new experimental feature: news items are now automatically generated after big changes like file uploads, version control updates and commits. Each project and language has it's own news tab and corresponding RSS feed. We'd love to hear your feedback on this feature. Translations for Pootle's UI can now be read from compiled .mo files. In previous betas live translation of the UI which is only useful as tool to learn how to use Pootle was the only option. But since it is slow and resource intensive it can now be disabled from the localsettings.py file. Pootle now can run safely under multithreaded Apache (or any other multithreaded Django compatible server for that matter) and is compatible with Django 1.1 as well as 1.0. We've added two small features that where requested on Bugzilla years ago: you can now remove languages from projects directly from the web interface. We've also added another merge strategy for file uploads: you can choose to make all new translations coming from uploaded files as suggestions (as opposed to only conflicts with existing translations). This should make reviewing translations much easier. As always, lots of time was spent improving stability and performance. File uploads and version control integration received special attention in this release and should be much faster now. Apart from that we closed lots of old, new and borderline ancient bugs on Bugzilla, so now we have lots of space for more. Please test and keep those bug reports coming. This beta depends on a yet to be released version of the Translate Toolkit. You'll have to use a snapshot release of the toolkit alongside Pootle. Both can be downloaded from http://translate.sourceforge.net/snapshots/Pootle-1.3.0-beta4/ Pootle depends on Django version 1.0 or 1.1 (http://www.djangoprojects.org) and lxml (http://codespeak.net/lxml/), make sure they're installed before attempting to run it. They should be easily installable through your Linux distro's package manager . You can run Pootle directly from source (an SVN checkout or just extracting the downloaded archive) just run the PootleServer command. it can also be installed using the setup.py command. Pootle should run fine out of the box, but advanced users (or anyone deploying under apache) will want to check the configuration options in the localsetting.py file (if you install using setup.py it'll be /etc/pootle/localsettings.py). Pootle uses caching extensively to speed up translation statistics and improve performance. For optimal performance (especially under apache) you should use memcached as your caching backend (edit localsettings.py to enable memcached support). Being a Django application, Pootle runs under Apache (mod_wsgi or mod_python) or from the command line. It can use any Django supported DBMS as its backend including the default sqlite and the ever popular MySQL. Remember you can download this beta from: http://translate.sourceforge.net/snapshots/Pootle-1.3.0-beta4/ Please check the README and INSTALL files as well as http://translate.sourceforge.net/wiki/pootle/installation_1.3beta for installation instructions. Keep well The Pootle development team ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
