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: RoboHTML vs. ForeHTML From:David Knopf <david -at- KNOPF -dot- COM> Date:Tue, 11 May 1999 07:58:22 -0700
Lydia Wong asked:
| We have recently been comparing RoboHelp and ForeHelp. The recent
| discussions on that have been very informative. We've followed those posts
| pretty closely, but they seemed to concentrate on WinHelp comparisons. We
| have some more specific questions about HTML-based help:
|
| Have any of you used both RoboHTML and ForeHTML, and if you
| preferred one or
| the other, which did you prefer?
|
| Also, have you tried using FrameMaker to create your source, converted the
| Frame files to HTML or HTML Help using WebWorks Publisher, and then used
| RoboHTML or ForeHTML for maintenance/clean up/whatever? If so,
| how did that
| go?
I can't comment on ForeHTML, as I haven't worked with it much. But I can say
we routinely convert FrameMaker source files to HTML using WebWorks
Publisher. There's no problem opening the converted files in RoboHELP, but
we don't generally do that because there is no need to. Once you set up your
WebWorks Publisher template correctly, the HTML files produced by WebWorks
Publisher are ready to go!
