DITA Open Toolkit Release 2.1 requires the Java Runtime Environment (JRE) or Java
Development Kit (JDK), version
DITA Open Toolkit Release 2.1.2 includes the following bug fixes:
Index terms starting with “Ñ” are no longer dropped from Spanish PDF indexes. They are now handled with the correct Spanish sort order and placed in a group between “N” and “O”, under the “Ñ” heading.
References to external code samples are now resolved properly when
Warnings for deprecated templates are now displayed with the correct message prefix:
DITA Open Toolkit Release 2.1.1 includes the following bug fixes:
Whitespace in
Any proportional table column widths expressed in the CALS table model as "*" are now normalized to the equivalent "1*" value to prevent errors while generating XHTML output.
In DITA Open Toolkit 2.0.1, the line ending characters in shell files were inadvertently changed to Windows (CRLF) line endings. The correct UNIX (LF) line endings have now been restored.
DITA Open Toolkit Release 2.1 includes the following new features and changes:
In PDF output, inline
Image metadata processing has been refactored to improve the processing speed by determining width and height without reading the entire image into memory.
Obsolete CHM configuration files have been removed from the PDF2 plugin.
The code for the transformation has been refactored into two separate steps to enable re-use in other plain-text—based transformation types. The first step generates an abstract syntax tree with div/span syntax, and the second takes that intermediate format and creates troff output. Two new extension points are available to override the processing performed in each step:
Milestone 1 included the following new features and changes:
The
DITA topics are now mapped to the HTML5
HTML5
Additional file formats referenced from
DITA-OT now fails with a fatal error (DOTA013F) if a specified .ditaval filter file is not available. This ensures that unexpected output is not generated if the filter file is missing or invalid.
The
The deprecated Java command line tool has been removed in favor of the
If you previously generated output via a Java command sequence such as
The custom
Support for the
The previous default behavior was to embed images as Base64-encoded text, but editors do not use this as a default. Instead, office packages such as LibreOffice will convert embedded images into linked images on opening and saving an ODT file.
Keydef processing has been removed from the XHTML rendering code
Keys are now resolved in one preprocessing step, whereas in earlier versions of DITA-OT, the XHTML code
returned to the
A new
If a custom DITA parser is defined, the preprocessing routines will use it during the gen-list and debug-filter stages to output DITA XML.
DITA Open Toolkit Release 2.1 provides fixes for the following bugs:
Milestone 1 provided fixes for the following bugs: