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: MIF2RTF vs. Quadralay? From:Frog Princess <frogprincess -at- ONLYMAIL -dot- COM> Date:Mon, 4 Jan 1999 17:12:59 -0800
>I, too, have been considering these options, but since the company I work
>for has decided to standardize on RoboHelp, we pretty much have to go with
>that. Luckily, the latest version (7.0) is pretty user-friendly and easy
to
>use. (thank goodness)
>
>We're just starting to evaluate it, so we're not quite sure how easy it is
>to port files from FrameMaker to RoboHelp. If anyone has already done
this,
>please let us know; I'm sure many would be curious to hear your opinion. I
>know I would.
I'm using FrameMaker 5.5 to write manuals, and converting the Frame text to
RTF to use in RoboHelp 6.0. (I don't have version 7.0 of RoboHelp yet
because I'm afraid to convert to a new version in the middle of a project
with a pressing deadline.)
My frustration is that the cross reference and index tags in FrameMaker
aren't converted to "jumps" or index entries in RoboHelp. When I import the
RTF file, all the tags are converted to strings of text. I have to go
through and delete each one, then recreate the "jumps" and index in
RoboHelp. Very time consuming.
Here's an example of how Frame's index tags appear in RoboHelp: