[Qgis-developer] Re: [Qgis-community-team] Fwd: [Live-demo] Translation tools - Pootle

[Otto Dassau]

Hi,

here is another experience from the method of the mapserver documentation
translation, also see:
http://trac.osgeo.org/mapserver/wiki/DocumentationTranslation

It doesn't seem to be perfect, but still better than our current solution, I
guess ;).

########

Am Wed, 11 Jan 2012 10:23:45 +0100
schrieb Lars Lingner <lars at lingner.eu>:
>
> Unfortunately the translation is not that user friendly.
> 
> You checkout the files, if necessary create a directory <lang>
> for a new language, or you work on an already existing folder.
> The document is divided into several rst files. Each <lang> directory only
> contains the translated files. A Makefile is then used to build the
> documentation, and if nothing is translated, there is a fallback to the
> English files/version. The setup is also adapted to the MapServer web
> server. If you translate offline, the links to the other language don't
> work.
>
> You see, it is not optimal. Additionally, you can not obtain a quick
> overview, where translations are missing, unless you read the
> document ... : /
> 
> Anyway, I don't know about any other/better setup that would simplify the
> work of translators.

########

Regards
Otto

Am Wed, 11 Jan 2012 10:19:02 +0100
schrieb Otto Dassau <dassau at gbd-consult.de>:

> Hi,
> 
> I was just talking to Astrid Emde and Lars Lingner. They have experience
> using rst in the Mapserver and OSGeo-Live project and they are satisfied
> with that for the documentation. I will get more information about their
> method the next days. 
> 
> From the OSGeo Live project I know that they use OmegaT (a desktop tool)
> for the translations in combination with subversion. Haven't seen anything
> about git supporty yet, will check more, but the tool works quite well, I
> tested it.
> 
> As soon as I know more about the tool chain (sphinx, svn, ...) they use for
> their project documentation, I write it to the list and we can decide, if
> that's, what we want to use for the documentation. 
> 
> For GUI translations of .ts files, pootle might be a good solution. At
> least we could test it again.
> 
> Regards
> Otto
> 
> Am Wed, 11 Jan 2012 09:05:08 +0100
> schrieb Otto Dassau <dassau at gbd-consult.de>:
> 
> > Hi,
> > 
> > I think Werner had a look at pootle during the hackfest in Poland. And I
> > remember that it looked like a good tool for the GUI (.po) files online
> > translations, but at that time not for documentation or manual pages. 
> > 
> > But maybe I am wrong and it has changed.
> > 
> > Regards
> > Otto
> > 
> > Am Wed, 11 Jan 2012 07:51:29 +0200
> > schrieb Tim Sutton <tim at linfiniti.com>:
> > 
> > > HI
> > > 
> > > I took a quick browse around - pootle looks like a great tool. Our
> > > original plan was to allow translators to directly edit the rst docs
> > > on github - simple and requiring no infrastructure from us. Pootle
> > > offers some advantages over this - but has anyone used it in earnest?
> > > How will it deal with updates to the original source docs?
> > > 
> > > Regards
> > > 
> > > Tim
> > > 
> > > On Wed, Jan 11, 2012 at 5:33 AM, Nathan Woodrow <madmanwoo at gmail.com>
> > > wrote:
> > > > FYI
> > > >
> > > > ---------- Forwarded message ----------
> > > > From: Alex Mandel <tech_dev at wildintellect.com>
> > > > Date: Wed, Jan 11, 2012 at 1:29 PM
> > > > Subject: [Live-demo] Translation tools - Pootle
> > > > To: "live-demo at lists.osgeo.org" <live-demo at lists.osgeo.org>
> > > >
> > > >
> > > > This came up on another OSGeo list and I thought it might be good for
> > > > us to look at. It's a web tool for managing translations and supports
> > > > reST (or whatever Sphinx is using) 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.
> > > >
> > > > Thanks,
> > > > Alex
> _______________________________________________
> Qgis-community-team mailing list
> Qgis-community-team at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team