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.
I understand what you are saying re: uncertainty and the possibility that MS
will change their mind. I also remember reading the speculation that
RoboHelp is dead. I fully understand that this is a time of uncertainty in
But I can't wait to see what will happen. Converting from WinHelp to HTML
*is* a matter of months for me. I have 139 WinHelp projects. The majority of
these projects are for .exe files that are programmed to call WinHelp. If
WinHelp is going away, I need to get "programming time" to get these .exe
files changed. Additionally, the plan is to add window-level access to help
as part of changing to .chm files. I also have to balance changes to the
system that are always landing in my Inbox. I am the lone writer so I need
to balance the conversion with other projects.
What I did last week, and finished yesterday, is to take a couple of baby
steps. There are ~12 topics that are used by 99.9% of all 139 projects. I
converted those 12 topics to HTML. I went through all my projects and
changed references to the HTML page instead of the WinHelp topic. I put
these 12 topics in a single .chm file, which I will have included in the
As soon as I find an easy way to access an .xls or a .pdf file from a .chm
build the directory path to the .xls file. I think it will work, but I
really don't understand why this code:
<p class="Body-Text"><a href="CABSBALW.XLS">CABS Balancing</a></p>
does not work and I need a solution like http://msdn.microsoft.com/library/default.asp?url=/library/en-us/htmlhelp/ht
ml/vsconOcxscriptslinkchm.asp just to open an Excel file... What's really
irritating is that if I don't compile the .html page as part of a .chm file,
the link works. I am thinking I will just distribute two .html pages outside
of the .chm file. These two pages will also <at some point> be available on
an internal web server so I won't need all that jibberish at some point.
2. Vista is a minimum of nine months away, maybe more. MS has plenty of time
to change their minds again, and again, about releasing the WinHelp
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