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.
No, that's not right. HTML Help was originally designed as a local or
network Help system (a replacement for WinHelp). Uncompiled, it was even
designed for use on the web. The only HATT that took Microsoft at their word
(we were writing the book for MSDN, so we thought we knew what was up) was
WexTech, which could write a browser-based Help version using the hhctrl.ocx
and one for non-IE browsers using the Microsoft JavaApplet -- all part of
the original release of HTML Help. Now, of course, the use of hhctrl.ocx in
an uncompiled HTML page will not work.
Later versions of HTML Help were even supposed to have the ability to
transparently update compiled HTML Help topics from a web site, but this was
never implemented (along with a lot of other neat things like multiple
categories in Information Types).
IMHO, HTML Help never was finished, and has been degraded in its
functionality since the initial release.
Regards,
Paul Neshamkin
pauln -at- helpauthors -dot- com
MS Help MVP
ComponentOne Doc-To-Help Certified Trainer and MVP
WexTech MVP, and Certified Trainer
-----Original Message-----
From: techwr-l-bounces+pauln=helpauthors -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+pauln=helpauthors -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf
Of Bill Swallow
Sent: Thursday, May 25, 2006 1:58 PM
To: TECHWR-L
Subject: Re: ANN: Microsoft update (WinHelp)
> ... which (unless you reduce security with some Registry hacks) won't
> run unless loaded from a local disk, and any uncompiled HTML Help
> won't work with the content in a different frame to the TOC or index.
> Because most organisations are unhappy about compromising security,
> effectively this kills HTML Help for anything not installed on your
> computer.
>
> FWIW, I've now spent enough time (non-chargeable time) working round
> the problems that MS's sledgehammer approach to HTML Help security
> issues has caused to seriously affect my income, and I'm going hoarse
> from the times I've uttered, "<fe>Thanks, Bill</fe>!" :(
To be fair, HTML Help was designed as a locally deployed UA solution, not a
networked UA solution. Personally I'm quite happy to comply with its
original intent rather than face the security issues found if Windows wasn't
properly patched to disallow the hacking of CHMs in networked
implementations. And uncompiled solutions do still work in both networked
and local implementations. I'm not sure what you're seeing there, but it
might be due to using certain ActiveX controls.
Java and JavaScript-driven HTML-based uncompiled UA solutions work fine from
my experience, multi-pane or no.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l
