Re: [libreoffice-l10n] LO Pootle

2011.01.04 17:55, Andras Timar rašė:
> 2011/1/4 Jan Holesovsky<kendy@suse.cz>
>
> > Hi Sophie, all,
> >
> > On 2010-12-30 at 15:18 +0300, Sophie Gautier wrote:
> >
> > > > I download/update my language .po files using svn (with a very simple
> > script)
> > > > and use Lokalize with a Translation Memory database, which is now 125M,
> > for
> > > > translation and a glossary for words of .5 MB. Uploading is using svn
> > commit.
> > > > Compared to using Pootle this is far more easy. Using svn or git for
> > download
> > > > and upload is using less bandwith, because only the differences are
> > > > transported.
> > > Thank you very much for your feedback on this. It's great if we can
> > > share others experience on this.
> > >
> > > The only thing I'm afraid of is the technical skills needed for the
> > > steps to download or upload the files. Also what will be the process
> > > under Windows, is it easy to commit on git or svn or whatever using
> > > other OS than Linux (I remember at the very beginning of the OOo FR
> > > site, I was under Windows 98 and comits to the cvs repository was not
> > > exactly what I call fun ;-)
> > I've just found
> >
> >   http://translate.sourceforge.net/wiki/pootle/version_control
> >
> > that describes how to connect Pootle with a version control system.
> >  From what I understand, this is built into Pootle.

Yep, it's possible. I haven't tested how well, or how it works though.

> > How does that sound?
> Sounds great - what to do next? Who has the right to set up a module in git
> (Kendy?), who can configure Pootle to use it (Rimas?). I think we should
> test a selected set of languages first (e.g. hu), then I will collect all
> translations from the different sources and upload them.

If it's enough if I say I would take a look without any due date, I can 
say so. But I don't mind anyone else looking into this either.

OTOH, I have only skimmed through the wiki page that Jan linked to 
(without much reading), and the procedure of setting stuff up looks 
pretty straightforward. What I'm not sure about is how well Pootle would 
handle version conflicts (e.g. a new file was checked in into git, but 
Pootle doesn't know it and treats it as unversioned). However, I guess 
the easiest way to figure this all out is to just try to use the 
feature. I don't want to give promises, but MAYBE I would look at it 
this weekend... :)

Good night,
Rimas


--
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***