I haven't tried it but I'm pretty sure it's possible, but you will have to edit each and every link by hand and the ToC, and the merged files entry in the HHP, and maybe some more. Maintenance will also be a pain because you'll have to recompile to test things.
If it were me. I'd throw it back to the team and say "I can do it, but it's a lot of work. You're paying the bill, how important is it?"
Note that if you simply do not deliver (some of) the sub-CHMs this will not break the parts which are delivered. Maybe that will satisfy them.
If you register the location of your Help files as part of the software installation process, you can store them in different folders and they'll still be able to find each other.
The normal place to register Help files is under the following key in the Windows registry:
Appending onto what Pete kindly offered up, RoboHelp HTML includes a nice tool that will facilitate this for you. The tool is called HTML Help Registration and is found in the Toolbox tab (RoboHelp 6 or earlier) or the Toolbox Pod (RoboHelp 7 or later).
Click View > Pods > Toolbox to open the Toolbox pod.
The Image above is scaled by the forums and looks bad. Click to see it at full size...
Many thanks for your valuable time and suggestions. It worked.
I registered 30 chm files, and the master CHM with all the links worked out fine even if I had placed the CHMs
RoboHelp HTML includes a nice tool that will facilitate this for you. The tool is called HTML Help
Registration and is found in the Toolbox tab (RoboHelp 6 or earlier) or the Toolbox Pod (RoboHelp 7 or later).
But, wait now the big query is how will it work in the release folder and customer machines.
These files are to be registered in the customer machine too.
So, my question is do you use any package tool to deliver the files to the client?
If we can write a patch file for the help files, then the customers will not have any
hassles of registration. They will need to just double-click on the exe file and it should work.
This is the only solution to this problem as far as I know.
1 person found this helpful
Are your Help files installed on your end-users' computers as part of a software installation process? If so, the developers with whom you're working should be able to register the location of the files as part of that process. If not, one solution may be to create a registration entries (.reg) file that contains the required entries and instruct the end-users to run this. See this Microsoft article for details:
This is problematic, however, because you can't be sure that the computer on which you've created the .reg file matches your users' computers. For example, a .reg file that registers the Help files under a location on the C: drive won't work on computers where the files are stored on the D: drive.