Re: [translate-pootle] Re: Web-based translation for GNOME

[David Fraser <davidf sjsoft com>]

Simos Xenitellis wrote:

> ÎÏÎÏ 16/ÎÎÏ/2005, ÎÎÎÏÎ ÎÎÏÎÏÏÎ ÎÎÎ ÏÏÎ 13:58, Î/Î Danilo Åegan ÎÎÏÎÏÎ:
>  
>
> > Hi Simos,
> >
> > Just to be clear: something like this should *not* be obligatory for
> > Gnome translation work (even though you never implied it would be, I'm
> > putting a disclaimer here :).
> >    
>
> Ack. 
> As Dwayne said, the translation management tools are to help translation
> teams that want to use them.
>
>  
>
> > While I think having web-based translation tool would be excellent for
> > official GTP, I find Pootle quite lacking in features.
> >
> > Today at 14:35, Simos Xenitellis wrote:
> >
> >    
> >
> > > b. The stat pages contain complete information to locate the .po/.pot
> > > files, such as branch, folder, location of .po files and so on. That
> > > info could be parsed from HTML. Any suggestions to have some other
> > > format for these data, that's easier to parse?
> > > c. There will be a dependancy to the structure of the HTML pages, unless
> > > again there is some sort of XML file, listing the complete information
> > > of the translation files.
> > >      
> > Look at gnome-i18n/status/data/translation-status.xml file for your
> > input.  At some times, l10n-status gets out of sync (between updates,
> > when someone does some changes to translation-status.xml), but that
> > shouldn't be too big of a problem. 
> >    
>
> Is there a generated .xml file that lists all the .po files, for
> example, for the Greek language?
> I suppose one would then use the following.
> Using the existing translation-status.xml, if a translation management
> tool wanted to work on the .po files for gnome-utils, release 2.10, it
> would parse the .xml file, then using:
>
>    <version release="gnome-2.10">
>      <component name="gnome-utils" dir="gnome-utils" group="desktop">
>        <podir dir="po"/>
>        <potname name="gnome-utils-2.0.pot"/>
>        <branch name="gnome-2-10"/>
>        <regenerate/>
>        <download/>
>      </component>
>    </version>
>
> it would test if 
> http://l10n-status.gnome.org/gnome-2.10/PO/gnome-utils.gnome-2-10.el.po
> [BASEURL+COMPONENTNAME+"."+BRANCHNAME+"."+LL+".po"]
> exists (so there is existing translation) and use it to continue
> translations.
> If the URL does not exist, it would load up
> http://l10n-status.gnome.org/gnome-2.10/PO/gnome-utils.gnome-2-10.pot
> [BASEURL+COMPONENTNAME+"."+BRANCHNAME + ".pot"]
> and start an initial translation.
>
> In addition to this, my initial concern is whether a translator (or a
> translation management tool) should use the .POT and .PO files from
> http://l10n-status.gnome.org/ rather than checking out all of GNOME CVS.
> It's quite tempting to use the files from http://l10n-status.gnome.org/
> and base whatever tools are created on them.
>
>  
>
> > Another approach is to use jhbuild modulesets files (Carlos has been
> > planning to use them for still unfinished new status pages).
> >
> >    
> >
> > > d. Web-translation tools could commit the changes using either a common
> > > CVS account (for example, for Pootle, you can either translate through
> > > the main installation at http://pootle.wordforge.org/ or install it on
> > > your own), or have team leaders (that want to do Web-based translation)
> > > put their username/password in the Web-translation system.
> > >      
> > Or perhaps simply e-mail the coordinator who would be able to commit
> > it on their own?  That's a completely valid option, and the one I
> > would most likely use if I end up using it at all.
> >    
>
> Ack.
> My personal preference would be to setup something like a
> https://www.gnome.gr/translate/ that would allow from a Web-interface to
> complete remaining translations (typically 5-20 messages) and have them
> moved upstream automatically. No need to manually cvs checkout, no emacs
> to edit ChangeLog, no manuall commit.
> In another setting, one would download initially a snapshot of the .po
> files for a specific language to work offline on them, have a
> weekend-long translation fest on the local network (thus responsive
> interface), manually verify the work for correctness and finally click
> on "Move upstream" to send off in one go to GNOME CVS. Or simply commit
> manually.
Oh for seamless moving of translations around ...
The main issue here is that I think generally you need someone to 
manually deal with any merge conflicts.
So I've been trying to resolve that first, and have some working code 
for Pootle that does it nicely as of today.
So version control stuff is next on my list ... but being able to move 
stuff between different Pootle or other web-translation sites would be 
great (particularly as there seem to be a few different translation 
sites around, its important to be able to move stuff around).

David