Hi everybody, Tx is a good translation platform, but may be we wanted too much from it and too fast.
So, it is allways possible to work with it - at least till we find and test a good and stable solution - as it follows: - create a Tx project, I've created one to test: https://www.transifex.com/projects/p/mageia-test/ - team members can work with it online, - team submitters gather the files and manually update them on svn, - this way "no svn" translators can use Tx online or download the files from websvn, translate them offline, and send them back to the submitter, - the submitter fill the gap between the Tx and svn, this way he can check and validate the updated strings. Oliver and Remy has to rely on team leaders and their assistants to ease their job and content to simply supervise them. Having a collaborative tool, even is it's not perfect, is better than not tool at all. Cheers, --- Florin Catalin RUSSEN Mageia i18n - Romanian Team "You don't need eyes to see, you need vision!" >________________________________ > From: Yaron Shahrabani <[email protected]> >To: List dedicated to internationalisation issues <[email protected]> >Sent: Thursday, 4 April 2013, 11:27 >Subject: Re: [Mageia-i18n] What was wrong with Transifex? > > >I think it can also push back, I've done it with Github once, we can set up a >test repository and see if it works before moving it into production. > > >YaronShahrabani ><Hebrew translator> > > >On Thu, Apr 4, 2013 at 12:47 AM, atilla ontas <[email protected]> wrote: > >2013/4/3 Oliver Burger <[email protected]> >> >>Just to summarize for those of you, who were not with us in the beginning: >>>- It was decided to use a web plattform, that can be used with our mageia >>>accounts >>>- At that time we opted for tx, because it "looked good" >>>- Tx always was a pain for me and akien because it does not have an svn >>>integration, so we had to sync manually between the svn and the tx database >>> >>>- At some time something broke inside the tx database, we were never quite >>>sure, what it was but it resulted in having loads of untranslated strings in >>>the po files although they were translated in tx >>> - When our servers were updated from Mdv2010.1 (which they were using in the beginning) to Mga1, something broke, misc (our then tx maintainer) who did try to solve it never found out, what it was, it must have been something with the underlying software (python, django, postgres, whatever) >>> >>>So yes, we do need a web platform. It should be >>>- easy to use for those i18n people who are not fond of using svn >>>- easy to maintain for the i18n team leaders (meaning it SHOULD have an svn >>>integration >>>- easy to maintain for our sysadmins >>>- give those people who prefer working directly with svn the freedom to do so >>> >>>As I see it, tx.net can't do that, but if you show me I'm wrong, I'm glad to >>>learn... >>> >>>Cheers, >>> >>>Oliver >>>Thank you. Did you read http://help.transifex.com/intro/one-dot-zero.html ? >>>From that page, i understand that tx can pull directly from VCS. But it >>>won't push back. Is it main problem? I didn't search for other problems, i >>>think those won't be problem if we use tx.net instead of own installation. >> >> >>I think a script can do svn push in tx. Add it to svn server as a cron job >>and it directly pull from tx and submit to svn. Is it so hard? I haven't look >>in Pootle. May be it worths than tx. >> > > >
