Further to merging the parent into the sub project - this
functionality works a treat when done in HTML Help Workshop, but
results in the infinite loop problem when done in RH - I think it
was okay in RH2002 and was subsequently "broken" in X4 (possibly
X5, but I've lost track of my versions).
With ehelp in/just finished its deaththroes and a fix
unlikely, we implemented solution #2 here:
Helpware
- Context IDs with Merged Help
Note: we couldn't get redirect.xhtm to be excluded from
search etc, so ours is named redirect.1.xhtm
Opening the sub help files individually (outside) the program
will only show the TOC of that help file, with no indication that
it is related to any others. The inter-chm links still work within
the topics, but the appropriate TOC won't display.
Within the app, the parent chm file is the only chm file
opened, ensuring the sub chm TOCs always display. Context calls are
redirected through an ini file and special redirect topic in the
parent chm.
Because we have many large products that may or may not be
available depending on who has what installed, we keep our IDs in
the individual projects and generate separate ini files containing
the mappings.
So:
SubA.chm has a corresponding ini file
SubA.ini which contains references like:
1000=its:Master.chm::/redirect.1.xhtm#its:SubA.chm::/FirstFolder/FirstTopic.htm
Our developers kindly wrote a batch file that converts the
Robohelp MAP ID report text output to a nicely formatted ini file,
so all we have to do is assign IDs in RH, run the report and run
the batch file.
Hopefully one of the solutions on this page can be of use.
Also, perhaps submit this functionality to the Adobe wishlist
- I'll have to remember to do that myself.
Adobe
Feature Request Form