| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE html
|
|---|
| 3 | PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|---|
| 4 | <html xml:lang="en-us" lang="en-us">
|
|---|
| 5 | <head>
|
|---|
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
|
|---|
| 7 | <meta name="copyright" content="(C) Copyright 2005"/>
|
|---|
| 8 | <meta name="DC.rights.owner" content="(C) Copyright 2005"/>
|
|---|
| 9 | <meta name="DC.Type" content="concept"/>
|
|---|
| 10 | <meta name="DC.Title" content="DITA-OT processing modules"/>
|
|---|
| 11 | <meta name="abstract" content="The DITA-OT processing pipeline is implemented using Ant. Individual modules within the Ant script are implemented in either Java or XSLT, depending on such factors as performance or requirements for customization. Virtually all Ant and XSLT modules can be extended by adding a plug-in to the toolkit; new Ant targets may be inserted before or after common processing, and new rules may be imported into common XSLT modules to override default processing."/>
|
|---|
| 12 | <meta name="description" content="The DITA-OT processing pipeline is implemented using Ant. Individual modules within the Ant script are implemented in either Java or XSLT, depending on such factors as performance or requirements for customization. Virtually all Ant and XSLT modules can be extended by adding a plug-in to the toolkit; new Ant targets may be inserted before or after common processing, and new rules may be imported into common XSLT modules to override default processing."/>
|
|---|
| 13 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/DITA-OTArchitecture.html"/>
|
|---|
| 14 | <meta name="DC.Format" content="XHTML"/>
|
|---|
| 15 | <meta name="DC.Identifier" content="processing-pipeline-modules"/>
|
|---|
| 16 | <meta name="DC.Language" content="en-us"/>
|
|---|
| 17 | <link rel="stylesheet" type="text/css" href="../commonltr.css"/>
|
|---|
| 18 | <link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
|
|---|
| 19 | <title>DITA-OT processing modules</title>
|
|---|
| 20 | </head>
|
|---|
| 21 | <body id="processing-pipeline-modules">
|
|---|
| 22 |
|
|---|
| 23 |
|
|---|
| 24 | <h1 class="title topictitle1">DITA-OT processing modules</h1>
|
|---|
| 25 |
|
|---|
| 26 |
|
|---|
| 27 | <div class="body conbody"><p class="shortdesc">The DITA-OT processing pipeline is implemented using Ant. Individual modules within the
|
|---|
| 28 | Ant script are implemented in either Java or XSLT, depending on such factors as performance or
|
|---|
| 29 | requirements for customization. Virtually all Ant and XSLT modules can be extended by adding a
|
|---|
| 30 | plug-in to the toolkit; new Ant targets may be inserted before or after common processing, and new
|
|---|
| 31 | rules may be imported into common XSLT modules to override default processing.</p>
|
|---|
| 32 |
|
|---|
| 33 | <div class="section"><h2 class="title sectiontitle">XSLT modules</h2>
|
|---|
| 34 | <p class="p">The XSLT modules use shell files. Typically, each shell file begins by importing common rules
|
|---|
| 35 | that apply to all topics. This set of common processing rules may in turn import additional common
|
|---|
| 36 | modules, such as those used for reporting errors or determining the document locale. After the
|
|---|
| 37 | common rules are imported, additional imports can be included in order to support processing for
|
|---|
| 38 | DITA specializations.</p>
|
|---|
| 39 | <p class="p">For example, XHTML processing is controlled by the <span class="ph filepath">xsl\dita2xhtml.xsl</span> file.
|
|---|
| 40 | The shell begins by importing common rules that are applicable to all general topics:
|
|---|
| 41 | <span class="ph filepath">xslhtml\dita2htmlImpl.xsl</span>. After that, additional XSLT overrides are imported
|
|---|
| 42 | for specializations that require modified processing. For example, an override for reference topics
|
|---|
| 43 | is imported in order to add default headers to property tables. Additional modules are imported for
|
|---|
| 44 | tasks, for the highlighting domain, and for several other standard specializations. After the
|
|---|
| 45 | standard XSLT overrides occur, plug-ins may add in additional processing rules for local styles or
|
|---|
| 46 | for additional specializations.</p>
|
|---|
| 47 | </div>
|
|---|
| 48 |
|
|---|
| 49 | <div class="section"><h2 class="title sectiontitle">Java modules</h2>
|
|---|
| 50 |
|
|---|
| 51 | <p class="p">Java modules are typically used when XSLT is a poor fit, such as for processes that make use of
|
|---|
| 52 | standard Java libraries (like those used for index sorting). Java modules are also used in many
|
|---|
| 53 | cases where a step involves copying files, such as the initial process where source files are parsed
|
|---|
| 54 | and copied to a temporary processing directory.</p>
|
|---|
| 55 |
|
|---|
| 56 | </div>
|
|---|
| 57 |
|
|---|
| 58 | </div>
|
|---|
| 59 |
|
|---|
| 60 | <div class="related-links">
|
|---|
| 61 | <div class="familylinks">
|
|---|
| 62 | <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../dev_ref/DITA-OTArchitecture.html" title="The DITA Open Toolkit (DITA-OT) is an open-source implementation of the OASIS specification for the Darwin Information Typing Architecture (DITA). The toolkit uses ANT, XSLT, and Java to implement transforming DITA content (maps and topics) into different deliverable formats.">Architecture of the DITA Open Toolkit</a></div>
|
|---|
| 63 | </div>
|
|---|
| 64 | </div>
|
|---|
| 65 |
|
|---|
| 66 | </body>
|
|---|
| 67 | </html>
|
|---|
