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: QUESTION: Moving from WinHelp to HTML Help From:"Tamminga, Ernie" <et -at- DSC -dot- COM> Date:Tue, 4 Nov 1997 07:20:56 -0800
You can ship either the compiled .chm file, or the entire swarm of html
files.
The latter course probably only makes sense if you anticipate a need for
being able easily to tweak one single topic (in this new world, read:
single html file) more or less in real-time, on your customer's server,
without having to recompile and re-ship the complete .chm file.
--------
Ernie Tamminga
Director, InfoEngineering
Digital Sound Corporation
-----------------------------------------------
Opinions expressed are my own, and not necessarily those of Digital
Sound Corporation
>-----Original Message-----
>From: Kathryn Marshall [SMTP:kmarshall -at- MODACAD -dot- COM]
>Sent: Monday, November 03, 1997 5:19 PM
>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>Subject: Re: QUESTION: Moving from WinHelp to HTML Help
>
><<SNIP>>
>I would imagine that you don't ship the individual help files (html)
>pages -- just the compiled ".chm" file -- the way you would send a .hlp
>file to a user not the actual source documents. Again, I can't say for
>sure because I just opened the box today.
>
>I'm interested in hearing more on this subject.
>
>-Kathryn
>
>> -----Original Message-----
>> From: Larry Weber [SMTP:larry_weber -at- HOTMAIL -dot- COM]
>> Sent: Monday, November 03, 1997 5:02 PM
>> To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>> Subject: QUESTION: Moving from WinHelp to HTML Help
>>
>> 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
>>
>> ~~
>> Posts: mailto:techwr-l -at- listserv -dot- okstate -dot- edu
>> Commands: mailto:listserv -at- listserv -dot- okstate -dot- edu (e.g. SIGNOFF TECHWR-L)
>> Archives: http://listserv.okstate.edu/archives/techwr-l.html,
>> Subjects: JOB:, QUESTION:, SUMMARY:, ANNOUNCE:, or none of these.
>>
>
>Posts: mailto:techwr-l -at- listserv -dot- okstate -dot- edu
>Commands: mailto:listserv -at- listserv -dot- okstate -dot- edu (e.g. SIGNOFF TECHWR-L)
>Archives: http://listserv.okstate.edu/archives/techwr-l.html,
>Subjects: JOB:, QUESTION:, SUMMARY:, ANNOUNCE:, or none of these.
>
>