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.
Subject:RoboHelp Question From:bdoonan -at- coreco -dot- com To:techwr-l -at- lists -dot- raycomm -dot- com Date:Thu, 11 Nov 1999 09:14:47 -0500
we have just received RoboHelp2000 for the purpose of evaluating the
software to ascertain if it fits our particular needs concerning generating
help files. Up until now, we have used Doc-To-Help. When using Doc-To-Help,
we would create a document in Word and then generate a help file from the
Word document. This gave us both a finished help file and a finished doc
file, the latter used to create the printed manual. It is important to our
company to create hardcopies and winhelp files of our manuals. Although
Doc-To-Help has worked for us, we would like more control over customizing
our help files. This is why we're evaluating RoboHelp.
I have had only a day with the RoboHelp software and manuals, but (am I
blind?) it doesn't talk about single sourcing at all. With RoboHelp, do you
have to create a separate help file unrelated to the doc file you will
create for the printed manual? In other words, is single sourcing or
quasi-single sourcing a feature with Robohelp? To create a separate doc
file and a separate help file seems to be twice the work.
This topic screamed "check the archives," which I did; however, I was
unhappy with the result.