I use DITA-FMx with FrameMaker v7.2 to convert a specific set of DITA content to a range of FrameMaker books, where each book displays its own unique formatting and structure.

DITA-FMx has the power to convert dita and/or xml files containing individual topics from within a ditamap to fully-functional FrameMaker books via different applications, where each application produces output each containing its own formatting and structural information.

--- Andy Lewis, RADVISION Ltd.

General:

• Create and edit 100% valid DITA 2.0 (or earlier) topic and map files.
• Exchange DITA files with those created in other XML editors.
• Provides well developed structure applications for topic and map editing that can be customized to suit your needs.
• Properly handles EDD/structapp with specialized elements (meaning that assuming you've properly set up the DTD and EDD, it will work with your specialized data model).
• New file names automatically generated based on proposed title and other criteria (unique ID, topic type, date, time, etc.).
• Ditaval Manager allows you to create and manage ditaval files from within FrameMaker.
• Reference Report command generates a report of all resolved or unresolved references in the current map or file as well as any references in referenced files.
• Create Archive command generates a ZIP archive of the current file and all referenced files.
• Flatten Conrefs command unlocks conrefs in FM files.
• Search for content in files on disk based on text, element, or attribute values.
• Where Used command generates a report listing all places a topic or element is referenced.
• Automatically generate a map and stub topic files from a simple tabbed list.
• Select custom element template when creating a new file so you start off with the whole topic structure in place.
• Add and update prolog data on file creation and file save.
• Enhanced whitespace normalization eliminates the problem of opening files created in other editors.

Topic editing:

• Context sensitive help (Alt+F1) on DITA elements; can be customized to add your specialized elements.
• Insert conrefs to all elements through an easy-to-use interface.
• Automatically resolve references (conrefs, xrefs, and links) on file open.
• Conditionalize prolog, comments, and data elements on file open (hide or just apply coloring).
• Automatically add IDs to elements if required.
• Supports FrameMaker-style xrefs ("Heading on page NN") as well as DITA-style xrefs and links.
• Supports ditaval filtering using conditions.
• Auto smart-spaces and auto smart-quotes makes it easier to work with code in documents.
• Manual line breaks are preserved in PDF output.
• Document dictionary entries are stored in the DITA files.
• Supports table cell rotation.
• Automatically set the status attribute for new and changed content.
• Multiple marker types round-trip to DITA as data elements.
• Supports optional columns in properties tables.
• Faster resolving of xrefs and conrefs on file open.
• Updated Reference Manager features:
  • Allows browsing for files "on disk" .. no need to open the file before placing an xref or conref.
  • Displays only the element tags for available elements that exist in the target file.

Map editing:

• Easy editing of DITA maps with a drag and drop interface.
• Manage relationship tables in an easy to use table structure.
• Open all topicrefs in a map with a single command.
• Newly created topics automatically added to map.
• Control the appearance of topicref elements in the map (title, filename, or both).
• Auto-open maps in document view (FM9/10 only).
• Full support for bookmap elements.

Structure application updates:

• Topic, Map, and Book applications have been updated to support all DITA 2.0 elements. >
• Default Topic application is less "book-like." Because DITA-sourced content may be used for many types of output, we have removed many of the print-specific layout and formatting features from the default Topic application. This helps authors to focus on the content rather than the formatting, and results in topics that are more useful in all deliverable formats.
• The Book application has been updated so the book title (as defined in the map) is passed on to the generated FM files as a footer variable.
• Supports the use of topic-specific DTDs.

Indexterm support:

• Seamlessly round-trip DITA's nested indexterm elements with FrameMaker markers.
• The index-see, index-see-also, and index-sort-as elements properly convert to FM marker syntax on import and export back to DITA elements on file save. An Options dialog allows for extensive control over the formatting and syntax of the imported markers.
• The indexterm elements now import as fm-indexterm elements. If you have complex indexterm elements that contain child elements other than indexterm, index-see, index-see-also, and index-sort-as, you can disable the indexterm to fm-indexterm conversion (in Options) in order to preserve the native DITA structure.
• Provides control over the formatting of index entries in PDF output.

Graphics:

• Dynamic updating of image placement based on attribute values or FrameMaker properties.
• Warning on save when anchored frame contains invalid objects (to prevent data loss).
• Provides visual placement of referenced graphics.
• Add callouts and other graphic overlay objects to images in FrameMaker and have them round-trip to DITA and back.

Integration with the XDocs 4.x CMS:

• Login/logout, create new files in the repository, as well as check out and check in files.
• Publish files through FrameMaker or use the XDocs Explorer to publish through the CMS.

Plays nicely with server-based file management systems:

• Properly resolves references to read-only files.
• Properly handles "slash-rooted" file references commonly used by server based systems.
• File references can use Windows UNC paths.

FrameMaker book publishing:

• The Generate Book from Map command handles conversion of a bookmap into an FM book in a similar way to the conversion of a map. All "top-level" topic references are converted into an FM file, and any child topicrefs are appended to that file. Any topic references within a frontmatter or backmatter wrapper element are considered "top-level" topic references and become FM files. Additionally, if your bookmap uses a part element to organize chapters, the file referenced by the part will become a separate FM file, and each chapter will be considered a top-level topic reference and will be added to the book after the generated part file.
• Additional book-build feature lets you include unstructured FM binary files in a generated book (great for adding a title page, but can be used for other content as well). The book title (from the map) is now imported into the generated list files as a variable (for use in headers/footers or elsewhere).
• Import map metadata as variables or conditional text settings in generated FM book.
• Pre and post book-build scripts ensure that all files are set up properly for each book build.
• Supports language-specific book-build INI files.
• Book-build INI settings can override the defaults to ensure a consistent book build.
• Use the topicref/@outputclass variable to specify the template applied to each book component.
• Numerous publishing options are now available that specify processes to be run on the generated book and components.
  • Add related-links from reltables as link or fm-link elements.
  • Flatten conrefs (for proper link functionality in PDFs).
  • Reload FM variables.
  • Convert xrefs and links into live Hyperlinks.
  • Move indexterms in the prolog into the topic title so they are not filtered out if the prolog is hidden.
  • Apply ditaval as conditions to perform ditaval-based filtering.
  • Move figure title elements to the end of a figure element.
  • Convert table title elements into "real" FM table titles so they appear on multiple pages, also supports the Table Continuation variable.
  • Assign numbering and pagination to the book component files based on their map element type.
  • In a bookmap, replace the "list" files with generated FM lists.
  • Apply templates to the book component files based on their map element type.
  • Run a custom FDK client or FrameScript. Now run multiple clients.
  • Hide "conditionalized" content (such as prolog, comments, and data elements).
  • Update the generated book and files.

DITA Open Toolkit support:

• Easily connect to any version of the DITA Open Toolkit.
• Publish a DITA map or bookmap through the DITA Open Toolkit to generate any standard or user-defined output target.
• Select a ditaval file in FM for conditional filtering.