Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Hi, I'm wondering if anyone has done this (merged help projects with context sensitivity) in RH8 (output: CHM) and whether there is any newer information. We have a master project with three slave CHMs, and we finally got those working together seamlessly, but without context sensitivity -- we're just getting started on that aspect. Any advice would be appreciated!
BTW, the requirement that I've found mentioned on various threads that the master project not contain any topics does not seem to apply (or, not anymore). On the contrary -- if there are no topics and no index entries, the index doesn't work. Same with the requirement that the window be defined as a global window ($global_windowname). Our project works fine (so far) even though the master project contains topics and the windows in the projects differ.
Copy link to clipboard
Copied
I am just focussing on your second paragraph about the parent having no topics etc.
First that is more for WebHelp and is because of the way cross project links are created. As with merged CHMs, you can have your source projects scattered all over the place and as long as you generate to one location, the merge will work. However, whilst you can do that with WebHelp it is not recommended. You would have a bit of a time creating cross project links as you would have to stop and work out the relative path in the output and manually enter that. By following the method on my site, you can use the interface to work out the relative path.
For WebHelp, the parent does have to have a topic but it is a redirect so it is not seen.It's quite OK to have other topics in the parent as long as you avoid parent / child links. With merged CHMs you don't need the redirect because, to repeat, cross project links are not an issue there.
Also in merged WebHelp, the parent index can be blank and the indexes in the child projects all display merged. I'm not sure that would be true in a merged CHM setup.
Key point here is to keep in mind different rules apply for merged WebHelp and merged CHMs and you need to keep that in mind whenever you read any post.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
Here I am back at it and wondering if there is an "automagic" way to merge the .chm files with RH9 ... has anybody explored this?
Thanks in advance,
msmanitoba
Copy link to clipboard
Copied
If you are using RoboHelp 9 maybe Item 13 in http://www.grainge.org/pages/authoring/rh9/using_rh9.htm will help.
Adobe are aware of the problem.
See www.grainge.org for RoboHelp and Authoring tips
Copy link to clipboard
Copied
RoboHelp 9 users should update to the just released Service Release 9.0.2.
See www.grainge.org for RoboHelp and Authoring tips