Home Explore Help
Sign In
bn
/
se
2
0
Fork 0
Files Issues 0 Pull Requests 0 Wiki
Tree: e89bfafc3a
Branches Tags
se
/
SE
/
stuff
/
dita-ot-2.3.3
/
doc
/
dev_ref
/
processing-structure.html

processing-structure.html 4.8 KB
History Raw

1234567891011121314151617181920212223 
  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 2016"><meta name="DC.rights.owner" content="(C) Copyright 2016"><meta name="DC.Type" content="concept"><meta name="description" content="The DITA-OT implements a multi-stage, map-driven architecture to process DITA content. Each stage in the process examines some or all of the content; some stages result in temporary files that are used by later steps, while others stages result in updated copies of the DITA content. Most of the processing takes place in a temporary working directory; the source files themselves are never modified."><meta name="DC.Relation" scheme="URI" content="../dev_ref/DITA-OTArchitecture.html"><meta name="DC.Format" content="XHTML"><meta name="DC.Identifier" content="processing-structure"><link rel="stylesheet" type="text/css" href="../css/commonltr.css"><link rel="stylesheet" type="text/css" href="../css/dita-ot-doc.css"><title>Processing structure</title></head><body id="processing-structure"><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 2.3</a></li><li><a href="../release-notes/index.html">Release Notes</a></li><li><a href="../getting-started/index.html">Getting Started</a></li><li><a href="../user-guide/index.html">User Guide</a></li><li><a href="../parameters/index.html">Parameter Reference</a></li><li><a href="../dev_ref/index.html">Developer Reference</a><ul><li><a href="../dev_ref/DITA-OTArchitecture.html">DITA-OT Architecture</a><ul><li class="active"><a href="../dev_ref/processing-structure.html">Processing structure</a></li><li><a href="../dev_ref/processing-pipeline-modules.html">Processing modules</a></li><li><a href="../dev_ref/processing-order.html">Processing order</a></li><li><a href="../dev_ref/DITA-OTPreprocess.html">Pre-processing modules</a></li><li><a href="../dev_ref/XhtmlWithNavigation.html">HTML-based processing modules</a></li><li><a href="../dev_ref/PdfDefault.html">PDF processing modules</a></li><li><a href="../dev_ref/OdtDefault.html">Open Document Format processing modules</a></li></ul></li><li><a href="../dev_ref/extending-the-ot.html">Extending the DITA-OT</a></li><li><a href="../dev_ref/plugin-creating.html">Creating plug-ins</a></li><li><a href="../dev_ref/plugin-extension-points.html">Extension points</a></li><li><a href="../dev_ref/pdf-customization.html">Customizing PDF output</a></li><li><a href="../dev_ref/migration.html">Migrating customizations</a></li></ul></li><li><a href="../user-guide/dita-and-dita-ot-resources.html">DITA Resources</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1">
    7. 

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

  8.   
    9. 

  9.   <div class="body conbody"><p class="shortdesc">The DITA-OT implements a multi-stage, map-driven architecture to process DITA content. Each stage in the
    10. 

  10.     process examines some or all of the content; some stages result in temporary files that are used by later steps,
    11. 

  11.     while others stages result in updated copies of the DITA content. Most of the processing takes place in a temporary
    12. 

  12.     working directory; the source files themselves are never modified.</p>
    13. 

  13.     <p class="p">The DITA-OT is designed as a pipeline. Most of the pipeline is common to all output formats; it is known as the
    14. 

  14.         <dfn class="term">pre-processing stage</dfn>. In general, any DITA process begins with this common set of pre-processing
    15. 

  15.       routines. Once the pre-processing is completed, the pipeline diverges based on the requested output format. Some
    16. 

  16.       processing is still common to multiple output formats; for example, Eclipse Help and HTML Help both use the same
    17. 

  17.       routines to generate XHTML topics, after which the two pipelines branch to create different sets of navigation
    18. 

  18.       files.</p>
    19. 

  19.     <p class="p">The following image illustrates how the pipeline works for some common output types: DocBook, PDF, Eclipse Help,
    20. 

  20.       XHTML, JavaHelp, and HTML Help.</p>
    21. 

  21.     <br><img class="image" src="images/mainarch.gif" width="624" alt="Diagram of some possible paths through the transform pipeline."><br>
    22. 

  22.   </div>
    23. 

  23. <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../dev_ref/DITA-OTArchitecture.html" title="The DITA Open Toolkit is an open-source implementation of the OASIS specification for the Darwin Information Typing Architecture. The toolkit uses Ant, XSLT, and Java to transform DITA content (maps and topics) into different deliverable formats.">Architecture of the DITA Open Toolkit</a></div></div></nav></article></main></body></html>
    24.