| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
|
|---|
| 3 | <concept id="processing-structure">
|
|---|
| 4 | <title>DITA-OT processing structure</title>
|
|---|
| 5 | <shortdesc>The DITA-OT implements a multi-stage, map-driven architecture to process DITA content.
|
|---|
| 6 | Each stage in the process examines some or all of the content; some stages result in temporary
|
|---|
| 7 | files that are used by later steps, while others stages result in updated copies of the DITA
|
|---|
| 8 | content. Most of the processing takes place in a temporary working directory; the source files
|
|---|
| 9 | themselves are never modified.</shortdesc>
|
|---|
| 10 | <conbody>
|
|---|
| 11 | <p>The DITA-OT is designed as a pipeline. Most of the pipeline is common to all output formats; it
|
|---|
| 12 | is known as the <term>pre-processing stage</term>. In general, any DITA process begins with this
|
|---|
| 13 | common set of pre-processing routines. Once the pre-processing is completed, the pipeline
|
|---|
| 14 | diverges based on the requested output format. Some processing is still common to multiple output
|
|---|
| 15 | formats; for example, Eclipse Help and HTML Help both use the same routines to generate XHTML
|
|---|
| 16 | topics, after which the two pipelines branch to create different sets of navigation files.</p>
|
|---|
| 17 | <p>The following image illustrates how the pipeline works for some common output types: Docbook,
|
|---|
| 18 | PDF, Eclipse Help, XHTML, JavaHelp, and HTML Help.</p>
|
|---|
| 19 | <image href="images/mainarch.gif" placement="break">
|
|---|
| 20 | <alt>Diagram of some possible paths through the transform pipeline.</alt>
|
|---|
| 21 | </image>
|
|---|
| 22 | </conbody>
|
|---|
| 23 | </concept>
|
|---|
