How to generate a Word file from a master help file?

Report · May 25, 2010

Hi,

I am using RoboHelp 7 for Word. I have a complex project (I inherited it--no way would I have done things this way!) that consists of about 112 projects. Of these, 111 have content and their CNTs refer to the CNT of the master project. The master project is basically just a shell, with only one topic and the CNT referring to topics in the sub-projects. All the sub-projects are included in the Dependencies as External Help Files.

I would like to generate a Word document of this help system. So far when I've tried just going to Printed Documentation and generating a Word file, it dies in just a matter of seconds. I can generate the master help project, however, and the system comes out right with all the sub-Help files.

Some people have suggested I generate the Word file for each sub-project and then create a master Word document linking to all. If I have to, I will, but I'm hoping for an easier, more automatic way to do it. Any ideas?

Thanks for any ideas.

Report · May 25, 2010

Welcome to the forum.

First of all RoboHelp for Word was never designed to produce merged help so it will always be a bit of a challenge. Some years ago I was sent a method produced by Jeremy Wadley and you can find that at http://www.grainge.org/pages/authoring/merging_webhelp/merging_method_word.htm

Printed documentation cannot be generated for a merge using either RoboHelp HTML or RoboHelp for Word. You do have to generate a document from each layout and then merge. The number of projects you have makes that an unenviable task but I am sorry to have to say that is the way it is.

Unless there is a valid reason for that number of projects I would be looking to reorganise the whole thing. At the same time maybe switching to RoboHelp HTML should be considered if that is practical.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.

Report · May 26, 2010

Thanks, Peter. That at least tells me what I cannot do and saves me time going down the wrong path. Unfortunately, I have to leave the original project as is, in RH for Word with so many separate files. But, for this printed documentation, I have more freedom. I think that I will import all the RTFs into RH for HTML and create a single new project in HTML. Only a few RTFs are updated each year, so it won't be too difficult a task to reimport the changed ones each time and republish the printed documentation.