If you are only creating merged Microsoft HTML help, then create a normal topic instead of creating the blank redirect topic. You will need a parent with at least one topic that is seen by the end user and is set as the default topic. You do not need the redirect topic described in Step 5 of the WebHelp instructions, indeed you must not use that method for this type of help. Setting up the merge: Parent project redirect The link is relying on the name of the CHM file and the location of the topic within the target CHM file. The reason you do not have to apply the same structure is that the links between topics in different child projects are created in a different way, as described below. Nevertheless, I recommend that you do as it does keep things tidy and it will also help if you have to create WebHelp at some point in the future. You do not have to use the same structure as is described in the Merged WebHelp content above. Stick with alphanumeric characters and no spaces. They have been found to cause problems with merged Microsoft HTML help. CHM filenamesĪvoid the use of underscores, the hash symbol and suchlike in the names of the CHM files you create. Also see the RoboHelp Tour if you are using the New UI versions of RoboHelp. It covers only what is different with merged Microsoft HTML help. This page should be read in conjunction with the page for Merging WebHelp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |