Copy link to clipboard
Copied
I have a massive publishing program with tens of thousands of pages in unstructured FrameMaker 8 files. we need to be able to go to print publication, html5, and many E-formats.
1. would it be better for us to use structured FrameMaker?
2. can FrameMaker alone handle all E-format outputs?
3. Where and how does robohelp fit into this equation?
4. We also need to produce PowerPoint slides and other supplements for instructors using our books. Many supplements are direct lifts of content in the frame files. Is there a good way to automate this process Using FrameMaker and/or robohelp? We need to include all tables and provide text bullets.
Copy link to clipboard
Copied
I'll let others address the structure/ebook/RH questions.
> 4. We also need to produce PowerPoint slides ...
Is PPT or PPTX strictly necessary? For the last 20 years I've always done my slides as PDF directly from FrameMaker. It's pretty easy to paste or reflow content onto landscape pages, adjusting format defs for the larger text sizes required.
Copy link to clipboard
Copied
FM12 can output in ePub 3, responsive HTML5, Mobi, KF8, Web Help and Microsoft CHM formats along with the PDF format. Going through RoboHelp, adds another 12 output formats, so depending upon what you mean by "E-formats", FM12 may suffice.
FWIW, Acrobat XI can produce PowerPoint slides from PDFs. So you can satisfy the requirement using that route or as Error suggests, stick with PDF slides (and use the Microtype Presentation Assistant to help with the slides - http://microtype.com/timesavers_Assistants.html ).
Copy link to clipboard
Copied
Does RoboHelp help perfect the output of any of the formats that FrameMaker supports? In my past experience, the HTML output from FrameMaker was horrendous.
Copy link to clipboard
Copied
It's a completely different approach for FM now. FM12 uses a subset of the RH processing to "publish" those formats. (FWIW, you can still create the simplistic HTML output using the mapping tables).
There's a fair bit of control in the mapping of the FM tags and some customization to the skins that you can apply. IIRC, there just a bit more depth to the controls in RH.
Copy link to clipboard
Copied
Does it make a difference whether you're using FrameMaker, Structured FrameMaker or the new FrameMaker for XML Authors?
Copy link to clipboard
Copied
The FM XML Author tool is just an authoring tool (i.e. you need the full FM to set up the structured application for this tool to use, if it's not one of the canned ones) and it can not "publish" (except for a watermarked PDF that is meant for "reviews" only).
Either structured or unstructured modes will allow you to publish to the multiple formats.
The question of whether you should switch to structured or continue in unstructured, really depends upon your requirements and what sort of ROI you're expecting compared to how much you're willing to invest. You will need help implementing the structured authoring environment for your needs, otherwise you would not be asking this question. Some considerations include: do you need to translate your content, is your content re-used in other publications, is the content updated, how is the content supplied/generated, what sort of editing/reviews are done, what sort of issues are you trying to fix in your current workflow, etc.
If your content is not originally authored in FM, i.e. FM is just the publishing platform, then you may not gain that many benefits by switching to the structured FM environment. However, if this is your primary authoring environment, then structured FM is hard to beat for controlling consistency and guiding authors.
Copy link to clipboard
Copied
Thanks Arnis.
1. If FM XML Author can't publish, what's it's purpose?
2. Your list of considerations:
Best, Paul
Copy link to clipboard
Copied
Paul,
1. When you have a large shop with many authors working with a structured XML-based application, you can deploy the FM XML Authoring tool to most of the staff for far less cost than a full FM license. The scenario assumes that the structured application is (already) developed using FM and that at least one FM seat is around (or from Adobe's prefered-POV, the FrameMaker Publishing Server @ $$$) to create the final outputs. This is primarily targeted at the DITA environment to compete against tools like Oxygen XML Author or Codex. It could be a consideration for your environment.
2. Your considerations:
You might want to contact Richard Hamilton at XML Press (http://xmlpress.net/) to find out about the pros & cons of a publisher using XML content and the tool sets in use.