Correct me if I am wrong but this sounds like you have integrated SVN with RH via the PushOK plugin? We haven't used this plugin, preferring to manually Update and Commit changes via the Windows Explorer menu items. This works well for us and allows you to move topics around and rename them whilst keeping the audit log history.
You are absolutely correct. My apologies for not mentioning PushOk. Completely spaced out. Up until now, it has done wonders for us and it has allowed us to manage everything from within Robohelp, alas nothing seems to be perfect.
You did however give me a few ideas so thank you big time!
To add to Colum's remark:
I noticed this in TFS and VSS, so I suspect the same goes for SVN: The problem here is that RoboHelp doesn't support moving files in version control. When you move a file, RoboHelp will delete the existing file and will add the file in the new location as a new file in the version control. So the problem here seems to be with RoboHelp instead of SVN.
I've been thinking about this a bit more. SVN would have revisions for the topic up to the point it was moved to a new folder. If the move to a new folder does not bring the history with it, the history is not deleted. It will still exist in the old revisions. So perhaps the way forward is to have a way of mapping the old revision to the new folder position. One way you could do this is to have a topic inside your project that lists things like the:
- Old location
- Last revision number
- New location
If this was in your project it would also be in SVN and therefore have a trail of what has been done.