Hello, I've got some good news and some bad news.
Good news --------- First the good news: translate-toolkit and Pootle have been completely migrated over to Subversion yesterday. The CVS repository has been locked down to prevent accidental commits. You can browse the new repository here: http://svn.sourceforge.net/viewvc/translate/ A quick primer. Checking out the trunk: svn checkout https://[EMAIL PROTECTED]/svnroot/translate/src/trunk translate Checking out a branch (you can find branches through the web interface): svn checkout https://[EMAIL PROTECTED]/svnroot/translate/src/branches/some-branch translate-some-branch Merging branches is a bit tricky, you'll probably want to read the corresponding sections of the Subversion book. `username` should be your standard SourceForge username. If you just want anonymous read-only access, leave 'username@' out. Note that your password is saved when committing, so you don't have to retype it every time. This behaviour can be disabled in Subversion's configuration. Getting diffs, updating, committing works as usual: svn diff; svn update; svn commit. If anyone is having difficulties with Subversion, I'll be happy to help. By the way, you might also want to tweak Subversion configuration so it works better with Python projects. In ~/.subversion/config, check these: - *.pyc should be included in global-ignores, which should be enabled - enable-auto-props = yes - Make sure you have this line in [auto-props]: *.py = svn:eol-style=native;svn:keywords=Id Bad news -------- We tried but were unable to export the South African translations completely to a different project. The cvs2svn script that we used to get a Subversion dump out of a CVS repository had a bug that prevented the conversion (I submitted a bug report). Yesterday in the late evening I tried to work around the bug and succeeded to get a Subversion dump. That was quite a dumpfile, almost 1GB in size, 200MB after gzipping (the original CVS repository was ~300MB). I tried to import that file into SourceForge, but the import failed. The failure could be due to my workaround in cvs2svn or simply because the repository was too big. I see several ways out of this: - Assuming that the workaround was the culprit, wait until cvs2svn developers provide a proper bugfix, then try the import again. - Assuming that the size was the culprit, cut some fat off the repository. The OO.org translations seem to be by far the largest in size. Maybe it would be acceptable to throw away some tags and revision history? -- Gintautas Miliauskas http://gintasm.blogspot.com
signature.asc
Description: PGP signature
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
