On 19 December 2011 12:13, atilla ontas <tarakbumba@gmail.com> wrote:
2011/12/19 Timothy Pearson <kb9vqf@pearsoncomputing.net>:
> <snip>
>>
>> But we do have an instance of launchpad, which the OP mentioned. I wonder
>> if we could use it for translations? (our launchpad service is the
>> Quickbuild)
>>
>
> The component you would be looking for is Rosetta.  I have heard nothing
> but complaints about it from those involved in Ubuntu development though,
> so I don't know if it is a good idea to rely on it.
>
> In the meantime we could allow translators direct write access to the
> translation files in GIT, those files being editable with KBabel or
> similar.
>
> Tim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net
> For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net
> Read list messsages on the Web archive: http://trinity-users.pearsoncomputing.net/
> Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
>
Thank you for all replies. I think a git access is a good beginnig. We
have write access to Mandriva svn repositories for example. But, for a
good translation team work it should be done via a web interface. I
humbly recommend transifex. It allows people who are interested in the
project can translate at anywhere and on any computer. For example, i
mostly work on translations launch times at work on a windows crap.
 Also, such an interface provides us a good translation statisctics.

Transiflex is really cool. My only reservation is that we can't have a local installation of it. I think we try and be as self hosting as possible.