Startsida Utforska Hjälp
Logga in
bn
/
se
2
0
Fork 0
Filer Ärenden 0 Pull-förfrågningar 0 Wiki
Träd: a4b429aad5
Grenar Taggar
se
/
SE
/
schema
/
WPS_Functions
/
dita-ot
/
dita-ot-3.3.3
/
doc
/
topics
/
migration.html

migration.html 13 KB
Historik Rå

123456789101112131415161718192021222324252627282930313233 
  1. <!DOCTYPE html
    2. 

  2.   SYSTEM "about:legacy-compat">
    3. 

  3. <html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2019"><meta name="DC.rights.owner" content="(C) Copyright 2019"><meta name="DC.type" content="reference"><meta name="description" content="If you have XSL transformation overrides, plug-ins or other customizations written prior to DITA-OT 3.3, you may need to make changes to ensure your overrides work properly with the latest toolkit versions."><meta name="DC.subject" content="upgrading, plug-ins, migrating, installing"><meta name="keywords" content="upgrading, plug-ins, migrating, installing"><meta name="DC.relation" scheme="URI" content="../topics/customizing.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-3.3.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-3.2.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-3.1.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-3.0.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-2.5.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-2.4.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-2.3.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-2.2.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-2.1.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-2.0.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-1.8.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-1.7.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-1.6.html"><meta name="DC.relation" scheme="URI" content="../topics/migrating-to-1.5.4.html"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="ID"><link rel="stylesheet" type="text/css" href="../css/commonltr.css"><link rel="stylesheet" type="text/css" href="../css/dita-ot-doc.css"><title>Migrating customizations</title></head><body id="ID"><header role="banner"><div class="header">
    4. 

  4.   <p>DITA Open Toolkit</p>
    5. 

  5.   <hr>
    6. 

  6. </div></header><nav role="toc"><ul><li><a href="../index.html">DITA Open Toolkit 3.3</a></li><li><a href="../release-notes/index.html">Release Notes</a></li><li><a href="../topics/installing-client.html">Installing DITA-OT</a></li><li><a href="../topics/alternative-input-formats.html">Authoring formats</a></li><li><a href="../topics/building-output.html">Building output</a></li><li><a href="../parameters/index.html">Setting parameters</a></li><li><a href="../topics/customizing.html">Customizing DITA-OT</a><ul><li><a href="../topics/html-customization.html">Customizing HTML</a></li><li><a href="../topics/pdf-customization.html">Customizing PDF</a></li><li><a href="../topics/custom-plugins.html">Working with plug-ins</a></li><li><a href="../extension-points/plugin-extension-points.html">Extension points</a></li><li class="active"><a href="../topics/migration.html">Migrating customizations</a><ul><li><a href="../topics/migrating-to-3.3.html">To 3.3</a></li><li><a href="../topics/migrating-to-3.2.html">To 3.2</a></li><li><a href="../topics/migrating-to-3.1.html">To 3.1</a></li><li><a href="../topics/migrating-to-3.0.html">To 3.0</a></li><li><a href="../topics/migrating-to-2.5.html">To 2.5</a></li><li><a href="../topics/migrating-to-2.4.html">To 2.4</a></li><li><a href="../topics/migrating-to-2.3.html">To 2.3</a></li><li><a href="../topics/migrating-to-2.2.html">To 2.2</a></li><li><a href="../topics/migrating-to-2.1.html">To 2.1</a></li><li><a href="../topics/migrating-to-2.0.html">To 2.0</a></li><li><a href="../topics/migrating-to-1.8.html">To 1.8</a></li><li><a href="../topics/migrating-to-1.7.html">To 1.7</a></li><li><a href="../topics/migrating-to-1.6.html">To 1.6</a></li><li><a href="../topics/migrating-to-1.5.4.html">To 1.5.4</a></li></ul></li><li><a href="../topics/globalization.html">Globalizing DITA content</a></li><li><a href="../topics/rebuilding-docs.html">Rebuilding documentation</a></li></ul></li><li><a href="../topics/troubleshooting-overview.html">Troubleshooting</a></li><li><a href="../reference/index.html">Reference</a></li><li><a href="../topics/dita-and-dita-ot-resources.html">Resources</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1">
    7. 

  7.   <h1 class="title topictitle1" id="ariaid-title1">Migrating customizations</h1>
    8. 

  8.   
    9. 

  9.   
    10. 

  10.   <div class="body refbody"><p class="shortdesc">If you have XSL transformation overrides, plug-ins or other customizations written prior to DITA-OT
    11. 

  11.       <span class="keyword">3.3</span>, you may need to make changes to ensure your overrides work properly with the latest
    12. 

  12.     toolkit versions. </p>
    13. 

  13.     <section class="section">
    14. 

  14.       <p class="p">In some cases, you may be able to remove old code that is no longer needed. In other cases, you may need to
    15. 

  15.         refactor your code to point to the modified extension points, templates or modes in recent toolkit versions.</p>
    16. 

  16.       <p class="p">When migrating customizations, identify the version of the toolkit you're currently using (base version) and
    17. 

  17.         the version of the toolkit you want to migrate to (target version). Then, review all of the migration changes
    18. 

  18.         described in <em class="ph i">all</em> of the versions from the base through the target. For instance, if you're currently on
    19. 

  19.         2.2 and want to move to 3.3, you should review all of the changes in 2.3 through 3.3. You may want to start at
    20. 

  20.         the oldest version and read forward so you can chronologically follow the changes, since it is possible that
    21. 

  21.         files or topics have had multiple changes. </p>
    22. 

  22.       <div class="note note note_note"><span class="note__title">Note:</span> <p class="p">DITA-OT releases follow
    23. 

  23.         <a class="xref" href="https://semver.org" target="_blank">Semantic Versioning 2.0.0</a> guidelines. Version numbers use the
    24. 

  24.             <code class="ph codeph"><var class="keyword varname">major</var>.<var class="keyword varname">minor</var>.<var class="keyword varname">patch</var></code> syntax, where
    25. 

  25.           <var class="keyword varname">major</var> versions may include incompatible API changes, <var class="keyword varname">minor</var> versions add
    26. 

  26.         functionality in a backwards-compatible manner and <var class="keyword varname">patch</var> versions are maintenance releases
    27. 

  27.         that include backwards-compatible bug fixes.</p><p class="p">Custom plug-ins developed for a previous <var class="keyword varname">major</var> version may require
    28. 

  28.         changes to work correctly with recent toolkit versions. Most plug-ins should be compatible with subsequent
    29. 

  29.           <var class="keyword varname">minor</var> and <var class="keyword varname">patch</var> versions of the <var class="keyword varname">major</var> release for
    30. 

  30.         which they were originally developed.</p></div>
    31. 

  31.     </section>
    32. 

  32.   </div>
    33. 

  33. <nav role="navigation" class="related-links"><ul class="ullinks"><li class="link ulchildlink"><strong><a href="../topics/migrating-to-3.3.html">Migrating to release 3.3</a></strong><br>DITA-OT 3.3 includes <span class="ph">new attribute sets for HTML5 customization, support for custom       integration processing, rotated table cells in PDF output, and hazard statements in HTML output</span>.</li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-3.2.html">Migrating to release 3.2</a></strong><br>DITA-OT 3.2 includes <span class="ph">new command-line options, support for RELAX NG parsing and       validation, preliminary processing for the XDITA authoring format proposed for Lightweight DITA, and a plug-in       registry that makes it easier to discover and install new plug-ins</span>.</li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-3.1.html">Migrating to release 3.1</a></strong><br>DITA-OT 3.1 includes <span class="ph">support for DITA 1.3 SVG domain elements, enhanced         <code class="keyword markupname xmlelement">&lt;codeblock&gt;</code> processing, and incremental improvements to Lightweight DITA processing and       PDF output</span>.</li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-3.0.html">Migrating to release 3.0</a></strong><br>DITA-OT 3.0 <span class="ph">adds support for Markdown, normalized DITA output, and the alternative       authoring formats proposed for Lightweight DITA. The map-first preprocessing approach provides a modern       alternative to the default <code class="ph codeph">preprocess</code> operation.</span></li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-2.5.html">Migrating to release 2.5</a></strong><br>In DITA-OT 2.5, several frequently-overridden legacy style settings were removed from the default PDF     plug-in. A separate plug-in can be used to restore the original settings.</li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-2.4.html">Migrating to release 2.4</a></strong><br>In DITA-OT 2.4, the <span class="keyword option">HTML5</span> transformation was refactored as an independent plug-in that no     longer depends on the <span class="keyword option">XHTML</span> plug-in. </li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-2.3.html">Migrating to release 2.3</a></strong><br>In DITA-OT 2.3, <span class="keyword option">HTML5</span> table processing has been refactored to use HTML5 best practices and     improved CSS properties. In PDF output, table heads and key columns no longer include shading, and unused     localization variables have been deprecated. The template for generated error messages has been updated to use a     single <code class="ph codeph">id</code> variable that contains the entire message ID.</li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-2.2.html">Migrating to release 2.2</a></strong><br>In DITA-OT 2.2, the <span class="keyword option">HTML5</span> transformation was refactored as its own plug-in and separate     plug-ins were created for each of the rendering engine-specific PDF transformations.    </li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-2.1.html">Migrating to release 2.1</a></strong><br>In DITA-OT 2.1, the <code class="ph codeph">insertVariable</code> template was deprecated for PDF transformations and     should be replaced with the <code class="ph codeph">getVariable</code> template. Various <code class="ph codeph">dita.<strong class="ph b">out.</strong>map.*</code>     targets have been deprecated in favor of updated <code class="ph codeph">dita.map.*</code> equivalents.</li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-2.0.html">Migrating to release 2.0</a></strong><br>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 <span class="keyword cmdname">dita</span> command simplifies distribution of     plugins by allowing installation from a URL.    </li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-1.8.html">Migrating to release 1.8</a></strong><br>In DITA-OT 1.8, certain stylesheets were moved to plug-in specific folders and various deprecated Ant     properties, XSLT stylesheets, parameters and modes were removed from the XHTML, PDF and ODT     transformations.</li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-1.7.html">Migrating to release 1.7</a></strong><br>In DITA-OT 1.7, a new preprocessing step implements flagging for HTML-based output formats. PDF processing     was corrected with regard to <code class="ph codeph">shortdesc</code> handling, and a new XSLT template mode was introduced for     HTML TOC processing. Several stylesheets were moved to plug-in specific folders and deprecated properties and XSLT     variables were removed. </li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-1.6.html">Migrating to release 1.6</a></strong><br>In DITA-OT 1.6, various <span class="ph filepath">demo</span> plug-ins were removed along with many deprecated     properties, targets, templates and modes. The PDF2 transformation no longer supports the beta version of DITA from     IBM, the "bkinfo" demo plug-in, or <span class="ph filepath">layout-masters.xml</span> configuration.</li><li class="link ulchildlink"><strong><a href="../topics/migrating-to-1.5.4.html">Migrating to release 1.5.4</a></strong><br>DITA-OT 1.5.4 adds new extension points to configure behavior based on file extensions, declare print     transformation types and add mappings to the PDF configuration catalog file. PDF output supports mirrored page     layout and uses new font family definitions. Support for several new languages was added for PDF and XHTML     output.</li></ul><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/customizing.html" title="There are several ways to customize and extend the toolkit. You can adjust various aspects of the default output by setting parameters or using custom stylesheets. For more complex customizations, use custom DITA-OT plug-ins to override other parts of processing.">Customizing DITA Open Toolkit</a></div></div></nav></article></main></body></html>
    34.