From your responses, I'm guessing that you're unclear on the
differing/converging aspects of RH source & output files in a
merged project. The best structural setup, in my opinion, is
Peter
Grainge's method.
Using that method for our "IMS" product help (42 child
projects), we have structured this:
C:/imsmerge
C:/imsmerge/imsportal/imsportal.xpj (contains a redirect page
only, to the home page [site_map.htm] in ims_start)
C:/imsmerge/projects
C:/imsmerge/projects/ims_start/ims_start.xpj (contains the
home page and other navigation pages)
C:/imsmerge/projects/projA/projA.xpj
C:/imsmerge/projects/projB/projB.xpj
etc.
The generation paths for them are these:
C:/imsgenerate/index.htm (output from the imsportal project,
with RH frameset info and pointer to start page in ims_start)
C:/imsgenerate/mergedProjects
C:/imsgenerate/mergedProjects/ims_start/start.htm (output
from the ims_start project)
C:/imsgenerate/mergedProjects/projA/start.htm (output from
the projA project)
C:/imsmerge/mergedProjects/projB/start.htm (output from the
projB project)
etc.
Therefore, a link from projA to ProjB needs to go back one
directory (into the mergedProjects directory), then into the
target:
EX: a href="../projB/MyTargetTopicLink.htm [tags not
included]
All our topics call a "feedback_script.js" file (a mailto:
setup), but that JavaScript file resides at the root (in the
imsgenerate directory), so that link is:
EX: script src="../../feedback_script.js"
language=javascript type="text/javascript" etc. [tags not included]
I'm not familiar with the Javahelp output either, but links
is links is links... That is, when you are working in the projA RH
project, and you want a link to projB, it's wise to actually have a
copy of that projB project on your machine so that RH can create
the proper link (unless you want to type in the correct path
yourself, which you can do). However, the link path structure must
be the same "relative" construct in the generated folders as it was
in the source folders.
Good luck,
Leon