Are you planning on extending your website with more languages? This can be a great way of reaching new customers and supporting existing customer. At transmachina, we can help you avoid the pitfalls and launch your multilingual website on time and on budget! Contact us today for some free advice.
Call now
Feel free to contact us at any time to discuss your multilingual or translation project.
I've always thought of doing this, and actually just recently, I also put my drupal repositories on an svn server that is available for everyone via http (previously, my repository was only available over ssh). I won't bother publishing the url here though, since that would water-down your effort.
I recently published a script for updating drupal modules in a subversion working directory. It's sort of like svn_load_dirs. It basically just deletes all the files in a module directory (except .svn dirs) and then untars the new module. Then it looks at the "svn status" output and looks for the "M", "?" or "!" and commits, add-commit, or remove-commits, respectively, thus bringing a module up to a new version.
The problem with this is that I lose my local changes, however, I can always do an "svn log" and merge some old changes back into the repository. I may make a script to do this as well. Because the commit message from the "update module" step I described above is always the same auto-generated type of message, I can search for them in the svn log output and detect which changes were my own. I can then auto-merge those back on top of HEAD. :-)
Great work!
I've always thought of doing this, and actually just recently, I also put my drupal repositories on an svn server that is available for everyone via http (previously, my repository was only available over ssh). I won't bother publishing the url here though, since that would water-down your effort.
I recently published a script for updating drupal modules in a subversion working directory. It's sort of like svn_load_dirs. It basically just deletes all the files in a module directory (except .svn dirs) and then untars the new module. Then it looks at the "svn status" output and looks for the "M", "?" or "!" and commits, add-commit, or remove-commits, respectively, thus bringing a module up to a new version.
The problem with this is that I lose my local changes, however, I can always do an "svn log" and merge some old changes back into the repository. I may make a script to do this as well. Because the commit message from the "update module" step I described above is always the same auto-generated type of message, I can search for them in the svn log output and detect which changes were my own. I can then auto-merge those back on top of HEAD. :-)