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.
> I'm worried that by choosing to use
> RoboHTML I will cut out a considerable swath of bankers who
> are still using Win 3.1 and/or don't have browsers installed. I guess I might
> be answering my own question here by saying that I should stick with
> RoboHelp, but I thought some of you folks might have some insight on the
> limitations of HTML help.
Short answer: if your software runs on Win 3.1 and does not require a browser,
you probably should stick to the 16 bit version of WinHelp. Many computers
running Win 3.1 do not have the disk space to install either of the major
browsers, and requiring new hardware for a browser just for help is asking a
bit much of your users. You could have them use Opera, which is very small and
is available in a 16 bit version. But bankers might be uncomfortable with the
maverick image of the company. And it costs $35.
I think you might be confusing authoring tools with deliverables.
The relevant deliverables here are:
* WinHelp
* HTMLHelp
* HTML based help
RoboHelp and RoboHTML are tools used to create those deliverables, and there
are other tools that you could use. The tool you use does not affect your users.
The deliverable does, though.
WinHelp (which comes in 16 and 32 bit versions) is available on any Windows
system, without installing any extra software.
HTMLHelp is a Microsoft technology. In order to use it, your customer must
have the Internet Explorer browser installed. In some cases, that isn't a
problem. In others, it is.
HTML based help is more an idea than a specific technology. The idea is to
present help through the browser. HTMLHelp is one example of HTML based
help, but most of the time, "HTML based help" refers to a more browser-neutral
(one that can be used with a wider variety of browsers) solution. Sometimes, a
browser-neutral solution is not a problem when HTMLHelp would be.
HTMLHelp and HTML based help provide better opportunities for multimedia.
HTMLHelp includes some interesting features, like the three-pane interface,
and promises more, like information classes. But WinHelp is a more mature
technology, and provides quicker response for the user, with less system
resource load.
Finally, as others have pointed out, determining the needs of your users is beyond
the reasonable scope of Blue Sky technical support. That's your job. You might
be able to get some suggestions out of the Blue Sky marketing group, although they
don't owe it to you.
---
Office:
mike -dot- huber -at- software -dot- rockwell -dot- com
Home:
nax -at- execpc -dot- com
