[Live-demo] Translation tools - Pootle

[Hamish]

Alex wrote:
> ...
> It's a web tool for managing translations and supports reST
> (or whatever Sphinx is using)

sphinx uses reST

> and svn integration all through a web portal. So no need for
> translators to download anything, just log in and translate.
> 
> It's called Pootle
> http://translate.sourceforge.net/wiki/pootle/features
> 
> Backed in Django. I don't have time right now since I'm working on the
> build infrastructure but if someone else wants to setup a test instance
> possibly on the osgeo adhoc machine I'd be happy to lend support.

I've installed the pootle package on adhoc, but not actually enabled the
server. see /usr/share/doc/pootle/README.Debian for considerations before
doing that.  (disabled by /etc/default/pootle)

here's a working example:  http://pootle.translate.org.za/
 (e.g. click on TuxPaint)
and another for GRASS:  (although I'm not sure how to use it)
  https://www.transifex.net/projects/p/grass6/


it seems more for gettext .po files that for full document translations
like the livedvd has. perhaps each paragraph of the document could be
_() macro'd? the livedvd needs are very similar to translating man pages
so I wouldn't be surprised if some sort of infrastructure support had
already been thought of/provided.

more on .po managing software here:
  http://grass.osgeo.org/wiki/GRASS_messages_translation#Software_to_translate:_.po_file_editors

see also some ideas about semi-automated full man page translations here:
  http://grass.osgeo.org/wiki/Updating_GRASS_Documentation#Translations
(dunno about resulting copyright issues if using an automated service 
though)


Hamish