Hi Phil
I wanted to think a bit on that.
You are, I believe, only talking about perhaps duplicating
the parent and not the children. The options are:
1] One parent with no redirect in it but minimal content. You
could have links to child projects but they will falsely report as
broken. That parent would work for both CHM and webhelp.
2] One parent with a redirect. For webhelp that would require
no changes but it would not work for a CHM output. If you simply
remove the redirect you would leave the CHM user facing a blank
page. That could be overcome with some minimal content and use of a
build tag to exclude it from webhelp. However, the content would
probably not sit comfortably with the content of what is otherwise
your default topic.
3] Two parents as you propose. That does avoid having to
remember to remove the redirect but you still have the issue of
what content is in the single topic, bearing in mind the default
topic, which is in a child using my method, already has that
content.
For webhelp only, I prefer the redirect but for "dual users"
such as yourself I think I would avoid the redirect and have a
parent with one topic and no links or a minimal number. The latter
will generate false reports of broken links but in this scenario
that should be manageable. In other words, option 1. However, you
are closer to what you need to produce so if two parents works
better, I see no reason why not.
On printing, how are you able to create printed documentation
in one go from an HTML setup? Are you perhaps talking about
selecting a book in the online help and selecting "All topics"? If
you are, have you looked at the formatting of the topics when
printed that way?
You say you have to spend a lot of time cleaning up documents
in Word. Some tidying up will be required for page breaks and table
borders but that should not take long. What are the problems you
have?
Help others by clicking Correct Answer if the question is answered. Found the answer elsewhere? Share it here. "Upvote" is for useful posts.