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:Re: Windows Help/Future Demand From:Jeff Jungblut <jeffmj -at- CRASH -dot- CTS -dot- COM> Date:Tue, 11 Jan 1994 17:16:13 GMT
In Article <ECS9401111831A -at- acec -dot- com>, Matthew Wong <wong -at- acec -dot- com> wrote:
>For those of you on the list who are developing the help facility for Windows
>applications I would like to hear from you about:
>1. Which of the two development routes would you recommend: (a) develop the
>RTF file with FrameMaker and then exeute the help compiler, or (b) use a
>Windows help authoring tool.
From personal experience, I would recommend using FrameMaker or Word for
Windows to create the RTF files. I tried a number of shareware help
authoring tools, including an early demo version of Help Magician, and I
found that they were all more trouble than they were worth for the specific
project I was working on.
>2. What Windows help authoring tool would you recommend: (a) RoboHelp, (b)
>Doc-to-Help, (c) Help Magician, and what are your reasons for
I haven't seen Doc-to-Help or the commercial version of Help Magician. An
article I read in one of the Windows magazines gave RoboHelp a great review.
>3. How are you presently developing your Windows help ?
I'm creating them in Word 5.1a on a Mac, then copying them to the Windows
machine for compilation and testing. I'm concurrently doing a Mac version
of the help file based on the same RTF files using QuickHelp on the Mac.
This may seem like a roundabout way of doing things, but I'm more
comfortable working on the Mac and writing macros in QuicKeys than using
Word for Windows and learning WordBasic. (I've used Word for Mac and
QuicKeys for years and don't have the time allotted in this project to learn
Jeff Jungblut Tecnhical Documentation Group
jeffmj -at- crash -dot- cts -dot- com Jostens Learning Corporation, San Diego