For the past few years I’ve represented Adobe at various Tech Comm conferences, including the last 2 STC Summits. In discussing options for FrameMaker to RoboHelp integration, I developed a “chalk-talk” that usually took about 15 minutes to draw out and explain. The end result looked something like this:
Available inputs and outputs using Frame and RoboHelp
In the diagram above, the solid lines represent inputs for both applications, while the broken lines represent traditional outputs. In some cases, like PDF output, there are overlaps between the capabilities of the two applications, where you can choose between the strengths of each application.
As one person observed, “It looks like 2 spiders mating”
While I can’t really argue that point, what I see instead is a blueprint for managing content using FrameMaker.
Now, when I give out this same info, I can just cross out the elements that a client might not be interested in, and give them the same perspective in less than 1/2 the time.
Most folks expect this process to be really involved, and to be both expensive and stressful. In reality, it takes only a few hours to map out the FrameMaker formatting into RoboHelp, and then another few hours to work out the formatting bugaboos in HTML and CSS, and to define your single source layouts in RoboHelp.
The first time through the process can have a learning curve, so plan on either seeking services or education from a training provider like roundpeg, or invest some time in online tutorials like those from RJ Jacquez at http://blogs.adobe.com/rjacquez/2009/05/linking_framemaker_9_books_in.html
Either can make the process both rapid and pain-free.
{ 2 comments… read them below or add one }
You might include RTF and HTML as FM outputs. The RTF can be fixed pretty quickly for Word display. The HTML is quite good, though it’s raw, and you have to incorporate the FM-gened .css into the HTML file itself. I use it to produce documentation for rDoc front matter.
Also, Camtasia single .swfs work.
{ 1 trackback }