Some frameworks, such as Grails, have plugins that can take care of static version control for you, taking care of correctly linking files called versions to where you use this file, and only overload the version of files that have been changed.
If you are in such an environment, these plugins are fantastic and usually work very well, but if not, the most common thing you can do would be to put together a series of scripts that are run using a pre- bind SVN script. Scripts will have to take care to format files that have been modified. Depending on which framework you use, displaying the name of the resource files in the code will be more problematic, but you can either write a plug-in that can understand it on the fly, based on an unidentified file name, pattern matching, or simply update the link directly in the code (something like sed or awk can do this, theoretically, although it will probably require impressive scripting skills)
So, the best solution would be to find a plugin for your framework that can handle it transparently for you. The next best option would be a series of pre-commit hook scripts that will update the modified files and then search / replace your codebase for the places where these file names should be updated and make changes.