Just to be safe, I do it everywhere these files exist.
Did I emphasize that these are output files from RH X5.0.2
build 801?
You need to watch what happens when you recompile and
republish. In my case, RH seems not to mind, or doesn't know, that
I've changed a particular output file, and if it has no internal
reason to overwrite it, RH leaves it unmolested in the published
directory.
As an aside, I see some places where RH dynamic html code
seems to be inserting tags on the fly, but I don't know enough to
analyze it. And I'm not sure that dynamic html carries through on
all browsers -- let alone Internet Explorer after V 5.5.
Sometimes I wondered why certain files were being
overwritten, because I thought they hadn't changed. Then I found
that, indeed, some of the housekeeping code needed to change
because I had done something with the TOC, for example. So I have
to make the changes again, in the newest output.
In one merged project, I give users optional access to the
subprojects individually. In this case, the subprojects are release
notes that can stand alone, and the merged project lets them use
the master TOC, Index and Search to look at "what's new" for a
number of years back.. This definitely requires all subprojects to
be patched.
Another point:
You can find some of the "defective" files, if that's what
they are, in the RH program folder RoboHelp
Office/RoboHTML/WebHelp5Ext. These are templates where you can fix
tags for some files and expect the patches to carry through to
output. As I've said in earlier posts, I can't be certain they make
any difference but they don't seem to hurt.
You may find that Adobe fixed some or all of this in RH6.
Regards,
Harvey