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:Move to HTML help? From:Geoff Hart <Geoff-h -at- MTL -dot- FERIC -dot- CA> Date:Mon, 3 May 1999 15:03:50 -0400
Sean Brierley is <<...at a point where I can lead the charge, all 40-
leagues of it, into the guns of HTML help. This is my call. Should I
Whenever someone proposes a change in a perfectly functional
way of doing things, I always ask two questions: What problems
are you trying to solve by making the move? Are there any major
advantages to HTML help that would justify the disruption of your
current process? Everything you stated in your query, combined
with my feel that HTML help still isn't really ready for prime time,
suggest that there's no advantage to making the switch, and
several potential disadvantages.
<<Okay, thoughts on HTML versus WinHelp considering a
timeframe of the next three years and assuming I have the tools,
time, and experience to get it done.>>
If you don't have a truly compelling reason to switch, why not relax,
monitor how the technology is evolving, and let others solve the
inevitable problems for you? By the time you really need to make
the jump, you'll be ready for it.