Migrating HTML to DITA

The HTML to DITA migration tool ships in the demo/ directory of the toolkit, and does not make use of the common toolkit processing for DITA content.

The DITA Open Toolkit release 1.2 or above provides a HTML to DITA migration tool, which migrates HTML files to DITA files. This migration tool originally comes from the developerWorks publication of Robert D. Anderson's how-to articles with the original h2d code. This migration tool is under demo\h2d directory. You can use it separately because it is not integrated into the main transformation of toolkit. The version in the toolkit is more recent, but the articles should be referenced for information on details of the program, as well as for information on how to extend it. There are links to the articles at the bottom of this page.

Preconditions

The preconditions to be considered before using the migration tool are listed below:

Post conditions

There are also some post conditions to consider after processing:

Known limitations

  1. Since Xalan doesn't allow to set the public and system IDs dynamically using a variable, when Xalan is used as the default XSLT processor, the output will contain:
    <!DOCTYPE topic PUBLIC "{$publicid}" "{$systemid}">

    Suggest to use Saxon as the processor to fix this problem. For other information on this problem, see the section "Other general migration notes" in the first developerWorks article.

Extension points

The HTML2DITA migration tool helps extension in the following listed ways: