3 Replies Latest reply on Sep 28, 2009 1:05 AM by Nick@Tag

    single sourcing topics across projects?

    Nick@Tag Level 2

      RH8 HTML.


      Hi all, so I've had a request from the powers that be and I'm wondering how I can go about it best.


      The scenario.

      I have my project in RH8, very large, published to webhelp and air browser based help.


      Another person is now setting about creating a document for best practices and other company wide things and within this document that they are going to create will be areas of work that I'm doing.


      Its possible, or likely this person will use RH also, so I'm wonderig if they create a project of their own, are they able to use topics from my project? and can these topics be single sourced, so if I update them in my project, the changes will be reflected in the same topics that they use?


      Because I only have one licence at the moment I can't test and find this out myself.

      I've looked around but cant find any information about it, so I'm thinking perhaps not?


      So basically, is it possible to have shared topics in various projects single source back to one governing topic that I or anyone else control? I'm guessing somewhere these 2 installations of RH will have to talk to each other to update the topics etc, so perhaps a server needs to be involved - is this where RHServer comes into play or Source control?


      I've looked at merged help, but its likely this persons output will be .doc, maybe webhelp - but even if it is would the functionality that I'm after exist?


      any advice appreciated.


        • 1. Re: single sourcing topics across projects?
          RoboColum(n) Level 5

          Installing RH over a server is a definite no-no. You'll have to have an additional RH licence to allow both of you to use it at the same time. Read this link to understand the difference between RH Server and RoboSourceControl. You definitely don't need RH Server although you could use RoboSourceControl (or another source control product). That would ensure two of you could not edit the same files at the same time.


          It sounds to me like you need to have a merged project setup. One project would have the content that the same in both documentation sets. You could each have another project that would include the merged content. This would work regardless of your output. For example you even produce webhelp and the other person output to a PDF if you wanted. If you are producing merged webhelp you do best to check out this link first.


          Read the RoboColum(n).

          • 2. Re: single sourcing topics across projects?
            Willam van Weelden Adobe Community Professional & MVP



            Apart from what Colum suggested, you can use a source control application to 'single source' your files. I use MS VSS and to 'single source' the file, I link files (using the same file within different VSS project) within VSS. I use a simple batch to get the latest version of these files for all projects every morning.

            Changing the file from any project will change the file in the source control database. Just getting the latest version in all projects, synchronizes the files.





            • 3. Re: single sourcing topics across projects?
              Nick@Tag Level 2

              Great, thanks for the responses.

              I think I'll try and get another licence or at least a trial set up on another machine and test this out.


              Think it will turn out that I will control the files that the other user may want to use, without them needing to make any changes. So source control might be the simpliest way to go.


              time for testing.