Copy link to clipboard
Copied
Issues while publishing HTML output from Adobe TCS Suite 4, using the structured FM 11:
I am publishing HTML (Web help) output from TCS 4, using the Structured FM 11. I created DITA topics, and DITAMAP, then created the Composite FM file. Then Ditabase template is applied to DITAMAP, then generated Composite FM file. We publish the PDF output from the book, which contains that Comp. FM file, title page (.fm file) and TOC (.fm file). With TCS, we have the option to publish the book into WebHelp format. However, the output shows an incorrect output.
The following issues were observed:
1. The title page and content seem to be of different font and formatting, where as in PDF output, we could generate it correctly.
2. In the bookmark section of HTML output, title1 is present but title2 is missing.
3. The HTML output is taking the original XML files' formatting, which is not consistent throughout, whereas PDF output shows correct formatting. I am not sure if I am following the correct steps to generate HTML output? Do I have to create a separate template to generate the HTML output from TCS? I think, TCS is using the Robo Help to publish the FM DITA files into WebHelp output. So I need to map the template in Robohelp with FM template.
I am not sure about this step.
Can you please let me know the correct steps to publish HTML output from TCS. Your suggestions will be highly appreciated.
Thanks,
Sanjeev
Copy link to clipboard
Copied
Question moved to the FrameMaker Integration forum.
See www.grainge.org for RoboHelp and Authoring tips

Copy link to clipboard
Copied
Publishing directly from FM depends on the creation of a settings.isf file being used. Getting your settings.isf file involves setting up a RH project and setting the conversion settings so that your FM content is mapped to the appropriate RH styles. Tweaking your css is also part of this. Once this is done, your settings.isf file can be used directly inside the FM publishing process to produce the correctly-styled help output.
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more