Automated Solutions for FrameMaker..

Posts tagged ‘TechComm’

God particle in FrameMaker !!

Something that the FrameMaker Users should be boastful about !!

Got to know about the important role of documenting the discovering the God particle was entrusted upon our dear tool-FrameMaker. Glad to be associated in some way to this great discovery by mankind.
For Physics enthusiasts this is a great video explaining a nice deal of what the Higg’s Boson is:

More Info on Higgs Boson can be read here:

Hope you had an opportunity to go through the Reviews on FrameMaker 11. List of all reviews have been documented in a single post on the Adobe’s blog.


Multiple XML Views in FM11

With the aim of breaking the cocoon of not being recognized as a complete XML editor, the XML views in the latest version of FrameMaker serve an apt reply to all those who did not recognize the XML capabilities in FrameMaker.

Following three views have been incorporated for technical communicators who author XMLs:


The USP of the product. Its WYSIWYG capability, that no other authoring tool provides. Authors will use this view to create and apply styles, modify layouts and page related settings like master pages for XML files. Moreover, the entire structured application creation and update workflows will be done in this view.

2. Author View

The view relevant for an author; devoid of everything related to print output aspects, to retain an author’s focus on just creation of content.

Author View

Author View

This content in this View is reflows according the document size. It is also devoid of the ability to view/apply Master Pages, so you would not see the multi-column layouts from your templates in the XML being authored.
We noticed a lot of menus and toolbar restricted in this view. Probably all those features that are meaningless in this view have been eliminated. Less clutter is better experience!

3. Code View

A view for advanced XML users who are conversant with XML, the code view, is packed with useful features like XPath and XSLT. A new tree based XML structure window is available in this view. However, we miss the power provided by the Structure View (available in WYSIWYG and Author View). On some serious thinking it’s absence starts to make sense as well.

XML view

XML view

Noticed some good authoring features in this view like attribute suggestions, auto-element-tag-closure and run-time validation against the DTD specified in the XML. Moreover, the XML open time in this view is much less compared to the other 2 views, probably because there’s no worry to display the WYSIWYG face of the document in the Code View.

Most importantly, the switching experience between views is smooth. While authoring in Code View or Author View if you want to verify the final print output, you can do so by just switching to WYSIWYG view. Just a mouse click does that for you!

Banner Text/Document Skeleton

If the authors in an organization need to be guided on what context each element in a structured application holds, then this is a great feature. For template designers, this is a feature that should definitely be explored because they can place a basic structure along with helpful information for authors who start authoring an XML. An instance of which can be seen while creating new DITA XMLs.
The term banner text looks misleading but this feature is about having placeholder content inside elements that guides the author with some text.

For example, we did a File .. New .. XML .. Dita Topic. It showed “banner” text in grey color, on which we could just click and start typing (it informs authors to type in the correct context), while the placeholder content vanishes.
So it actually guides the author in two ways:

  • Where exactly to start authoring content in a document.
  • Setting the context right for what context to author in.
banner text

Banner Text

Moreover, we foresee common usage where the placeholder can contain some warning/essential prerequisites that the author should be aware of. The Help guide says that you can extend this to content other than DITA too! (via EDD).

Print ready DITA Publishing from FrameMaker 11

For the authors that author in DITA standard and love the FrameMaker book capabilities, this is a feature to appreciate. Hopefully it would reduce the post processing effort which organizations commonly spend on publishing ditamaps from FrameMaker.
In FrameMaker 11, users can now generate print ready output from a DITA Map project. Essentially the ditamap to Book with FM components workflow has been enhanced in the latest FrameMaker release.

DITAMap saved as Book

The output would now now also include generation of cover page, ToC, Index, List of figures, List of tables etc.

Book with TOC, Index etc. published from FrameMaker

These properties are configurable in the ditafm-output.ini file (%appdata%\Adobe\FrameMaker\11). Numbering and pagination are  automatically handled as part of this book building process.

Many options are present in this ini file. We did not use all, but it goes to show a lot many parameters, left upon the user to configure as per the publishing requirements. For example, numbering notation for chapter, section and sub section components, Pagination (double sided or single sided) and presence of an option to generate flat books (pre-FrameMaker 9 era). And trust me a lot more to explore in this ini.

A few examples of entries in the ini file:



This ini file seems very long and is undocumented. Looks like users will need to figure out the meaning of the individual options themselves 😐

Ease of Content migration – Smart paste structured content

Do you author in DITA ? Need to assemble your content from various sources(HTML, Word etc.)?

“Smart Paste” offers a great and a quick solution. Tools people can customize this functionality to work for other XML specifications as well. Full points to FrameMaker team for this feature.
Our experience:

  • Created a new DITA topic file.
  • Copied some paragraphs along with images and tables from the Web
  • Smart pasted the content in FrameMaker
  • With very minor tweaks, we could realize completely valid and relevant structure in the DITA topic being authored
Source Page

Source Page

Pasted Content

Pasted Content

Productive: Yes. Cool: Definitely!