TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
My experience was to apply RoboHelp as a process to the completed
document. Whenever I would receive information from engineering, I
would change the Frame Source and run the help conversion process
again. I could do it for a single topic, a whole chapter, or the
whole manual, depending on the scope of the changes.
There were some mighty challenges to this in RoboHelp 2003. For
example, I couldn't map Frame paragraph styles to standard H1, H2, H3
an H4 paragraph tags in RoboHelp. This was a particular problem
because my final destination was JavaHelp, which does not understand
custom paragraph styles. I wound up trying to write awk scripts to
reformat the heading paragraphs as standard HTML headings.
