Sara,
What I would do in your situation is to create a CHM file
that has all your content, but use the WinHelp 2000 viewer to
display the HTML topic in your WinHelp file on the right hand side.
You would have to code a topic-level macro to jump to the correct
topic in the CHM file. You will also need to distribue the CHM file
with your WinHelp projet files so, for example, if you have
APP1.HLP, you would also distribute APP1.CHM.
This approach does three things for you:
1) it allows you to code your content in HTML while you wait
for Dev to catch up
2) it allows you to be ready for when Dev says, "we're
starting the conversion of our apps."
3) it allows you to do the conversion to HTML in pieces. You
only have to add the topic-level macros to those topics that have
been converted to HTML. You can still have some topics in WinHelp.
I do this now for our internal help file and it works well.
When Dev changes, you will already have your content in HTML
and will only have to make changes that are based upon any
interface changes. Otherwise, you would have to code the HTML as
part of the conversion from WinHelp to HTML and also code the HTML
to adapt the changes that are made to the interface.
Hint: At the same time that you are creating the CHM file,
you should be coding your Index and building the TOC, even though
no one will see the TOC and Index until you are 100% using CHM
files.
Paul Hanson
Technical Writer
Adobe Community Expert - RoboHelp
http://www.macromedia.com/support/forums/team_macromedia/team_members/200.html
Quintrex Data Systems
http://www.quintrex.com