About DITA InPrint

DITA InPrint solves a key challenge for organizations considering migrating their technical and business documentation to DITA: publishing documents that conform to corporate standards.

When it comes to policies and procedures, product user guides, manufacturing work instructions, and other mainstream business publications, senior management are not willing to compromise on appearances. They demand conformance with corporate templates and file formats, usually Microsoft® Word® and PDF.

This is a problem for corporate and technical communication teams that want to take advantage of the incredible productivity benefits delivered by authoring, managing, and publishing content in DITA XML. Until now, there was no easy way to design publishing templates for DITA content that conformed to corporate standards. Nor was there any easy way to publish DITA documents to styled Microsoft Word documents, the most common format for distributing, reviewing, and printing corporate documentation.

The result: a tough sell to senior management on the benefits of moving to DITA. And even if management approves a move to DITA, documentation teams face delays and/or thousands of dollars in fees charged by consultants and programmers to customize authoring and publishing tools to make them output documents that conform to corporate standards.

But now, DITA InPrint makes it easy for non-technical users to design publishing templates that conform to corporate standards. And it enables users to easily publish DITA XML content with those templates to fully styled Microsoft Word and PDF documents.

Key Benefits of DITA InPrint 1.0:*

  • Users design and maintain publishing templates entirely in a powerful, easy-to-use graphical user interface (Apache OpenOffice™ Writer). No programming required!
  • Outputs to PDF, Microsoft Word (.doc), and OpenOffice Writer (.odt). No separate PDF renderer required.
  • Rich PDF support includes:
    • Password-protected contents and editing/printing permissions
    • Inclusion of DITA bookmeta content in PDF properties
  • Supports all OpenOffice styling features, including:
    • Paragraph styles
    • Character styles
    • Page styles
    • Frame styles
    • List styles
    • Table autoformats (borders and backgrounds)
  • Supports all graphic formats supported by OpenOffice, including:
    • Bitmap graphic formats: JPEG, GIF, TIFF, PNG, BMP, and many others
    • Structured graphic formats, including SVG, EMF/WMF, and AutoCAD DXF.
      These formats permit infinite zooming without loss of detail in PDF, Word, and OpenOffice.
  • Supports MathML 2.0, as external objects merged into the output using the @href attribute on <image> elements.
  • Can automatically generate a fully styleable:
    • Table of Contents, up to 10 levels deep
    • List of Figures
    • List of Tables
    • Alphabetical Index, up to 3 levels deep
  • Supports landscape orientation on figures and tables
  • Easily installs into the DITA Open Toolkit (OT) as a plugin, enabling integration into any editor or content management system that can use the OT to publish
  • Runs in all environments in which the DITA OT runs, including Microsoft® Windows®, Apple® OS X®, and Linux
  • Fully extensible to support new DITA topic and domain specializations
  • Supports all DITA 1.2 re-use features, including keys and content references.
  • Supports DITA 1.2 ditaval filtering. Future versions will support ditaval flagging.

DITA InPrint 1.0 currently supports the following DITA 1.2 elements:*

  • All base map elements
  • All bookmap elements
  • All map and bookmap metadata elements (output as document properties)
  • All base topic elements, except <required-cleanup>, <prolog>, <longdescref>, <longquoteref>, <object>, <param>, <data>, <data-about>, <foreign>, <unknown>, <titlealts>, <navtitle>, <searchtitle>, and specializations of those elements.
  • All typographic domain elements
  • All task topic elements
  • All concept topic elements
  • All reference topic elements
  • <title> elements in <glossentry> topics
  • <indexterm> in topic <prolog> and body
  • All highlighting domain elements
  • All programming domain elements
  • All software domain elements
  • All user interface domain elements
  • All task requirements (aka “machinery task”) domain elements

* Features, benefits, and technical specifications subject to change without notice.