In this guest blog, Certified Adobe Expert and Trainer, Kevin Siegel of ICONLOGIC, covers a powerful technique when publishing from FrameMaker through RoboHelp via Technical Communication Suite (TCS4). In this blog, Kevin touches on many principles he shared in one episode of his 3-part webinar series, “2) Explore TCS4: FrameMaker to RoboHelp to eBook … Oh My!“
_____________________
TCS4, FrameMaker to RoboHelp: Excluding Content
Linking content created in Adobe FrameMaker to an Adobe RoboHelp project is as simple as visiting the Project Manager pod, right-clicking the **Project Files **folder and then choosing FrameMaker Document.
To control how the content that exists in FrameMaker will be handled by RoboHelp, you would next choose File > Project Settings > Import and choose an appropriate CSS from the CSS for Style Mapping drop-down menu. (In the image below, I’ve elected to use the default CSS that comes with RoboHelp.)
Back on the Project Manager, you finish the Link process by right-clicking the FrameMaker content within the Project Files folder and choosing . All of the content contained within the linked FrameMaker files will be converted into RoboHelp topics. It’s really that easy. And since the FrameMaker content is linked to the RoboHelp project, should you make any changes to the FrameMaker content, you can quickly update the corresponding RoboHelp content by right-clicking the FrameMaker content within the RoboHelp Project Files folder and choosing .
It’s a good bet that there will be some content contained within the FrameMaker source files that you simply do not want to appear in the RoboHelp project. For instance, in the image below you can see that I’m using a callout (Stress anyone?) in the left margin of one of my FrameMaker documents. The callout, which is using a FrameMaker format called , is simply a graphical element to break up the page.
