Migrating to release 3.3
DITA-OT 3.3 includes new attribute sets for HTML5 customization, support for custom integration processing, rotated table cells in PDF output, and hazard statements in HTML output.
Secure connections to the plug-in registry
registry key in the
config/configuration.properties file to switch the URI schema to
https://, so the entry reads https://plugins.dita-ot.org/.For more information, see Adding plug-ins via the registry.
Base plug-in files moved to plugins directory
Various XSLT files and other resources have been moved from the root of the DITA-OT installation directory to the base plug-in directory plugins/org.dita.base.
If your plug-ins use the plugin URI scheme as recommended in the
Plug-in coding conventions, this change should not require any modifications to custom plug-in
code:
In XSLT, use the
pluginURI scheme in<xsl:import>and<xsl:include>to reference files in other plug-ins.Instead of:
<xsl:import href="../../org.dita.base/xsl/common/output-message.xsl"/>use:
<xsl:import href="plugin:org.dita.base:xsl/common/output-message.xsl"/>As with the plug-in directory property in Ant, this allows plug-ins to resolve to the correct directory even when a plug-in moves to a new location. The plug-in is referenced using the syntax
plugin:plugin-id:path/within/plugin/file.xsl.
Relocated catalog
Along with the other base plug-in files, the catalog-dita.xml file has
been moved from the root of the DITA-OT installation directory to plugins/org.dita.base.
External systems that rely on this catalog should be updated with the new location. Ant scripts and DITA-OT
plug-ins should use the plug-in directory property to refer to the file as
${dita.plugin.org.dita.base.dir}/catalog-dita.xml. A placeholder with a
<nextCatalog> entry is provided in the original location for backwards compatibility,
but this file may be removed in an upcoming release.
<nextCatalog catalog="plugins/org.dita.base/catalog-dita.xml"/>
Deprecated properties
The templates key in configuration properties has been deprecated in favor
of the <template> element in plugin.xml.
New attribute sets for HTML5 customization
articlebannerfootermainnavigationtoc