Re: Hello / Transifex !

Yes I've checked the transifex documentation and starting from v1.0
transifex doesn't interact with svn anymore (btw he gets the po files
automaticaly via http)

The problem is to push the files from transifex to our svn.

So I guess we have to code something around transifex to do this
automatically

I will make a quick install to first see how it works and what can be
done. I'm used to develop with django so I hope I can come up with some
solutions.. I'll keep you posted on this

JP

Le mardi 15 février 2011 à 18:42 +0100, Wolfgang Bornath a écrit :
> 2011/2/15 Jean-Philippe Braun <jpbraun-4qZELD6FgxhWk0Htik3J/[email protected]>:
> > Hello,
> >
> > It seems that you can do this with the transifex client : see
> > http://help.transifex.net/user-guide/client/client-0.4.html
> >
> > It allows you to work on po files locally (online or offline) and then
> > push them back to the transifex server
> 
> As we found out during tests and discussed at Fosdem the current
> transifex has problems to work together with svn. Here some excerpts
> from an irc meeting last week:
> 
> 18:38:05 <Jehane> we have said that transifex can not commit in svn in
> the way we want to work
> 18:38:51 <misc> yup
> 18:39:08 <Jehane> 'cause we are planning to have proofread of the
> string before commit
> 18:39:26 <misc> so the idea is to use transifex as a staging area
> 18:39:44 <Jehane> and it's not possible to have a "to proofread"
> status in transifex (as far as I know)
> 18:40:03 <misc> let's say that a developper create a shiny new
> software that display duck
> 18:40:23 <misc> so he create the software, tx fetch the .po
> 18:40:42 <TeaAge> what about using transifex for translation and after
> string freeze the commiiter have to push the .po to svn manually
> 18:40:44 <TeaAge> ?
> 18:40:51 <misc> TeaAge: that's what we proposed, yes
> 18:41:38 <misc> so translators send their work in progress on transifex
> 18:42:05 <misc> once the .po is ready ie have been proofread, either
> someone from the team commit the .po ( using tx-client )
> 18:42:16 <misc> or the developpers fetch it ( usig tx-client again )
> ...
> 18:43:53 <misc> Jehane: tx do not use svn
> 18:44:11 <misc> tx store the .po in a postgresql databse
> 18:44:31 <misc> ( or anything supported by the django framework, ie
> mysql/sqlite/oracle/pgsql )
> 18:44:55 <misc> the previous version was using svn to store
> everything, but it was inflexible, IIRC
> 18:45:38 <Jehane> ok; so how tx is updating .po files when they are
> updated in the source repository ? (news strings, etc)
> 18:45:49 <misc> Jehane: it depends
> 18:46:25 <misc> either it can fetch them using tx-client, or people
> can update by hand ( ie upload using the web )
> .....
> <misc> #info tx do not preserve comment and history
> Explanation:
> <Jerzy> each pot files stars with comments, like: some descrpitive
> title, translators and so on. It is generic.
> 18:52:50 <Jerzy> after editing some entries are added by translators
> (their names, email, year)
> 18:53:31 <Jerzy> tx reverts all comments to its generic form
> 18:53:48 <Jerzy> from pot file
> 18:54:04 <misc> mhh, it doesn't simply add the information as given by
> the date and username ?
> 18:54:06 <Jerzy> history of translators is lost
>