Hello,

I'm trying to use Pootle in the SIP Communicator project and I have some 
troubles making it work nicely with svn.

Indeed, the internal file format used in Pootle is PO gettext, and in 
our project we are working with the java .properties translation file 
format. Converting .properties files to .pot and .po is an easy process 
thanks to the translation toolkit, but this is an operation that needs 
to be done manually. I'd like to integrate Pootle with our version 
control to simplify the process.

Is there an easy method to tell Pootle that my files have to be 
processed through po2prop before the commit? Even then, I'm afraid that 
Pootle will track only the .po files and that the resulting .properties 
files will be ignored. Also, I'd like to avoid storing .po files in my 
version control. We have the same problem when checking out files from 
our version control, these need to be converted into po or pot after 
checkout.

I found a *very* complex solution involving temporary repositories, svn 
hooks, and cron jobs, but I'd like to know if there is an elegant 
solution out there?

Martin

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Translate-pootle mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/translate-pootle

Reply via email to