RoboHelp 6 Arrives; Puts Death Rumors To Rest

By kaycee on January 25, 2007 -- 6:31am

Having just begun testing RoboHelp6 I have already found the following drawbacks using FrameMaker as the source:

1. No direct import of FM files, must first save as MIF.

2. Does not correctly identify all paragaph styles and has no style mapping facility as in WebWorks. Embeds inline styles as approximation.

3. Does not import TIFF graphic files. You are prompted for an external plugin, sent to Adobe Knowledge Base search page, enter TIF-LZW (shown in RHelp prompt). Nothing found.

By ScottAbel on January 25, 2007 -- 7:34am

Thanks for your feedback. I’m just now evaluating RoboHelp, so your views are very helpful. I’m also sponsoring an Adobe RoboHelp demonstration in Indianapolis, February 9, where I will ask Adobe about their plans for the future. I expect that if there are any issues in this new version of RoboHelp they are already addressing them. Additionally, Adobe’s new application pack approach may mean there’s a FrameMaker to RoboHelp conversion application pack in the making.

Scott Abel
The Content Wrangler

By Redwing38 on January 29, 2007 -- 1:11pm

Hmmm. Still no XML output, though. In the world I work in, this seems to be a no-brainer. We went to Flare when MMedia and Adobe kept saying nothing. Flare’s still a little buggy, but two things matter a lot to me; communication from the organization, and XML output.

Thanks for this article.

By PeterJ on March 13, 2007 -- 10:37am

RoboHelp 6.0 is fantastic news for any Robohelp User. The future just gets brighter and brighter with rumours of the Robohelp 7.0 release being worked on and may be released this year. We have just upgraded and find the additional condition tag features a robosource control update the most usefull updates. Early days I guess, but at least the product seems to have a formidable future at last. Time to uninstall the trial versions of the other tools we’ve been struggling with and get on with some work!