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.
The only note I would add is that you have to ship the help viewer, too.
See the technical FAQ at http://www.bristol.com for more information.
Tech Pubs Manager
Seagate Software (Durham, NC, USA) mailto:alexiap -at- seagatesoftware -dot- com
>From: Gurudutt Kamath [SMTP:guruk -at- GIASBM01 -dot- VSNL -dot- NET -dot- IN]
>Sent: Wednesday, October 01, 1997 4:04 AM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: Re: HyperHelp files
>You do not need to send the.hh file. This file is required by the windows
>help compiler to achieve context sensitivity. Once you compile the help
>file, the help file is all that is required. You will appreciate I am
>saying this based on my knowledge of RoboHelp and WinHelp. It should be
>the same for other help systems too.
>On Wed, 1 Oct 1997, Hareesh Kumar K N wrote:
>> One of my colleagues here is using HyperHelp to generate the help files. He
>> wanted to find out whether we need to send the .hh files also to the client
>> when we ship the help files. Does the .hh files contain some critical data,
>> required to run the help files?