Moving OOo translation project over to Rosetta/Launchpad

[Tim Morley]

Jordi Mallach skribis:

> Thanks for your interest in Rosetta. At least one other team has
> successfully worked on translating OpenOffice.org using Rosetta, (the
> Kurdish team), and we're happy to get interest from other teams.
>
> How many active translators are there in the Esperanto team right now?

Depends strictly how you define "active"  ;o)  but there are two  
currently contributing work, me proofreading and coordinating their  
efforts, as well as two others who have been previously active and  
may return to the project at some point.

>> Feature Request 1, an absolute must-have: our existing .po files  
>> are packed
>> full of comments...
>
> Rosetta won't throw away this information, of course! The current
> version of Rosetta can and will show both translator and programmer
> comments in the interface. The current limitation that would bite  
> you is
> that while you can see them, you can't edit them to add more.

OK, that's considerably better than I thought, although still not  
ideal as you say.

Would this workaround be possible: export the .po file from Rosetta,  
add any comments to that, then re-import it? (Rather clumsy, yes, but  
would it be possible?)

> We have thought about how to support this in a clever way, but the  
> UI is
> tricky to get right for this feature.

Hmm... I'm sure you're aware of poEdit already -- could you not model  
this bit of the interface on that? You'd have a box to the side of  
the Original String/Translated String bit that would show the  
comment, with a checkbox under it labelled "Edit Comments". If you  
check the box, the comments become editable.

>> Feature Request 2, a would-be-nice-to-have: it'd be good to know  
>> *who*
>> translated *what*...
>
> Rosetta stores which launchpad user submitted which translation,  
> for all
> projects. We currently just show a list of the people who have
> contributed to a certain translation, and who was the last  
> contributor.
> We don't show what you're looking for, but the information is in the
> database. If there's a big demand, we might be able to use it somehow.
> That shouldn't be a too difficult feature.

Well, as a proof-reader, it's certainly an enormous help.  I  
understand you've got all sorts of priorities to attend to, but this  
would certainly get my vote as a Feature Worth Having.

>> I've also got a question: is it easy enough to upload the .po  
>> files we've done
>> so far to Rosetta?
>
> It is very easy.

That's good. One other thing springs to mind: if I've got a  
translator who pays for his internet connection by the minute, am I  
right in assuming he'll be able to download the .po-file he's going  
to work on, translate a couple of hundred entries in it, then merge  
his work back into Rosetta? (How are clashes dealt with in this case,  
e.g. if someone else has translated some of the same strings in the  
meantime?)


Tim