| 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="XHTML processing modules"/>
|
|---|
| 11 | <meta name="abstract" content="The DITA-OT ships with several varieties of XHTML output, each of which follows roughly the same path through the processing pipeline. All XHTML-based transformation begin with the same call to the pre-processing module, after which they generate XHTML files and then branch to create the transformation-specific navigation files."/>
|
|---|
| 12 | <meta name="description" content="The DITA-OT ships with several varieties of XHTML output, each of which follows roughly the same path through the processing pipeline. All XHTML-based transformation begin with the same call to the pre-processing module, after which they generate XHTML files and then branch to create the transformation-specific navigation files."/>
|
|---|
| 13 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/DITA-OTArchitecture.html"/>
|
|---|
| 14 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/XhtmlCommon.html"/>
|
|---|
| 15 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/XhtmlDefault.html"/>
|
|---|
| 16 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/XhtmlEclipse.html"/>
|
|---|
| 17 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/XhtmlTocjs.html"/>
|
|---|
| 18 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/XhtmlCHM.html"/>
|
|---|
| 19 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/XhtmlJavahelp.html"/>
|
|---|
| 20 | <meta name="DC.Format" content="XHTML"/>
|
|---|
| 21 | <meta name="DC.Identifier" content="xhtmlwithnavigation"/>
|
|---|
| 22 | <meta name="DC.Language" content="en-us"/>
|
|---|
| 23 | <link rel="stylesheet" type="text/css" href="../commonltr.css"/>
|
|---|
| 24 | <link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
|
|---|
| 25 | <title>XHTML processing modules</title>
|
|---|
| 26 | </head>
|
|---|
| 27 | <body id="xhtmlwithnavigation">
|
|---|
| 28 |
|
|---|
| 29 |
|
|---|
| 30 | <h1 class="title topictitle1">XHTML processing modules</h1>
|
|---|
| 31 |
|
|---|
| 32 |
|
|---|
| 33 | <div class="body conbody"><p class="shortdesc">The DITA-OT ships with several varieties of XHTML output, each of which follows roughly
|
|---|
| 34 | the same path through the processing pipeline. All XHTML-based transformation begin with the same
|
|---|
| 35 | call to the pre-processing module, after which they generate XHTML files and then branch to create
|
|---|
| 36 | the transformation-specific navigation files.</p>
|
|---|
| 37 |
|
|---|
| 38 | <div class="section">
|
|---|
| 39 | </div>
|
|---|
| 40 |
|
|---|
| 41 | </div>
|
|---|
| 42 |
|
|---|
| 43 | <div class="related-links">
|
|---|
| 44 | <ul class="ullinks">
|
|---|
| 45 | <li class="link ulchildlink"><strong><a href="../dev_ref/XhtmlCommon.html">Common XHTML processing</a></strong><br/>
|
|---|
| 46 | After the pre-processing operation runs, XHTML-based builds each run a common series of Ant targets to generate XHTML file. Navigation may be created before or after this set of common routines.</li>
|
|---|
| 47 | <li class="link ulchildlink"><strong><a href="../dev_ref/XhtmlDefault.html">Default XHTML processing</a></strong><br/>
|
|---|
| 48 | After the XHTML files are generated by the common routine, the <samp class="ph codeph">dita.map.xhtml</samp> target is called by the <span class="keyword parmname">xhtml</span> transformation. This target generates a TOC file called <span class="ph filepath">index.html</span>, which can be loaded into a frameset.</li>
|
|---|
| 49 | <li class="link ulchildlink"><strong><a href="../dev_ref/XhtmlEclipse.html">Eclipse help processing</a></strong><br/>
|
|---|
| 50 | The <span class="keyword option">eclipsehelp</span> transformation generates XHTML-based output and files that are needing to create an Eclipse Help system plug-in. Once the normal XHTML process has run, the <samp class="ph codeph">dita.map.eclipse</samp> target is used to create a set of control files and navigation files.</li>
|
|---|
| 51 | <li class="link ulchildlink"><strong><a href="../dev_ref/XhtmlTocjs.html">TocJS processing</a></strong><br/>
|
|---|
| 52 | The <span class="keyword option">tocjs</span> transformation was originally created as a plug-in that distributed outside of the toolkit, but it now ships bundled in the default packages. This XHTML-based output type creates a JavaScript based frameset with TOC entries that expand and collapse.</li>
|
|---|
| 53 | <li class="link ulchildlink"><strong><a href="../dev_ref/XhtmlCHM.html">HTML Help processing</a></strong><br/>
|
|---|
| 54 | The <span class="keyword option">htmlhelp</span> transformation created HTML Help control files. If the build runs on a system that has the HTML Help compiler installed, the control files are compiled into a CHM file.</li>
|
|---|
| 55 | <li class="link ulchildlink"><strong><a href="../dev_ref/XhtmlJavahelp.html">JavaHelp processing</a></strong><br/>
|
|---|
| 56 | The <span class="keyword option">javahelp</span> transformation runs several additional Ant targets after the XHTML processing is completed in order to create control files for the JavaHelp output.</li>
|
|---|
| 57 | </ul>
|
|---|
| 58 |
|
|---|
| 59 | <div class="familylinks">
|
|---|
| 60 | <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>
|
|---|
| 61 | </div>
|
|---|
| 62 | </div>
|
|---|
| 63 |
|
|---|
| 64 | </body>
|
|---|
| 65 | </html>
|
|---|
