I will start inviting translators around September 2011. (I hope to have a dummy translation ready by then) Please contact us via the mailinglist if you like to help.
[Updated to follow reality. Rescheduling now as Subversion 1.7 is on its way]Tobias commented
I think, there's no need for this. If you are a programmer and use Visual Studio, it's simply needed to know English technical terms. The terms are the same or similar in other languages, or often in other languages the English term is commonly used.
If you do not know the SVN basics, a translation is fruitless.
A view years ago, I wanted to have a translation for another subversion tool (to german).
When I had this translation, I were none the wiser. A book In german then helped, and since that time, I don't want a translation of SVN terms at all.
Note that it is possible to leave the project name empty in the ‘add to subversion’ dialogs. This makes the entire path/url user editable.Tobias commented
In this scenario the solution selves should not stand under version control!
=> the projects within one SLN are located in very different repo-dirs!
( In fact, every user should build his own SLN, depending on what Module he is responsible for .
For other Modules (Assemblies he is not responsible for), he can add a reference to a binary version, exported once from repository) )Tobias shared this idea ·