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.
Re: Converting Word Winhelp files to FrameMaker 5.5.6-Take 2
Subject:Re: Converting Word Winhelp files to FrameMaker 5.5.6-Take 2 From:David Knopf <david -at- KNOPF -dot- COM> Date:Tue, 11 May 1999 07:52:14 -0700
Gemmell,Dal asked about converting WinHelp RTFs to Frame, and concluded with
the following question:
| I am not using a HAT, but would be interested in hearing how
| using RoboHelp
| would make my life easier.
If you were using RoboHELP, you would choose a 'Save As Printed
Documentation' command (not the actual command name, but you get the idea).
RoboHELP would convert all the WinHelp RTFs to standard Word DOC files,
automatically stripping out all the WinHelp-specific footnote codes, saving
the graphics as either embedded or referenced, generating a TOC and an
index, etc. Then, you would open Frame, import the DOC file(s) created by
RoboHELP and start editing. No need for manual pre-processing!
With WebWorks Publisher, you could perform this entire process in reverse.
That is, you could write the manual in FrameMaker, and then use WebWorks
Publisher to convert your Frame files to compiler-ready WinHelp source
files. We do it all the time, and yes it actually works. (Please don't write
to tell me that print and online are fundamentally different ... I know, I
know! And we have no trouble accommodating the differences using WebWorks
Publisher.)
