What's the smartest way to organize SVN for translated versions of the same project?

Answer 1

Hmm, generally you want to keep from having duplicates of "neutral" files, and you should never be translating files with actual logic in them (unless, of course, the logic itself varies between languages).

You could easily put the invariant CSS and JS files in a seperate top-level directory both in your source tree and on the server, though, so that shouldn't be too much of an issue.

There's no clever SVN trick you can use to avoid having to change all of the HTML files, but won't you probably need to update the translations for that anyways?

Answer 2

You should use svn:externals property for the purpose. Here is a brief tutorial.

In short, the property will help you reuse the same directories in different part of the repository. You can isolate common files in a directory and reference the directory in your localization directories.