Support for Subversion

Question

We already use Subversion. Having another repository to manage just for help files seems like a step backwards.

I'm thinking that maybe we won't bother with RoboSource Control 3.1 and just use Subversion even though there seems to be no support for it as a RSC 3.1 Repo. SO that means we won't be using RSC 3.1 at all which is a pity.

What have others in this sort of situation done? How well has it worked?

RoboColum_n_ · Answer

Hi Chapmasj and welcome to the RH community.

We have never used the in-built RoboSource Control application preferring to use a third party application. Previously we have used MS Visual SourceSafe but more recently we have migrated to using SubVersion. Our main reason was not using RoboSource Control was the need to integrate the output with our application's build process. As our Development department uses SubVersion it makes sense for us to just output the help to the location where it can be automatically built into the application.

Our experiences have been positive on the whole. Using SubVersion for RoboHelp projects does have a learning curve, not least because even opening a project in RoboHelp flags it as having changed in SubVersion. Also you need to understand the RH Project file associations. For example adding a new topic complete with a TOC entry, index keyword and glossary entry updates numerous files. There is a small issue with the .SVN folder that SubVersion creates. You can read about that here, although this is not an issue for us.

Read the RoboColum(n) for a tips, tricks and musings on the Technical Communication Suite products.
Follow the RoboColum(n) on Twitter

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.