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.
This should provide a few links to a few useful pages.
I did download a .pdf from one of these links, entitled "Creating HTML
Help with Microsoft's HTML Help Workshop" (78 pages; haven't looked
through it yet (forgot I had it, actually). I can e-mail it to you if
> We'll be using Microsoft's HTML Help Workshop and
> probably Front Page as the HTML editor (although I may
> bring in my copy of DreamWeaver...)
One weird thing I've noticed about HTML Help Workshop ... was twice
project, I was able to view the pages just fine -- until I compiled
the project. When I clicked on the new pages, I got the error "This
page can not be displayed." The first time, I was able to remove the
pages, recompile, replace the pages, and recompile, and then I was
able to view my pages just fine in he .chm.
The second time it happened, my original "solution" didn't work.
Instead, I had to completely rebuild my project.
Fortunately, it was only about twenty pages.
> I figure that the best way to take the files out of
> HDK and into HTML Help will be to simply put the Word
> files into HTML - any comments about this?
Doable; may require some tweaking, though. Popups are
> now for the hard question: one help file will be able
> to be called from 2 different applications. Is there
> a way to make the text in the title bar change
> depending on where the file is called from?
Not sure on this one. Probably some sort of API call would do the
"If it's not on fire, it's a software problem."
--Your IS Department