Release of free, open source, XMLmind DITA Converter v3.3

August 21, 2018

Submitted by Hussein Shafie, XMLmind.


  • Full Lightweight DITA (AKA LwDITA) support, whether XDITA (very small subset of DITA XML, plus new audio and video elements), HDITA (topics and maps written in HTML5) or MDITA Extended Profile (topics and maps written in Markdown).

    XMLmind DITA Converter can of course process DITA documents comprising a mix of XDITA, HDITA, MDITA and (full) DITA topics and maps.

    However for this to work, you must be using a Java 1.8+ runtime. More information in "Lightweight DITA support".

  • Adding class line-numbers to the outputclass attribute of any element specializing pre numbers the lines of this element.

    Adding class tab-width-N to the outputclass attribute of any element specializing pre “expands” the tab characters found in this element and also performs other whitespace normalizations.

    Note that when the outputclass attribute of any element specializing pre contains class line-numbers and/or class language-L (which triggers syntax highlighting), then class tab-width-8 is implicitly specified too, that is, whitespace normalization is automatically performed. If this is not what you want, please explicitly add class tab-width-0 to outputclass.

    More information in "Fancy code blocks".

  • Upgraded XMLmind Web Help Compiler (whc for short) to version 2.1.3_01.
  • Upgraded Saxon to version
  • Distribution ditac-N_N_N-plus-fop.zip now contains Apache FOP 2.3 (including hyphenation and MathML support). This XSL-FO processor is automatically declared and thus, ready to be used to generate PDF or PostScript.

Bug fixes:

  • Elements draft-comment and required-cleanup were not filtered out prior to generating text for TOC entries, figure list entries, index entries, etc.


  • XSLT stylesheet parameter text-file-encoding is no longer supported. By default, the character encoding of the text file included using a coderef element is automatically determined by ditac (e.g. by examining the BOM or <?xml encoding="XXX"?>). You may specify this character encoding explicitly by adding a format="text; charset=XXX" attribute to the coderef element. Example: <coderef format="text; charset=US-ASCII" href="../src/sieve.cpp"/>.


  • XSLT stylesheet parameter use-multimedia-extensions is no longer supported. When set to 'yes' and when RenderX XEP was used to generate PDF, a proprietary extension called rx:media-object was used to embed audio and video objects in the output file.

More information in http://www.xmlmind.com/ditac/changes.shtml#v3.3.0.

News items may be commercial in nature and are published as received.