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: Move to HTML help? From:"Brierley, Sean" <Brierley -at- QUODATA -dot- COM> Date:Mon, 3 May 1999 15:28:35 -0400
I didn't anticipate this response, but I think I'd reply the same way as
Geoff. With that thought, let me clarify that there is no on-going process
to change. Whichever path I choose, be it WinHelp or HTML help, it will be
the commencement of a process not the continuation of something tried and
The current situation is that on-line help development at my place fell on
hard times six months before I was hired. None has really been done in a
year, or so. New products and major changes to existing products give me
quite a large backlog of projects. However, as far as on-line help goes, I
am essentially starting anew. There is no on-going process to interrupt or
Thus, are there compelling reasons to start the on-line help projects as
HTML projects or should I continue with WinHelp. I am very familiar with
WinHelp but am not married to it.
As far as tools go, the tool is new and will create either help system.
There is not any comfort associated with using this tool for one kind of
help over another.
So, Win or HTML?
sean -at- quodata -dot- com
>>>From: Geoff Hart [mailto:Geoff-h -at- mtl -dot- feric -dot- ca]
>>>Sent: Monday, May 03, 1999 3:04 PM
>>>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>>>Cc: Brierley -at- QUODATA -dot- COM
>>>Subject: Move to HTML help?
>>>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.