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:Help tools and manuals From:Dan Glovier <dan -at- COYOTE -dot- TSH -dot- COM> Date:Thu, 29 Feb 1996 11:14:06 -0600
My company is producing a new product in a Microsoft environment (we're one
of those fancy Microsoft Solution Provider people). Due to this status, the
People Who Make Decisions think it would be a good thing if we did the help
file and manual with a Microsoft product. They want a separate look, feel,
and layout for each of these docs. That means two separate files. This is a
big piece of software. I would guess the printed manual would be around
Well, for the help file we could use Doc-to-Help with MSW 6.0, but I am
concerned on how D2H will handle a super big file. Any suggestions, comments,
or different ideas? What does Microsoft use for their help files?
I think that the printed manual will have to be done in a different tool than
MSW 6.0. We used to use Ventura 4.1.1 for our manuals, but now that Corel has
basically killed its uses in the tech document field, we have not yet migrated
somewhere else. Frame seems to be the way to go. Has anyone had any experience
with their Ventura filter/converter?
Thanks in advance,
dglovier -at- tsh -dot- com