This content has been marked as final. Show 5 replies
In order to create an HTML help project in RH I would create it in RH, not create a word doc then import it. (For a legacy situation I might import once.) If the document is created and maintained in RH then you engineer out the problems of duplicate IDs....
Thank your for your response.
Unfortunately, this is not an option.
The document is created by another department which does not take kindly to learning and using new tools when old tools suffice for their goals (which is documentation) and new tools only serve to help the software people. (Software people get no respect :( )
Any other suggestions?
Use the Track Changes feature in Word, which will identify the specific edits/deletes made by this other department. Then manually make the changes in your RH HTML project, instead of importing over and over.
Thank you for your reply.
That will work with small updates to the document. With large amounts of updates, it will probably be more work than to just import the doc into a new project and just remap the IDs.
(Normally, we only get the document after it has gone through all the approval process; i.e. all changes are accepted. But, we can request the doc with changes still intacted.)
If you have any other suggestions, it would be appreciated.
Thank you for your help.
Sorry, I have to disagree with your estimate, for the main reason that all those reviewers will be manipulating the Word document with their own formatting quirks, which will only serve to corrupt the doc file and make its repeated importation increasingly problematic.
Remember, you're looking to convert a binary file with tons of macros into HTML code, essentially a flat text file. I suspect that remapping the IDs will end up being the least of your problems as you go further into repeated review cycles.