diff --git a/dev_ref/dev_ref.ditamap b/dev_ref/dev_ref.ditamap index a2f86eef4..b4a244608 100644 --- a/dev_ref/dev_ref.ditamap +++ b/dev_ref/dev_ref.ditamap @@ -58,13 +58,16 @@ - - - + + To 2.2 + To 2.1 + To 2.0 + To 1.8 + To 1.7 - - + To 1.6 + To 1.5.4 diff --git a/dev_ref/migrating-to-2.0.dita b/dev_ref/migrating-to-2.0.dita new file mode 100644 index 000000000..0eb2e0a8f --- /dev/null +++ b/dev_ref/migrating-to-2.0.dita @@ -0,0 +1,54 @@ + + + + + Migrating to Release 2.0 + In DITA-OT 2.0, XSLT templates were converted to XSLT 2.0, variable typing was + implemented, and some older templates were refactored or removed. In addition, the + dita command simplifies distribution of plugins by allowing installation + from a URL.There are likely other changes that should be noted + here. See + + + +
+ All Transformations — Variable Typing +

XSLT stylesheets were converted to XSLT 2.0. With that change, variable types were also + implemented. Plugins that change template variable values will need to make the following + changes:

+
    +
  • Declare the same types defined in the default templates with as.
    • +
  • Ensure that the generated values conform to the declared type.
    • +
+
+ +

For example:

+ <xsl:variable name="urltest"> +<xsl:variable name="urltest" as="xs:boolean"> + +
+ All Transformations — Refactoring +

Much of the toolkit code was refactored for release 2.0. Customization changes that were + based on a specific template in a previous version of the toolkit might not work because + the modified template is no longer used. If this is the case, the changes will need to be + reimplemented based on the new XSLT templates.

+
+ +
+ HTML5 +

A new transformation type has been added. Customizations that + previously modified the XHTML output to generate valid HTML5 should still work, but basing + your customization on the new transformation type might simplify the customization and + reduce the work required to maintain compatibility with future versions of the toolkit.

+ The transformation was refactored with release 2.2. Before + basing your customization on the changes in release 2.0, consider whether you might want to + move to release 2.2 instead. See . +
+
+ Plugin Installation and Distribution +

Plugins can now be installed or uninstalled from a ZIP archive using the new + dita command. Plugins can also be installed from a referenced URL. See + .

+
+ + diff --git a/dev_ref/migrating-to-2.1.dita b/dev_ref/migrating-to-2.1.dita new file mode 100644 index 000000000..7975c93b8 --- /dev/null +++ b/dev_ref/migrating-to-2.1.dita @@ -0,0 +1,27 @@ + + + + + Migrating to Release 2.1 + In DITA-OT 2.1, the insertVariable template was deprecated for PDF + transformations.There are likely other changes that should be + noted here. See + + +
+ PDF +

The following template has been deprecated:

+
    +
  • insertVariable
    • +
+

Calls to that template will result in warnings in the build log. To update your plugin, + make the following changes:

+ <xsl:call-template name="insertVariablegetVariable"> + <xsl:with-param name="theVariableIDid" select="var-id"/> + <xsl:with-param name="theParametersparams"> + params + </xsl:with-param> +</xsl:call-template> +
+ + diff --git a/dev_ref/migrating-to-2.2.dita b/dev_ref/migrating-to-2.2.dita new file mode 100644 index 000000000..37bd4ffee --- /dev/null +++ b/dev_ref/migrating-to-2.2.dita @@ -0,0 +1,72 @@ + + + + + Migrating to Release 2.2 + In DITA-OT 2.2, the transformation was refactored as its own + plugin and separate plugins were created for each of the rendering engine-specific PDF + transformations.There are likely other changes that should be + noted here. + +
+ HTML5 +

The transformation introduced in release 2.0 as part of the + plugin has been moved to a separate plugin. + Customizations that extended the previous HTML5 output under the + plugin will probably need to be refactored on the new HTML5 plugin.

+
+
+ PDF +

Processing specific to Apache FOP, Antenna House Formatter, and RenderX XEP has been + separated into separate plugins for each of those rendering engines. Customizations that + extended this processing might need to extend the new org.dita.pdf2.fop, + org.dita.pdf2.axf, or org.dita.pdf2.xep plugins.

+

PDF customizations that are not specific to a rendering engine can continue to extend the + org.dita.pdf2 plugin as before.

+
+
+ Consider whether some of the folloing might be useful:
    +
  • some elements are mapped differently ;see http://www.dita-ot.org/2.1/release-notes/index.html
    • +
  • +
  • The customFileUtils code used to handle input and output + in earlier versions of DITA-OT has been replaced with the Apache Commons IO utilities library.
      +
    • 1803 Use Commons IO
      • +
    • +

  • Support for theargs.odt.img.embed parameter has been removed from OpenDocument + format transformations.

    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.
      +
    • 1832 Remove support for args.odt.img.embed
      • +
    • +

  • 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 thekeydef.xml file to look up targets for phrase elements and pull in + text when needed. This change affects non-linking elements that can't take + @href attributes, such as + <ph>, <keyword>, + <cite>, <dt>, + <term>, and + <indexterm> (when + $INDEXSHOW is active).
      +
    • 1837 Remove keydef processing from XHTML rendering + code
      • +
    • +

  • A newdita.parser extension point has been added to + allow plug-ins to contribute a custom parser for DITA files.

    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.
      +
    • 1847 Extension-point for custom DITA parsers
      • +
    • +
+
+ +