I'm developing a set of policy manuals that will be
accessible from both a new application that we are building as well
as our intranet site. The policy manuals will not be the system
help files. Our IT folks are using CHM format for the help file and
want the business to publish the policy manuals in the CHM format.
Apparently it's easier for them to build context sensitive help and
policy manual hooks with chm then web help. These files will not be
distributed to the client desktops but will be accessible from the
network.... The necessary changes have been made to the network
server and desktops to allow the CHMs to be opened from a specific
My policy manuals have hyperlinks between the different
projects. In addition I have merged to manuals with the intent of
merging more to provide a consolidated ability to search for
policies accross our office's units and services. (Note plural
services all sharing a common application)
Interestingly after publishing the currently three projects
(one being a consolidated project for two manuals.) and after our
IT copied the chms to the production environment, I tested the
product and found that the hyperlinks navigate back to the files
where I originally published them. Regretably because of change
management protocols I can't publish directly to the production
A similar problem exists with the merged projects.
I was able to go into TrueCode and have the CHM in effect
default to the current folder where I just want to bring up a
specific topic bring in a chm file stored in the same folder using
My problem is that I can't get get the a hyperlink to do the
same thing but open up the entire chm in a new window with it's own
table of contents, index, search. The best that I could do was:
p><a href="file://c:/Documents and
Getting rid of the folder info, leaving just the file name does not
work. Ideally I don't want to specify the server folder information
since this could change over time and would mean many changes.
In addition I can't see how do do anything similar with a
merged project. Maybe there's something in a baggage file but I
don't know which one.
Unfortunately there is not much HTML type support inhouse.
There is a work around for the servers and we have that up
and running. So good news there.
I have been able to resolve all issues except being able to
get one CHM to open up another CHM without having the pathway
specifically defined. For example: p><a
works fine. But take away the pathway and it doesn't. Tried
href="file://../PGS_Jurisdiction_Manual_(09-08-2006).chm" and tried
href="file://PGS_Jurisdiction_Manual_(09-08-2006).chm" Don't want
to hardcode pathways in several projects.
I was just hoping I was doing something wrong or could use a