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:QUESTION: Moving from WinHelp to HTML Help From:Larry Weber <larry_weber -at- HOTMAIL -dot- COM> Date:Mon, 3 Nov 1997 17:02:09 PST
This is a question for those intrepid souls out there diving into the
HTML Help fray and those planning such a move:
HOW and WHY are you implementing HTML Help at this time? From what I
understand, you presently can only develop HTML Help for one of the two
major browsers. Are you shipping a browser? Next, where do the HTML
files reside? Do they reside on a single server that your users access
via the internet, or do you actually ship the HTML files and store them
on the user's machines?
If the HTML files reside on an internet server, have you gotten feedback
concerning the response time to access the HTML file vs. response time
to access a local WinHelp file? How does this architecture handle
context-sensitive Help? Also, have you collected any data about the
types of information that users access (i.e., have you made any
conclusions about what users actually USE in the online doc)?
Finally, is it just me, or does anyone else get the feeling that this
HTML Help thing is (presently) more trendy than actually feasible?
Larry Weber
larry_weber -at- hotmail -dot- com
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com