1 | <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
---|
2 | <!--
|
---|
3 | | LICENSE: This file is part of the DITA Open Toolkit project hosted on
|
---|
4 | | Sourceforge.net. See the accompanying license.txt file for
|
---|
5 | | applicable licenses.
|
---|
6 | *-->
|
---|
7 | <!--
|
---|
8 | | (C) Copyright IBM Corporation 2006. All Rights Reserved.
|
---|
9 | *-->
|
---|
10 | <html lang="en-us" xml:lang="en-us">
|
---|
11 | <head>
|
---|
12 | <meta content="text/html; charset=utf-8" http-equiv="Content-Type" />
|
---|
13 | <meta name="copyright" content="(C) Copyright 2005" />
|
---|
14 | <meta name="DC.rights.owner" content="(C) Copyright 2005" />
|
---|
15 | <meta content="public" name="security" />
|
---|
16 | <meta content="index,follow" name="Robots" />
|
---|
17 | <meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
---|
18 | <meta content="topic" name="DC.Type" />
|
---|
19 | <meta name="DC.Title" content="The Docbook to DITA transform" />
|
---|
20 | <meta name="abstract" content="This directory provides the docbook-to-dita transform." />
|
---|
21 | <meta name="description" content="This directory provides the docbook-to-dita transform." />
|
---|
22 | <meta scheme="URI" name="DC.Relation" content="../README.html" />
|
---|
23 | <meta scheme="URI" name="DC.Relation" content="../doc/ditaWriter.html" />
|
---|
24 | <meta scheme="URI" name="DC.Relation" content="../doc/ditaWriterMake.html" />
|
---|
25 | <meta content="XHTML" name="DC.Format" />
|
---|
26 | <meta content="docbook2dita" name="DC.Identifier" />
|
---|
27 | <meta content="en-us" name="DC.Language" />
|
---|
28 | <link href="../commonltr.css" type="text/css" rel="stylesheet" />
|
---|
29 | <title>The Docbook to DITA transform</title>
|
---|
30 | </head>
|
---|
31 | <body id="docbook2dita"><a name="docbook2dita"><!-- --></a>
|
---|
32 |
|
---|
33 |
|
---|
34 | <h1 class="topictitle1">The Docbook to DITA transform</h1>
|
---|
35 |
|
---|
36 |
|
---|
37 | <div><p>This directory provides the docbook-to-dita transform. </p>
|
---|
38 |
|
---|
39 | <p>The Docbook-to-DITA transform uses a design pattern that might be called <dfn class="term">a
|
---|
40 | dialogue transform</dfn>. This approach makes a strict separation between
|
---|
41 | the input and output logic. Generating an output element requires a conversation
|
---|
42 | between the output writer and the input reader:</p>
|
---|
43 |
|
---|
44 | <dl>
|
---|
45 | <dt class="dlterm">DITA writer</dt>
|
---|
46 |
|
---|
47 | <dd>The DITA writer knows how to generate DITA output. After producing an
|
---|
48 | element, the writer requests the attributes and content of the element from
|
---|
49 | the reader. For instance, the paragraph output rule generates a <samp class="codeph"><p></samp> element
|
---|
50 | and then requests the id attribute and other attributes of the paragraph and
|
---|
51 | then the paragraph content. Where the content is a simple sequence (for instance,
|
---|
52 | as with a topic or list), the writer requests in the subelements individually. </dd>
|
---|
53 |
|
---|
54 |
|
---|
55 | <dt class="dlterm">Docbook reader</dt>
|
---|
56 |
|
---|
57 | <dd>The Docbook reader knows how to read Docbook input. When the DITA writer
|
---|
58 | requests an attribute or content, the reader is responsible for satisfying
|
---|
59 | the request from the current input context. For instance, when the DITA paragraph
|
---|
60 | writer requests an id attribute, the reader might copy the id attribute from
|
---|
61 | the current Docbook input element or from a nearby Docbook input element.
|
---|
62 | The reader can also generate an id attribute or skip the id attribute. Similarly,
|
---|
63 | when the DITA paragraph writer requests paragraph content, the reader can
|
---|
64 | provide paragraph content by invoking the output rules on any of the text
|
---|
65 | and subelements from the input (often but not necessarily from content of
|
---|
66 | the current input element).</dd>
|
---|
67 |
|
---|
68 | </dl>
|
---|
69 |
|
---|
70 | <p>This directory provides the following modules:</p>
|
---|
71 |
|
---|
72 | <dl>
|
---|
73 | <dt class="dlterm">docbook2dita.xsl</dt>
|
---|
74 |
|
---|
75 | <dd>This module combines the Docbook reader and DITA writer to transform Docbook
|
---|
76 | input to DITA output.</dd>
|
---|
77 |
|
---|
78 |
|
---|
79 | <dt class="dlterm">dbReader.xsl</dt>
|
---|
80 |
|
---|
81 | <dd>This module provides the base Docbook reader. The module can be extended
|
---|
82 | by other modules that override the base module to handle requests from the
|
---|
83 | DITA writer in different ways.</dd>
|
---|
84 |
|
---|
85 | </dl>
|
---|
86 |
|
---|
87 | </div>
|
---|
88 |
|
---|
89 | <div>
|
---|
90 | <ul class="ullinks">
|
---|
91 | <li class="ulchildlink"><strong><a href="../doc/ditaWriter.html">DITA writer</a></strong><br />
|
---|
92 | This directory contains the DITA output writer.</li>
|
---|
93 | <li class="ulchildlink"><strong><a href="../doc/ditaWriterMake.html">DITA writer make</a></strong><br />
|
---|
94 | This transform generates the DITA writer from the DITA schema modules</li>
|
---|
95 | </ul>
|
---|
96 |
|
---|
97 | <div class="familylinks">
|
---|
98 | <div class="parentlink"><strong>Parent topic:</strong> <a href="../README.html" title="This plugin provides a transform from Docbook to DITA and some proof-of-concept examples of interoperability.">Docbook and DITA</a></div>
|
---|
99 | </div>
|
---|
100 | </div>
|
---|
101 |
|
---|
102 | </body>
|
---|
103 | </html>
|
---|