![]() |
Linking Word Documents to RoboHelp Classic Versions |
![]() |
|
Linking was introduced in RoboHelp 7. This page is about the screens you will encounter when linking Word documents to RoboHelp 9 and above up to and including RoboHelp 2019 Classic. If you are using RoboHelp New UI, see the RoboHelp Tour for the steps. It is a much improved process.
If your are using RoboHelp 9, it is vital that Service Release 9.0.2 is applied to your machine as that updated the process in important ways. What is described below will not work unless that service release is applied.
The process for RoboHelp 9 is the same for RoboHelp 10 and above except that in later versions you will be given the option during the import to automap the styles. RoboHelp will then match any Word styles with identical style names found in your CSS.
Parts of the linking process are shared with importing and you may find it easier to understand linking if you look at importing first. In describing the process here I will be using the same Word document that I used when describing importing. I do recommend that you use that document to follow these steps so that you know you are getting the expected results and what you get is not tainted by something unique to your own documents. Click here to download.
For the purposes of following the process here, please work with a new project so that it is not affected by any settings applied to an existing project.
Typically you will be linking to a document that has been produced by others and over which you have little or no control. However, if you can clean up the document as described in Before You Start in the Importing Using RoboHelp page, it will help get a better end result.
Note the Link Option field.
- If you select Create a Reference, RoboHelp leaves the Word document where it is on your network so that any changes to that original are reflected when you next generate an output.
- If you select Create a Copy and Link, RoboHelp copies the file to the project and any subsequent changes to the original will not reflect when you generate an output. You might want to use this method when there is a document that cannot be used as needed by the owners of the document but where it contains content you need. You would edit your copy and update that as required using Word's Compare with the two copies of the document. Former users of RoboHelp for Word might also use this option so that they can edit in Word.
In the Load Settings From field, if you have previously imported or linked to a Word document and exported the settings, you can reuse them by browsing to the ISF file that was created. Otherwise leave the field unchanged. If you have not selected an ISF file, you will not be able to Edit the Word Document Conversion Settings at this stage.
When you link a Word document, there is no option to add the TOC / Index / Glossary to one that already exists in the project as there is when importing. The reason is that RoboHelp would not be able to tidy up redundant entries when you update the link at a later stage.
After the link is created, right click the document in Project Manager and select Properties. A window will open at the Content Settings tab. There you can create a new TOC / Index / or Glossary. Do that and then open the TOC / Index / Glossary that you will use when you generate the help.
If you now go to the document and make a change, back in RoboHelp you will note the document again shows the warning triangle to let you know the topics are no longer in synchronisation. If you attempt to generate a fresh output a dialog will be displayed asking if you want to update. Assuming you do, click Yes and you will see a progress bar while RoboHelp updates the topics, then you will see the usual layout dialog.
You do not have to wait until you generate a layout to update the topics. At any time you can right click the document and select one of the options for updating.
The HTML will not be the same as with imported documents but it does display correctly with the documents I have tested.
Generally the idea is not to edit the topics created as the update process will overwrite any changes you have made. However, if there are reasons for making changes that you do not want overwritten when the topics are updated in the future, you can prevent specific topics from being overwritten. There is not an option to preserve just specific areas.
Right click the document in Project Manager (not the topic) and select Properties. In the File Update Settings tab, tick the topics that are not to be updated.
In Step 4 of The Process I stated that the settings applied in Project Settings will apply to all linked documents. I can envisage scenarios where the requirement would be to have a different appearance for different topics. If that is your requirement, try these methods
When you map the styles, in the RoboHelp Style field set that to the [Source] option. You will then get whatever has been set in each of the Word documents. That will of course only work if the Word document has the styles you want.
In Editing the Topics above I explained how you can stop topics created from a linked document from being updated. In theory you can use that to apply different styles to different documents. I say "in theory" simply because I have not tested it. The steps to follow would be:
Repeat the process for each of your documents in turn applying the different mappings you want.
Whenever you generate a new output you will have to manually check whether the source documents have changed. For any document that has changed:
If you find the information and tutorials on my site save you time figuring it out for yourself and help improve what you produce, please consider making a small donation.
Date |
Changes to this page |
31 Jan 2020 |
Amended to show only for Classic versions. |
17 Jun 2019 |
Amended to cover applicable RoboHelp versions. |
06 Feb 2017 |
Topic reviewed. Any screenshots may differ in your version of RoboHelp but the functionality is the same. |
01 Jan 2013 |
Step 7 revised. |
22 Dec 2012 |
Step 7 added to The Process. Covers including the index, TOC and glossary. |
23 Nov 2012 |
Amended to cover RoboHelp 10 as well. Automapping added to process. |
19 Jan 2012 |
New topic |