OliverCheers,As I see it, tx.net can't do that, but if you show me I'm wrong, I'm glad to learn...- give those people who prefer working directly with svn the freedom to do so- easy to maintain for our sysadmins- easy to maintain for the i18n team leaders (meaning it SHOULD have an svn integration- easy to use for those i18n people who are not fond of using svnSo yes, we do need a web platform. It should be- 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 that time we opted for tx, because it "looked good"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 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)