adita

SE/stuff/dita-ot-3.3.3/docsrc/samples/tasks/spraypainting.xml

@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+<!-- (C) Copyright IBM Corporation 2001, 2005. All Rights Reserved. -->
+
+<task id="spraypaint" xml:lang="en-us">
+  <title>Spray painting</title>
+  <shortdesc>When paint is applied using a spray nozzle, it is referred to as spray painting.</shortdesc>
+  <taskbody>
+    <context>
+      <p>The garage is a good place to spray paint.</p></context>
+    <steps>
+      <step>
+        <cmd>Move the car out of the garage to avoid getting paint on it.</cmd>
+      </step>
+      <step>
+        <cmd>Place newspaper, cardboard, or a drop-cloth on the garage floor.</cmd>
+      </step>
+      <step>
+        <cmd>Place the object to be painted on the covered area.</cmd>
+      </step>
+      <step>
+        <cmd>Follow the directions on the paint can to paint the object.</cmd>
+      </step>
+      <step>
+        <cmd>Let the paint dry thoroughly before you move the object.</cmd>
+      </step>
+    </steps>
+  </taskbody>
+  <related-links>
+    <link href="../concepts/paint.xml" format="dita" type="concept"/>
+  </related-links>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/samples/tasks/takinggarbage.xml

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+<!-- (C) Copyright IBM Corporation 2001, 2005. All Rights Reserved. -->
+
+<task id="takinggarbage" xml:lang="en-us">
+  <title>Taking out the garbage</title>
+  <shortdesc>Regular garbage removal is necessary for the proper functioning of a home.</shortdesc>
+  <taskbody>
+    <context>
+      <p>Your municipality collects garbage from homes once a week, usually early in the morning.</p></context>
+    <steps>
+      <step>
+        <cmd>Find out from the town what day of the week garbage is collected in your neighborhood.</cmd>
+      </step>
+      <step>
+        <cmd>The night before collection, place the garbage cans on the curb.</cmd>
+      </step>
+      <step>
+        <cmd>After the garbage has been collected, move the cans back into your garage.</cmd>
+      </step>
+    </steps>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/samples/tasks/washingthecar.xml

@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+<!-- (C) Copyright IBM Corporation 2001, 2005. All Rights Reserved. -->
+
+<task id="washcar" xml:lang="en-us">
+  <title>Washing the car</title>
+  <shortdesc>Keep your car looking great by washing it regularly.</shortdesc>
+  <taskbody>
+    <steps>
+      <step>
+        <cmd>Move the car onto the driveway.</cmd>
+      </step>
+      <step>
+        <cmd>Attach the water hose to a spout and pull the free end over to the car.</cmd>
+      </step>
+      <step>
+        <cmd>Fill a bucket with soapy water.</cmd>
+      </step>
+      <step>
+        <cmd>Use a sponge to apply the soapy water to the car and scrub off the dirt.</cmd>
+      </step>
+      <step>
+        <cmd>Rinse the car by spraying clean water from the hose.</cmd>
+      </step>
+      <step>
+        <cmd>Dry the car using a dampened chamois.</cmd>
+      </step>
+    </steps>
+    <result>
+      <p>
+        <image href="../image/carwash.jpg" height="171" width="249">
+          <alt>washing the car</alt>
+        </image>
+      </p>
+    </result>
+  </taskbody>
+  <related-links>
+    <link href="../concepts/waterhose.xml" format="dita" type="concept"/>
+  </related-links>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/settings.gradle

@@ -0,0 +1 @@
+rootProject.name = 'docs'

SE/stuff/dita-ot-3.3.3/docsrc/site.ditamap

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map xml:lang="en-US">
+  <title>DITA Open Toolkit <keyword keyref="release"/></title>
+
+  <mapref href="resources/common-toc.ditamap"/>
+
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/DITA-messages-details.xml

@@ -0,0 +1,805 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="errormessages" xml:lang="en-US">
+  <title conref="DITA-messages.xml#msgs/title" conaction="pushreplace">DITA-OT error messages</title>
+  <shortdesc conref="DITA-messages.xml#msgs/shortdesc" conaction="pushreplace">This topic lists each error message
+    generated by the toolkit and provides additional information that might be helpful in understanding and resolving
+    the error condition. If your toolkit installation includes custom plug-ins that define additional messages, you can
+    add to this list by rebuilding the DITA-OT documentation.</shortdesc>
+  <refbody>
+    <section id="overview" conref="DITA-messages.xml#msgs/overview" conaction="pushreplace">
+      <p>Each message ID is composed of a message prefix, a message number, and a letter that indicates the severity
+        level (I, W, E, or F). </p>
+      <p>The toolkit uses the following severity scale:</p>
+      <dl id="severity-levels">
+        <dlentry>
+          <dt>Info (I)</dt>
+          <dd>Informational messages highlight the progress of transformation and call attention to conditions of which
+            you should be aware. For example, draft comments are enabled and will be rendered in the output.</dd>
+        </dlentry>
+        <dlentry>
+          <dt>Warning (W)</dt>
+          <dd>The toolkit encountered a problem that should be corrected. Processing will continue, but the output might
+            not be as expected.</dd>
+        </dlentry>
+        <dlentry>
+          <dt>Error (E)</dt>
+          <dd>The toolkit encountered a more severe problem, and the output is affected. For example, some content is
+            missing or invalid, or the content is not rendered in the output</dd>
+        </dlentry>
+        <dlentry>
+          <dt>Fatal (F)</dt>
+          <dd>The toolkit encountered a severe condition, processing stopped, and no output is generated.</dd>
+        </dlentry>
+      </dl>
+      <p>Plug-ins may be used to add additional messages to the toolkit; for more information, see <xref
+          keyref="rebuilding-docs"/>.</p>
+    </section>
+    <simpletable>
+      <sthead>
+        <stentry>Individual cells in this table may be used to push additional explanations for any existing error
+          message into the generated message topic.</stentry>
+      </sthead>
+      <strow>
+        <stentry>To add additional explanation to any message, add the explanation to this table in a single cell, and
+          set the following attributes on the <xmlelement>stentry</xmlelement> tag:
+          <ul>
+            <li><codeph>conref="DITA-messages.xml#msgs/MESSAGEID-extra"</codeph> -- for example, use the following to
+              add additional info to message DOTX001F:
+              <codeph>conref="DITA-messages.xml#msgs/DOTX001F-extra"</codeph></li>
+            <li><codeph>conaction="pushreplace"</codeph></li>
+          </ul></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA001F-extra" conaction="pushreplace">Default transformation types
+          that ship with the toolkit include dita, eclipsehelp, html5, htmlhelp, markdown variants, pdf (or pdf2),
+          tocjs, troff, xhtml, and xhtml. Additional transformation types may be available if toolkit plug-ins are
+          installed.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA002F-extra" conaction="pushreplace">The input parameter was not
+          specified, so there is no DITA or DITAMAP file to transform. Ensure the parameter is set properly; see <xref
+            keyref="parameters-base">DITA-OT common parameters (args.input)</xref> if you are unsure how to specify the
+          input file.
+        <indexterm>DITA maps<indexterm>input file</indexterm></indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA003F-extra" conaction="pushreplace">An alternate stylesheet was
+          specified to run in place of the default XSLT output process, but that stylesheet could not be loaded. Please
+          correct the parameter to specify a valid stylesheet.<indexterm>XSLT<indexterm>stylesheet error</indexterm></indexterm></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA004F-extra" conaction="pushreplace">This optional parameter is used
+          to set an extension for DITA topic documents in the temporary processing directory. Only "dita", ".dita",
+          "xml", or ".xml" are allowed.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA006W-extra" conaction="pushreplace">If the CSSPATH uses an absolute
+          path, it should be one that can still be accessed after the files are moved to another system (such as
+            <codeph>http://www.example.org/</codeph>). Absolute paths on the local file system will be broken if the
+          content is moved to a new system.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA007E-extra" conaction="pushreplace">The running footer file, which
+          contains content to be added to the bottom of each XHTML output topic, cannot be located or read. This is
+          usually caused by a typo in the parameter value. You should also ensure that the value is not specified with
+          "file:" as a prefix.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA008E-extra" conaction="pushreplace">The running header file, which
+          contains content to be added to the top of each XHTML output topic, cannot be located or read. This is usually
+          caused by a typo in the parameter value. You should also ensure that the value is not specified with "file:"
+          as a prefix.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA009E-extra" conaction="pushreplace">The running heading file, which
+          contains content to be added to the <xmlelement>head</xmlelement> section of each HTML output topic, cannot be
+          located or read. This is usually caused by a typo in the parameter value. You should also ensure that the
+          value is not specified with "file:" as a prefix.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA066F-extra" conaction="pushreplace">An alternate stylesheet was
+          specified to run in place of the default XSL-FO output process, but that stylesheet could not be loaded.
+          Please correct the parameter to specify a valid stylesheet.</stentry>
+      </strow>
+      <strow>
+        <!-- This condition and the next belong to the org.dita.pdf2 plugin. Not sure if they should be moved below. -->
+        <stentry conref="DITA-messages.xml#msgs/DOTA067W-extra" conaction="pushreplace">According to the OASIS DITA
+          Specification, the <xmlelement>index-see</xmlelement> element should be ignored if the parent
+            <xmlelement>indexterm</xmlelement> contains other <xmlelement>indexterm</xmlelement> children.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA068W-extra" conaction="pushreplace">According to the OASIS DITA
+          Specification, the <xmlelement>index-see-also</xmlelement> element should be ignored if the parent
+            <xmlelement>indexterm</xmlelement> contains other <xmlelement>indexterm</xmlelement> children.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTA069F-extra" conaction="pushreplace">Please ensure that the input
+          file path and file name were entered correctly.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ005F-extra" conaction="pushreplace"/>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ009E-extra" conaction="pushreplace">The transform was unable to
+          create files properly during the transform; results may not be as expected.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ012F-extra" conaction="pushreplace">This message may indicate an
+          invalid input file (such as accidentally specifying a PDF file as input rather than a DITA map file), an input
+          file that uses elements which are not allowed, are not part or a DITA file that has errors and cannot be
+          parsed as XML. You could also be using a specialized DITA document type that needs external plug-ins in order
+          to be parsed correctly. The message issued by the XML parser should provide additional information to help
+          diagnose the cause.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ013E-extra" conaction="pushreplace">This message may indicate a
+          reference to an invalid file (such as accidentally referencing a PDF or unknown XML file as if it was DITA), a
+          referenced file that uses elements which are not allowed, or a referenced DITA file that has errors and cannot
+          be parsed as XML. You could also be using a specialized DITA document type that needs external plug-ins in
+          order to be parsed correctly. The message issued by the XML parser should provide additional information to
+          help diagnose the cause.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ014W-extra" conaction="pushreplace">An empty
+            <xmlelement>indexterm</xmlelement> element was found, and will appear in the index as ***. This index term
+          should be removed from the source.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ020W-extra" conaction="pushreplace">This will appear when one
+          installed plug-in requires another in order to function correctly, but the required plug-in is not found. The
+          installed plug-in will be ignored.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ021W-extra" conaction="pushreplace">This may appear if filter
+          conditions on the root element of a topic cause the entire topic to be filtered out. To remove this message,
+          you could place any filter conditions on the reference to this file, which will prevent the build from
+          accessing this file.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ022F-extra" conaction="pushreplace">Either the input file or the
+          ditaval file should change, otherwise your build is explicitly excluding all content.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ023E-extra" conaction="pushreplace">Check whether the image exists
+          in the source location or already exists in the output directory.
+          <indexterm>image</indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ025E-extra" conaction="pushreplace">This message should only appear
+          in the following cases:
+          <ul>
+            <li>Errors earlier in the transform prevented this step of the transform from running; correct any errors
+              and try the build again.</li>
+            <li>An Ant build or plug-in is directly calling the toolkit’s topic merge module, and is doing so
+              improperly; in this case the Ant build or plug-in needs to be fixed.</li>
+            <li>In the past, problems have been encountered when calling this module with an absolute path; this should
+              no longer be an issue, but may be fixed in older releases by updating the Ant build or plug-in.</li>
+          </ul></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ026E-extra" conaction="pushreplace">This message should only appear
+          if an Ant build or plug-in is directly calling the toolkit’s topic merge module, or if earlier errors resulted
+          in problems with some of the content. If the topic merge module is called correctly, then this indicates a
+          program error that should be reported to the DITA-OT development team via the <xref keyref="dita-ot-issues"/>.
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ028E-extra" conaction="pushreplace">When referencing a non-DITA
+          file, the format attribute should indicate the type of file referenced (such as "html" for HTML topics or
+          "pdf" for PDF files). Otherwise, the transform may attempt to parse the referenced document as a DITA
+          topic.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ029I-extra" conaction="pushreplace">The domains attribute is used in
+          specialized DITA documents to help determine which domain elements are legal. This message will only appear if
+          a DITA specialization was not defined properly.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ030I-extra" conaction="pushreplace">All specialized DITA elements
+          must define a class attribute to provide ancestry information. This message will only appear if a specialized
+          DITA element did not define a class attribute, or if non-DITA elements are included in a DITA
+          context.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ031I-extra" conaction="pushreplace">This informational message is
+          intended to help you catch filter conditions that may have been specified improperly; if the value is correct,
+          no action is needed.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ033E-extra" conaction="pushreplace"/>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ034F-extra" conaction="pushreplace">DITA processing is based on
+          class attributes defined for every element. Usually these are defaulted in the DTD or Schema; if no DTD or
+          Schema is used, the class attributes must be explicitly included in the map or topic.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ035F-extra" conaction="pushreplace">This will appear when a topic is
+          outside the scope of the map; for example, if the main input map references
+            <filepath>"../other-directory/some.dita"</filepath>. The result would cause an output file to be created
+          outside of the output directory. See <xref keyref="parameters-base">DITA-OT common parameters (outer.control
+            and generate.copy.outer)</xref> for details.
+          <indexterm>generate.copy.outer</indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ036W-extra" conaction="pushreplace">This will appear when a topic is
+          outside the scope of the map; for example, if the main input map references
+            <filepath>"../other-directory/some.dita"</filepath>. The result would cause an output file to be created
+          outside of the output directory. If you do not want to see the warning message, please use the Ant parameter
+          'outer.control', and set the value to "quiet". Otherwise, move the referenced file into the input dita/map
+          directory. See <xref keyref="parameters-base">DITA-OT common parameters (outer.control and
+            generate.copy.outer)</xref> for details.
+          <indexterm>generate.copy.outer</indexterm></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ037W-extra" conaction="pushreplace">DITA processing is based on
+          class attributes defined for every element. Usually these are defaulted in the DTD or Schema; if validation
+          against the DTD or Schema is turned off, the class attributes must be explicitly included in the map or
+          topic.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ038E-extra" conaction="pushreplace">This appears to indicate an
+          error in creating specialized metadata elements. Please verify that the document type you are using is
+          complete and complies with DITA Specialization rules.
+          <indexterm>metadata<indexterm>specialization error</indexterm></indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ039E-extra" conaction="pushreplace">Please see the topic on <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute"
+            format="html" scope="external">Conref Push</xref> in the DITA specification for details on expected syntax
+          for this function.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ040E-extra" conaction="pushreplace">Please see the topic on <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute"
+            format="html" scope="external">Conref Push</xref> in the DITA specification for details on expected syntax
+          for this function.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ041E-extra" conaction="pushreplace">The conref attribute must be a
+          URI reference to a DITA element. Please see the topic on <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing"
+            format="html" scope="external">URI-based addressing</xref> in the DITA specification for details on the
+          expected syntax.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ042E-extra" conaction="pushreplace">The conref push function was
+          used to replace a single element with two or more alternatives. Only one element may directly replace another
+          using conref push. See <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute"
+            format="html" scope="external">Conref Push</xref> in the DITA specification for more information about the
+          conref push "replace" function.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ043W-extra" conaction="pushreplace">The target for a conref push
+          action does not exist; please make sure that the syntax is correct and that the target exists. See the topic
+          on <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing"
+            format="html" scope="external">URI-based addressing</xref> in the DITA specification for details on the
+          expected syntax. If the syntax is correct, it is possible that the target was filtered out of your build using
+          a DITAVAL file.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ044W-extra" conaction="pushreplace">Please see the topic on <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute"
+            format="html" scope="external">Conref Push</xref> in the DITA specification for details on expected syntax
+          for this function.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ045I-extra" conaction="pushreplace">This informational message is
+          intended to help you catch catch duplicate key definitions; if the keys are defined as expected, no action is
+          needed.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ046E-extra" conaction="pushreplace">See <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconkeyrefattribute.html#theconkeyrefattribute"
+            format="html" scope="external">the conkeyref definition</xref> for details on expected syntax and
+          usage.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ047I-extra" conaction="pushreplace">This message is intended to help
+          you locate incorrectly specified keys; if the key was specified correctly, this message may be
+          ignored.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ049W-extra" conaction="pushreplace">A DITA Subject Scheme map was
+          used to limit values that are available to the specified attribute. Please correct the attribute so that it
+          uses one of the allowed values.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ050W-extra" conaction="pushreplace">The Eclipse index will contain a
+          value such as "See also otherEntry", but otherEntry does not exist in this index. The index reference will be
+          broken unless this plug-in is <i>always</i> loaded into Eclipse with another plug-in that defines otherEntry
+          as an index term.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ051E-extra" conaction="pushreplace">The target for a coderef
+          element, which specifies an external text-based file, could not be located or loaded. Please verify that the
+          reference is correct.
+          <p>Note that for security reasons, references to code samples outside of the scope of the map directory are
+            not supported by default, as this could allow a reference to access and display any restricted or hidden
+            file on the system. If you are certain that the path is valid and the file should be loaded, the current
+            workaround is to set a parameter to allow these references. See <xref keyref="parameters-base">DITA-OT
+              common parameters (outer.control and generate.copy.outer)</xref> for details.<indexterm>generate.copy.outer</indexterm></p></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ052E-extra" conaction="pushreplace">DITA-OT supports a special
+          syntax on coderef elements to specify the character set of the target document. See <xref
+            keyref="extended-functionality"/> for details on the expected syntax.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ053W-extra" conaction="pushreplace">By default, DITA-OT supports the
+          extensions "dita" and "xml" for DITA topics, as mandated by the DITA specification. Please verify that your
+          topics use one of these extensions, or configure the toolkit to allow additional extensions.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ054E-extra" conaction="pushreplace">This message indicates that the
+          <xmlatt>href</xmlatt> value specified in <varname>%1</varname> does not use proper URI syntax. This may occur when
+          <xmlatt>href</xmlatt> includes characters that should be escaped (such as the space character, which should be
+          <codeph>%20</codeph> when in a URI). In strict processing mode this will cause a build failure;
+          in other processing modes the build will continue using the value in <varname>%2</varname>.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ068E-extra" conaction="pushreplace">A conref "mark" action has been
+          used to mark a target element without a corresponding content reference target. This may occur when the order
+          of the "mark" element and the pushed element is reversed.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ069E-extra" conaction="pushreplace">
+          <p>A circular reference was found in key definitions: a series of key references where the last key references
+            the first.</p>
+          <p>This may occur if a <xmlelement>topicref</xmlelement> element contains both a key name in the
+              <xmlatt>keys</xmlatt> attribute and a reference to the same key in the <xmlatt>keyref</xmlatt> attribute,
+            or if a <xmlatt>keyref</xmlatt> attribute points to a key that refers back to the referencing element.</p>
+          <p>To resolve this issue, change the target of the <xmlatt>keyref</xmlatt> so the key is defined by pointing
+            to a resource other than itself.</p>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ070I-extra" conaction="pushreplace">
+          <p>When a <xmlatt>class</xmlatt> attribute does not use the expected syntax, this usually indicates that
+              <xmlatt>class</xmlatt> has been explicitly set on a DITA element. The attribute should be removed from the
+            document so that the expected default value can be automatically used.</p>
+          <p>If this is a non-DITA element, it needs to be placed inside a <xmlelement>foreign</xmlelement> element so
+            that is not validated against DITA rules.
+          <indexterm>validate</indexterm>
+          </p>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTJ071E-extra" conaction="pushreplace">
+          <p>Ensure that the DITAVAL file exists. If more than one DITAVAL file is specified, ensure that the paths are
+            delimited using the file path separator character appropriate for your operating system (semicolon
+              ‘<codeph>;</codeph>’ on Windows, or colon ‘<codeph>:</codeph>’ on macOS or Linux).</p>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX001W-extra" conaction="pushreplace">This build uses generated text,
+          such as the phrase "Related information" (which is generated above many link groups). The toolkit was unable
+          to locate the string <varname>%1</varname> for your specified language, so the string will appear in the
+          default language. This generally indicates that the toolkit’s strings need to be updated to support your
+          language, or that your language setting is incorrect.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX002W-extra" conaction="pushreplace">The Eclipse help system requires
+          a title in the project files generated from your map. Please add a title to your input map to get valid
+          Eclipse help output.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX003I-extra" conaction="pushreplace">Eclipse uses anchor references
+          to connect with other TOC files. For this to work in content generated from a DITA map, the anchorref element
+          must reference either an existing Eclipse TOC XML file, or another DITA map (which will presumably also be
+          converted to an Eclipse TOC).
+          <indexterm>table of contents<indexterm>Eclipse Help</indexterm></indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX004I-extra" conaction="pushreplace">Eclipse builds use DITA’s
+            <xmlelement>navref</xmlelement> element to pull in other Eclipse TOC files. The build found a
+            <xmlelement>navref</xmlelement> element that does not reference any other file; the element will be
+          ignored.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX005E-extra" conaction="pushreplace">To remove this message, provide
+          a navigation title for the referenced object in the map or topic, or ensure that you are referencing a valid
+          local DITA target.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX006E-extra" conaction="pushreplace">Set the format attribute to
+          identify the format of the file. If the reference is to a DITA document, ensure that the document uses a valid
+          DITA extension (default supported extensions are "dita" and "xml").</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX007I-extra" conaction="pushreplace">The HTML Help compiler will only
+          include some types of information in the compiled CHM file; the current reference will not be
+          included.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX008E-extra" conaction="pushreplace">Ensure that the file exists and
+          can be read. <ph conref="DITA-messages-details.xml#errormessages/changeExtension"/></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX008W-extra" conaction="pushreplace">To fix the table of contents,
+          specify a navigation title in your map or ensure that the referenced file is local and can be accessed. <ph
+            conref="DITA-messages-details.xml#errormessages/changeExtension"/>
+          <indexterm>table of contents<indexterm>navigation title</indexterm></indexterm>
+          <indexterm>table of contents<indexterm>DOTX008W</indexterm></indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX009W-extra" conaction="pushreplace">No title was found in the
+          specified topic, so the table of contents will use the indicated fallback value for this topic.
+          <indexterm>table of contents<indexterm>DOTX009W</indexterm></indexterm>
+          <indexterm>table of contents<indexterm>no title</indexterm></indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX010E-extra" conaction="pushreplace">The conref attribute must be a
+          URI reference to an existing DITA element. Please see the topic on <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing"
+            format="html" scope="external">URI-based addressing</xref> in the DITA specification for details on the
+          expected syntax. <ph id="changeExtension">Note that the name of the file in this message may have be changed
+            to use a standard dita topic file extension ('.dita' or '.xml'), instead of the original extension used by
+            the file; it may also include a path to the temporary directory rather than to the original.</ph>
+          <p>If the target element exists in your source file, check to make sure it is not filtered out of the build
+            with a DITAVAL file (which will remove the target before conref processing runs).</p></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX011W-extra" conaction="pushreplace">When pulling content with a
+          conref attribute, you may only pull from a single element, but the target ID appears twice in the referenced
+          topic. <ph conref="DITA-messages-details.xml#errormessages/changeExtension"/></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX012W-extra" conaction="pushreplace">This message is deprecated and
+          should no longer appear in any logs.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX013E-extra" conaction="pushreplace">This may appear if (for example)
+          you have a <xmlelement>ph</xmlelement> element that references another phrase, but that phrase itself contains
+          a reference to the original. This will result in an infinite loop. The toolkit will stop following the conref
+          trail when this is detected; you will need to correct the reference in your source files. <ph
+            conref="DITA-messages-details.xml#errormessages/changeExtension"/></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX014E-extra" conaction="pushreplace">The conref attribute must be a
+          URI reference to a DITA element. Please see the topic on <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing"
+            format="html" scope="external">URI-based addressing</xref> in the DITA specification for details on the
+          expected syntax.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX015E-extra" conaction="pushreplace">The conref attribute must be a
+          URI reference to a DITA element. Please see the topic on <xref
+            href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing"
+            format="html" scope="external">URI-based addressing</xref> in the DITA specification for details on the
+          expected syntax. <ph conref="DITA-messages-details.xml#errormessages/changeExtension"/></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX016W-extra" conaction="pushreplace">This warning is intended to
+          catch instances where a non-DITA format setting unexpectedly cascades to a DITA topic, which will prevent the
+          topic from being processed. To remove this message, set the format attribute directly on the indicated
+          reference. <ph conref="DITA-messages-details.xml#errormessages/changeExtension"/></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX017E-extra" conaction="pushreplace">Found a value such as &lt;xref
+          href="">link text&lt;/xref>. The empty href attribute is not serving a purpose and has caused problems with
+          some tools in the past; you should remove the attribute entirely or specify a value.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX018I-extra" conaction="pushreplace">The type attribute in DITA is
+          intended to describe the type of the target; for example, a reference to a concept topic may use
+          type="concept". Generally, this attribute is optional, and the DITA-OT build will automatically determine the
+          value during processing. In this case, the type attribute lists a more general type than what is actually
+          found. This is not an error but may result in unexpected sorting for links to this topic.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX019W-extra" conaction="pushreplace">The type attribute in DITA is
+          intended to describe the type of the target; for example, a reference to a concept topic may use
+          type="concept". Generally, this attribute is optional, and the DITA-OT build will automatically determine the
+          value during processing. In this case, the specified type value does not match the target, which may cause
+          your links to sort inappropriately.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX020E-extra" conaction="pushreplace">DITA-OT is only able to
+          dynamically retrieve titles when the target is a local (not peer or external) DITA resource.
+        <indexterm start="navtitle">navtitle</indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX021E-extra" conaction="pushreplace">DITA-OT is only able to
+          dynamically retrieve titles when the target is a local DITA resource.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX022W-extra" conaction="pushreplace">The build was unable to get a
+          title from the referenced topic; instead, a navigation title will be created based on the specified
+            <xmlelement>linktext</xmlelement> element inside of <xmlelement>topicmeta</xmlelement>.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX023W-extra" conaction="pushreplace">If the target is a local DITA
+          topic, ensure the reference is correct and the topic is available. Otherwise, provide a navigation title, and
+          ensure the scope and format attributes are set appropriately.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX024E-extra" conaction="pushreplace">DITA-OT is only able to
+          dynamically retrieve titles and link text when the target is a local (not peer or external) DITA
+          resource.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX025E-extra" conaction="pushreplace">DITA-OT is only able to
+          dynamically retrieve titles when the target is a local DITA resource.
+        <indexterm end="navtitle"/></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX026W-extra" conaction="pushreplace">The referenc to this document
+          did not specify any link text for generated map-based links; the navigation title will be used as
+          fallback.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX027W-extra" conaction="pushreplace">The referenced file did not
+          specify any link text for generated map-based links, and no fallback text could be located. Any links
+          generated from this reference will have incorrect link text.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX028E-extra" conaction="pushreplace">The link or cross reference has
+          no target specified and will not generate a link.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX029I-extra" conaction="pushreplace">The type attribute in DITA is
+          intended to describe the type of the target; for example, a reference to a concept topic may use
+          type="concept". Generally, this attribute is optional, and the DITA-OT build will automatically determine the
+          value during processing. In this case, the type attribute lists a more general type than what is actually
+          found. This is not an error but may result in unexpected sorting for links to this topic.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX030W-extra" conaction="pushreplace">The type attribute in DITA is
+          intended to describe the type of the target; for example, a reference to a concept topic may use
+          type="concept". Generally, this attribute is optional, and the DITA-OT build will automatically determine the
+          value during processing. In this case, the specified type value does not match the target, which may cause
+          your links to sort inappropriately.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX031E-extra" conaction="pushreplace">The build attempted to access
+          the specified file in order to retrive a title or short description, but the file could not be found. If the
+          file exists, it is possible that a DITAVAL file was used to remove the file’s contents from the build. Be
+          aware that the path information above may not match the link in your topic.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX032E-extra" conaction="pushreplace">When a link or cross reference
+          does not have content, the build will attempt to pull the target’s title for use as link text. If the target
+          is unavailable, be sure to set the scope attribute to an appropriate value. If the target does not have a
+          title (such as when linking to a paragraph), be sure to provide link text inside the cross
+          reference.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX033E-extra" conaction="pushreplace">An <xmlelement>xref</xmlelement>
+          element specifies type="li", which indicates a link to a list item, but the item number could not be
+          determined to use as link text. Please specify link text inside the reference, or ensure that you are
+          referencing an available list item.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX034E-extra" conaction="pushreplace">The cross reference goes to a
+          list item in an unordered list. The process could not automatically generate link text because the list item
+          is not numbered. Please provide link text within the cross reference.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX035E-extra" conaction="pushreplace">An <xmlelement>xref</xmlelement>
+          element specifies type="fn", which indicates a link to a footnote, but the footnote number could not be
+          determined to use as link text. Please specify link text inside the reference, or ensure that you are
+          referencing an available footnote.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX036E-extra" conaction="pushreplace">An <xmlelement>xref</xmlelement>
+          element specifies type="dlentry", which indicates a link to a definition list entry, but the term could not be
+          located to use as link text. Please specify link text inside the reference, or ensure that you are referencing
+          an available definition list entry</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX037W-extra" conaction="pushreplace">No title was found for the
+          current document, so the HTML output file will set the <xmlelement>title</xmlelement> to "***". This value
+          generally appears in the title bar at the top of a browser.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX038I-extra" conaction="pushreplace">The
+            <xmlelement>object</xmlelement> element in HTML does not support using longdescref for accessibility. To
+          make the object accessible, you may need to add text before or after the element. You may also be able to
+          handle it with a <xmlelement>param</xmlelement> element inside the object.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX039W-extra" conaction="pushreplace">This message is generated when
+          creating draft output in order to help you locate all topics that need to be cleaned up; the cleanup items
+          will appear in your output with styling that makes it stand out. The content will be hidden when the draft
+          parameter is not active.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX040I-extra" conaction="pushreplace">This message is generated when
+          creating draft output in order to help you locate all topics that have draft comments. Each comment will
+          appear in your HTML output; the comments will be hidden when the draft parameter is not active.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX041W-extra" conaction="pushreplace">Because of the way XML and DITA
+          are defined, it is generally not possible to prohibit adding a second title to a section during editing (or to
+          force that title to come first). However, the DITA specification states that only one title should be used in
+          a section. When multiple titles are found, only the first one will appear in the output.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX042I-extra" conaction="pushreplace">If it is important to flag this
+          piece of information, try placing a flag on the block element that contains your phrase. If you just want to
+          have an image next to the phrase, you may place an image directly into the document.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX043I-extra" conaction="pushreplace">DITA-OT is able to remove
+          duplicate links in most cases. However, if two links to the same resource use different attributes or link
+          text, it is possible for them to appear together. For example, if the same link shows up with role="next" and
+          again with no specified role, it may show up as both the "Next topic" link and as a related link. Note that
+          links generated from a <xmlelement>reltable</xmlelement> in a DITA map will have the role attribute set to
+          "friend".
+          <indexterm><xmlelement>reltable</xmlelement><index-see-also>relationship tables</index-see-also></indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX044E-extra" conaction="pushreplace">The
+            <xmlelement>area</xmlelement> element in an image map must provide a link target for the specified area.
+          Please add an <xmlelement>xref</xmlelement> element as a child of <xmlelement>area</xmlelement> and ensure
+          that it specifies a link target.
+        <indexterm>image map</indexterm></stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX045W-extra" conaction="pushreplace">Cross reference text inside the
+            <xmlelement>area</xmlelement> element is used to provide accessibility for screen readers that can identify
+          different areas of an image map. If text cannot be retrieved automatically by referencing a DITA element, it
+          should be specified directly in the cross reference.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX046W-extra" conaction="pushreplace">The specified value was passed
+          as-is through to the <xmlelement>area</xmlelement> element in the HTML.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX047W-extra" conaction="pushreplace">The area element is intended to
+          define a region in an image map; coordinates must be specified in order to define that region.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX048I-extra" conaction="pushreplace">The build will not look for peer
+          or external topics before compiling your CHM file, so they may not be included. If you are referencing an
+          actual HTML file that will not be available, it cannot be included in the project, and you should set the toc
+          attribute to "no" on your topicref element. Otherwise, check to be sure your HTML file was included in the
+          CHM; if it was not, you will need to place it in the correct location with your other output files and
+          recompile.
+          <indexterm>table of contents<indexterm>HTML Help</indexterm></indexterm>
+        </stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX049I-extra" conaction="pushreplace">The PDF, ODT, and RTF output
+          processes cannot automatically convert non-DITA content into DITA in order to merge it with the rest of your
+          content. The referenced items are ignored.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX050W-extra" conaction="pushreplace">Eclipse requires that an ID be
+          specified when creating an Eclipse Help project; the toolkit expects to locate that ID on the root element of
+          your input map.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX052W-extra" conaction="pushreplace">The toolkit is attempting to add
+          generated text, such as the string "Related information" that appears above links. The requested string could
+          not be found in any language. Your output may contain a meaningful string, or it may contain a code that was
+          intended to map to a string. This likely indicates an error in a plug-in or XSL override; either the string
+          was requested incorrectly, or you will need to provide a mapping for the string in all of the languages you
+          require.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX053E-extra" conaction="pushreplace">This will occur if a map
+          references another map, and then that second map (or another further nested map) references the original map.
+          The result is an infinite nesting of maps; please correct the chain of map references to remove circular
+          reference.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX054W-extra" conaction="pushreplace">This will occur when a DITAVAL
+          file contains multiple styling rules that apply to the same element.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX055W-extra" conaction="pushreplace">The "flagit" named template was
+          deprecated in DITA-OT version 1.4, when the OASIS standard formalized the DITAVAL syntax. The template is
+          removed in DITA-OT 1.6. Stylesheets that used this template need to be updated.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX056W-extra" conaction="pushreplace">The build attempted to access
+          the specified file in order to retrive a title or short description, but the file could not be found. If the
+          file exists, it is possible that a DITAVAL file was used to remove the file’s contents from the build. Another
+          possibility is that the file is located outside of the scope of the main input directory, and was not
+          available because the <xref keyref="parameters-base">onlytopic.in.map</xref> parameter was specified. Be aware
+          that the path information above may not match the link in your topic.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX057W-extra" conaction="pushreplace">The link appears to use valid
+          syntax to reference a DITA element, but that element cannot be found. Please verify that the element exists,
+          and is not removed from the build by DITAVAL based filtering.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX058W-extra" conaction="pushreplace">Processing for terms, acronyms,
+          or abbreviated forms will associate the key from the element’s keyref attribute with a glossentry (glossary
+          entry) topic. This message will appear if the key was defined, but was not associated with a glossentry topic.
+          The process will try to use the best available fallback (usually the title of the referenced topic).</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX060W-extra" conaction="pushreplace">Processing for abbreviated form
+          elements will associate the key from the element’s keyref attribute with a glossentry (glossary entry) topic.
+          This message will appear if the key was defined, but was not associated with a glossentry topic. This element
+          is only supported with keys that are associated with glossary topics; the element will not generate any
+          output. Please correct the reference, or use a different element to reference your topic.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX061W-extra" conaction="pushreplace">According to the DITA
+          Specification, references from maps should either go to DITA Maps, DITA Topics, or any non-DITA resource.
+          References below the topic level should only be made from cross references (using
+            <xmlelement>xref</xmlelement> or similar) inside of a topic. For details, see the href attribute description
+          in the OASIS standard’s definition of the <xref
+            href="http://docs.oasis-open.org/dita/v1.2/os/spec/langref/topicref.html" format="html" scope="external"
+            >topicref element</xref>.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX063W-extra" conaction="pushreplace">This will appear when generating
+          PDF or ODT output that includes a link to a local topic, but the referenced topic is not part of the map
+          itself. This will result in a broken link. You should include the topic in your map or remove the link from
+          the build.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX064W-extra" conaction="pushreplace">The copy-to attribute is used to
+          copy a topic over a document that already exists. Please make sure that any copy-to attributes use a unique
+          name so that the copy will not overwrite existing content.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX065W-extra" conaction="pushreplace">Two different topics are copied
+          to the same location using copy-to; as a result, one of these files would be over-written. Only the first
+          instance of this copy-to value will be recognized. Please correct the use of copy-to attributes.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX066W-extra" conaction="pushreplace">This message indicates that your
+          custom XSLT or plug-ins rely on templates that will be removed in an upcoming release. Typically this occurs
+          when a named template has been converted to a mode template; any code that uses the deprecated template should
+          be updated.</stentry>
+      </strow>
+      <strow>
+        <stentry conref="DITA-messages.xml#msgs/DOTX067E-extra" conaction="pushreplace">This PDF build uses generated
+          text, such as the phrase "Related information" (which is generated above many link groups). The toolkit was
+          unable to locate the string <varname>%1</varname> for your specified language, so the string will appear in
+          the default language. This generally indicates that the toolkit’s strings need to be updated to support your
+          language, or that your language setting is incorrect.</stentry>
+      </strow>
+    </simpletable>
+    <section>
+      <title>Additional explanation for messages in the <filepath>org.dita.pdf2</filepath> plugin</title>
+      <simpletable>
+        <strow>
+          <stentry conref="DITA-messages.xml#msgs/PDFJ002E-extra" conaction="pushreplace">The PDF index process relies
+            on pre-defined letter headings when sorting terms. The specified term does not begin with a character that
+            can be mapped to an existing heading. Typically this term would be placed in a "Special characters" group,
+            but the current language did not specify such a group when setting up the index sort process.</stentry>
+        </strow>
+        <strow>
+          <stentry conref="DITA-messages.xml#msgs/PDFJ003I-extra" conaction="pushreplace">The PDF index process relies
+            on pre-defined letter headings when sorting terms. The specified term does not begin with a character that
+            can be mapped to an existing heading, so it has been placed under a heading for terms that begin with
+            special characters such as punctuation. If this term should be sorted under a new or existing letter
+            heading, please open an issue with DITA-OT to correct the sort.</stentry>
+        </strow>
+        <strow>
+          <stentry conref="DITA-messages.xml#msgs/PDFX011E-extra" conaction="pushreplace">Found an
+              <xmlelement>index-see</xmlelement> element as a child of a term that also exists as a standalone index
+            term, or as a term that also uses <xmlelement>index-see-also</xmlelement>. When using
+              <xmlelement>index-see</xmlelement> with an index term, that term should not be used to create page
+            references and should not reference additional terms. Treating the <xmlelement>index-see</xmlelement> as
+              <xmlelement>index-see-also</xmlelement>.</stentry>
+        </strow>
+        <strow>
+          <stentry conref="DITA-messages.xml#msgs/DOTX072I-extra" conaction="pushreplace"><indexterm>navtitle</indexterm></stentry>
+        </strow>
+      </simpletable>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/alternative-input-formats.dita

@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="alternative-authoring-formats">
+  <title>Alternative authoring formats</title>
+  <titlealts>
+    <navtitle>Authoring formats</navtitle>
+  </titlealts>
+  <shortdesc>DITA-OT³ supports several alternative input formats in addition to standard DITA XML, including Markdown
+    and the proposed XDITA, MDITA and HDITA authoring formats currently in development for Lightweight DITA.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm start="lwdita">Lightweight DITA</indexterm> <!-- https://github.com/dita-ot/dita-ot/issues/3318 -->
+        <indexterm>LwDITA<index-see>Lightweight DITA</index-see></indexterm>
+        <indexterm>MDITA<index-see>Lightweight DITA</index-see></indexterm>
+        <indexterm>XDITA<index-see>Lightweight DITA</index-see></indexterm>
+        <indexterm>HDITA<index-see>Lightweight DITA</index-see></indexterm>
+        <indexterm>authoring formats</indexterm>
+        <indexterm>input formats<index-see>authoring formats</index-see></indexterm>
+        <indexterm>formats<index-see>authoring formats</index-see><index-see>transformations</index-see></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/ant.dita

@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="ant">
+  <title>Ant</title>
+  <shortdesc>Ant is a Java-based, open-source tool that is provided by the Apache Foundation. It can be used to declare
+    a sequence of build actions. It is well suited for both development and document builds. The toolkit ships with a
+    copy of Ant.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Ant<indexterm>overview</indexterm></indexterm>
+        <indexterm>build.xml</indexterm>
+        <indexterm>files<indexterm>build.xml</indexterm></indexterm>
+        <indexterm>XSLT<indexterm>Ant</indexterm></indexterm>
+        <indexterm>Java<indexterm>Ant</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>DITA-OT uses Ant to manage the XSLT scripts that are used to perform the various transformation; it also uses Ant
+      to manage intermediate steps that are written in Java. </p>
+    <p>The most important Ant script is the <filepath>build.xml</filepath> file. This script defines and combines common
+      pre-processing and output transformation routines; it also defines the DITA-OT extension points.</p>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/building-output.dita

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="tranforming-dita-content">
+  <title>Building output</title>
+  <shortdesc>You can use the <cmdname>dita</cmdname> command-line tool, Ant, or the Java API to transform DITA content
+    to the various output formats that DITA Open Toolkit supports.</shortdesc>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/building-with-ant.dita

@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="runant" xml:lang="en">
+  <title>Building output using Ant</title>
+  <shortdesc>You can build output by using an Ant build script to provide the DITA-OT parameters.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlatt>default</xmlatt></indexterm>
+        <indexterm>macOS<indexterm>Ant</indexterm></indexterm>
+        <indexterm>Linux<indexterm>Ant</indexterm></indexterm>
+        <indexterm>Windows<indexterm>Ant</indexterm></indexterm>
+        <indexterm>Ant<indexterm>publishing with</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <steps>
+      <step>
+        <cmd conref="../resources/conref-task.dita#ID/open-terminal"/>
+      </step>
+      <step>
+        <cmd>Issue the following command:</cmd>
+        <choicetable frame="topbot" relcolwidth="1* 3*">
+          <chrow platform="linux mac">
+            <choption>Linux or macOS&#xA0;</choption>
+            <chdesc>
+              <cmdname>bin/ant</cmdname>
+              <option>-f</option>
+              <codeph><varname>build-script</varname>
+                <varname>target</varname></codeph>
+            </chdesc>
+          </chrow>
+          <chrow platform="windows">
+            <choption>Windows</choption>
+            <chdesc>
+              <cmdname>bin\ant</cmdname>
+              <option>-f</option>
+              <codeph><varname>build-script</varname>
+                <varname>target</varname></codeph>
+            </chdesc>
+          </chrow>
+        </choicetable>
+        <info> where:
+          <ul>
+            <li><varname>build-script</varname> is name of the Ant build script.</li>
+            <li><varname>target</varname> is an optional switch that specifies the name of the Ant target that you want
+              to run. <p>If you do not specify a target, the value of the <xmlatt>default</xmlatt> attribute for the Ant
+                project is used.</p>
+            </li>
+          </ul></info>
+      </step>
+    </steps>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/creating-an-ant-build-script.dita

@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="creating-an-ant-build-script">
+  <title>Creating an Ant build script</title>
+  <shortdesc>Instead of typing the DITA-OT parameters at the command prompt, you might want to create an Ant build
+    script that contains all of the parameters.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>link</xmlelement></indexterm>
+        <indexterm><xmlatt>name</xmlatt></indexterm>
+        <indexterm><xmlatt>default</xmlatt></indexterm>
+        <indexterm>Ant<indexterm>build script</indexterm></indexterm>
+        <indexterm>relationship tables<indexterm>PDF</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <steps>
+      <step>
+        <cmd>Create an XML file that contains the following content:</cmd>
+        <info>
+          <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version="1.0" encoding="UTF-8" ?>
+&lt;project name="%project-name%" default="%default-target%" basedir=".">
+
+  &lt;property name="dita.dir" location="%path-to-DITA-OT%"/>
+
+  &lt;target name="%target-name%">
+    &lt;ant antfile="${dita.dir}/build.xml">
+      &lt;property name="args.input" value="%DITA-input%"/>
+      &lt;property name="transtype" value="html5"/>
+    &lt;/ant>
+  &lt;/target>
+
+&lt;/project></codeblock>
+        </info>
+        <info>You will replace the placeholder content (indicated by the % signs) with content applicable to your
+          environment.</info>
+      </step>
+      <step>
+        <cmd>Specify project information:</cmd>
+        <substeps>
+          <substep importance="optional">
+            <cmd>Set the value of the <xmlatt>name</xmlatt> attribute to the name of your project.</cmd>
+          </substep>
+          <substep>
+            <cmd>Set the value of the <xmlatt>default</xmlatt> attribute to the name of a target in the build
+              script.</cmd>
+            <info>If the build script is invoked without specifying a target, this target will be run.</info>
+          </substep>
+        </substeps>
+      </step>
+      <step>
+        <cmd>Set the value of the <parmname>dita.dir</parmname> property to the location of the DITA-OT
+          installation.</cmd>
+        <info>This can be a fully qualified path, or you can specify it relative to the location of the Ant build script
+          that you are writing. </info>
+      </step>
+      <step>
+        <cmd>Create the Ant target:</cmd>
+        <substeps>
+          <substep>
+            <cmd>Set the value of the <xmlatt>name</xmlatt> attribute.</cmd>
+          </substep>
+          <substep>
+            <cmd>Specify the value for the <parmname>args.input</parmname> property.</cmd>
+          </substep>
+          <substep>
+            <cmd>Specify the value of the <parmname>transtype</parmname> property.</cmd>
+          </substep>
+        </substeps>
+      </step>
+      <step>
+        <cmd>Save the build script.</cmd>
+      </step>
+    </steps>
+    <example>
+      <p>The following Ant build script generates CHM and PDF output for the sample DITA maps.</p>
+      <p>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/ant_sample/build-chm-pdf.xml"/></codeblock></p>
+      <p>In addition to the mandatory parameters (<parmname>args.input</parmname> and <parmname>transtype</parmname>),
+        the chm and pdf targets each specify some optional parameters:
+        <ul>
+          <li>The <parmname>args.gen.task.lbl</parmname> property is set to YES, which ensures that headings are
+            automatically generated for the sections of task topics.</li>
+          <li>The <parmname>output.dir</parmname> property specifies where DITA-OT writes the output of the
+            transformations.</li>
+        </ul></p>
+      <p>The pdf target also specifies that related links should be generated in the PDF, but only those links that are
+        created by relationship tables and <xmlelement>link</xmlelement> elements.</p>
+      <p>Finally, the all target simply specifies that both the chm and pdf target should be run.</p>
+    </example>
+    <postreq>Another resource for learning about Ant scripts are the files in the <filepath
+        conref="../resources/conref-task.dita#ID/samples-dir"/><filepath>/ant_sample/</filepath> directory. This
+      directory contains sample Ant build files for common output formats, as well as templates that you can use to
+      create your own Ant scripts.</postreq>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/custom-plugins.dita

@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="custom-plugins">
+  <title>Working with plug-ins</title>
+  <shortdesc id="plugins-creating">You can install or create DITA-OT plug-ins to change the default output types in
+    various ways, add entirely new kinds of output formats, or implement DITA topic specializations.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>DITA<indexterm>specializations</indexterm></indexterm>
+        <indexterm start="plugins">plug-ins</indexterm>
+        <indexterm>plug-ins<indexterm>benefits</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>working with</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <conbody>
+
+    <p>A plug-in consists of a directory, typically stored within the <filepath>plugins/</filepath> subdirectory of the
+      DITA-OT installation. Every plug-in is controlled by a file named <filepath>plugin.xml</filepath>, which is
+      located in the root directory of the plug-in.</p>
+
+    <section id="plugin-benefits">
+      <title>Plug-in benefits</title>
+      <p>Plug-ins allow you to extend the toolkit in a way that is consistent, easy-to-share, and possible to preserve
+        through toolkit upgrades.</p>
+      <p>The DITA-OT plug-in mechanism provides the following benefits:</p>
+      <ul>
+        <li>Plug-ins can easily be shared with other users, teams, or companies. Typically, all users need to do is to
+          unzip and run a single installation command. With many builds, even that installation step is automatic.</li>
+        <li>Plug-ins permit overrides or customizations to grow from simple to complex over time, with no increased
+          complexity to the extension mechanism.</li>
+        <li>Plug-ins can be moved from version to version of DITA-OT by reinstalling or copying the directory from one
+          installation to another. There is no need to re-integrate code based on updates to DITA-OT core
+          processing.</li>
+        <li>Plug-ins can build upon each other. If you like a plug-in, simply install that plug-in, and then create your
+          own plug-in that builds on top of it. The two plug-ins can then be distributed to your team as a unit, or you
+          can share your own extensions with the original provider.</li>
+      </ul>
+    </section>
+
+    <section>
+      <title>Plug-in details</title>
+      <p>The following topics provide additional information on working with plug-ins and creating your own.</p>
+    </section>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/customization.ditamap

@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <title>Customizing/Extending DITA-OT</title>
+
+  <mapref href="html-customization.ditamap"/>
+  <mapref href="pdf-customization.ditamap"/>
+  <mapref href="plug-ins.ditamap"/>
+  <mapref href="../extension-points/extension-points.ditamap"/>
+  <mapref href="migration.ditamap"/>
+  <mapref href="globalizing.ditamap"/>
+  <topicref keyref="rebuilding-docs"/>
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/customizing.dita

@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="customizing" xml:lang="en-US">
+  <title>Customizing DITA Open Toolkit</title>
+  <titlealts>
+    <navtitle>Customizing DITA-OT</navtitle>
+  </titlealts>
+  <shortdesc>There are several ways to customize and extend the toolkit. You can adjust various aspects of the default
+    output by setting parameters or using custom stylesheets. For more complex customizations, use custom DITA-OT
+    plug-ins to override other parts of processing.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>plug-ins<indexterm>best practices</indexterm></indexterm>
+        <indexterm>upgrading<indexterm>default plug-ins</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section>
+      <p>A single XSL file can be used as an override by passing it in as a parameter. For example, when building XHTML
+        content, the XSL parameter allows users to specify a single local XSL file (inside or outside of the toolkit)
+        that is called in place of the default XHTML code. Typically, this code imports the default processing code, and
+        overrides a couple of processing routines. This approach is best when the override is very minimal, or when the
+        style varies from build to build. However, any extension made with this sort of override is also possible with a
+        plug-in.</p>
+      <p>Creating a plug-in can be very simple to very complex, and is generally the best method for changing or
+        extending the toolkit. Plug-ins can be used to accomplish almost any modification that is needed for toolkit
+        processing, from minor style tweaks to extensive, complicated new output formats.</p>
+      <p>Editing DITA-OT code directly is strongly discouraged. Modifying the code directly significantly increases the
+        work and risk involved with future upgrades. It is also likely that such modifications will break plug-ins
+        provided by others, limiting the functions available to the toolkit.</p>
+      <note type="warning">Any changes made directly in the code would be overwritten when upgrading to newer versions
+        of DITA-OT, so users that have customized their toolkit installation in this way are often “stuck” on older
+        versions of the toolkit and unable to take advantage of improvements in recent versions of DITA-OT.</note>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/determining-version-of-ditaot.dita

@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="determining-version-of-dita-ot">
+  <title>Checking the DITA-OT version number</title>
+  <titlealts>
+    <navtitle>Checking the version</navtitle>
+  </titlealts>
+  <shortdesc>You can determine the DITA Open Toolkit version number from a command prompt.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>macOS<indexterm>DITA-OT version</indexterm></indexterm>
+        <indexterm>Linux<indexterm>DITA-OT version</indexterm></indexterm>
+        <indexterm>Windows<indexterm>DITA-OT version</indexterm></indexterm>
+        <indexterm>command line<indexterm>checking DITA-OT version</indexterm></indexterm>
+        <indexterm>installing<indexterm>check current version</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <steps>
+      <step>
+        <cmd conref="../resources/conref-task.dita#ID/open-terminal"/>
+      </step>
+      <step>
+        <cmd>Issue the following command:</cmd>
+        <choicetable frame="topbot" relcolwidth="1* 3*">
+          <chrow platform="linux mac">
+            <choption>Linux or macOS&#xA0;</choption>
+            <chdesc>
+              <cmdname>bin/dita</cmdname>
+              <parmname>--version</parmname>
+            </chdesc>
+          </chrow>
+          <chrow platform="windows">
+            <choption>Windows</choption>
+            <chdesc>
+              <cmdname>bin\dita</cmdname>
+              <parmname>--version</parmname>
+            </chdesc>
+          </chrow>
+        </choicetable>
+        <info>
+          <note conref="../resources/conref-task.dita#ID/dita-in-path"/>
+        </info>
+      </step>
+    </steps>
+    <result>
+      <p>The DITA-OT version number appears on the console:</p>
+      <codeblock><systemoutput>DITA-OT version <keyword keyref="maintenance-version"/></systemoutput></codeblock>
+    </result>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita-and-dita-ot-resources.dita

@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="ID">
+  <title>DITA and DITA-OT resources</title>
+  <titlealts>
+    <navtitle>Resources</navtitle>
+  </titlealts>
+  <shortdesc>In addition to the DITA Open Toolkit documentation, there are other resources about DITA and DITA-OT that
+    you might find helpful.</shortdesc>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita-command-help.dita

@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="accessing-help-from-the-cl-tool">
+  <title>Accessing help for the dita command</title>
+  <shortdesc>You can access a list of supported parameters for the <cmdname>dita</cmdname> command by passing the
+      <parmname>--help</parmname> option on the command line.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>macOS<indexterm>help</indexterm></indexterm>
+        <indexterm>Linux<indexterm>help</indexterm></indexterm>
+        <indexterm>Windows<indexterm>help</indexterm></indexterm>
+        <indexterm>command line<indexterm>help</indexterm></indexterm>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>help</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <steps>
+      <step>
+        <cmd conref="../resources/conref-task.dita#ID/open-terminal"/>
+      </step>
+      <step>
+        <cmd>Issue the following command:</cmd>
+        <choicetable frame="topbot" relcolwidth="1* 3*">
+          <chrow platform="linux mac">
+            <choption>Linux or macOS&#xA0;</choption>
+            <chdesc>
+              <cmdname>bin/dita</cmdname>
+              <parmname>--help</parmname>
+            </chdesc>
+          </chrow>
+          <chrow platform="windows">
+            <choption>Windows</choption>
+            <chdesc>
+              <cmdname>bin\dita</cmdname>
+              <parmname>--help</parmname>
+            </chdesc>
+          </chrow>
+        </choicetable>
+        <info>
+          <note conref="../resources/conref-task.dita#ID/dita-in-path"/>
+        </info>
+      </step>
+    </steps>
+    <result>
+      <p>A brief description of the supported parameters appears in the command-line window.</p>
+    </result>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita-resources.ditamap

@@ -0,0 +1,52 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <title>DITA and DITA-OT resources</title>
+
+  <topicref format="html" href="https://www.dita-ot.org" scope="external">
+    <topicmeta>
+      <linktext>DITA-OT project website: dita-ot.org</linktext>
+      <shortdesc>The DITA-OT project website at dita-ot.org provides information about the latest toolkit releases,
+        including download links, release notes, and documentation for recent DITA-OT versions.</shortdesc>
+    </topicmeta>
+  </topicref>
+  <topicref format="html" href="http://groups.yahoo.com/group/dita-users/" scope="external">
+    <topicmeta>
+      <linktext>Yahoo! dita-users group</linktext>
+      <shortdesc>The original DITA list-serv is a vital resource for the DITA community. People post regularly, both
+        asking for and offering help. While the archived messages can be difficult to search, this is a treasure trove
+        of information.</shortdesc>
+    </topicmeta>
+  </topicref>
+  <topicref format="html" href="https://groups.google.com/d/forum/dita-ot-users" scope="external">
+    <topicmeta>
+      <linktext>DITA-OT Users Google Group</linktext>
+      <shortdesc>General interest DITA-OT product forum, for questions on any aspect of the toolkit — from installation
+        and getting started to questions about specific overrides, plug-ins, and customizations.</shortdesc>
+    </topicmeta>
+  </topicref>
+  <topicref format="html" href="https://dita-ot.slack.com" scope="external">
+    <topicmeta>
+      <linktext>DITA-OT Development Slack team</linktext>
+      <shortdesc>Forum for discussion related to DITA-OT development and design. Topics in this forum are more technical
+        in nature, covering upcoming design or code changes. To request an invitation and join in the discussion, visit
+          <xref href="http://slack.dita-ot.org" format="html" scope="external">slack.dita-ot.org</xref>.</shortdesc>
+    </topicmeta>
+  </topicref>
+  <topicref format="html" href="http://www.oasis-open.org/committees/dita/" scope="external">
+    <topicmeta>
+      <linktext>Home page for the DITA Technical Committee</linktext>
+      <shortdesc>The OASIS DITA Technical Committee develops the DITA standard.</shortdesc>
+    </topicmeta>
+  </topicref>
+  <topicref format="html" href="http://dita-archive.xml.org/wiki/the-dita-open-toolkit" scope="external">
+    <topicmeta>
+      <linktext>DITA-OT project archive</linktext>
+      <shortdesc>The DITA-OT project archive at dita-archive.xml.org provides news about earlier toolkit releases, and
+        release notes for legacy versions.</shortdesc>
+    </topicmeta>
+  </topicref>
+  <topicref keyref="books"/>
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2dita.dita

@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="normalized-dita">
+  <title>Normalized DITA</title>
+  <shortdesc>The <codeph>dita</codeph> transformation generates normalized topics and maps from DITA input. The
+    normalized output includes the results of DITA Open Toolkit pre-processing operations, which resolve map references,
+    keys, content references, code references and push metadata back and forth between maps and topics.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>normalized DITA</indexterm></indexterm>
+        <indexterm>transformations<indexterm>normalized DITA</indexterm></indexterm>
+        <indexterm>DITA<indexterm>normalized</indexterm></indexterm>
+        <indexterm>metadata<indexterm>map</indexterm></indexterm>
+        <indexterm>metadata<indexterm>topic</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>dita2dita</indexterm></indexterm>
+        <indexterm>dita2dita</indexterm>
+        <indexterm>relationship tables<indexterm>normalized DITA</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <body>
+    <p>In comparison to the source DITA files, the normalized DITA files are modified in the following ways:</p>
+    <ul>
+      <li>References from one DITA map to another are resolved</li>
+      <li>Map-based links, such as those generated by map hierarchy and relationship tables, are added to the
+        topics.</li>
+      <li>Link text is resolved.</li>
+      <li>Map attributes that cascade are made explicit on child elements.</li>
+      <li>Map metadata such as index entries and copyrights are pushed into topics.</li>
+      <li>Topic metadata such as navigation titles, link text and short descriptions are pulled from topics into the
+        map.</li>
+      <li>XML comments are removed.</li>
+    </ul>
+    <section id="applications">
+      <title>Applications</title>
+      <p>Normalized output may be useful in situations where post-processing of DITA content is required, but the
+        downstream systems are limited in their ability to resolve DITA references.</p></section>
+    <section id="generating-normalized-dita-output">
+      <title>Generating normalized DITA output</title>
+      <p>Run the <cmdname>dita</cmdname> command and set the value of the output <parmname>--format</parmname> option to
+          <option>dita</option>:</p><codeblock xml:space="preserve"><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>dita</option></codeblock>
+      <p>where:</p>
+      <ul>
+        <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+          conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+      </ul>
+    </section>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2eclipsehelp.dita

@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="dita2eclipsehelp" xml:lang="en-US">
+  <title>Eclipse help</title>
+  <shortdesc>The <option>eclipsehelp</option> transformation generates XHTML output, CSS files, and the control files
+    that are needed for Eclipse help.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>transformations<indexterm>Eclipse Help</indexterm></indexterm>
+        <indexterm>Eclipse Help<index-see-also>transformations</index-see-also></indexterm>
+        <indexterm>plug-ins<indexterm>dita2eclipsehelp</indexterm></indexterm>
+        <indexterm>dita2eclipsehelp</indexterm>
+        <indexterm>CSS<indexterm>Eclipse Help</indexterm></indexterm>
+        <indexterm>table of contents<indexterm>Eclipse Help</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>In addition to the XHTML output and CSS files, this transformation returns the following files, where
+        <varname>mapname</varname> is the name of the master DITA map.</p>
+    <simpletable outputclass="table-hover" frame="all" relcolwidth="2* 3*">
+      <sthead>
+        <stentry>File name</stentry>
+        <stentry>Description</stentry>
+      </sthead>
+      <strow>
+        <stentry><filepath>plugin.xml</filepath></stentry>
+        <stentry>Control file for the Eclipse plug-in</stentry>
+      </strow>
+      <strow>
+        <stentry><filepath><varname>mapname</varname>.xml</filepath></stentry>
+        <stentry>Table of contents</stentry>
+      </strow>
+      <strow>
+        <stentry><filepath>index.xml</filepath></stentry>
+        <stentry>Index file</stentry>
+      </strow>
+      <strow>
+        <stentry><filepath>plugin.properties</filepath></stentry>
+        <stentry/>
+      </strow>
+      <strow>
+        <stentry><filepath>META-INF/MANIFEST.MF</filepath></stentry>
+        <stentry/>
+      </strow>
+    </simpletable>
+    <p>To run the Eclipse help transformation, set the <parmname>transtype</parmname> parameter to
+        <option>eclipsehelp</option>, or pass the <parmname>--format</parmname>=<option>eclipsehelp</option> option to
+      the <cmdname>dita</cmdname> command line.</p>
+    <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>eclipsehelp</option></codeblock>
+    <p>where:</p>
+    <ul>
+      <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+        conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+    </ul>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2html5.dita

@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="dita2html5" xml:lang="en">
+  <title>HTML5</title>
+  <shortdesc>The <option>html5</option> transformation generates HTML5 output and a table of contents (TOC)
+    file.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>nav</xmlelement></indexterm>
+        <indexterm>languages<indexterm>right-to-left</indexterm></indexterm>
+        <indexterm>HTML<index-see-also>HTML5</index-see-also></indexterm>
+        <indexterm>HTML5<index-see-also>transformations</index-see-also></indexterm>
+        <indexterm>transformations<indexterm>HTML5</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>dita2html5</indexterm></indexterm>
+        <indexterm>dita2html5</indexterm>
+        <indexterm>CSS<indexterm>HTML5</indexterm></indexterm>
+        <indexterm>HTML5<indexterm>CSS</indexterm></indexterm>
+        <indexterm>table of contents<indexterm>HTML5</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>The HTML5 output is always associated with the default DITA-OT CSS file (<filepath>commonltr.css</filepath> or
+        <filepath>commonrtl.css</filepath> for right-to-left languages). You can use toolkit parameters to add a custom
+      style sheet that overrides the default styles, or generate a <xmlelement>nav</xmlelement> element with a
+      navigation TOC in topic pages.</p>
+    <p>To run the HTML5 transformation, set the <parmname>transtype</parmname> parameter to <option>html5</option>, or
+      pass the <parmname>--format</parmname>=<option>html5</option> option to the <cmdname>dita</cmdname> command
+      line.</p>
+    <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>html5</option></codeblock>
+    <p>where:</p>
+    <ul>
+      <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+        conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+    </ul>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2htmlhelp.dita

@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="dita2htmlhelp" xml:lang="en-US">
+  <title>HTML Help</title>
+  <shortdesc>The <option>htmlhelp</option> transformation generates HTML output, CSS files, and the control files that
+    are needed to produce a Microsoft Compiled HTML Help (.chm) file.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>transformations<indexterm>HTML Help</indexterm></indexterm>
+        <indexterm>HTML Help<index-see-also>transformations</index-see-also></indexterm>
+        <indexterm>CHM<index-see>HTML Help</index-see></indexterm>
+        <indexterm>Microsoft HTML Help Workshop</indexterm>
+        <indexterm>.hhc</indexterm>
+        <indexterm>.hhk</indexterm>
+        <indexterm>.hhp</indexterm>
+        <indexterm>plug-ins<indexterm>dita2htmlhelp</indexterm></indexterm>
+        <indexterm>dita2htmlhelp</indexterm>
+        <indexterm>CSS<indexterm>HTML Help</indexterm></indexterm>
+        <indexterm>index<indexterm>HTML Help</indexterm></indexterm>
+        <indexterm>table of contents<indexterm>HTML Help</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>In addition to the HTML output and CSS files, this transformation returns the following files, where
+        <varname>mapname</varname> is the name of the master DITA map.</p>
+    <simpletable outputclass="table-hover" frame="all" relcolwidth="2* 3*">
+      <sthead>
+        <stentry>File name</stentry>
+        <stentry>Description</stentry>
+      </sthead>
+      <strow>
+        <stentry><filepath><varname>mapname</varname>.hhc</filepath></stentry>
+        <stentry>Table of contents</stentry>
+      </strow>
+      <strow>
+        <stentry><filepath><varname>mapname</varname>.hhk</filepath></stentry>
+        <stentry>Sorted index</stentry>
+      </strow>
+      <strow>
+        <stentry><filepath><varname>mapname</varname>.hhp</filepath></stentry>
+        <stentry>HTML Help project file</stentry>
+      </strow>
+      <strow>
+        <stentry><filepath><varname>mapname</varname>.chm</filepath></stentry>
+        <stentry>
+          <p>Compiled HTML Help file</p>
+          <note>The compiled file is only generated if the HTML Help Workshop is installed on the build system.</note>
+        </stentry>
+      </strow>
+    </simpletable>
+    <p>To run the HTML Help transformation, set the <parmname>transtype</parmname> parameter to
+        <option>htmlhelp</option>, or pass the <parmname>--format</parmname>=<option>htmlhelp</option> option to the
+        <cmdname>dita</cmdname> command line.</p>
+    <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>htmlhelp</option></codeblock>
+    <p>where:</p>
+    <ul>
+      <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+        conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+    </ul>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2markdown.dita

@@ -0,0 +1,51 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="markdown">
+  <title>Markdown</title>
+  <shortdesc>Along with Markdown input, DITA-OT now provides three new transformation types to convert DITA content to
+    Markdown, including the original syntax, GitHub-Flavored Markdown, and GitBook.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Markdown</indexterm>
+        <indexterm>transformations<indexterm>Markdown</indexterm></indexterm>
+        <indexterm>GitHub-Flavored Markdown</indexterm>
+        <indexterm>GitBook</indexterm>
+        <indexterm>plug-ins<indexterm>dita2markdown</indexterm></indexterm>
+        <indexterm>dita2markdown</indexterm>
+        <indexterm>table of contents<indexterm>Markdown</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <body>
+    <p>The new output formats can be used to feed DITA content into Markdown-based publishing systems or other workflows
+      that lack the ability to process DITA XML.</p>
+    <section id="generating-markdown-output">
+      <title>Generating Markdown output</title>
+      <p>Markdown output can be generated by passing one of the following transformation types to the dita command with
+        the <parmname>--format</parmname> option:</p>
+      <ul>
+        <li>
+          <p>To publish Markdown DITA files, use the <option>markdown</option> transtype.</p></li>
+        <li>
+          <p>To generate
+            <xref keyref="gfm-spec"/> files, use the <option>markdown_github</option> transtype.</p></li>
+        <li>
+          <p>To publish GitHub-Flavored Markdown and generate a <filepath>SUMMARY.md</filepath> table of contents file
+            for publication via
+            <xref format="html" href="https://www.gitbook.com" scope="external">GitBook</xref>, use the
+              <option>markdown_gitbook</option> transtype.</p></li>
+      </ul>
+      <p>Run the <cmdname>dita</cmdname> command and set the value of the output <parmname>--format</parmname> option to
+        the desired format, for example:</p>
+      <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>markdown</option></codeblock>
+      <p>where:</p>
+      <ul>
+        <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+          conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+      </ul></section>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2pdf.dita

@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="dita2pdf" xml:lang="en-US">
+  <title>PDF</title>
+  <shortdesc>The <option>pdf</option> transformation generates output in Portable Document Format.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>PDF<index-see-also>transformations</index-see-also></indexterm>
+        <indexterm>transformations<indexterm>PDF</indexterm></indexterm>
+        <indexterm>PDF<indexterm>plug-in, history of</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>dita2pdf</indexterm></indexterm>
+        <indexterm>dita2pdf</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>This transformation was originally created as a plug-in and maintained outside of the main toolkit code. It was
+      created as a more robust alternative to the demo PDF transformation in the original toolkit, and thus was known as
+      PDF2. The plug-in was bundled into the default toolkit distribution with release 1.4.3.</p>
+    <p>To run the PDF transformation, set the <parmname>transtype</parmname> parameter to <option>pdf</option>, or pass
+      the <parmname>--format</parmname>=<option>pdf</option> option to the <cmdname>dita</cmdname> command line.</p>
+    <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>pdf</option></codeblock>
+    <p>where:</p>
+    <ul>
+      <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+        conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+    </ul>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2tocjs.dita

@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="dita2tocjs" xml:lang="en-US">
+  <title>TocJS</title>
+  <shortdesc>The <option>tocjs</option> transformation generates XHTML output, a frameset, and a JavaScript-based table
+    of contents with expandable and collapsible entries. The transformation was originally created by Shawn McKenzie as
+    a plug-in and was added to the default distribution in DITA-OT release 1.5.4.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>transformations<indexterm>TocJS</indexterm></indexterm>
+        <indexterm>TocJS<index-see-also>transformations</index-see-also></indexterm>
+        <indexterm>XHTML</indexterm>
+        <indexterm>plug-ins<indexterm>dita2tocjs</indexterm></indexterm>
+        <indexterm>dita2tocjs</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>The <option>tocjs</option> transformation was updated so that it produces XHTML output and uses a default
+      frameset.</p>
+    <p>To run the TocJS transformation, set the <parmname>transtype</parmname> parameter to <option>tocjs</option>, or
+      pass the <parmname>--format</parmname>=<option>tocjs</option> option to the <cmdname>dita</cmdname> command
+      line.</p>
+    <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>tocjs</option></codeblock>
+    <p>where:</p>
+    <ul>
+      <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+        conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+    </ul>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2troff.dita

@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="dita2troff" xml:lang="en-US">
+  <title>troff</title>
+  <shortdesc>The <option>troff</option> transformation produces output for use with the troff viewer on Unix-style
+    platforms, particularly for programs such as the man page viewer.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>tables<indexterm><xmlelement>table</xmlelement></indexterm></indexterm>
+        <indexterm><xmlelement>simpletable</xmlelement></indexterm>
+        <indexterm>UNIX</indexterm>
+        <indexterm>transformations<indexterm>troff</indexterm></indexterm>
+        <indexterm>troff<index-see-also>transformations</index-see-also></indexterm>
+        <indexterm>plug-ins<indexterm>dita2troff</indexterm></indexterm>
+        <indexterm>dita2troff</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>Each DITA topic generally produces one troff output file. The <option>troff</option> transformation supports most
+      common DITA structures, but it does not support <xmlelement>table</xmlelement> or
+        <xmlelement>simpletable</xmlelement> elements. Most testing of troff output was performed using the Cygwin Linux
+      emulator.</p>
+    <p>To run the troff transformation, set the <parmname>transtype</parmname> parameter to <option>troff</option>, or
+      pass the <parmname>--format</parmname>=<option>troff</option> option to the <cmdname>dita</cmdname> command
+      line.</p>
+    <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>troff</option></codeblock>
+    <p>where:</p>
+    <ul>
+      <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+        conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+    </ul>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/dita2xhtml.dita

@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="dita2xhtml" xml:lang="en-US">
+  <title>XHTML</title>
+  <shortdesc>The <option>xhtml</option> transformation generates XHTML output and a table of contents (TOC) file. This
+    was the first transformation created for DITA Open Toolkit, and originally served as the basis for all HTML-based
+    transformations.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>languages<indexterm>right-to-left</indexterm></indexterm>
+        <indexterm>transformations<indexterm>XHTML</indexterm></indexterm>
+        <indexterm>XHTML<index-see-also>transformations</index-see-also></indexterm>
+        <indexterm>HTML</indexterm>
+        <indexterm>plug-ins<indexterm>dita2xhtml</indexterm></indexterm>
+        <indexterm>dita2xhtml</indexterm>
+        <indexterm>CSS<indexterm>XHTML</indexterm></indexterm>
+        <indexterm>table of contents<indexterm>XHTML</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>The XHTML output is always associated with the default DITA-OT CSS file (<filepath>commonltr.css</filepath> or
+        <filepath>commonrtl.css</filepath> for right-to-left languages). You can use toolkit parameters to add a custom
+      style sheet to override the default styles.</p>
+    <p>To run the XHTML transformation, set the <parmname>transtype</parmname> parameter to <option>xhtml</option>, or
+      pass the <parmname>--format</parmname>=<option>xhtml</option> option to the <cmdname>dita</cmdname> command
+      line.</p>
+    <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>input-file</varname> <parmname>--format</parmname>=<option>xhtml</option></codeblock>
+    <p>where:</p>
+    <ul>
+      <li conref="../resources/conref-task.dita#ID/novice-variables-1"
+        conrefend="../resources/conref-task.dita#ID/novice-variables-2"/>
+    </ul>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/enabling-debug-mode.dita

@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="t-enabling-debug-mode">
+  <title>Enabling debug mode</title>
+  <shortdesc>When the debug mode is enabled, additional diagnostic information is written to the log file. This
+    information, which includes environment variables and stack trace data, can help you determine the root cause of a
+    problem.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>property</xmlelement></indexterm>
+        <indexterm>command line<indexterm>debugging</indexterm></indexterm>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>debugging</indexterm></indexterm>
+        <indexterm>debugging<indexterm>args.debug</indexterm></indexterm>
+        <indexterm>environment variables</indexterm>
+        <indexterm>stack trace</indexterm>
+        <indexterm>args.debug</indexterm>
+        <indexterm>Ant<indexterm>args.debug</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <steps>
+      <step>
+        <cmd>From the command prompt, add the following parameters:</cmd>
+        <choicetable>
+          <chhead>
+            <choptionhd>Application</choptionhd>
+            <chdeschd>Parameters</chdeschd>
+          </chhead>
+          <chrow>
+            <choption><cmdname>dita</cmdname> command</choption>
+            <chdesc><parmname>--debug</parmname>,
+              <parmname>-debug</parmname>, or
+              <parmname>-d</parmname></chdesc>
+          </chrow>
+          <chrow>
+            <choption>Ant</choption>
+            <chdesc><codeph>-v -Dargs.debug=yes</codeph></chdesc>
+          </chrow>
+          <!--<chrow importance="deprecated">
+            <choption>Command-line tool</choption>
+            <chdesc><codeph>/d</codeph> or <codeph>-debug</codeph></chdesc>
+          </chrow>-->
+        </choicetable>
+        <info>
+          <p>You also can add a <xmlelement>property</xmlelement> element to an Ant target in your build file, for
+            example: <codeblock outputclass="language-xml">&lt;property name="args.debug" value="yes"/></codeblock></p></info>
+      </step>
+    </steps>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/globalization-languages.dita

@@ -0,0 +1,330 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="dita-globalization-languages" xml:lang="en-US">
+  <title>Supported languages</title>
+  <shortdesc>The following languages are supported for all PDF, XHTML, and HTML5-based transformation types.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlatt>xml:lang</xmlatt></indexterm>
+        <indexterm>Arabic</indexterm>
+        <indexterm>Bosnian</indexterm>
+        <indexterm>Belarusian</indexterm>
+        <indexterm>Bulgarian</indexterm>
+        <indexterm>Catalan</indexterm>
+        <indexterm>Chinese</indexterm>
+        <indexterm>Croatian</indexterm>
+        <indexterm>Czech</indexterm>
+        <indexterm>Danish</indexterm>
+        <indexterm>Dutch</indexterm>
+        <indexterm>English</indexterm>
+        <indexterm>Estonian</indexterm>
+        <indexterm>Finnish</indexterm>
+        <indexterm>French</indexterm>
+        <indexterm>German</indexterm>
+        <indexterm>Greek</indexterm>
+        <indexterm>Hebrew</indexterm>
+        <indexterm>Hungarian</indexterm>
+        <indexterm>Hindi</indexterm>
+        <indexterm>Icelandic</indexterm>
+        <indexterm>Indonesian</indexterm>
+        <indexterm>Italian</indexterm>
+        <indexterm>Japanese</indexterm>
+        <indexterm>Kazakh</indexterm>
+        <indexterm>Korean</indexterm>
+        <indexterm>Latvian</indexterm>
+        <indexterm>Lithuanian</indexterm>
+        <indexterm>Malay</indexterm>
+        <indexterm>Montenegrin</indexterm>
+        <indexterm>Norwegian</indexterm>
+        <indexterm>Polish</indexterm>
+        <indexterm>Portuguese</indexterm>
+        <indexterm>Romanian</indexterm>
+        <indexterm>Russian</indexterm>
+        <indexterm>Serbian</indexterm>
+        <indexterm>Slovak</indexterm>
+        <indexterm>Slovenian</indexterm>
+        <indexterm>Spanish</indexterm>
+        <indexterm>Swedish</indexterm>
+        <indexterm>Thai</indexterm>
+        <indexterm>Turkish</indexterm>
+        <indexterm>Ukrainian</indexterm>
+        <indexterm>Urdu</indexterm>
+        <indexterm>Vietnamese</indexterm>
+        <indexterm>languages<indexterm>supported, list of</indexterm></indexterm>
+        <indexterm>language codes</indexterm>
+        <indexterm>strings</indexterm>
+        <indexterm>generated text</indexterm>
+        <indexterm>index<indexterm>sorting</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <refsyn>
+      <note>While language codes listed below use the conventional capitalization style of "aa-BB" and "aa-Script-BB",
+        DITA-OT processing is not case sensitive when reading these values from the <xmlatt>xml:lang</xmlatt>
+        attribute.</note>
+    </refsyn>
+    <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+      <title>Supported languages</title>
+      <tgroup cols="3">
+        <colspec colwidth="3*" colname="language"/>
+        <colspec colwidth="2*" colname="code"/>
+        <colspec colwidth="5*" colname="notes"/>
+        <thead>
+          <row>
+            <entry>Language</entry>
+            <entry>Language&#xA0;code</entry>
+            <entry>Notes</entry>
+          </row>
+        </thead>
+        <tbody>
+          <row>
+            <entry><ph xml:lang="ar">العربية</ph> (Arabic)</entry>
+            <entry>ar or ar-EG</entry>
+            <entry>Defaults to right-to-left presentation.</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="be">Беларуская</ph> (Belarusian)</entry>
+            <entry>be or be-BY</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="bs">Bosanski</ph> (Bosnian)</entry>
+            <entry>bs or bs-BA</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="bg">Български</ph> (Bulgarian)</entry>
+            <entry>bg or bg-BG</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="ca">Català</ph> (Catalan)</entry>
+            <entry>ca-ES</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="zh-CN">简体中文</ph> (Simplified Chinese)</entry>
+            <entry>zh-CN or zh-Hans</entry>
+            <entry>PDF index is not properly collated by default.</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="zh-TW">繁體中文</ph> (Traditional Chinese)</entry>
+            <entry>zh-TW or zh-Hant</entry>
+            <entry>PDF index is not properly collated by default.</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="hr">Hrvatski</ph> (Croatian)</entry>
+            <entry>hr or hr-HR</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="cs">Čeština</ph> (Czech)</entry>
+            <entry>cs or cs-CZ</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="da">Dansk</ph> (Danish)</entry>
+            <entry>da or da-DK</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="nl">Nederlands</ph> (Dutch)</entry>
+            <entry>nl or nl-NL</entry>
+            <entry>Subset of generated text also available for Belgian Dutch (nl-BE)</entry>
+          </row>
+          <row>
+            <entry>English (US)</entry>
+            <entry>en or en-US</entry>
+            <entry>Subset of generated text also available for British English (en-GB) and Canadian English
+              (en-CA)</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="et">Eesti</ph> (Estonian)</entry>
+            <entry>et or et-EE</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="fi">Suomi</ph> (Finnish)</entry>
+            <entry>fi or fi-FI</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="fr">Français</ph> (French)</entry>
+            <entry>fr or fr-FR</entry>
+            <entry>Subset of generated text also available for Belgian French (fr-BE), Canadian French (fr-CA), and
+              Swiss French (fr-CH)</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="de">Deutsch</ph> (German)</entry>
+            <entry>de or de-DE</entry>
+            <entry>Subset of generated text also available for Swiss German (de-CH)</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="el">Ελληνικά</ph> (Greek)</entry>
+            <entry>el or el-GR</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="he">עברית</ph> (Hebrew)</entry>
+            <entry>he or he-IL</entry>
+            <entry>Defaults to right-to-left presentation.</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="hi">हिन्दी</ph> (Hindi)</entry>
+            <entry>hi or hi-HI</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="hu">Magyar</ph> (Hungarian)</entry>
+            <entry>hu or hu-HU</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="is">Íslenska</ph> (Icelandic)</entry>
+            <entry>is or is-IS</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="id">Bahasa Indonesia</ph> (Indonesian)</entry>
+            <entry>id or id-ID</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="it">Italiano</ph> (Italian)</entry>
+            <entry>it or it-IT</entry>
+            <entry>Subset of generated text also available for Swiss Italian (it-CH)</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="ja">日本語</ph> (Japanese)</entry>
+            <entry>ja or ja-JP</entry>
+            <entry>PDF index is not properly collated by default.</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="kk">Қазақша</ph> (Kazakh)</entry>
+            <entry>kk or kk-KZ</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="ko">한국어</ph> (Korean)</entry>
+            <entry>ko or ko-KR</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="lv">Latviešu</ph> (Latvian)</entry>
+            <entry>lv or lv-LV</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="lt">Lietuvių</ph> (Lithuanian)</entry>
+            <entry>lt or lt-LT</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="mk">Македонски</ph> (Macedonian)</entry>
+            <entry>mk or mk-MK</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="ms">Bahasa Melayu</ph> (Malay)</entry>
+            <entry>ms or ms-MY</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="sr-Latn-ME">Crnogorski</ph> (Montenegrin)</entry>
+            <entry>sr-Latn-ME</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="no">Norsk</ph> (Norwegian)</entry>
+            <entry>no or no-NO</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="pl">Polski</ph> (Polish)</entry>
+            <entry>pl or pl-PL</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="pt">Português</ph> (Portuguese)</entry>
+            <entry>pt or pt-PT</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="pt-BR">Português do Brasil</ph> (Brazilian Portuguese)</entry>
+            <entry>pt-BR</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="ro">Română</ph> (Romanian)</entry>
+            <entry>ro or ro-RO</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="ru">Русский</ph> (Russian)</entry>
+            <entry>ru or ru-RU</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="sr">Српски</ph> (Serbian - Cyrillic script)</entry>
+            <entry>sr, sr-CS, sr-RS, or sr-SP</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="sr-Latn-RS">Srpski</ph> (Serbian - Latin script)</entry>
+            <entry>sr-Latn-RS</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="sk">Slovenčina</ph> (Slovak)</entry>
+            <entry>sk or sk-SK</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="sl">Slovenščina</ph> (Slovenian)</entry>
+            <entry>sl or sl-SI</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="es">Español</ph> (Spanish)</entry>
+            <entry>es or es-ES</entry>
+            <entry>Also supported using es-419 (Latin American Spanish).</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="sv">Svenska</ph> (Swedish)</entry>
+            <entry>sv or sv-SE</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="th">ภาษาไทย</ph> (Thai)</entry>
+            <entry>th or th-TH</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="tr">Türkçe</ph> (Turkish)</entry>
+            <entry>tr or tr-TR</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="uk">Українська</ph> (Ukrainian)</entry>
+            <entry>uk or uk-UA</entry>
+            <entry/>
+          </row>
+          <row>
+            <entry><ph xml:lang="ur">اردو</ph> (Urdu)</entry>
+            <entry>ur or ur-PK</entry>
+            <entry>Defaults to right-to-left presentation.</entry>
+          </row>
+          <row>
+            <entry><ph xml:lang="vi">Tiếng Việt</ph> (Vietnamese)</entry>
+            <entry>vi or vi-VN</entry>
+            <entry/>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/globalization-support.dita

@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="globalization-support">
+  <title>Globalization support</title>
+  <titlealts>
+    <navtitle>Globalization support</navtitle>
+  </titlealts>
+  <shortdesc>DITA Open Toolkit offers globalization support in the following areas: generated text, index sorting, and
+    bi-directional text.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlatt>dir</xmlatt></indexterm>
+        <indexterm><xmlatt>index:lang</xmlatt></indexterm>
+        <indexterm>languages<indexterm>index sorting</indexterm></indexterm>
+        <indexterm>languages<indexterm>right-to-left</indexterm></indexterm>
+        <indexterm>languages<indexterm>bi-directional</indexterm></indexterm>
+        <indexterm>English</indexterm>
+        <indexterm>strings</indexterm>
+        <indexterm>index<indexterm>sorting</indexterm></indexterm>
+        <indexterm>bi-directional languages</indexterm>
+        <indexterm>generated text</indexterm>
+        <indexterm>CSS<indexterm>bi-directional languages</indexterm><indexterm>right-to-left languages</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>
+      <dl>
+        <dlentry>
+          <dt>Generated text</dt>
+          <dd><term>Generated text</term> is text that is rendered automatically in the output that is generated by
+            DITA-OT; this text is not located in the DITA source files. The following are examples of generated text:
+            <ul>
+              <li>The word "Chapter" in a PDF file.</li>
+              <li>The phrases "Related concepts," "Related tasks," and "Related reference" in HTML output.</li>
+            </ul></dd>
+        </dlentry>
+        <dlentry>
+          <dt>Index sorting</dt>
+          <dd>DITA-OT can use only a single language to sort indexes.<draft-comment author="Kristen James Eberlein"
+              time="11 August 2012">What does the ICU for Java provide? Does index sorting occur if ICU for Java is NOT
+              installed?</draft-comment></dd>
+        </dlentry>
+        <dlentry>
+          <dt>Bi-directional text</dt>
+          <dd>DITA-OT contains style sheets (CSS files) that support both left-to-right (LTR) and right-to-left (RTL)
+            languages in HTML based transformations. PDF supports both LTR and RTL rendering based on the document
+            language. The <xmlatt>dir</xmlatt> attribute can be used to override the default rendering direction.</dd>
+        </dlentry>
+      </dl>When DITA-OT generates output, it takes the first value for the <xmlatt>xml:lang</xmlatt> attribute that it
+      encounters, and then it uses that value to create generated text, perform index sorting, and determine which
+      default CSS file is used. If no value for the <xmlatt>xml:lang</xmlatt> attribute is found, the toolkit defaults
+      to U.S. English. You can use the <xref href="../parameters/configuration-properties.dita"
+        >configuration.properties</xref> to change the default language.</p>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/globalization.dita

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="dita-globalization" xml:lang="en-US">
+  <title>Globalizing DITA content</title>
+  <shortdesc>The DITA standard supports content that is written in or translated to any language. In general, DITA Open
+    Toolkit passes content through to the output format unchanged. DITA-OT uses the values for the
+      <xmlatt>xml:lang</xmlatt> and <xmlatt>dir</xmlatt> attributes that are set in the source content to provide
+    globalization support.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlatt>dir</xmlatt></indexterm>
+        <indexterm><xmlatt>index:lang</xmlatt></indexterm>
+        <indexterm>languages<indexterm>supported</indexterm></indexterm>
+        <indexterm>translating</indexterm>
+        <indexterm>localizing</indexterm>
+        <indexterm>globalizing</indexterm>
+        <indexterm>strings</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/globalizing.ditamap

@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <title>Globalizing DITA content</title>
+  <topicref keyref="globalization">
+    <topicref keyref="globalization-support"/>
+    <topicref keyref="plugin-addgeneratedtext"/>
+    <topicref keyref="globalization-languages"/>
+  </topicref>
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-css.dita

@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="custom-html-css">
+  <title>Adding custom CSS</title>
+  <shortdesc>To modify the appearance of the default HTML output that DITA Open Toolkit generates, you can reference a
+    custom Cascading Style Sheet (CSS) file with the typography, colors, and other presentation aspects that define your
+    corporate identity.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>cascading style sheet<index-see>CSS</index-see></indexterm>
+        <indexterm>CSS<indexterm>adding custom</indexterm></indexterm>
+        <indexterm>HTML<indexterm>CSS</indexterm></indexterm>
+        <indexterm>HTML5<indexterm>CSS</indexterm></indexterm>
+        <indexterm>transformations<indexterm>HTML5</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>You can use this approach when you need to adjust the look and feel of the default output for a single project,
+        but don’t want to create a custom DITA-OT plug-in.</p>
+      <p>You can version the CSS file along with the DITA source files in your project, so stylesheet changes can be
+        tracked along with modifications to topic content.</p>
+      <p>You may also find this approach useful as you develop a custom stylesheet. Once the CSS rules stabilize, you
+        can bundle the CSS file in a custom DITA-OT plug-in to ensure consistent HTML output across
+      projects.</p></context>
+    <steps>
+      <step>
+        <cmd>Create a custom CSS file and store it in your project along with your DITA source files.</cmd>
+        <stepxmp>
+          <note>As a starting point, you can use the CSS file that is used for the DITA-OT documentation. This file is
+            available in the installation folder under <filepath>docsrc/resources/dita-ot-doc.css</filepath>.</note>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>Set the <parmname>args.css</parmname> parameter to the name of your custom CSS file.</cmd>
+        <info>
+          <p>The value of this parameter should be only the file name. The relative path to the file can be specified
+            with <parmname>args.cssroot</parmname>.</p></info>
+      </step>
+      <step>
+        <cmd>Set the <parmname>args.copycss</parmname> parameter to <option>yes</option>.</cmd>
+        <info>
+          <p>This setting ensures that your custom CSS file will be copied to the output directory.</p></info>
+      </step>
+      <step>
+        <cmd>Set <parmname>args.cssroot</parmname> to the folder path that contains your custom CSS file.</cmd>
+        <info>
+          <p>The value you enter here will be interpreted relative to the location of the input map file. If your map is
+            stored at the root level of your project folder and the CSS file is stored in a subfolder named
+              <filepath>resources</filepath>, set <parmname>args.cssroot</parmname> to
+          <option>resources</option>.</p></info>
+      </step>
+      <step importance="optional">
+        <cmd>Set <parmname>args.csspath</parmname> to specify the location of the CSS file in the output folder.</cmd>
+        <info>
+          <p>If <parmname>args.csspath</parmname> is not set, the custom CSS file will be copied to the root level of
+            the output folder. To copy the CSS file to a subfolder named <filepath>css</filepath>, set
+              <parmname>args.csspath</parmname> to <option>css</option>.</p></info>
+      </step>
+    </steps>
+    <result>
+      <note type="tip">For an example of HTML output generated using this method, see the HTML5 version of the DITA-OT
+        documentation included in the installation folder under <filepath>doc/index.html</filepath>.</note>
+    </result>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-header.dita

@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="custom-html-header">
+  <title>Adding custom headers and footers</title>
+  <titlealts>
+    <navtitle>Headers and footers</navtitle>
+  </titlealts>
+  <shortdesc>You add a custom header to include a publication title, company logo, or other common branding elements in
+    HTML output. A custom footer can also be added with copyright information, legal boilerplate, or other fine
+    print.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>header</xmlelement></indexterm>
+        <indexterm><xmlelement>footer</xmlelement></indexterm>
+        <indexterm><xmlelement>div</xmlelement><indexterm>HTML header</indexterm><indexterm>HTML footer</indexterm></indexterm>
+        <indexterm><xmlatt>role</xmlatt></indexterm>
+        <indexterm>HTML5<indexterm>headers</indexterm></indexterm>
+        <indexterm>HTML5<indexterm>footers</indexterm></indexterm>
+        <indexterm>CSS<indexterm>adding custom</indexterm></indexterm>
+        <indexterm>CSS<indexterm>HTML5</indexterm></indexterm>
+        <indexterm>HTML5<indexterm>CSS</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>In HTML5 output, the contents of the header file will be wrapped in an HTML5 <xmlelement>header</xmlelement>
+        element with the <xmlatt>role</xmlatt> attribute set to <option>banner</option>. The footer file contents are
+        wrapped in an HTML5 <xmlelement>footer</xmlelement> element with the <xmlatt>role</xmlatt> attribute set to
+          <option>contentinfo</option>.</p>
+      <p>For example, the DITA-OT documentation includes a simple header banner with the publication title and a
+        horizontal rule to separate the header from the generated topic content: </p>
+      <p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../resources/header.xml"/></codeblock>
+      </p>
+      <note>Header and footer files should be specified using absolute paths and must contain valid XML. A common
+        practice is to place all content into a <xmlelement>div</xmlelement> element.</note>
+    </context>
+    <steps>
+      <step>
+        <cmd>Set <parmname>args.hdr</parmname> to include an XML file as a running header that appears above the page
+          content.</cmd>
+        <info> </info>
+      </step>
+      <step>
+        <cmd>Set <parmname>args.ftr</parmname> to include an XML file as a running footer that appears below the page
+          content.</cmd>
+      </step>
+      <step importance="optional">
+        <cmd>Add custom CSS rules to style headers and/or footers.</cmd>
+        <info>
+          <p>For example, the DITA-OT documentation stylesheet includes the following header rules: </p>
+          <p><codeblock outputclass="language-css normalize-space show-line-numbers show-whitespace"><coderef href="../resources/dita-ot-doc.css#token=header-coderef,end-header-ref"/></codeblock>
+          </p>
+        </info>
+      </step>
+    </steps>
+    <result>
+      <note type="tip">For an example of HTML output generated using this method, see the HTML5 version of the DITA-OT
+        documentation included in the installation folder under <filepath>doc/index.html</filepath>.</note>
+    </result>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-navigation.dita

@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="custom-html-navigation">
+  <title>Adding navigation to topics</title>
+  <titlealts>
+    <navtitle>Adding navigation</navtitle>
+  </titlealts>
+  <shortdesc>In HTML5 output, you can set a parameter to include table-of-contents navigation in the
+      <xmlelement>nav</xmlelement> element of each page. The navigation can be rendered in a sidebar or menu via
+    CSS.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>nav</xmlelement></indexterm>
+        <indexterm>HTML5<indexterm>navigation, adding</indexterm></indexterm>
+        <indexterm>transformations<indexterm>HTML5</indexterm></indexterm>
+        <indexterm>CSS<indexterm>adding custom</indexterm></indexterm>
+        <indexterm>nav-toc</indexterm>
+        <indexterm>HTML5<indexterm>nav-toc</indexterm></indexterm>
+        <indexterm>table of contents<indexterm>HTML5</indexterm></indexterm>
+        <indexterm>table of contents<indexterm>nav-toc</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>Earlier versions of DITA-OT used the TocJS transformation to render a JavaScript-based table of contents in an
+        XHTML frameset for topic navigation. While this approach is still supported for XHTML output, recent toolkit
+        versions provide a modern HTML5 navigation alternative.</p>
+      <p>As of DITA-OT 2.2, the <parmname>nav-toc</parmname> parameter can be used in HTML5 transformations to embed
+        navigation directly in topics using native HTML5 elements without JavaScript or framesets.</p></context>
+    <steps>
+      <step>
+        <cmd>Set the <parmname>nav-toc</parmname> parameter to one of the following options:</cmd>
+        <choices>
+          <choice>The <option>partial</option> option creates a table of contents with the portion of the navigation
+            hierarchy that contains the current topic (along with its parents, siblings and children).</choice>
+          <choice>The <option>full</option> option embeds the complete navigation for the entire map in each
+            topic.</choice>
+        </choices>
+      </step>
+      <step importance="optional">
+        <cmd>Add custom CSS rules to style the navigation.</cmd>
+        <info>
+          <p>For example, the DITA-OT documentation stylesheet includes the following rules to place the table of
+            contents on the left side of the browser viewport and highlight the current topic in bold:</p>
+          <p>
+            <codeblock outputclass="language-css normalize-space show-line-numbers show-whitespace"><coderef href="../resources/dita-ot-doc.css#token=nav-coderef,end-nav-ref"/></codeblock>
+          </p>
+        </info>
+      </step>
+    </steps>
+    <result>
+      <note type="tip">For an example of HTML output generated using this method, see the HTML5 version of the DITA-OT
+        documentation included in the installation folder under <filepath>doc/index.html</filepath>.</note>
+    </result>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-parameters.dita

@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="custom-html-parameters">
+  <title>Setting parameters for custom HTML</title>
+  <titlealts>
+    <navtitle>Setting HTML parameters</navtitle>
+  </titlealts>
+  <shortdesc>For simple branded HTML pages, you can adjust the look and feel of the default output to match your company
+    style by setting parameters to include custom CSS, header branding, or table-of-contents navigation in topics.
+    (These changes do not require a custom plug-in.)</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>HTML<indexterm>parameters</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-plugin-bundle-css.dita

@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="custom-html-plugin-bundle-css">
+  <title>Bundling CSS in a custom HTML plug-in</title>
+  <titlealts>
+    <navtitle>Bundling custom CSS</navtitle>
+  </titlealts>
+  <shortdesc>You can create a DITA-OT plug-in that provides a custom stylesheet with the typography and colors that
+    define your corporate identity. Coworkers can install this plug-in to ensure consistent HTML output across projects
+    without having to copy the stylesheet to each project.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>require</xmlelement></indexterm>
+        <indexterm>HTML<indexterm>custom plug-in</indexterm></indexterm>
+        <indexterm>HTML<indexterm>CSS</indexterm></indexterm>
+        <indexterm>CSS<indexterm>HTML transforms</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>This scenario walks through the process of creating a very simple plug-in
+          (<codeph>com.example.html5-custom-css</codeph>) that creates a new transformation type:
+          <option>html5-custom-css</option>. </p>
+      <p>The <option>html5-custom-css</option> transformation includes a custom CSS file and sets four parameters to
+        integrate the custom stylesheet in the generated HTML5 output. These parameter settings make the following
+        changes:</p>
+      <ul>
+        <li>
+          <p>Specify the <filepath>css</filepath> subfolder of the plug-in as the source directory for custom CSS with
+              <parmname>args.cssroot</parmname>.</p></li>
+        <li>
+          <p>Specify the name of the custom CSS file with <parmname>args.css</parmname>.</p>
+          <p>The value of this parameter tells DITA-OT to use the <filepath>custom.css</filepath> file provided by the
+            plug-in.</p></li>
+        <li>
+          <p>Ensure that the CSS file is copied to the output directory by setting <parmname>args.copycss</parmname> to
+              <option>yes</option>.</p></li>
+        <li>
+          <p>Set the destination path for CSS files in the output folder with <parmname>args.csspath</parmname>.</p>
+          <p>CSS files are copied to the root level of the output folder by default. Setting this parameter places CSS
+            files in a dedicated <filepath>css</filepath> subfolder.</p></li>
+      </ul>
+      <p>All four parameters are set in the Ant script (<filepath>build_html5-custom-css.xml</filepath>).</p>
+    </context>
+    <steps>
+      <step>
+        <cmd>In the <filepath>plugins</filepath> directory, create a directory named
+            <filepath>com.example.html5-custom-css</filepath>.</cmd>
+      </step>
+      <step>
+        <cmd>In the new <filepath>com.example.html5-custom-css</filepath> directory, create a plug-in configuration file
+            (<filepath>plugin.xml</filepath>) that declares the new <option>html5-custom-css</option> transformation and
+          its dependencies.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample <filepath>plugin.xml</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-custom-css/plugin.xml"/></codeblock>
+          </fig>
+          <note>This plug-in will extend the default HTML5 transformation, so the <xmlelement>require</xmlelement>
+            element explicitly defines <filepath>org.dita.html5</filepath> as a dependency.</note>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>In the <filepath>com.example.html5-custom-css</filepath> directory, create a subdirectory named
+            <filepath>css</filepath>.</cmd>
+      </step>
+      <step>
+        <cmd>In the new <filepath>css</filepath> subdirectory, create a file named <filepath>custom.css</filepath> with
+          your custom CSS rules.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample <filepath>custom.css</filepath> file</title>
+            <codeblock outputclass="language-css normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-custom-css/css/custom.css"/></codeblock>
+          </fig>
+          <note type="tip">When you first create the plug-in, you may want to include a rule in your custom stylesheet
+            that makes it readily apparent when the custom styles are applied (the example above will change body text
+            to “red”). Once you have verified that the plug-in works as intended, replace the placeholder rule with your
+            own custom styles.</note>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>In the <filepath>com.example.html5-custom-css</filepath> root directory, add an Ant script
+            (<filepath>build_html5-custom-css.xml</filepath>) to define the transformation type.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample build file: <filepath>build_html5-custom-css.xml</filepath></title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-custom-css/build_html5-custom-css.xml"/></codeblock>
+          </fig>
+        </stepxmp>
+      </step>
+    </steps>
+    <result>
+      <note type="tip">The files for this sample plug-in are included in the DITA-OT installation directory under
+          <filepath>docsrc/samples/plugins/com.example.html5-custom-css/</filepath> and on
+        <xref href="https://github.com/dita-ot/docs/tree/develop/samples/plugins/com.example.html5-custom-css"
+          format="html" scope="external">GitHub</xref>.</note>
+      <p>The plug-in directory has the following layout and files:</p>
+      <codeblock>com.example.html5-custom-css
+├── build_html5-custom-css.xml
+├── css
+│   └── custom.css
+└── plugin.xml</codeblock>
+    </result>
+    <postreq>
+      <ol>
+        <li>Run <filepath conref="../resources/conref-task.dita#ID/dita-cmd"/>
+          <parmname>--install</parmname> to install the plug-in and make the <option>html5-custom-css</option>
+          transformation available.</li>
+        <li>Build output with the new transformation type to verify that the plug-in works as intended.
+          <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>my.ditamap</varname> <parmname>--format</parmname>=<option>html5-custom-css</option></codeblock>
+        </li>
+        <li>Refine the styles in your <filepath>custom.css</filepath> file as necessary.</li>
+      </ol>
+    </postreq>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-plugin-javascript.dita

@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="custom-html-plugin-webfont">
+  <title>Inserting JavaScript in generated HTML</title>
+  <titlealts>
+    <navtitle>Inserting JavaScript</navtitle>
+  </titlealts>
+  <shortdesc>JavaScript code can be bundled in a custom plug-in and automatically inserted into the generated HTML pages
+    to enable web analytics or dynamic content delivery.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>footer</xmlelement></indexterm>
+        <indexterm><xmlelement>require</xmlelement></indexterm>
+        <indexterm><xmlelement>head</xmlelement></indexterm>
+        <indexterm>transformations<indexterm end="html"/></indexterm> <!-- LE: This range is not appearing in the FOP index. -->
+        <indexterm>HTML5<indexterm>JavaScript, adding</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>This scenario walks through the process of creating a very simple plug-in
+          (<codeph>com.example.html5-javascript</codeph>) that creates a new transformation type:
+          <option>html5-javascript</option>. </p>
+      <p>The <option>html5-javascript</option> transformation includes a custom page footer file with a JavaScript
+        tracking snippet and sets the <parmname>args.ftr</parmname> parameter to integrate the script content in the
+        HTML5 <xmlelement>footer</xmlelement> element of the generated pages.</p>
+      <note>This example inserts a tracking snippet for Google Analytics, but the basic approach is the same for other
+        analytics platforms or similar use cases that require custom JavaScript.</note>
+    </context>
+    <steps>
+      <step>
+        <cmd>In the <filepath>plugins</filepath> directory, create a directory named
+            <filepath>com.example.html5-javascript</filepath>.</cmd>
+      </step>
+      <step>
+        <cmd>In the new <filepath>com.example.html5-javascript</filepath> directory, create a plug-in configuration file
+            (<filepath>plugin.xml</filepath>) that declares the new <option>html5-javascript</option> transformation and
+          its dependencies.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample <filepath>plugin.xml</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-javascript/plugin.xml"/></codeblock>
+          </fig>
+          <note>This plug-in will extend the default HTML5 transformation, so the <xmlelement>require</xmlelement>
+            element explicitly defines <filepath>org.dita.html5</filepath> as a dependency.</note>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>In the <filepath>com.example.html5-javascript</filepath> directory, create a subdirectory named
+            <filepath>include</filepath>.</cmd>
+      </step>
+      <step>
+        <cmd>In the new <filepath>include</filepath> subdirectory, create a file named
+            <filepath>javascript.ftr.xml</filepath> with your custom JavaScript code.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample <filepath>javascript.ftr.xml</filepath> file</title>
+            <codeblock outputclass="language-javascript normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-javascript/include/javascript.ftr.xml"/></codeblock>
+          </fig>
+          <p>The division wrapper will be discarded when generating HTML files, and the contents will be inserted into
+            the <xmlelement>footer</xmlelement> element of each page.</p>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>In the <filepath>com.example.html5-javascript</filepath> root directory, add an Ant script
+            (<filepath>build_html5-javascript.xml</filepath>) to define the transformation type and set the path to the
+          JavaScript footer file created in the previous step.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample build file: <filepath>build_html5-javascript.xml</filepath></title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-javascript/build_html5-javascript.xml"/></codeblock>
+          </fig>
+        </stepxmp>
+      </step>
+    </steps>
+    <result>
+      <note type="tip">The files for this sample plug-in are included in the DITA-OT installation directory under
+          <filepath>docsrc/samples/plugins/com.example.html5-javascript/</filepath> and on <xref
+          href="https://github.com/dita-ot/docs/tree/develop/samples/plugins/com.example.html5-javascript" format="html"
+          scope="external">GitHub</xref>.</note>
+      <p>The plug-in directory has the following layout and files:</p>
+      <codeblock>com.example.html5-javascript
+├── build_html5-javascript.xml
+├── include
+│   └── javascript.ftr.xml
+└── plugin.xml</codeblock>
+    </result>
+    <postreq>
+      <ol>
+        <li>Run <filepath conref="../resources/conref-task.dita#ID/dita-cmd"/>
+          <parmname>--install</parmname> to install the plug-in and make the <option>html5-javascript</option>
+          transformation available.</li>
+        <li>Build output with the new transformation type to verify that the plug-in works as intended.
+          <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>my.ditamap</varname> <parmname>--format</parmname>=<option>html5-javascript</option></codeblock></li>
+        <li>Open one of the generated HTML topic files in a modern web browser and check the JavaScript
+            <uicontrol>Console</uicontrol>. When the page is loaded, <msgph>Adding Google Analytics tracker</msgph> will
+          appear on the console to verify that the sample script is loaded.</li>
+        <li>Remove the <codeph>console.log</codeph> debugging message from the sample JavaScript code, and replace the
+            <codeph>'UA-XXXXX-Y'</codeph> placeholder string with the tracking ID of the Google Analytics property you
+          wish to track.</li>
+      </ol>
+      <note type="tip">This example places the JavaScript code in the page footer to ensure that page display is not
+        delayed while the script is loaded. If your JavaScript code supports pre-loading and your application targets
+        modern browsers that recognize the <codeph>async</codeph> script attribute, you may prefer to insert the
+        JavaScript snippet in the <xmlelement>head</xmlelement> element of the generated HTML files using the
+          <parmname>args.hdf</parmname> parameter intead.</note>
+    </postreq>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-plugin-webfont.dita

@@ -0,0 +1,147 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="custom-html-plugin-webfont">
+  <title>Embedding web fonts in HTML output</title>
+  <titlealts>
+    <navtitle>Embedding web fonts</navtitle>
+  </titlealts>
+  <shortdesc>A custom plug-in can be created to generate HTML output that uses custom fonts for enhanced typographic
+    features, extended character sets or a unique corporate identity.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>require</xmlelement></indexterm>
+        <indexterm><xmlelement>link</xmlelement></indexterm>
+        <indexterm><xmlelement>head</xmlelement></indexterm>
+        <indexterm>HTML<indexterm>custom plug-in</indexterm></indexterm>
+        <indexterm>HTML<indexterm>fonts</indexterm></indexterm>
+        <indexterm>CSS<indexterm>web fonts</indexterm></indexterm>
+        <indexterm>fonts<indexterm>HTML</indexterm></indexterm>
+        <indexterm>web fonts<index-see>fonts</index-see></indexterm>
+        <indexterm>custom.css</indexterm>
+        <indexterm>build_html5-webfont.xml</indexterm>
+        <indexterm>plugin.xml</indexterm>
+        <indexterm>org.dita.html5</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>This scenario walks through the process of creating a very simple plug-in
+          (<codeph>com.example.html5-webfont</codeph>) that creates a new transformation type:
+          <option>html5-webfont</option>. </p>
+      <p>The <option>html5-webfont</option> transformation includes a custom CSS file and sets five parameters to
+        integrate font links and a custom stylesheet in the generated HTML5 output. These parameter settings make the
+        following changes:</p>
+      <ul>
+        <li>
+          <p>Specify a file that links to the font from the document head with <parmname>args.hdf</parmname>.</p></li>
+        <li>
+          <p>Specify the <filepath>css</filepath> subfolder of the plug-in as the source directory for custom CSS with
+              <parmname>args.cssroot</parmname>.</p></li>
+        <li>
+          <p>Specify the name of the custom CSS file with <parmname>args.css</parmname>.</p>
+          <p>The value of this parameter tells DITA-OT to use the <filepath>custom.css</filepath> file provided by the
+            plug-in.</p></li>
+        <li>
+          <p>Ensure that the CSS file is copied to the output directory by setting <parmname>args.copycss</parmname> to
+              <option>yes</option>.</p></li>
+        <li>
+          <p>Set the destination path for CSS files in the output folder with <parmname>args.csspath</parmname>.</p>
+          <p>CSS files are copied to the root level of the output folder by default. Setting this parameter places CSS
+            files in a dedicated <filepath>css</filepath> subfolder.</p></li>
+      </ul>
+      <p>All five parameters are set in the Ant script (<filepath>build_html5-webfont.xml</filepath>).</p>
+    </context>
+    <steps>
+      <step>
+        <cmd>In the <filepath>plugins</filepath> directory, create a directory named
+            <filepath>com.example.html5-webfont</filepath>.</cmd>
+      </step>
+      <step>
+        <cmd>In the new <filepath>com.example.html5-webfont</filepath> directory, create a plug-in configuration file
+            (<filepath>plugin.xml</filepath>) that declares the new <option>html5-webfont</option> transformation and
+          its dependencies.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample <filepath>plugin.xml</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-webfont/plugin.xml"/></codeblock>
+          </fig>
+          <note>This plug-in will extend the default HTML5 transformation, so the <xmlelement>require</xmlelement>
+            element explicitly defines <filepath>org.dita.html5</filepath> as a dependency.</note>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>In the <filepath>com.example.html5-webfont</filepath> directory, create a subdirectory named
+            <filepath>include</filepath>.</cmd>
+      </step>
+      <step>
+        <cmd>In the new <filepath>include</filepath> subdirectory, create a file named
+            <filepath>webfont.hdf.xml</filepath> with your custom font links.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample <filepath>webfont.hdf.xml</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-webfont/include/webfont.hdf.xml"/></codeblock>
+          </fig>
+          <p>This example uses the <xref keyref="noto-sans-font"/> font. You can use multiple fonts by creating
+            additional <xmlelement>link</xmlelement> references in this file. The division wrapper will be discarded
+            when generating HTML files, and the contents will be inserted into the <xmlelement>head</xmlelement> element
+            of each page.</p>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>In the <filepath>com.example.html5-webfont</filepath> directory, create a subdirectory named
+            <filepath>css</filepath>.</cmd>
+      </step>
+      <step>
+        <cmd>In the new <filepath>css</filepath> subdirectory, create a file named <filepath>custom.css</filepath> with
+          the stylesheet rules that apply the custom <codeph>font-family</codeph> to the desired elements.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample <filepath>custom.css</filepath> file</title>
+            <codeblock outputclass="language-css normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-webfont/css/custom.css"/></codeblock>
+          </fig>
+          <p>This example uses <xref keyref="noto-sans-font"/> for all body content. In practice, you would normally use
+            different fonts for headings, body content, tables, etc. by creating additional rules in your CSS file.</p>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>In the <filepath>com.example.html5-webfont</filepath> root directory, add an Ant script
+            (<filepath>build_html5-webfont.xml</filepath>) to define the transformation type.</cmd>
+        <stepxmp>
+          <fig>
+            <title>Sample build file: <filepath>build_html5-webfont.xml</filepath></title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.html5-webfont/build_html5-webfont.xml"/></codeblock>
+          </fig>
+        </stepxmp>
+      </step>
+    </steps>
+    <result>
+      <note type="tip">The files for this sample plug-in are included in the DITA-OT installation directory under
+          <filepath>docsrc/samples/plugins/com.example.html5-webfont/</filepath> and on <xref
+          href="https://github.com/dita-ot/docs/tree/develop/samples/plugins/com.example.html5-webfont" format="html"
+          scope="external">GitHub</xref>.</note>
+      <p>The plug-in directory has the following layout and files:</p>
+      <codeblock>com.example.html5-webfont
+├── build_html5-webfont.xml
+├── css
+│   └── custom.css
+├── include
+│   └── webfont.hdf.xml
+└── plugin.xml</codeblock>
+    </result>
+    <postreq>
+      <ol>
+        <li>Run <filepath conref="../resources/conref-task.dita#ID/dita-cmd"/>
+          <parmname>--install</parmname> to install the plug-in and make the <option>html5-webfont</option>
+          transformation available.</li>
+        <li>Build output with the new transformation type to verify that the plug-in works as intended.
+          <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>my.ditamap</varname> <parmname>--format</parmname>=<option>html5-webfont</option></codeblock>
+        </li>
+        <li>Refine the styles in your <filepath>custom.css</filepath> file to adjust the font usage as necessary.</li>
+      </ol>
+    </postreq>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-plugins.dita

@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="custom-html-plugins">
+  <title>Custom HTML plug-ins</title>
+  <shortdesc>For more complex customizations, you can create custom DITA-OT plug-ins that bundle custom fonts,
+    JavaScript, and stylesheets; modify the HTML markup, or override other aspects of HTML processing.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>HTML<indexterm>custom plug-in</indexterm></indexterm>
+        <indexterm>HTML<indexterm>fonts</indexterm></indexterm>
+        <indexterm>HTML<indexterm>JavaScript</indexterm></indexterm>
+        <indexterm>HTML<indexterm>CSS</indexterm></indexterm>
+        <indexterm>HTML<indexterm>markup, adding</indexterm></indexterm>
+        <indexterm>CSS<indexterm>HTML</indexterm></indexterm>
+        <indexterm>fonts<indexterm>HTML</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <note>These examples are not intended to be used as-is, but illustrate basic techniques you can use in your own
+      plug-ins. In practise, custom plug-ins often combine several of these approaches.</note>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization-properties-file.dita

@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="custom-html-properties-file">
+  <title>Customizing HTML with a <filepath>.properties</filepath> file</title>
+  <titlealts>
+    <navtitle>Using a properties file</navtitle>
+  </titlealts>
+  <shortdesc>You can also use a <filepath>.properties</filepath> file to reference a set of build parameters when
+    building output with the <cmdname>dita</cmdname> command. The DITA-OT documentation uses a
+      <filepath>.properties</filepath> file to include custom CSS, header branding, and table-of-contents navigation in
+    the HTML5 output.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>.properties file</indexterm></indexterm>
+        <indexterm>HTML<indexterm>build properties</indexterm></indexterm>
+        <indexterm>CSS<indexterm>.properties file</indexterm></indexterm>
+        <indexterm>.properties file</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+
+    <steps>
+      <step>
+        <cmd>Create a <filepath>.properties</filepath> file to store the parameter settings for your
+          customization.</cmd>
+        <info>
+          <note type="tip">You can use the <filepath>.properties</filepath> for the DITA-OT documentation as a starting
+            point for your own customizations. This file is available in the installation folder under
+              <filepath>docsrc/samples/properties/docs-build-html5.properties</filepath>.</note>
+        </info>
+        <stepxmp>
+          <p>For example:</p>
+          <fig>
+            <title>The <filepath>docsrc/samples/properties/docs-build-html5.properties</filepath> file</title>
+            <codeblock outputclass="language-properties normalize-space show-line-numbers show-whitespace"><coderef href="../samples/properties/docs-build-html5.properties"/></codeblock>
+          </fig>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>Reference your <filepath>.properties</filepath> file with the <cmdname>dita</cmdname> command when building
+          your output.</cmd>
+        <stepxmp>
+          <codeblock><cmdname>dita</cmdname> <parmname>--input</parmname>=<varname>my.ditamap</varname> <parmname>--format</parmname>=<option>html5</option> <parmname>--propertyfile</parmname>=<varname>my.properties</varname></codeblock>
+        </stepxmp>
+        <info/>
+      </step>
+    </steps>
+    <result>
+      <note>For an example of HTML output generated using this method, see the HTML5 version of the DITA-OT
+        documentation included in the installation folder under <filepath>doc/index.html</filepath>.</note>
+    </result>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization.dita

@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="customizing-html-output">
+  <title>Customizing HTML output</title>
+  <titlealts>
+    <navtitle>Customizing HTML</navtitle>
+  </titlealts>
+  <shortdesc>You can adjust the look and feel of your HTML output without creating a DITA-OT plug-in by including custom
+    CSS, headers and footers, or table-of-contents navigation in topics.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>HTML<indexterm>customizing</indexterm></indexterm>
+        <indexterm>transformations<indexterm start="html">HTML</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>HTML5</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/html-customization.ditamap

@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <title>Customizing HTML output</title>
+  <topicref keyref="html-customization" collection-type="family">
+    <topicref keyref="html-customization-parameters" collection-type="family">
+      <topicref keyref="html-customization-navigation"/>
+      <topicref keyref="html-customization-css"/>
+      <topicref keyref="html-customization-header"/>
+      <topicref keyref="generate-copy-outer"/>
+    </topicref>
+    <topicref keyref="html-customization-properties-file"/>
+    <topicref keyref="html-customization-plugins">
+      <topicref keyref="html-customization-plugin-bundle-css"/>
+      <topicref keyref="html-customization-plugin-webfont"/>
+      <topicref keyref="html-customization-plugin-javascript"/>
+    </topicref>
+  </topicref>
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/implement-saxon-collation-uri-resolvers.dita

@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="implement-saxon-collation-uri-resolvers">
+  <title>Implementing custom Saxon collation URI resolvers</title>
+  <titlealts>
+    <navtitle>Custom collation URI resolvers</navtitle>
+  </titlealts>
+  <shortdesc>Plug-ins can provide custom URI resolvers that provide collators for specific collation URIs.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Saxon<indexterm><xmlelement>service</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>jar</xmlelement></indexterm></indexterm>
+        <indexterm><xmlatt>xsl:sort</xmlatt></indexterm>
+        <indexterm>Chinese</indexterm>
+        <indexterm>I18N<indexterm>plug-in</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm end="plugin-ideas"/></indexterm>
+        <indexterm>plug-ins<indexterm end="plugins-saxon"/></indexterm>
+        <indexterm>XSLT<indexterm>URI resolver</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>To do custom sorting and grouping in XSLT, you identify collators using URIs that Saxon resolves to collator
+      implementations. You implement the mapping from collation URIs to collators through custom collation URI
+      resolvers.</p>
+    <p>For example, the DITA Community I18N plugin provides a custom collator for doing dictionary-based sorting and
+      grouping of Simplified Chinese. </p>
+    <p>To allow multiple plug-ins to contribute collation URI resolvers, DITA-OT defines a superinterface of Saxon’s
+        <codeph>CollationUriResolver</codeph> interface,
+        <codeph>org.dita.dost.module.saxon.DelegatingCollationUriResolver</codeph>, that takes a base resolver.</p>
+    <p>Implementations of <codeph>DelegatingCollationUriResolver</codeph> should delegate to their base resolver if they
+      do not resolve the URI specified on the resolve request. When multiple plug-ins provide resolvers it results in a
+      chain of resolvers, ending with the built-in Saxon default resolver.</p>
+    <note>The order in which plug-ins will be processed during collation URI resolver configuration is variable, so two
+      plug-ins should not try to resolve the same collation URI. In that case the first one configured will be used at
+      run time.</note>
+    <p>A typical delegating collation URI resolver looks like
+      this:<codeblock outputclass="language-java">public class DCI18nCollationUriResolver implements DelegatingCollationUriResolver {
+
+  public static final String DITA_COMMUNITY_I18N_ZH_CNAWARE_COLLATOR =
+      "http://org.dita-community.i18n.zhCNawareCollator";
+  public static final String LANG_URI_PARAM = "lang";
+
+  private CollationURIResolver baseResolver;
+
+  public DCI18nCollationUriResolver() {
+      super();
+      this.baseResolver = StandardCollationURIResolver.getInstance();
+  }
+
+
+  public net.sf.saxon.lib.StringCollator resolve(String uri, Configuration configuration) 
+          throws XPathException {
+      ZhCnAwareCollator collator = resolveToZhCnAwareCollator(uri, null, configuration);
+      if (null == collator) {
+          return baseResolver.resolve(uri, configuration);
+      }
+      return (StringCollator) collator;
+  }
+
+
+  @Override
+  public void setBaseResolver(CollationURIResolver baseResolver) {
+    this.baseResolver = baseResolver;
+  }
+  
+  /* ... Code to evaluate the collation URI and provide the appropriate collator goes here */
+}</codeblock></p>
+    <p>To implement a custom collation URI resolver:
+      <ol>
+        <li>Add your plugin’s JAR file in the DITA-OT class path as described in <xref keyref="plugin-javalib"/>.</li>
+        <li>Implement an instance of <codeph>org.dita.dost.module.saxon.DelegatingCollationUriResolver</codeph> as
+          described above.</li>
+        <li>Include a file named <filepath>org.dita.dost.module.saxon.DelegatingCollationUriResolver</filepath> in the
+          directory <filepath>META-INF/services</filepath> in the compiled JAR that your plug-in provides. Each line of
+          the file must be the name of a class that implements
+            <codeph>org.dita.dost.module.saxon.DelegatingCollationUriResolver</codeph>:<codeblock>org.example.i18n.saxon.MyCollationUriResolver</codeblock>
+          <p>You can create the services file using <xmlelement>service</xmlelement> elements in an Ant
+            <xmlelement>jar</xmlelement>
+            task:<codeblock outputclass="language-xml">&lt;jar destfile="${basedir}/target/lib/example-saxon.jar">
+  ⋮
+  &lt;service type="org.dita.dost.module.saxon.DelegatingCollationUriResolver">
+    &lt;provider classname="org.example.i18n.saxon.MyCollationUriResolver"/>
+  &lt;/service>
+  ⋮
+&lt;/jar></codeblock></p></li>
+        <li>To use the collator in XSLT style sheets, specify the collation URI on <xmlatt>xsl:sort</xmlatt> elements (or
+          anywhere a collator URI can be
+          specified):<codeblock outputclass="language-xml">&lt;xsl:apply-templates select="word">
+  &lt;xsl:sort collation="http://org.example.i18n.MyCollator"/>
+&lt;/xsl:apply-templates></codeblock></li>
+      </ol></p>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/implement-saxon-customizations.dita

@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="implement-saxon-customizations">
+  <title>Adding Saxon customizations</title>
+  <shortdesc>Plug-ins can contribute XSLT extension functions and collation URI resolvers. These customizations are
+    automatically configured to work with Saxon when transformations are run using the DITA-OT
+      <xmlelement>pipeline</xmlelement> task with custom XSLT.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Saxon<indexterm><xmlelement>service</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>jar</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>pipeline</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>xslt</xmlelement></indexterm></indexterm>
+        <indexterm>Saxon<index-see-also>Ant</index-see-also></indexterm>
+        <indexterm>Ant<index-see-also>Saxon</index-see-also></indexterm>
+        <indexterm>I18N<indexterm>plug-in</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm start="plugins-saxon">Saxon</indexterm></indexterm>
+        <indexterm>XSLT<indexterm>Saxon</indexterm></indexterm>
+        <indexterm>preprocessing<indexterm>extension points, Saxon</indexterm></indexterm>
+        <indexterm>Java<indexterm>ServiceLoader</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>Plug-ins can provide the following Saxon extensions:
+      <ul>
+        <li>Extension functions</li>
+        <li>Collation URI resolvers</li>
+      </ul></p>
+    <p>Extensions are declared in plug-in-provided JAR files using the Java ServiceLoader feature that looks for
+      service-declaring files in JAR files and loads classes. This requires adding one or more files in the
+        <filepath>META-INF/services</filepath> directory in plug-in-provided JAR files.</p>
+    <p>You can create the file manually or generate it dynamically using <xmlelement>service</xmlelement> elements in
+      Ant <xmlelement>jar</xmlelement> tasks. See the topics for the different extension types for details.</p>
+    <p>These extensions use the DITA Open Toolkit Ant <xmlelement>pipeline</xmlelement> element to wrap
+        <xmlelement>xslt</xmlelement> elements. You can do this in plug-ins as shown in this excerpt from the DITA
+      Community I18N plugin’s <filepath>build.xml</filepath>
+      file:<codeblock outputclass="language-xml">&lt;target name="org.dita-community.i18n-saxon-extension-test">
+  &lt;pipeline message="Test the DITA Community i18n Saxon extension functions"
+            taskname="i18n-extension-function-test">
+    &lt;xslt
+      in="${dita.plugin.org.dita-community.i18n.dir}/test/xsl/data/test-data.xml"
+      style="${dita.plugin.org.dita-community.i18n.dir}/test/xsl/test-extension-functions.xsl"
+      out="${basedir}/out/extension-function-test-results.xml"
+      >
+
+    &lt;/xslt>
+  &lt;/pipeline>
+&lt;/target></codeblock></p>
+    <p>Normal XSLT extensions to built-in transformation types will automatically have the extensions available to
+      them.</p>
+    <p>The dynamic Saxon configuration is implemented in the class <codeph>org.dita.dost.module.XsltModule</codeph>,
+      which backs the <xmlelement>pipeline</xmlelement>/<xmlelement>xslt</xmlelement> element.</p>
+    <p> </p>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/implement-saxon-extension-functions.dita

@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="implement-saxon-extension-functions">
+  <title>Implementing Saxon extension functions</title>
+  <titlealts>
+    <navtitle>Saxon extensions</navtitle>
+  </titlealts>
+  <shortdesc>Plug-ins can contribute Saxon extension functions for use in XSLT transformations run by DITA Open
+    Toolkit.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Saxon<indexterm><xmlelement>service</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>jar</xmlelement></indexterm></indexterm>
+        <indexterm>XSLT<indexterm>Saxon</indexterm></indexterm>
+        <indexterm>Java<indexterm>extension functions</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>Starting with Saxon 9.2, the mechanism for implementing extension functions has changed such that Saxon HE, in
+      particular, can no longer use the older “reflexive” mechanism for finding Java extension functions using a magic
+      URL. Instead, you implement extension functions and then register them directly on the Saxon Configuration object.
+      DITA-OT provides a dynamic mechanism to perform this registration for plug-in-provided extension functions.</p>
+    <p>To implement extension functions, you must do the following:
+      <ol>
+        <li>Add your plug-in’s JAR file in the DITA-OT class path as described in <xref keyref="plugin-javalib"/>.</li>
+        <li>For each function, implement a class that extends
+            <codeph>net.sf.saxon.lib.ExtensionFunctionDefinition</codeph>. This class provides the namespace name and
+          function name for the function as well as details about its arguments and so on. See <xref
+            keyref="saxon-java-extensions-impl"/> in the Saxon documentation.</li>
+        <li>Include a file named <filepath>net.sf.saxon.lib.ExtensionFunctionDefinition</filepath> in the directory
+            <filepath>META-INF/services</filepath> in the compiled JAR that your plug-in provides. Each line of the file
+          must be the name of a class that implements <codeph>net.sf.saxon.lib.ExtensionFunctionDefinition</codeph>: <codeblock>com.example.saxon.functions.Add
+com.example.saxon.functions.Substract</codeblock>
+          <p>You can create the file using <xmlelement>service</xmlelement> elements in an Ant
+              <xmlelement>jar</xmlelement>
+            task:<codeblock outputclass="language-xml">&lt;jar destfile="${basedir}/target/lib/example-saxon.jar">
+  ⋮
+  &lt;service type="net.sf.saxon.lib.ExtensionFunctionDefinition">
+    &lt;provider classname="com.example.saxon.functions.Add"/>
+    &lt;provider classname="com.example.saxon.functions.Subtract"/>
+  &lt;/service>
+  ⋮
+&lt;/jar></codeblock></p></li>
+        <li>In your XSLT transformations, declare the namespace the functions are bound
+          to:<codeblock outputclass="language-xml">&lt;xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
+                xmlns:xs="http://www.w3.org/2001/XMLSchema"
+                <b>xmlns:eg="http://example.com/saxon-extensions"</b>
+                version="2.0"></codeblock></li>
+      </ol></p>
+    <p>You should then be able to use the extension functions as you would any other
+      function:<codeblock outputclass="language-xml">&lt;xsl:variable name="test" select="<b>eg:add(1, 2)</b>"/></codeblock></p>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/increasing-the-jvm.dita

@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="t-increasing-the-JVM">
+  <title>Increasing Java memory allocation</title>
+  <titlealts>
+    <navtitle>Increasing Java memory</navtitle>
+  </titlealts>
+  <shortdesc>If you are working with large documents with extensive metadata or key references, you will need to
+    increase the memory allocation for the Java process. You can do this from the command-line prompt for a specific
+    session, or you can increase the value of the <codeph>ANT_OPTS</codeph> environment variable.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>macOS<indexterm>increase Java memory</indexterm></indexterm>
+        <indexterm>Linux<indexterm>increase Java memory</indexterm></indexterm>
+        <indexterm>Windows<indexterm>increase Java memory</indexterm></indexterm>
+        <indexterm>command line<indexterm>increase Java memory</indexterm></indexterm>
+        <indexterm>operating system<index-see>Linux</index-see><index-see>macOS</index-see><index-see>Windows</index-see></indexterm>
+        <indexterm>Java<indexterm>memory</indexterm></indexterm>
+        <indexterm><codeph>ANT_OPTS</codeph></indexterm>
+        <indexterm>Java<indexterm><codeph>ANT_OPTS</codeph></indexterm></indexterm>
+        <indexterm>metadata<indexterm>processing time, effect on</indexterm></indexterm>
+        <indexterm>memory</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <steps-unordered>
+      <step>
+        <cmd>To change the value for a specific session, from the command prompt, issue the following command:</cmd>
+        <choicetable>
+          <chhead>
+            <choptionhd>Platform</choptionhd>
+            <chdeschd>Command</chdeschd>
+          </chhead>
+          <chrow platform="unix">
+            <choption>Linux or macOS&#xA0;</choption>
+            <chdesc><codeph>export ANT_OPTS=$ANT_OPTS -Xmx<varname>1024</varname>M</codeph></chdesc>
+          </chrow>
+          <chrow platform="windows">
+            <choption>Windows</choption>
+            <chdesc><codeph>set ANT_OPTS=%ANT_OPTS% -Xmx<varname>1024</varname>M</codeph></chdesc>
+          </chrow>
+        </choicetable>
+        <info>
+          <p>This increases the JVM memory allocation to 1024 megabytes. The amount of memory which can be allocated is
+            limited by available system memory and the operating system.</p></info>
+      </step>
+      <step>
+        <cmd>To persistently change the value, change the value allocated to the <codeph>ANT_OPTS</codeph> environment
+          variable on your system.</cmd>
+      </step>
+    </steps-unordered>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/input-formats.ditamap

@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD LIGHTWEIGHT DITA Map//EN" "lw-map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <topicmeta>
+    <navtitle>Input formats</navtitle>
+  </topicmeta>
+
+  <topicref keyref="markdown-input"/>
+  <topicref keyref="lwdita-input"/>
+  <topicref keyref="markdown-dita-syntax-reference"/>
+
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/installing-client.dita

@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="installing-client" xml:lang="en-US">
+  <title>Installing DITA Open Toolkit</title>
+  <titlealts>
+    <navtitle>Installing DITA-OT</navtitle>
+  </titlealts>
+  <shortdesc id="what-is-client">The DITA-OT distribution package can be installed on Linux, macOS, and Windows. It
+    contains everything that you need to run the toolkit except for Java.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>macOS<indexterm>installing DITA-OT</indexterm></indexterm>
+        <indexterm>Linux<indexterm>installing DITA-OT</indexterm></indexterm>
+        <indexterm>Windows<indexterm>installing DITA-OT</indexterm></indexterm>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>installing</indexterm></indexterm>
+        <indexterm>installing<indexterm>DITA-OT</indexterm></indexterm>
+        <indexterm>Java<indexterm>Java Development Kit (JDK)</indexterm><indexterm>Java Runtime Environment (JRE)</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <prereq>
+      <ul>
+        <li>
+          <p>Ensure that you have a Java Runtime Environment (JRE) or Java Development Kit (JDK).</p>
+          <p conkeyref="reusable-components/java-clients"/></li>
+        <li importance="optional" platform="windows">If you want to generate HTML Help, ensure that you have HTML Help
+          Workshop installed.
+          <p>You can download the Help Workshop from <xref keyref="download.html-help-workshop"/>.</p></li>
+      </ul>
+    </prereq>
+    <steps>
+      <step>
+        <cmd><ph conref="../resources/conref-task.dita#ID/download-ot"/></cmd>
+      </step>
+      <step>
+        <cmd>Extract the contents of the package to the directory where you want to install DITA-OT.</cmd>
+      </step>
+      <step importance="optional">
+        <cmd>Add the absolute path for the <filepath>bin</filepath> directory to the <varname>PATH</varname> system
+          variable.</cmd>
+        <stepresult>
+          <p>This defines the necessary environment variable to run the <cmdname>dita</cmdname> command from the command
+            line.</p>
+          <note type="tip">This step is recommended, as it allows the <cmdname>dita</cmdname> command to be run from any
+            location on the file system and makes it easier to transform DITA content from any folder.</note>
+        </stepresult>
+      </step>
+    </steps>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/installing-via-homebrew.dita

@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="installing-via-homebrew">
+  <title>Installing on macOS via Homebrew</title>
+  <titlealts>
+    <navtitle>Installing via Homebrew</navtitle>
+  </titlealts>
+  <shortdesc>An alternative installation method can be used to install DITA-OT on macOS via <xref keyref="homebrew"/>,
+    the platform’s most popular open-source package manager.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>macOS</indexterm>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>Homebrew</indexterm></indexterm>
+        <indexterm>installing<indexterm>Homebrew</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <prereq>
+      <p>The steps below assume you have already installed <xref keyref="homebrew"/> according to the instructions at
+          <xref keyref="homebrew">brew.sh</xref>.</p>
+      <note type="tip">Verify that your <varname>PATH</varname> environment begins with
+          <filepath>/usr/local/bin</filepath> to ensure that Homebrew-installed software takes precedence over any
+        programs of the same name elsewhere on the system.</note>
+    </prereq>
+    <steps>
+      <step>
+        <cmd>Update Homebrew to make sure the latest package formulas are available on your system:</cmd>
+        <stepxmp><codeblock>$ <cmdname>brew update</cmdname>
+Already up-to-date.</codeblock></stepxmp>
+        <stepresult>
+          <p>Homebrew responds with a list of any new or updated formulæ.</p></stepresult>
+      </step>
+      <step importance="optional">
+        <cmd>Check the version of DITA-OT that is available from Homebrew:</cmd>
+        <stepxmp><codeblock>$ <cmdname>brew info dita-ot</cmdname>
+<systemoutput>dita-ot: stable <keyword keyref="maintenance-version"/>
+DITA Open Toolkit is an implementation of the OASIS DITA specification
+https://www.dita-ot.org/
+/usr/local/Cellar/dita-ot/<keyword keyref="maintenance-version"/> (<varname>number of files</varname>, <varname>package size</varname>) *
+  Built from source on <varname>YYYY-MM-DD</varname> at <varname>hh:mm:ss</varname>
+From: https://github.com/Homebrew/homebrew-core/blob/master/Formula/dita-ot.rb
+==> Requirements
+Required: java >= 1.8 ✔</systemoutput>
+</codeblock></stepxmp>
+        <stepresult>
+          <p>The version of the DITA-OT formula is shown, along with basic information on the package.</p></stepresult>
+      </step>
+      <step>
+        <cmd>Install the <codeph>dita-ot</codeph> package:</cmd>
+        <stepxmp><codeblock>$ <cmdname>brew install dita-ot</cmdname>
+<systemoutput>Downloading…</systemoutput></codeblock></stepxmp>
+        <stepresult>
+          <p>Homebrew will automatically download the latest version of the toolkit, install it in a subfolder of the
+            local package Cellar and symlink the <cmdname>dita</cmdname> command to
+              <filepath>/usr/local/bin/dita</filepath>.</p></stepresult>
+      </step>
+      <step importance="optional">
+        <cmd>Verify the installation:</cmd>
+        <stepxmp><codeblock>$ <cmdname>which dita</cmdname>
+<systemoutput>/usr/local/bin/dita</systemoutput></codeblock></stepxmp>
+        <stepresult>
+          <p>The response confirms that the system will use the Homebrew-installed version of DITA-OT.</p></stepresult>
+      </step>
+      <step importance="optional">
+        <cmd>Check the DITA-OT version number:</cmd>
+        <stepxmp><codeblock>$ <cmdname>dita</cmdname> <parmname>--version</parmname>
+<systemoutput>DITA-OT version <keyword keyref="maintenance-version"/></systemoutput></codeblock></stepxmp>
+        <stepresult>The DITA-OT version number appears on the console.</stepresult>
+      </step>
+    </steps>
+    <result>
+      <p>You can now run the <cmdname>dita</cmdname> command to transform DITA content.</p></result>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/installing.ditamap

@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <title>Installing</title>
+
+  <topicref keyref="prerequisite-software"/>
+  <topicref keyref="determining-version-of-ditaot"/>
+  <!-- ↓ branch-filter ↓ -->
+  <topicref href="using-dita-command.dita"
+            keys="first-build-using-dita-command" locktitle="yes">
+    <topicmeta>
+      <navtitle>Building output</navtitle>
+    </topicmeta>
+    <ditavalref href="../resources/novice.ditaval">
+      <ditavalmeta>
+        <dvrResourcePrefix>first-build-</dvrResourcePrefix>
+      </ditavalmeta>
+    </ditavalref>
+  </topicref>
+  <!-- ↑ end-filtering ↑ -->
+  <topicref keyref="installing-via-homebrew"/>
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/log-files.dita

@@ -0,0 +1,116 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="loghandling">
+  <title>Log files</title>
+  <shortdesc>When you run DITA-OT, key information is logged on the screen. This information can also be written to a
+    log file. If you encounter a problem, you can analyze this information to determine the source of the problem and
+    then take action to resolve it.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Apache FOP<indexterm>log files</indexterm></indexterm>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>logging</indexterm></indexterm>
+        <indexterm>logging</indexterm>
+        <indexterm>Ant<indexterm>logging</indexterm></indexterm>
+        <indexterm>debugging<index-see-also>logging</index-see-also></indexterm>
+        <indexterm>Java<indexterm>logging</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <p>The logging behavior varies depending on whether you use the <cmdname>dita</cmdname> command or Ant to invoke a
+      toolkit build.</p>
+    <dl>
+      <dlentry>
+        <dt><cmdname>dita</cmdname> command</dt>
+        <dd>By default, only warning and error messages are written to the screen. If you use the
+            <parmname>-v</parmname> option, logging will be more verbose and informative messages are also written out.
+          The <parmname>-l</parmname> option can be used to write the log messages into a file.</dd>
+      </dlentry>
+      <dlentry>
+        <dt>Ant</dt>
+        <dd>By default, status information is written to the screen. If you issue the <parmname>-l</parmname> parameter,
+          the build runs silently and the information is written to a log file with the name and location that you
+          specified.</dd>
+      </dlentry>
+    </dl>
+    <section>
+      <title>Using other Ant loggers</title>
+      <p>You also can use other Ant loggers; see
+        <xref href="https://ant.apache.org/manual/listeners.html" format="html" scope="external">Listeners &amp;
+          Loggers</xref> in the Ant documentation for more information.</p>
+      <p>For example, you can use the <b>AnsiColorLogger</b> to colorize the messages written on the screen.</p>
+      <dl>
+        <dlentry>
+          <dt><cmdname>dita</cmdname> command</dt>
+          <dd>
+            <p>To use a custom Ant logger with the <cmdname>dita</cmdname> command, add the logger to the
+                <codeph>ANT_ARGS</codeph> environment variable by calling the following command before calling the
+                <cmdname>dita</cmdname> command:</p>
+            <codeblock>export ANT_ARGS="-logger org.apache.tools.ant.listener.AnsiColorLogger"</codeblock>
+            <p>Now you will get colorized messages when the <cmdname>dita</cmdname> command runs.</p>
+            <note type="tip">Environment variables can also be set permanently. See
+              <xref href="https://www.java.com/en/download/help/path.xml" format="html" scope="external">How do I set or
+                change the PATH system variable?</xref> for information on how to set the <codeph>PATH</codeph>
+              environment variable. You can set the <codeph>ANT_ARGS</codeph> environment variable in the same
+              way.</note>
+          </dd>
+        </dlentry>
+        <dlentry>
+          <dt>Ant</dt>
+          <dd>
+            <p>If you prefer to launch DITA-OT directly from Ant, you can also add the logger to the
+                <codeph>ANT_ARGS</codeph> environment variable, as explained above. You can also set the logger with the
+                <codeph>-logger</codeph> parameter when calling Ant.</p>
+            <codeblock>ant -logger org.apache.tools.ant.listener.AnsiColorLogger</codeblock>
+          </dd>
+        </dlentry>
+      </dl>
+    </section>
+    <section>
+      <title>FOP debug logging</title>
+      <div outputclass="div-index">
+        <indexterm>logback.xml</indexterm>
+        <indexterm>classpath<indexterm>logging</indexterm></indexterm>
+      </div>
+      <p>In PDF processing with <tm trademark="Apache" tmtype="tm">Apache</tm> FOP, DITA-OT 3.1 now uses the Simple
+        Logging Facade for Java (SLF4J), allowing for better control and formatting of FOP log messages. To reduce noise
+        on the console, all FOP messages are set to the Info level and hidden by default.</p>
+      <p>To enable debug logging, modify the <filepath>config/logback.xml</filepath> file or add your own
+          <filepath>logback.xml</filepath> to the classpath with a higher priority to override the default settings. For
+        more information, see the
+        <xref href="https://logback.qos.ch/manual/configuration.html" format="html" scope="external">Logback
+          configuration documentation</xref>.</p>
+      <note type="attention">Enabling FOP debug logging will dramatically increase the size of generated log
+        files.</note>
+    </section>
+    <!--<section><title>Analyze messages on the screen</title><p>During the building process, some information or messages
+        occur on the screen to tell you about the status, warnings, errors, or fatal errors. You need to analyze the
+        messages to solve the problems. <ul>
+          <li>If the build succeeded with some warning messages on the screen, it means that there are something
+            incorrect within the user input parameters or source DITA files; but you can still get the correct
+            output.</li>
+          <li>If the build succeeded with some error messages on the screen, it means that there are something incorrect
+            within the user input parameters or source DITA files; the output maybe not correct.</li>
+          <li>If the build failed with fatal error message on the screen, it means that there are something illegal or
+            invalid within the user input parameters or source DITA files; you may get no output, or wrong output.</li>
+        </ul>
+      </p></section>-->
+    <!--<section><title>Analyze messages in the log file</title><p>A log file in plain text format is generated in the log
+        directory, which has a name combined with both input file name and transformation type. You can open it and find more
+        detailed information, which are helpful for solving problems. You can use the same way introduced above to
+        analyze the messages and solve the problems.</p><p>The log directory can be specified by:</p><ul>
+        <li>using Ant, with argument <codeph>-logfile=<userinput>log-file</userinput></codeph></li>
+        <li>using command-line tool, the parameter <codeph>/logdir:<userinput>log-dir</userinput></codeph>.</li>
+      </ul></section>-->
+    <!--<section><title>Turn on debug mode</title><p>Under debug mode, diagnostic information, such as: environment
+        variables, stack trace, will be logged into the log file. These information can help the user or developer to go
+        deep into the problems and find the root cause.</p><p>By default, the debug mode is disabled. To turn on the
+        debug mode on, you need to follow the usage below: <ul>
+          <li>Append <codeph>-v</codeph> and <codeph>-Dargs.debug=yes</codeph> in Ant command.</li>
+          <li>Append <codeph>/d</codeph> or <codeph>/debug</codeph> in command-line tool.</li>
+        </ul></p></section>-->
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/lwdita-input.dita

@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="lwdita-input">
+  <title>Preview support for Lightweight DITA</title>
+  <titlealts>
+    <navtitle>Lightweight DITA</navtitle>
+  </titlealts>
+  <shortdesc>DITA-OT provides preview support for the authoring formats proposed for
+    <xref keyref="lwdita"/>, or “<term>LwDITA</term>”. The XDITA, MDITA and HDITA formats are alternative
+    representations of DITA content in XML, Markdown and HTML5.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>topicref</xmlelement></indexterm>
+        <indexterm><xmlatt>format</xmlatt></indexterm>
+        <indexterm>authoring formats<indexterm>Lightweight DITA</indexterm></indexterm>
+        <indexterm>metadata<indexterm>Lightweight DITA</indexterm></indexterm>
+        <indexterm>DITA 1.3<indexterm>Lightweight DITA</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <body>
+    <note type="attention">Since
+      <xref keyref="lwdita"/> has not yet been released as a formal specification, the implementation for XDITA, MDITA
+      and HDITA authoring formats is subject to change. Future versions of DITA Open Toolkit will be updated as LwDITA
+      evolves.</note>
+    <section>
+      <title>XDITA</title>
+      <p>XDITA is the LwDITA authoring format that uses XML to structure information. XDITA is a subset of DITA, with
+        new multimedia element types added to support interoperability with HTML5. XDITA is designed for users who want
+        to write DITA content but who do not want (or need) the full power of DITA.</p>
+      <p>The XDITA parser included in the <codeph>org.lwdita</codeph> plug-in provides preliminary support for XDITA
+        maps and XDITA topics.</p>
+      <p>To apply XDITA-specific processing to topics in an XDITA map or a full DITA 1.3 map, set the
+          <xmlatt>format</xmlatt> attribute on a <xmlelement>topicref</xmlelement> to <codeph>xdita</codeph>:</p>
+      <p>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;map>
+  &lt;topicref href="xdita-topic.xml" <b>format="xdita"</b>/>
+&lt;/map></codeblock>
+      </p>
+      <note type="tip">For examples of cross-format content sharing between topics in XDITA, HDITA, extended-profile
+        MDITA, and DITA 1.3, see the LwDITA sample files in the DITA-OT installation directory under
+          <filepath>plugins/org.oasis-open.xdita.v0_2_2/samples</filepath>.</note>
+    </section>
+    <section>
+      <title>MDITA</title>
+      <p>MDITA is the LwDITA authoring format based on Markdown. It is designed for users who want to write structured
+        content with the minimum of overhead, but who also want to take advantage of the reuse mechanisms associated
+        with the DITA standard and the multi-channel publishing afforded by standard DITA tooling.</p>
+      <p>Recent proposals for LwDITA include two profiles for authoring MDITA topics:</p>
+      <ul>
+        <li>The “<term>Core profile</term>” is based on
+          <xref keyref="gfm-spec"/> and includes elements that are common to many other Markdown implementations.</li>
+        <li>The “<term>Extended profile</term>” borrows additional features from other flavors of Markdown to represent
+          a broader range of DITA content with existing plain-text syntax conventions.</li>
+      </ul>
+      <p>The Markdown DITA parser included in the <codeph>org.lwdita</codeph> plug-in provides preliminary support for
+        these profiles and additional Markdown constructs as described in the syntax reference.</p>
+      <p>To apply LwDITA-specific processing to Markdown topics, set the <xmlatt>format</xmlatt> attribute to
+          <codeph>mdita</codeph>:</p>
+      <p>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;map>
+  &lt;topicref href="mdita-topic.md" <b>format="mdita"</b>/>
+&lt;/map></codeblock>
+      </p>
+      <p>In this case, the first paragraph in the topic will be treated as a short description, for example, and
+        additional metadata can be specified for the topic via a YAML front matter block.</p>
+      <note>Setting the <xmlatt>format</xmlatt> attribute to <codeph>mdita</codeph> triggers stricter parsing than the
+        more lenient document parsing approach that is applied to <codeph>markdown</codeph> documents.</note>
+      <note type="attention">The MDITA map format is not yet supported. To include Markdown content in publications, use
+        an XDITA map or a DITA 1.3 map.</note>
+    </section>
+
+    <section>
+      <title>HDITA</title>
+      <p>HDITA is the LwDITA authoring format based on HTML5, which is intended to support structured content authoring
+        with tools designed for HTML authoring. HDITA also uses custom data attributes to provide interoperability with
+        DITA.</p>
+      <p>The HDITA parser included in the <codeph>org.lwdita</codeph> plug-in provides preliminary support for these
+        constructs.</p>
+      <p>To apply LwDITA-specific processing to HTML topics, set the <xmlatt>format</xmlatt> attribute to
+          <codeph>hdita</codeph>:</p>
+      <p>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;map>
+  &lt;topicref href="hdita-topic.html" <b>format="hdita"</b>/>
+&lt;/map></codeblock>
+      </p>
+      <note type="attention">The HDITA map format is not yet supported. To include HDITA content, use an XDITA map or a
+        DITA 1.3 map.</note>
+    </section>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/markdown-dita-syntax-reference.dita

@@ -0,0 +1,357 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="markdown-dita-syntax-reference">
+  <title>Markdown DITA syntax reference</title>
+  <titlealts>
+    <navtitle>Markdown DITA syntax</navtitle>
+  </titlealts>
+  <shortdesc>Markdown DITA uses
+    <xref keyref="commonmark"/> as the underlying markup language.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Pandoc</indexterm>
+        <indexterm end="lwdita"/>
+        <indexterm>UTF</indexterm>
+        <indexterm>DITA<indexterm>specializations</indexterm></indexterm>
+        <indexterm>Markdown</indexterm>
+        <indexterm>CommonMark</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <body>
+    <p>Markdown DITA files must be UTF-8 encoded.</p>
+    <section id="titles-and-document-structure">
+      <title>Titles and document structure</title>
+      <p>Each header level will generate a topic and associated title:</p>
+      <codeblock outputclass="language-markdown" xml:space="preserve"># Topic title
+
+## Nested topic title</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;topic id="topic_title"&gt;
+  &lt;title&gt;Topic title&lt;/title&gt;
+  &lt;topic id="nested_topic_title"&gt;
+    &lt;title&gt;Nested topic title&lt;/title&gt;
+  &lt;/topic&gt;
+&lt;/topic&gt;</codeblock>
+      <p>Pandoc
+        <xref format="html#extension-header_attributes" href="http://pandoc.org/MANUAL.html#extension-header_attributes"
+          scope="external">header_attributes</xref> can be used to define <codeph>id</codeph> or
+          <codeph>outputclass</codeph> attributes:</p><codeblock outputclass="language-markdown" xml:space="preserve"># Topic title {#carrot .juice}</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;topic id="carrot" outputclass="juice"&gt;
+  &lt;title&gt;Topic title&lt;/title&gt;</codeblock>
+      <p>If topic ID is not defined using header_attributes, the ID is generated from title contents.</p>
+      <p>Pandoc
+        <xref format="html#extension-pandoc_title_block"
+          href="http://pandoc.org/MANUAL.html#extension-pandoc_title_block" scope="external">pandoc_title_block</xref>
+        extension can be used to group multiple level 1 headers under a common
+      title:</p><codeblock outputclass="language-markdown" xml:space="preserve">% Common title
+
+# Topic title
+
+# Second title</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;topic id="common_title"&gt;
+  &lt;title&gt;Common title&lt;/title&gt;
+  &lt;topic id="topic_title"&gt;
+    &lt;title&gt;Topic title&lt;/title&gt;
+  &lt;/topic&gt;
+  &lt;topic id="second_title"&gt;
+    &lt;title&gt;Second title&lt;/title&gt;
+  &lt;/topic&gt;
+&lt;/topic&gt;</codeblock></section>
+    <section id="topic-content">
+      <title>Topic content</title>
+      <p>In LwDITA compatible documents (MDITA) the first paragraph is treated as a <codeph>shortdesc</codeph> element.
+        In generic Markdown documents all paragraphs appear inside the <codeph>body</codeph> element.</p></section>
+    <section id="specialization-types">
+      <title>Specialization types</title>
+      <p>The following class values in
+        <xref format="html#extension-header_attributes" href="http://pandoc.org/MANUAL.html#extension-header_attributes"
+          scope="external">header_attributes</xref> have a special meaning on level 1 headers:</p>
+      <ul>
+        <li>
+          <p><codeph>concept</codeph></p></li>
+        <li>
+          <p><codeph>task</codeph></p></li>
+        <li>
+          <p><codeph>reference</codeph></p></li>
+      </ul>
+      <p>They can be used to change the Markdown DITA topic type to one of the built-in structural specialization
+        types.</p><codeblock outputclass="language-markdown" xml:space="preserve"># Task {.task}
+
+Context
+
+1.  Command
+
+    Info.</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;task id="task"&gt;
+  &lt;title&gt;Task &lt;/title&gt;
+  &lt;taskbody&gt;
+    &lt;context&gt;
+      &lt;p&gt;Context&lt;/p&gt;
+    &lt;/context&gt;
+    &lt;steps&gt;
+      &lt;step&gt;
+        &lt;cmd&gt;Command&lt;/cmd&gt;
+        &lt;info&gt;
+          &lt;p&gt;Info.&lt;/p&gt;
+        &lt;/info&gt;
+      &lt;/step&gt;
+    &lt;/steps&gt;
+  &lt;/taskbody&gt;
+&lt;/task&gt;</codeblock></section>
+    <section id="sections">
+      <title>Sections</title>
+      <p>The following class values in
+        <xref format="html#extension-header_attributes" href="http://pandoc.org/MANUAL.html#extension-header_attributes"
+          scope="external">header_attributes</xref> have a special meaning on header levels other than 1:</p>
+      <ul>
+        <li>
+          <p><codeph>section</codeph></p></li>
+        <li>
+          <p><codeph>example</codeph></p></li>
+      </ul>
+      <p>They are used to generate
+        <xref format="html" href="http://docs.oasis-open.org/dita/v1.2/os/spec/langref/section.html" scope="external"
+            ><codeph>section</codeph></xref> and
+        <xref format="html" href="http://docs.oasis-open.org/dita/v1.2/os/spec/langref/example.html" scope="external"
+            ><codeph>example</codeph></xref>
+      elements:</p><codeblock outputclass="language-markdown" xml:space="preserve"># Topic title
+
+## Section title {.section}
+
+## Example title {.example}</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;topic id="topic_title"&gt;
+  &lt;title&gt;Topic title&lt;/title&gt;
+  &lt;body&gt;
+    &lt;section&gt;
+      &lt;title&gt;Section title&lt;/title&gt;
+    &lt;/section&gt;
+    &lt;example&gt;
+      &lt;title&gt;Example title&lt;/title&gt;
+    &lt;/example&gt;
+  &lt;/body&gt;
+&lt;/topic&gt;</codeblock></section>
+    <section id="links">
+      <title>Links</title>
+      <p>The format of local link targets is detected based on file extension. The following extensions are treated as
+        DITA files:</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <tgroup cols="2">
+          <colspec/>
+          <colspec/>
+          <thead>
+            <row>
+              <entry>extension</entry>
+              <entry>format</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry><codeph>.dita</codeph></entry>
+              <entry><codeph>dita</codeph></entry>
+            </row>
+            <row>
+              <entry><codeph>.xml</codeph></entry>
+              <entry><codeph>dita</codeph></entry>
+            </row>
+            <row>
+              <entry><codeph>.md</codeph></entry>
+              <entry><codeph>markdown</codeph></entry>
+            </row>
+            <row>
+              <entry><codeph>.markdown</codeph></entry>
+              <entry><codeph>markdown</codeph></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <p>All other link targets use <codeph>format</codeph> from file extension and are treated as non-DITA files.
+        Absolute links targets are treated as external scope
+      links:</p><codeblock outputclass="language-markdown" xml:space="preserve">[Markdown](test.md)
+[DITA](test.dita)
+[HTML](test.html)
+[External](http://www.example.com/test.html)</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;xref href="test.md"&gt;Markdown&lt;/xref&gt;
+&lt;xref href="test.dita"&gt;DITA&lt;/xref&gt;
+&lt;xref href="test.html" format="html"&gt;HTML&lt;/xref&gt;
+&lt;xref href="http://www.example.com/test.html" format="html" scope="external"&gt;External&lt;/xref&gt;</codeblock></section>
+    <section id="images">
+      <title>Images</title>
+      <div outputclass="div-index">
+        <indexterm>images<indexterm>Markdown</indexterm></indexterm>
+      </div>
+      <p>Images used in inline content will result in inline placement. If a block level image contains a title, it will
+        be treated as an image wrapped in
+      figure:</p><codeblock outputclass="language-markdown" xml:space="preserve">An inline ![Alt](test.jpg).
+
+![Alt](test.jpg)
+
+![Alt](test.jpg "Title")</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;p&gt;An inline &lt;image href="test.jpg"&gt;&lt;alt&gt;Alt&lt;/alt&gt;&lt;/image&gt;.&lt;/p&gt;
+&lt;image href="test.jpg" placement="break"&gt;
+  &lt;alt&gt;Alt&lt;/alt&gt;
+&lt;/image&gt;
+&lt;fig&gt;
+  &lt;title&gt;Title&lt;/title&gt;
+  &lt;image href="test.jpg"&gt;
+    &lt;alt&gt;Alt&lt;/alt&gt;
+  &lt;/image&gt;
+&lt;/fig&gt;</codeblock></section>
+    <section id="key-references">
+      <title>Key references</title>
+      <p>Key reference can be used with
+        <xref format="html" href="http://spec.commonmark.org/0.18/#shortcut-reference-link" scope="external">shortcut
+          reference
+      links</xref>:</p><codeblock outputclass="language-markdown" xml:space="preserve">[key]
+![image-key]</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;xref keyref="key"/&gt;
+&lt;image keyref="image-key"/&gt;</codeblock></section>
+    <section id="inline">
+      <title>Inline</title>
+      <p>The following inline elements are
+      supported:</p><codeblock outputclass="language-markdown" xml:space="preserve">**bold**
+*italic*
+`code`
+~~strikethrough~~</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;b&gt;bold&lt;/b&gt;
+&lt;i&gt;italic&lt;/i&gt;
+&lt;codeph&gt;code&lt;/codeph&gt;
+&lt;ph status="deleted"&gt;strikethrough&lt;/ph&gt;</codeblock></section>
+    <section id="lists">
+      <title>Lists</title>
+      <p>Unordered can be marked up with either hyphen or ampersand:</p><codeblock outputclass="language-markdown" xml:space="preserve">*   one
+*   two
+    -   three
+    -   four</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;ul&gt;
+  &lt;li&gt;one&lt;/li&gt;
+  &lt;li&gt;two
+    &lt;ul&gt;
+      &lt;li&gt;three&lt;/li&gt;
+      &lt;li&gt;four&lt;/li&gt;
+    &lt;/ul&gt;
+  &lt;/li&gt;
+&lt;/ul&gt;</codeblock>
+      <p>Ordered can be marked up with either number or number sign, followed by a period:</p><codeblock outputclass="language-markdown" xml:space="preserve">1.  one
+2.  two
+    #.  three
+    #.  four</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;ol&gt;
+  &lt;li&gt;one&lt;/li&gt;
+  &lt;li&gt;two
+    &lt;ol&gt;
+      &lt;li&gt;three&lt;/li&gt;
+      &lt;li&gt;four&lt;/li&gt;
+    &lt;/ul&gt;
+  &lt;/li&gt;
+&lt;/ul&gt;</codeblock>
+      <p>Definition lists use the
+        <xref format="html" href="http://michelf.com/projects/php-markdown/extra/#def-list" scope="external">PHP
+          Markdown Extra</xref> format:</p><codeblock outputclass="language-markdown" xml:space="preserve">Term
+:   Definition.</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;dl&gt;
+  &lt;delentry&gt;
+    &lt;dt&gt;Term&lt;/dt&gt;
+    &lt;dd&gt;Defintion.&lt;/dd&gt;
+  &lt;/delentry&gt;
+&lt;/dl&gt;</codeblock>
+      <p>Each definition entry must have only one term and contain only inline content.</p></section>
+    <section id="tables">
+      <title>Tables</title>
+      <div outputclass="div-index">
+        <indexterm>tables<indexterm>Markdown</indexterm></indexterm>
+      </div>
+      <p>Tables use
+        <xref format="html" href="http://fletcherpenney.net/multimarkdown/" scope="external">MultiMarkdown</xref> table
+        extension format:</p><codeblock outputclass="language-markdown" xml:space="preserve">| First Header | Second Header | Third Header |
+| ------------ | :-----------: | -----------: |
+| Content      | *Long Cell*                 ||
+| Content      | **Cell**      | Cell         |</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;table&gt;
+  &lt;tgroup cols="3"&gt;
+    &lt;colspec colname="col1"/&gt;
+    &lt;colspec colname="col2" align="center"/&gt;
+    &lt;colspec colname="col3" align="right"/&gt;
+    &lt;thead&gt;
+      &lt;row&gt;
+        &lt;entry&gt;First Header &lt;/entry&gt;
+        &lt;entry&gt;Second Header &lt;/entry&gt;
+        &lt;entry&gt;Third Header &lt;/entry&gt;
+      &lt;/row&gt;
+    &lt;/thead&gt;
+    &lt;tbody&gt;
+      &lt;row&gt;
+        &lt;entry&gt;Content &lt;/entry&gt;
+        &lt;entry namest="col2" nameend="col3"&gt;&lt;i&gt;Long Cell&lt;/i&gt;&lt;/entry&gt;
+      &lt;/row&gt;
+      &lt;row&gt;
+        &lt;entry&gt;Content &lt;/entry&gt;
+        &lt;entry&gt;&lt;b&gt;Cell&lt;/b&gt;&lt;/entry&gt;
+        &lt;entry&gt;Cell &lt;/entry&gt;
+      &lt;/row&gt;
+    &lt;/tbody&gt;
+  &lt;/tgroup&gt;
+&lt;/table&gt;</codeblock>
+      <p>Table cells may only contain inline content and column spans; block content and row spans are not supported by
+        Markdown DITA.</p></section>
+    <section id="metadata">
+      <title>Metadata</title>
+      <div outputclass="div-index">
+        <indexterm>metadata<indexterm>Lightweight DITA</indexterm></indexterm>
+        <indexterm>metadata<indexterm>Markdown</indexterm></indexterm>
+        <indexterm>Pandoc</indexterm>
+      </div>
+      <p>
+        <xref format="html" href="http://www.yaml.org/" scope="external">YAML</xref> metadata block as defined in Pandoc
+        <xref format="html#extension-yaml_metadata_block"
+          href="http://pandoc.org/MANUAL.html#extension-yaml_metadata_block" scope="external"
+          >pandoc_metadata_block</xref> can be used to specify different metadata elements. The supported elements
+        are:</p>
+      <ul>
+        <li>
+          <p><codeph>author</codeph></p></li>
+        <li>
+          <p><codeph>source</codeph></p></li>
+        <li>
+          <p><codeph>publisher</codeph></p></li>
+        <li>
+          <p><codeph>permissions</codeph></p></li>
+        <li>
+          <p><codeph>audience</codeph></p></li>
+        <li>
+          <p><codeph>category</codeph></p></li>
+        <li>
+          <p><codeph>keyword</codeph></p></li>
+        <li>
+          <p><codeph>resourceid</codeph></p></li>
+      </ul>
+      <p>Unrecognized keys are output using <codeph>data</codeph>
+      element.</p><codeblock outputclass="language-markdown" xml:space="preserve">---
+author:
+  - Author One
+  - Author Two
+source: Source
+publisher: Publisher
+permissions: Permissions
+audience: Audience
+category: Category
+keyword:
+  - Keyword1
+  - Keyword2
+resourceid:
+  - Resourceid1
+  - Resourceid2
+workflow: review
+---
+
+# Sample with YAML header</codeblock><codeblock outputclass="language-xml" xml:space="preserve">&lt;title&gt;Sample with YAML header&lt;/title&gt;
+&lt;prolog&gt;
+  &lt;author&gt;Author One&lt;/author&gt;
+  &lt;author&gt;Author Two&lt;/author&gt;
+  &lt;source&gt;Source&lt;/source&gt;
+  &lt;publisher&gt;Publisher&lt;/publisher&gt;
+  &lt;permissions view="Permissions"/&gt;
+  &lt;metadata&gt;
+    &lt;audience audience="Audience"/&gt;
+    &lt;category&gt;Category&lt;/category&gt;
+    &lt;keywords&gt;
+      &lt;keyword&gt;Keyword1&lt;/keyword&gt;
+      &lt;keyword&gt;Keyword2&lt;/keyword&gt;
+    &lt;/keywords&gt;
+  &lt;/metadata&gt;
+  &lt;resourceid appid="Resourceid1"/&gt;
+  &lt;resourceid appid="Resourceid2"/&gt;
+  &lt;data name="workflow" value="review"/&gt;
+&lt;/prolog&gt;</codeblock></section>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/markdown-input.dita

@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="markdown-input">
+  <title>Markdown content</title>
+  <shortdesc>
+    <xref keyref="markdown"/> is a lightweight markup language that allows you to write using an easy-to-read plain text
+    format and convert to structurally valid markup as necessary.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlatt>format</xmlatt></indexterm>
+        <indexterm>authoring formats<indexterm>Markdown</indexterm></indexterm>
+        <indexterm>Markdown</indexterm>
+        <indexterm>CommonMark</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>In the words of its creators:</p>
+
+    <lq>“The overriding design goal for Markdown’s formatting syntax is to make it as readable as possible. The idea is
+      that a Markdown-formatted document should be publishable as-is, as plain text, without looking like it’s been
+      marked up with tags or formatting instructions.”</lq>
+
+    <p>DITA Open Toolkit now allows you to use Markdown files directly in topic references and export DITA content as
+      Markdown.</p>
+
+    <p>These features enable lightweight authoring scenarios that allow subject matter experts to contribute to DITA
+      publications without writing in XML, and support publishing workflows that include DITA content in Markdown-based
+      publishing systems.</p>
+
+    <section>
+      <title>Adding Markdown topics</title>
+      <p>To add a Markdown topic to a DITA publication, create a topic reference in your map and set the
+          <xmlatt>format</xmlatt> attribute to <codeph>markdown</codeph> so the toolkit will recognize the source file
+        as Markdown and convert it to DITA:</p>
+      <p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version="1.0" encoding="utf-8"?>
+&lt;!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+&lt;map>
+  &lt;topicref href="markdown-dita-topic.md" <b>format="markdown"</b>/>
+&lt;/map></codeblock></p>
+      <p>The <codeph>markdown</codeph> format uses a relatively lenient document parsing approach to support a wide
+        range of content and Markdown syntax constructs. </p>
+      <note>The Markdown support is based on
+        <xref keyref="commonmark"/>, a strongly defined, highly compatible specification of Markdown.</note>
+    </section>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-ant-to-dita.dita

@@ -0,0 +1,102 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA General Task//EN" "generalTask.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="migrating-ant-to-dita">
+  <title>Migrating Ant builds to use the <cmdname>dita</cmdname> command</title>
+  <titlealts>
+    <navtitle>Migrating Ant builds</navtitle>
+  </titlealts>
+  <shortdesc>Although DITA Open Toolkit still supports Ant builds, switching to the <cmdname>dita</cmdname> command
+    offers a simpler command interface, sets all required environment variables and allows you to run DITA-OT without
+    setting up anything beforehand.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Ant<indexterm><xmlelement>exec</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>dita-cmd</xmlelement></indexterm><indexterm><cmdname>dita</cmdname>
+            command, benefits of</indexterm></indexterm>
+        <indexterm>dita-cmd</indexterm>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>migrating Ant scripts</indexterm></indexterm>
+        <indexterm>classpath<indexterm><cmdname>dita</cmdname> command</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>Building output with the <cmdname>dita</cmdname> command is often easier than using Ant. In particular, you can
+        use <filepath>.properties</filepath> files to specify sets of DITA-OT parameters for each build.</p>
+      <p>You can include the <cmdname>dita</cmdname> command in shell scripts to perform multiple builds.</p>
+      <note conref="../resources/conref-task.dita#ID/dita-in-path"/>
+    </context>
+    <steps>
+      <step>
+        <cmd>In your Ant build file, identify the properties set in each build target.</cmd>
+        <info>
+          <note>Some build parameters might be specified as properties of the project as a whole. You can refer to a
+            build log to see a list of all properties that were set for the build.</note>
+        </info>
+      </step>
+      <step>
+        <cmd>Create a <filepath>.properties</filepath> file for each build and specify the needed build parameters, one
+          per line, in the format <codeph>name = value</codeph>.</cmd>
+      </step>
+      <step>
+        <cmd>Use the <cmdname>dita</cmdname> command to perform each build, referencing your
+            <filepath>.properties</filepath> with the <parmname>--propertyfile</parmname>=<varname>file</varname>
+          option.</cmd>
+      </step>
+    </steps>
+    <example>
+      <title>Example: Ant build</title>
+      <p>Prior to DITA-OT 2.0, an Ant build like this was typically used to define the properties for each target.</p>
+      <p>Sample build file: <filepath id="samples-dir"
+          ><varname>dita-ot-dir</varname>/docsrc/samples</filepath><filepath>/ant_sample/build-chm-pdf.xml</filepath>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/ant_sample/build-chm-pdf.xml"/></codeblock></p></example>
+    <example>
+      <title>Example: <filepath>.properties</filepath> files with <cmdname>dita</cmdname> command</title>
+      <p>The following <filepath>.properties</filepath> files and <cmdname>dita</cmdname> commands are equivalent to the
+        example Ant build.</p>
+      <p>Sample <filepath>.properties</filepath> file: <filepath conref="../resources/conref-task.dita#ID/samples-dir"
+          /><filepath>/properties/chm.properties</filepath></p>
+      <p>
+        <codeblock outputclass="language-properties normalize-space show-line-numbers show-whitespace"><coderef href="../samples/properties/chm.properties"/></codeblock></p>
+      <p>Sample <filepath>.properties</filepath> file: <filepath conref="../resources/conref-task.dita#ID/samples-dir"
+          /><filepath>/properties/pdf.properties</filepath></p>
+      <p>
+        <codeblock outputclass="language-properties normalize-space show-line-numbers show-whitespace"><coderef href="../samples/properties/pdf.properties"/></codeblock></p>
+      <p>Run from <filepath conref="../resources/conref-task.dita#ID/samples-dir"/>:</p>
+      <codeblock><cmdname>dita</cmdname> <parmname>--input</parmname>=<filepath>sequence.ditamap</filepath> <parmname>--format</parmname>=<option>htmlhelp</option> \
+     <parmname>--propertyfile</parmname>=<filepath>properties/chm.properties</filepath>
+<cmdname>dita</cmdname> <parmname>--input</parmname>=<filepath>taskbook.ditamap</filepath> <parmname>--format</parmname>=<option>pdf</option> \
+     <parmname>--propertyfile</parmname>=<filepath>properties/pdf.properties</filepath></codeblock>
+    </example>
+    <example>
+      <title>Example: Call the <cmdname>dita</cmdname> command from an Ant build</title>
+      <p>In some cases, you might still want to use an Ant build to implement some pre- or post-processing steps, but
+        also want the convenience of using the <cmdname>dita</cmdname> command with <filepath>.properties</filepath>
+        files to define the parameters for each build. This can be accomplished with Ant’s <xmlelement>exec</xmlelement>
+        task.</p>
+      <p>This example uses a <xmlelement>dita-cmd</xmlelement> Ant macro defined in the <filepath
+          conref="../resources/conref-task.dita#ID/samples-dir"/><filepath>/ant_sample/dita-cmd.xml</filepath> file:</p>
+      <p>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/ant_sample/dita-cmd.xml#line=11,32"/></codeblock></p>
+      <p>You can use this macro in your Ant build to call the <cmdname>dita</cmdname> command and pass the
+          <parmname>input</parmname>, <parmname>format</parmname> and <parmname>propertyfile</parmname> parameters as
+        follows:
+        <codeblock outputclass="language-xml">&lt;dita-cmd input="sample.ditamap" format="pdf" propertyfile="sample.properties"/></codeblock>
+      </p>
+      <p>This approach allows you to use Ant builds to perform additional tasks at build time while allowing the
+          <cmdname>dita</cmdname> command to set the classpath and ensure that all necessary JAR libraries are
+        available.</p>
+      <note>The attributes defined in the Ant macro are required and must be supplied each time the task is run. To set
+        optional parameters in one build (but not another), use different <filepath>.properties</filepath> files for
+        each build.</note>
+      <p>Sample build file: <filepath conref="../resources/conref-task.dita#ID/samples-dir"
+          /><filepath>/ant_sample/build-chm-pdf-hybrid.xml</filepath></p>
+      <p>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/ant_sample/build-chm-pdf-hybrid.xml"/></codeblock>
+      </p>
+    </example>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-1.5.4.dita

@@ -0,0 +1,191 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="ID" rev="1.5.4">
+
+  <title>Migrating to release 1.5.4</title>
+  <titlealts>
+    <navtitle>To 1.5.4</navtitle>
+  </titlealts>
+
+  <shortdesc>DITA-OT 1.5.4 adds new extension points to configure behavior based on file extensions, declare print
+    transformation types and add mappings to the PDF configuration catalog file. PDF output supports mirrored page
+    layout and uses new font family definitions. Support for several new languages was added for PDF and XHTML
+    output.</shortdesc>
+  
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>deprecated features<indexterm><codeph>print_transtypes</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>page-margin-left</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>page-margin-right</codeph></indexterm></indexterm>
+        <indexterm>languages<indexterm>supported</indexterm></indexterm>
+        <indexterm>Finnish</indexterm>
+        <indexterm>Hebrew</indexterm>
+        <indexterm>Indonesian</indexterm>
+        <indexterm>Kazakh</indexterm>
+        <indexterm>Malay</indexterm>
+        <indexterm>Romanian</indexterm>
+        <indexterm>Russian</indexterm>
+        <indexterm>Swedish</indexterm>
+        <indexterm>I18N<indexterm><parmname>org.dita.pdf2.i18n.enabled</parmname></indexterm></indexterm>
+        <indexterm end="migrate"/>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section id="section_vc5_gld_g2">
+      <title>Configuration properties file changes</title>
+      <p>In previous versions, the <filepath>lib/configuration.properties</filepath> file was generated by the
+        integration process. Integration has been changed to generate
+          <filepath>lib/org.dita.dost.platform/plugin.properties</filepath> and the role of the old
+          <filepath>lib/configuration.properties</filepath> has been changed to contain defaults and configuration
+        options, such as default language.</p>
+      <p>The <codeph>dita.plugin.org.dita.*.dir</codeph> properties have been changed to point to the DITA-OT base
+        directory.</p>
+      <p>To allow access to configuration files, the <filepath>lib</filepath> directory needs to be added to the Java
+        classpath.</p>
+    </section>
+    <section>
+      <title>New plug-in extension points </title>
+      <p>New plug-in extension points have been added allow configuring DITA-OT behavior based on file extensions.</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <tgroup cols="3">
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <thead>
+            <row>
+              <entry>Extension point</entry>
+              <entry>Description</entry>
+              <entry>Default values</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry><parmname>dita.topic.extension</parmname></entry>
+              <entry>DITA topic</entry>
+              <entry><filepath>.dita</filepath>, <filepath>.xml</filepath></entry>
+            </row>
+            <row>
+              <entry><parmname>dita.map.extensions</parmname></entry>
+              <entry>DITA map</entry>
+              <entry><filepath>.ditamap</filepath></entry>
+            </row>
+            <row>
+              <entry><parmname>dita.html.extensions</parmname></entry>
+              <entry>HTML file</entry>
+              <entry><filepath>.html</filepath>, <filepath>.htm</filepath></entry>
+            </row>
+            <row>
+              <entry><parmname>dita.resource.extensions</parmname></entry>
+              <entry>Resource file</entry>
+              <entry><filepath>.pdf</filepath>, <filepath>.swf</filepath></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <p>Both HTML and resource file extensions are used to determine if a file in source is copied to output.</p>
+      <p>A new plug-in extension point has been added to declare transformation types as print types.</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <tgroup cols="2">
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <thead>
+            <row>
+              <entry>Extension point</entry>
+              <entry>Description</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry><parmname>dita.transtype.print</parmname></entry>
+              <entry>Declare transformation type as a print type.</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <p>The <codeph>print_transtypes</codeph> property in <filepath>integrator.properties</filepath> has been
+        deprecated in favor of <parmname>dita.transtype.print</parmname>.</p>
+    </section>
+    <section>
+      <title>Plugin URI scheme</title>
+      <p>Support for the <keyword>plugin</keyword> URI scheme has been added to XSLT stylesheets. Plug-ins can refer to
+        files in other plug-ins without hard-coding relative paths, for example: </p>
+      <codeblock outputclass="language-xml" xml:space="preserve">&lt;xsl:import href="plugin:org.dita.pdf2:xsl/fo/topic2fo_1.0.xsl"/&gt;</codeblock>
+    </section>
+    <section>
+      <title>XHTML</title>
+      <p>Support for the following languages has been added:</p>
+      <ul>
+        <li>Indonesian</li>
+        <li>Kazakh</li>
+        <li>Malay</li>
+      </ul>
+    </section>
+    <section>
+      <title>PDF</title>
+      <p>Support for mirrored page layout was added. The default is the unmirrored layout. The following XSLT
+        configuration variables have been deprecated:</p>
+      <ul id="ul_hkv_oyj_bd">
+        <li><codeph>page-margin-left</codeph></li>
+        <li><codeph>page-margin-right</codeph></li>
+      </ul>
+      <p>The following variables should be used instead to control page margins:</p>
+      <ul id="ul_yda_wyj_bd">
+        <li><codeph>page-margin-outside</codeph></li>
+        <li><codeph>page-margin-inside</codeph></li>
+      </ul>
+      <p>The <parmname>args.bookmap-order</parmname> property has been added to control how front and back matter are
+        processed in bookmaps. The default is to reorder the frontmatter content as in previous releases.</p>
+      <p>A new extension point has been added to add mappings to the PDF configuration catalog file.</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <tgroup cols="2">
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <thead>
+            <row>
+              <entry>Extension point</entry>
+              <entry>Description</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry><parmname>org.dita.pdf2.catalog.relative</parmname></entry>
+              <entry>Configuration catalog includes.</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <p>Support for the following languages has been added:</p>
+      <ul>
+        <li>Finnish</li>
+        <li>Hebrew</li>
+        <li>Romanian</li>
+        <li>Russian</li>
+        <li>Swedish</li>
+      </ul>
+      <p>PDF processing no longer copies images or generates XSL FO to output directory. Instead, the temporary
+        directory is used for all temporary files and source images are read directly from source directory. The legacy
+        processing model can be enabled by setting <parmname>org.dita.pdf2.use-out-temp</parmname> to
+          <option>true</option> in configuration properties; support for the legacy processing model may be removed in
+        future releases.</p>
+      <p>Support for FrameMaker index syntax has been disabled by default. To enable FrameMaker index syntax, set
+          <parmname>org.dita.pdf2.index.frame-markup</parmname> to <option>true</option> in configuration
+        properties.</p>
+      <p>A configuration option has been added to disable internationalization (I18N) font processing and use
+        stylesheet-defined fonts. To disable I18N font processing, set <parmname>org.dita.pdf2.i18n.enabled</parmname>
+        to <codeph>false</codeph> in configuration properties.</p>
+      <p>The XSLT parameters <parmname>customizationDir</parmname> and <parmname>fileProfilePrefix</parmname> have been
+        removed in favor of the <parmname>customizationDir.url</parmname> parameter.</p>
+      <p>A new shell stylesheet has been added for FOP and other shell stylesheets have also been revised. Plug-ins
+        which have their own shell stylesheets for PDF processing should make sure all required stylesheets are
+        imported.</p>
+      <p>Font family definitions in stylesheets have been changed from Sans, Serif, and Monospaced to sans-serif, serif,
+        and monospace, respectively. The I18N font processing still uses the old logical names and aliases are used to
+        map the new names to old ones. </p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-1.6.dita

@@ -0,0 +1,197 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="ID" rev="1.6">
+
+  <title>Migrating to release 1.6</title>
+  <titlealts>
+    <navtitle>To 1.6</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 1.6, various <filepath>demo</filepath> plug-ins were removed along with many deprecated
+    properties, targets, templates and modes. The PDF2 transformation no longer supports the beta version of DITA from
+    IBM, the "bkinfo" demo plug-in, or <filepath>layout-masters.xml</filepath> configuration.</shortdesc>
+  
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>deprecated features<indexterm><filepath>demo</filepath> folder</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>workdir</codeph> processing instruction</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>workdir</codeph> processing instruction</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>topic pull templates, list of</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>"bkinfo" demo plug-in</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><filepath>layout-masters.xml</filepath></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>PDF2 templates, list of</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>XHTML templates, list of</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>ODT templates, list of</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section>
+      <p>Support for the old DITAVAL format (used before OASIS added DITAVAL to the standard in 2007) has been
+        removed.</p>
+      <p>The <filepath>demo</filepath> folder has been deprecated and the following plug-ins have been moved to the
+          <filepath>plugins</filepath> folder:</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <tgroup cols="2">
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <thead>
+            <row>
+              <entry>old path</entry>
+              <entry>new path</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry><filepath>demo/dita11</filepath></entry>
+              <entry><filepath>plugins/org.dita.specialization.dita11</filepath></entry>
+            </row>
+            <row>
+              <entry><filepath>demo/dita132</filepath></entry>
+              <entry><filepath>plugins/org.dita.specialization.dita132</filepath></entry>
+            </row>
+            <row>
+              <entry><filepath>demo/eclipsemap</filepath></entry>
+              <entry><filepath>plugins/org.dita.specialization.eclipsemap</filepath></entry>
+            </row>
+            <row>
+              <entry><filepath>demo/fo</filepath></entry>
+              <entry><filepath>plugins/org.dita.pdf2</filepath></entry>
+            </row>
+            <row>
+              <entry><filepath>demo/tocjs</filepath></entry>
+              <entry><filepath>plugins/com.sophos.tocjs</filepath></entry>
+            </row>
+            <!-- These plugins are pulled from ext-plugins during build -->
+            <row>
+              <entry><filepath>demo/h2d</filepath></entry>
+              <entry><filepath>plugins/h2d</filepath></entry>
+            </row>
+            <row>
+              <entry><filepath>demo/legacypdf</filepath></entry>
+              <entry><filepath>plugins/legacypdf</filepath></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <p>The remaining plug-ins in the demo folder have been moved to a separate repository at <xref
+          href="https://github.com/dita-ot/ext-plugins" scope="external" format="html"
+          >github.com/dita-ot/ext-plugins</xref>.</p>
+    </section>
+    <section>
+      <p>The deprecated property <codeph>dita.input.valfile</codeph> should be replaced with the new argument property
+          <codeph>args.filter</codeph>.</p>
+      <p>The <codeph>dita-preprocess</codeph> target has been removed and dependencies should be replaced with a target
+        sequence <codeph>build-init, preprocess</codeph>.</p>
+      <p>Support for the <codeph>args.message.file</codeph> argument has been removed as message configuration has
+        become static configuration.</p>
+      <p>The <codeph>workdir</codeph> processing instruction has been deprecated in favor of
+          <codeph>workdir-uri</codeph>. The only difference between the two processing instructions is that
+          <codeph>workdir-uri</codeph> contains a URI instead of a system path.</p>
+    </section>
+    <section>
+      <title>Preprocessing</title>
+      <p>The following deprecated templates and modes have been removed in topic pull stylesheets:</p>
+      <ul>
+        <li>inherit</li>
+        <li>get-stuff</li>
+        <li>verify-type-attribute</li>
+        <li>classval</li>
+        <li>getshortdesc</li>
+        <li>getlinktext</li>
+        <li>blocktext</li>
+        <li>figtext</li>
+        <li>tabletext</li>
+        <li>litext</li>
+        <li>fntext</li>
+        <li>dlentrytext</li>
+        <li>firstclass</li>
+        <li>invalid-list-item</li>
+        <li>xref</li>
+      </ul>
+    </section>
+    <section>
+      <title>PDF2</title>
+      <p>The following deprecated items are no longer supported in the PDF transform:</p>
+      <ul>
+        <li>Support for the beta version of DITA, available from IBM before the OASIS standard was created in 2005.</li>
+        <li>Support for the "bkinfo" demo plug-in, used to support book metadata before OASIS created the BookMap format
+          in 2007.</li>
+        <li>Support for <filepath>layout-masters.xml</filepath> configuration. Plug-ins should use the
+            <codeph>createDefaultLayoutMasters</codeph> template instead.</li>
+      </ul>
+      <p>The following extension-points have been added:</p>
+      <ul>
+        <li><codeph>dita.conductor.pdf2.param</codeph> to add XSLT parameters to XSL FO transformation.</li>
+      </ul>
+      <p>Custom PDF2 shell stylesheets need to be revised to not include separate IBM and OASIS DITA stylesheets. The
+            <filepath><varname>*</varname>_1.0.xsl</filepath> stylesheets have been removed and their imports must be
+        removed from shell stylesheets.</p>
+      <p>The following template modes have been deprecated:</p>
+      <ul>
+        <li>toc-prefix-text</li>
+        <li>toc-topic-text</li>
+      </ul>
+      <p>The following named templates have been removed:</p>
+      <ul>
+        <li>processTopic</li>
+        <li>createMiniToc</li>
+        <li>processTopicTitle</li>
+        <li>createTopicAttrsName</li>
+        <li>processConcept</li>
+        <li>processReference</li>
+        <li>getTitle</li>
+        <li>placeNoteContent</li>
+        <li>placeImage</li>
+        <li>processUnknowType</li>
+        <li>insertReferenceTitle</li>
+        <li>buildRelationships</li>
+        <li>processTask</li>
+      </ul>
+      <p>The main FO generation process now relies on the merging process to rewrite duplicate IDs. The default merging
+        process did this already in previous releases, but now also custom merging processes must fulfill the duplicate
+        ID rewrite requirement.</p>
+    </section>
+    <section>
+      <title>XHTML</title>
+      <p>The following named templates have been deprecated:</p>
+      <ul>
+        <li>make-index-ref</li>
+      </ul>
+      <p>The following deprecated templates have been removed:</p>
+      <ul>
+        <li>revblock-deprecated</li>
+        <li>revstyle-deprecated</li>
+        <li>start-revision-flag-deprecated</li>
+        <li>end-revision-flag-deprecated</li>
+        <li>concept-links</li>
+        <li>task-links</li>
+        <li>reference-links</li>
+        <li>relinfo-links</li>
+        <li>sort-links-by-role</li>
+        <li>create-links</li>
+        <li>add-linking-attributes</li>
+        <li>add-link-target-attribute</li>
+        <li>add-user-link-attributes</li>
+      </ul>
+      <p>The removed templates have been replaced by other templates in earlier releases and plug-ins should be changed
+        to use the new templates.</p>
+    </section>
+    <section>
+      <title>ODT</title>
+      <p>The following deprecated templates have been removed:</p>
+      <ul>
+        <li>revblock-deprecated</li>
+        <li>revstyle-deprecated</li>
+        <li>start-revision-flag-deprecated</li>
+        <li>end-revision-flag-deprecated</li>
+      </ul>
+      <p>The removed templates have been replaced by other templates in earlier releases and plug-ins should be changed
+        to use the new templates.</p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-1.7.dita

@@ -0,0 +1,104 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="ID" rev="1.7">
+
+  <title>Migrating to release 1.7</title>
+  <titlealts>
+    <navtitle>To 1.7</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 1.7, a new preprocessing step implements flagging for HTML-based output formats. PDF processing
+    was corrected with regard to <codeph>shortdesc</codeph> handling, and a new XSLT template mode was introduced for
+    HTML TOC processing. Several stylesheets were moved to plug-in specific folders and deprecated properties and XSLT
+    variables were removed. </shortdesc>
+  
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>deprecated features<indexterm><codeph>dita.input</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dita.input.dirname</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dita.extname</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>XHTML, flagging-related templates</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>page-margin-left</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>page-margin-right</codeph></indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section>
+      <p>A new job status file <filepath>.job.xml</filepath> has been introduced and replaces
+          <filepath>dita.list</filepath> and <filepath>dita.xml.properties</filepath> as the normative source for job
+        status. If you have custom processing which modifies the job properties, you should change your code to modify
+          <filepath>.job.xml</filepath> instead.</p>
+      <p>Support for the following deprecated properties has been removed:</p>
+      <ul>
+        <li><codeph>dita.input</codeph></li>
+        <li><codeph>dita.input.dirname</codeph></li>
+        <li><codeph>dita.extname</codeph></li>
+      </ul>
+      <p>Stylesheets for the following transformation types have moved to plug-in specific folders:</p>
+      <ul>
+        <li><option>docbook</option></li>
+        <li><option>eclipsecontent</option></li>
+        <li><option>troff</option></li>
+        <li><option>wordrtf</option></li>
+      </ul>
+      <p>If custom plug-ins have hard coded paths to these stylesheets, update references to use either
+          <codeph>plugin</codeph> URIs in <codeph>xsl:import</codeph> instructions or use <codeph>dita.plugin.*</codeph>
+        Ant properties.</p>
+      <p>The integration process has been changed to use strict mode by default. For old plug-ins which are not valid,
+          <keyword>lax</keyword> processing mode can still be used.</p>
+      <p>Plug-ins that use the <codeph>MessageUtils</codeph> Java class must use <codeph>getInstance</codeph> method to
+        access the <codeph>MessageUtils</codeph> instance, as <codeph>getMessage</codeph> methods have been changed to
+        instance methods.</p>
+    </section>
+    <section>
+      <title>Preprocessing</title>
+      <p>The preprocessing Ant dependency chain has been cleaned up. Tasks no longer depend on the previous task in the
+        default chain, but rather the whole preprocess dependency chain is defined by the <codeph>preprocess</codeph>
+        task.</p>
+    </section>
+    <section>
+      <title>HTML</title>
+      <p>Core TOC generation has been moved to a separate XSLT stylesheet
+          <filepath>xsl/map2htmtoc/map2htmlImpl.xsl</filepath> and the new templates use the mode <codeph>toc</codeph>.
+        Plug-ins which override HTML TOC processing should change the map processing templates to <codeph>toc</codeph>
+        mode.</p>
+    </section>
+    <section>
+      <title>HTML and extended transformation types</title>
+      <p>Flagging logic has been pulled out of the core X/HTML code and moved to a preprocess step. This significantly
+        simplifies and optimizes the X/HTML code, while making flagging logic available to any other transformation
+        type. The new preprocess step implements all flagging logic; for each active flag, it adds a DITA-OT specific
+        hint into the intermediate topics (implemented as a specialization of the DITA &lt;foreign&gt; element). As part
+        of this change, all flagging-related templates in the XHTML code (such as start-flagit and gen-style) are
+        deprecated.</p>
+      <p>If you override the X/HTML transforms, you may need to update your overrides to use the new flagging logic. In
+        most cases this just means deleting calls to the deprecated templates; in some cases, the calls can be replaced
+        with 2 lines to process flags in new places. You should compare your override to the updated XHTML code and
+        update as needed. See <xref keyref="flagging-migration"/> for details.</p>
+      <p>Plug-ins that provide support for new transforms need to ensure that they properly support the DITA
+        &lt;foreign&gt; element, which should be ignored by default; if so, this change will have no immediate impact.
+        Support for flagging new transformation types may be more easily added based on this update, because there is no
+        need to re-implement flagging logic, but this is not required. See <xref keyref="preprocess-flagging"/> for
+        details on how to add flagging support.</p>
+    </section>
+    <section>
+      <title>PDF</title>
+      <p>The following deprecated XSLT variables have been removed:</p>
+      <ul>
+        <li><codeph>page-margin-left</codeph></li>
+        <li><codeph>page-margin-right</codeph></li>
+      </ul>
+      <p>XSLT stylesheets have been split to separate specialization topic code and new <codeph>xsl:import</codeph>
+        instructions have been added to <filepath>topic2fo.xsl</filepath>. Plug-ins which define their own shell
+        stylesheet should be revised to import all the required stylesheet modules.</p>
+      <p>PDF processing used to replace topic <codeph>shortdesc</codeph> with map <codeph>shortdesc</codeph>, but this
+        behavior was incorrect and was removed to comply with the DITA specification.</p>
+      <p>A new <codeph>#note-separator</codeph> variable string was added to facilitate customization.</p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-1.8.dita

@@ -0,0 +1,125 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="ID" rev="1.8">
+
+  <title>Migrating to release 1.8</title>
+  <titlealts>
+    <navtitle>To 1.8</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 1.8, certain stylesheets were moved to plug-in specific folders and various deprecated Ant
+    properties, XSLT stylesheets, parameters and modes were removed from the XHTML, PDF and ODT
+    transformations.</shortdesc>
+  
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>deprecated features<indexterm><codeph>dita.script.dir</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dita.resource.dir</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dita.empty</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>args.message.file</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>ImgUtils</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><filepath>artwork-preprocessor.xsl</filepath></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><filepath>otdita2fo_frontend.xsl</filepath></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>insertVariable.old</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>XSLT mode, <codeph>layout-masters-processing</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>XSLT mode, <codeph>toc-prefix-text</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>XSLT mode, <codeph>toc-topic-text</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>args.fo.include.rellinks</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>Legacy PDF</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>args.odt.include.rellinks</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>disableRelatedLinks</codeph></indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section>
+      <p>Stylesheets for the following transformation types have moved to plug-in specific folders:</p>
+      <ul>
+        <li><option>eclipsehelp</option></li>
+        <li><option>htmlhelp</option></li>
+        <li><option>javahelp</option></li>
+        <li><option>odt</option></li>
+        <li><option>xhtml</option></li>
+      </ul>
+    </section>
+    <section>
+      <title>Preprocessing</title>
+      <p>The following deprecated Ant properties have been removed:</p>
+      <ul>
+        <li><codeph>dita.script.dir</codeph>, use <codeph>${dita.plugin.<varname>id</varname>.dir}</codeph> instead</li>
+        <li><codeph>dita.resource.dir</codeph>, use <codeph>${dita.plugin.org.dita.base.dir}/resource</codeph>
+          instead</li>
+        <li><codeph>dita.empty</codeph></li>
+        <li><codeph>args.message.file</codeph></li>
+      </ul>
+    </section>
+    <section>
+      <title>XHTML</title>
+      <p>XSLT Java extension <codeph>ImgUtils</codeph> has been removed from stylesheets and been replaced with
+        preprocessing module <codeph>ImageMetadataModule</codeph>. The old <codeph>ImgUtils</codeph> Java classes are
+        still included in the build.</p>
+    </section>
+    <section>
+      <title>PDF</title>
+      <div outputclass="div-index">
+        <indexterm>args.rellinks</indexterm>
+        <indexterm>PDF<indexterm>related links</indexterm><indexterm>args.rellinks</indexterm></indexterm>
+      </div>
+      <p>The following deprecated XSLT stylesheets have been removed:</p>
+      <ul>
+        <li><filepath>artwork-preprocessor.xsl</filepath></li>
+        <li><filepath>otdita2fo_frontend.xsl</filepath></li>
+      </ul>
+      <p>The following deprecated XSLT templates have been removed:</p>
+      <ul>
+        <li><codeph>insertVariable.old</codeph></li>
+      </ul>
+      <p>The following deprecated XSLT modes have been removed:</p>
+      <ul>
+        <li><codeph>layout-masters-processing</codeph></li>
+        <li><codeph>toc-prefix-text</codeph>, use <codeph>tocPrefix</codeph> mode instead</li>
+        <li><codeph>toc-topic-text</codeph>, use <codeph>tocText</codeph> mode instead</li>
+      </ul>
+      <p>Link generation has been simplified by removing deprecated arguments in favor of
+        <codeph>args.rellinks</codeph>. The following deprecated Ant properties have been removed:</p>
+      <ul>
+        <li><codeph>args.fo.include.rellinks</codeph></li>
+      </ul>
+      <p>The following XSLT parameters have been removed:</p>
+      <ul>
+        <li><codeph>antArgsIncludeRelatedLinks</codeph></li>
+        <li><codeph>disableRelatedLinks</codeph></li>
+      </ul>
+      <p>A call to a named template <codeph>pullPrologIndexTerms.end-range</codeph> has been added to
+          <codeph>processTopic*</codeph> templates to handle topic wide index ranges.</p>
+    </section>
+    <section>
+      <title>Legacy PDF</title>
+      <p>The following deprecated XSLT stylesheets have been removed:</p>
+      <ul>
+        <li><filepath>dita2fo-shell_template.xsl</filepath></li>
+        <li><filepath>topic2fo-shell.xsl</filepath></li>
+      </ul>
+    </section>
+    <section>
+      <title>ODT</title>
+      <p>Link generation has been simplified by removing deprecated arguments in favor of
+        <codeph>args.rellinks</codeph>. The following deprecated Ant properties have been removed:</p>
+      <ul>
+        <li><codeph>args.odt.include.rellinks</codeph></li>
+      </ul>
+      <p>The following XSLT parameters have been added:</p>
+      <ul>
+        <li><codeph>include.rellinks</codeph></li>
+      </ul>
+      <p>The following XSLT parameters have been removed:</p>
+      <ul>
+        <li><codeph>disableRelatedLinks</codeph></li>
+      </ul>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-2.0.dita

@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-2.0">
+
+  <title>Migrating to release 2.0</title>
+  <titlealts>
+    <navtitle>To 2.0</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 2.0, XSLT templates were converted to XSLT 2.0, variable typing was implemented, and some older
+    templates were refactored or removed. In addition, the <cmdname>dita</cmdname> command simplifies distribution of
+    plugins by allowing installation from a URL.<draft-comment author="staylor">There are likely other changes that
+      should be noted here. See <xref keyref="2.0-release-notes"/>. </draft-comment>
+  </shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlatt>as</xmlatt></indexterm>
+        <indexterm><cmdname>dita</cmdname> command<indexterm>plug-ins</indexterm></indexterm>
+        <indexterm>uninstalling</indexterm>
+        <indexterm>removing<index-see>uninstalling</index-see></indexterm>
+        <indexterm>deinstalling<index-see>uninstalling</index-see></indexterm>
+        <indexterm>XSLT<indexterm>2.0</indexterm></indexterm>
+        <indexterm>Customization directory</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 2.0 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the <xref keyref="2.0-release-notes"/>.</note>
+    </section>
+    <refbodydiv>
+      <section>
+        <title>All transformations — variable typing</title>
+        <p>XSLT stylesheets were converted to XSLT 2.0. With that change, variable types were also implemented. Plug-ins
+          that change template variable values will need to make the following changes:</p>
+        <ul>
+          <li>Declare the same types defined in the default templates with <xmlatt>as</xmlatt>.</li>
+          <li>Ensure that the generated values conform to the declared type.</li>
+        </ul>
+      </section>
+      <example>
+        <p>For example:</p>
+        <codeblock outputclass="language-xml">&lt;xsl:variable name="urltest">
+&lt;xsl:variable name="urltest" <b>as="xs:boolean"</b>></codeblock>
+      </example>
+      <section>
+        <title>All transformations — refactoring</title>
+        <p>Much of the toolkit code was refactored for release 2.0. Customization changes that were based on a specific
+          template in a previous version of the toolkit might not work because the modified template is no longer used.
+          If this is the case, the changes will need to be reimplemented based on the new XSLT templates.</p>
+      </section>
+    </refbodydiv>
+    <section>
+      <title>HTML5</title>
+      <p>A new <option>HTML5</option> transformation type has been added. Customizations that previously modified the
+        XHTML output to generate valid HTML5 should still work, but basing your customization on the new transformation
+        type might simplify the customization and reduce the work required to maintain compatibility with future
+        versions of the toolkit.</p>
+      <note>The <option>HTML5</option> transformation was refactored with release 2.2. Before basing your customization
+        on the changes in release 2.0, consider whether you might want to move to release 2.2 instead. See <xref
+          keyref="migrating-to-2.2"/>.</note>
+    </section>
+    <section>
+      <title>Plug-in installation and distribution</title>
+      <p>Plug-ins can now be installed or uninstalled from a ZIP archive using the new <cmdname>dita</cmdname> command.
+        Plug-ins can also be installed from a referenced URL. See <xref keyref="dita-command-arguments"/>.</p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-2.1.dita

@@ -0,0 +1,174 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-2.1">
+
+  <title>Migrating to release 2.1</title>
+  <titlealts>
+    <navtitle>To 2.1</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 2.1, the <codeph>insertVariable</codeph> template was deprecated for PDF transformations and
+    should be replaced with the <codeph>getVariable</codeph> template. Various <codeph>dita.<b>out.</b>map.*</codeph>
+    targets have been deprecated in favor of updated <codeph>dita.map.*</codeph> equivalents.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>ph</xmlelement></indexterm>
+        <indexterm><xmlelement>keyword</xmlelement></indexterm>
+        <indexterm><xmlelement>cite</xmlelement></indexterm>
+        <indexterm><xmlelement>dt</xmlelement></indexterm>
+        <indexterm><xmlelement>term</xmlelement></indexterm>
+        <indexterm><xmlelement>indexterm</xmlelement></indexterm>
+        <indexterm><xmlatt>href</xmlatt></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>help</codeph> build target</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>imagefile</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>image.list</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>htmlfile</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>html.list</codeph></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>copy-subsidiary</codeph> target</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>copy-subsidiary-check</codeph> target</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>depend.preprocess.copy-subsidiary.pre</parmname> extension points</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>PDF, <codeph>insertVariable</codeph> template</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><varname>keydefs</varname> variable</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>KEYREF-FILE</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>displaytext</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>keys</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>target</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>pull-in-title</codeph> template</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>common-processing-phrase-within-link</codeph> template</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dita.out.map.xhtml.toc</codeph> target</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dita.out.map.htmlhelp.*</codeph> targets</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dita.out.map.javahelp.*</codeph> targets</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>args.odt.img.embed</parmname></indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 2.1 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the <xref keyref="2.1-release-notes"/>.</note>
+    </section>
+
+    <section>
+      <p>The custom<systemoutput>FileUtils</systemoutput> code used to handle input and output in earlier versions of
+        DITA-OT has been replaced with the <xref href="http://commons.apache.org/proper/commons-io/" format="html"
+          scope="external">Apache Commons IO</xref> utilities library. </p>
+    </section>
+
+    <section>
+      <title>Deprecated targets</title>
+      <p>The following build targets have been deprecated and will be removed in an upcoming release:</p>
+      <ul>
+        <li>The <codeph>help</codeph> target that includes a reference to the current DITA-OT version during the build
+          process.</li>
+      </ul>
+    </section>
+
+    <section>
+      <title>Preprocessing</title>
+      <p>The following Ant properties and generated list files have been deprecated:</p>
+      <ul>
+        <li><parmname>imagefile</parmname> property and <codeph>image.list</codeph> file</li>
+        <li><parmname>htmlfile</parmname> property and <codeph>html.list</codeph> file</li>
+      </ul>
+      <p>The following pre-processing targets and extension points have been deprecated:</p>
+      <ul>
+        <li>The <codeph>copy-subsidiary</codeph> target used to copy subsidiary files</li>
+        <li>The <codeph>copy-subsidiary-check</codeph> target used to check for subsidiary files</li>
+        <li>The <parmname>depend.preprocess.copy-subsidiary.pre</parmname> extension point used to insert an Ant target
+          before the <codeph>copy-subsidiary</codeph> step in the pre-processing stage.</li>
+      </ul>
+      <p>A new<systemoutput>dita.parser</systemoutput> extension point has been added to allow plug-ins to contribute a
+        custom parser for DITA files. If a custom DITA parser is defined, the preprocessing routines will use it during
+        the gen-list and debug-filter stages to output DITA XML.</p>
+    </section>
+
+    <section>
+      <title>PDF</title>
+      <p>The following template has been deprecated:</p>
+      <ul>
+        <li><codeph>insertVariable</codeph>, use <codeph>getVariable</codeph> instead</li>
+      </ul>
+      <p>Calls to that template will result in warnings in the build log.</p>
+      <p>To update your plug-in, make the following changes:</p>
+      <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;xsl:call-template name="<line-through>insertVariable</line-through><b>getVariable</b>">
+  &lt;xsl:with-param name="<line-through>theVariableID</line-through><b>id</b>" select="<varname>var-id</varname>"/>
+  &lt;xsl:with-param name="<line-through>theParameters</line-through><b>params</b>">
+    <varname>params</varname>
+  &lt;/xsl:with-param>
+&lt;/xsl:call-template></codeblock>
+    </section>
+
+    <section>
+      <title>HTML-based output formats</title>
+      <draft-comment author="Roger" time="2016-04-03 18:30">
+        <p>Further information required on recommended replacements for deprecated items.</p>
+      </draft-comment>
+      <p>The <varname>keydefs</varname> variable and the following XSL parameters have been deprecated:
+        <ul>
+          <li><parmname>KEYREF-FILE</parmname></li>
+          <li><parmname>displaytext</parmname></li>
+          <li><parmname>keys</parmname></li>
+          <li><parmname>target</parmname></li>
+        </ul>
+      </p>
+      <p>The following template modes have been deprecated:
+        <ul>
+          <li><codeph>pull-in-title</codeph></li>
+          <li><codeph>common-processing-phrase-within-link</codeph></li>
+        </ul>
+      </p>
+    </section>
+
+    <section>
+      <title>XHTML</title>
+      <div outputclass="div-index">
+        <indexterm>keydef</indexterm>
+      </div>
+      <p>The <codeph>dita.<b>out.</b>map.xhtml.toc</codeph> target has been deprecated and should be replaced with the
+        updated <codeph>dita.map.xhtml.toc</codeph> equivalent.</p>
+      <p>Keydef processing has been removed from the XHTML rendering code. Keys are now resolved in one preprocessing
+        step, whereas in earlier versions of DITA-OT, the XHTML code returned to the <filepath>keydef.xml</filepath>
+        file to look up targets for phrase elements and pull in text when needed.</p>
+      <p>This change affects non-linking elements that can’t take <xmlatt>href</xmlatt> attributes, such as
+          <xmlelement>ph</xmlelement>, <xmlelement>keyword</xmlelement>, <xmlelement>cite</xmlelement>,
+          <xmlelement>dt</xmlelement>, <xmlelement>term</xmlelement>, and <xmlelement>indexterm</xmlelement> (when
+          <codeph>$INDEXSHOW</codeph> is active).</p>
+    </section>
+
+    <section>
+      <title>HTMLHelp</title>
+      <p>The <codeph>dita.<b>out.</b>map.htmlhelp.*</codeph> targets have been deprecated and should be replaced with
+        the updated <codeph>dita.map.htmlhelp.*</codeph> equivalents:</p>
+      <ul>
+        <li><codeph>dita.out.map.htmlhelp.hhp</codeph>, use <codeph>dita.map.htmlhelp.hhp</codeph> instead</li>
+        <li><codeph>dita.out.map.htmlhelp.hhc</codeph>, use <codeph>dita.map.htmlhelp.hhc</codeph> instead</li>
+        <li><codeph>dita.out.map.htmlhelp.hhk</codeph>, use <codeph>dita.map.htmlhelp.hhk</codeph> instead</li>
+      </ul>
+    </section>
+    <section>
+      <title>JavaHelp</title>
+      <div outputclass="div-index">
+        <indexterm>JavaHelp</indexterm>
+      </div>
+      <p>The <codeph>dita.<b>out.</b>map.javahelp.*</codeph> targets have been deprecated and should be replaced with
+        the updated <codeph>dita.map.javahelp.*</codeph> equivalents:</p>
+      <ul>
+        <li><codeph>dita.out.map.javahelp.toc</codeph>, use <codeph>dita.map.javahelp.toc</codeph> instead</li>
+        <li><codeph>dita.out.map.javahelp.map</codeph>, use <codeph>dita.map.javahelp.map</codeph> instead</li>
+        <li><codeph>dita.out.map.javahelp.set</codeph>, use <codeph>dita.map.javahelp.set</codeph> instead</li>
+        <li><codeph>dita.out.map.javahelp.index</codeph>, use <codeph>dita.map.javahelp.index</codeph> instead</li>
+      </ul>
+    </section>
+
+    <section>
+      <title>OpenDocument Text</title>
+      <p>Support for the <parmname>args.odt.img.embed</parmname> parameter has been removed from OpenDocument Text
+        transformations. The previous default behavior was to embed images as Base64-encoded text, but editors do not
+        use this as a default. Instead, office packages such as LibreOffice will convert embedded images into linked
+        images on opening and saving an ODT file.</p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-2.2.dita

@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-2.2">
+
+  <title>Migrating to release 2.2</title>
+  <titlealts>
+    <navtitle>To 2.2</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 2.2, the <option>HTML5</option> transformation was refactored as its own plug-in and separate
+    plug-ins were created for each of the rendering engine-specific PDF transformations.<draft-comment author="staylor">
+      There are likely other changes that should be noted here. </draft-comment>
+  </shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>toc</xmlelement></indexterm>
+        <indexterm><xmlelement>preface</xmlelement></indexterm>
+        <indexterm><xmlelement>frontmatter</xmlelement></indexterm>
+        <indexterm><xmlelement>bookmap</xmlelement></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>.notetitle</codeph> classes</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>user.input.file</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>user.input.dir</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>InputMapDir</parmname></indexterm></indexterm>
+        <indexterm>RenderX<indexterm>plug-in</indexterm></indexterm>
+        <indexterm>Antenna House<indexterm>plug-in</indexterm></indexterm>
+        <indexterm>Apache FOP<indexterm>plug-in</indexterm></indexterm>
+        <indexterm>table of contents<indexterm>PDF</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 2.2 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the <xref keyref="2.2-release-notes"/>.</note>
+    </section>
+    <section>
+      <title>HTML5</title>
+      <p>The <option>HTML5</option> transformation introduced in release 2.0 as part of the <option>XHTML</option>
+        plug-in has been moved to a separate <option>HTML5</option> plug-in. Customizations that extended the previous
+        HTML5 output under the <option>XHTML</option> plug-in will probably need to be refactored on the new HTML5
+        plug-in.</p>
+      <p>Note title processing has been revised to use a common <codeph>note__title</codeph> class for note elements of
+        all types. The legacy <codeph><varname>{$type}</varname>title</codeph> classes (such as
+          <codeph>.notetitle</codeph>, <codeph>.cautiontitle</codeph>, <codeph>.tiptitle</codeph>, etc.) are included
+        for backwards compatibility, but are deprecated and will be removed in an upcoming release. Stylesheets that
+        apply formatting overrides to note titles should be revised to replace the deprecated class selectors with the
+        equivalent descendant selectors, for example <codeph>.note_note .note__title</codeph>, <codeph>.note_caution
+          .note__title</codeph>, <codeph>.note_tip .note__title</codeph>, etc.</p>
+    </section>
+    <section>
+      <title>PDF</title>
+      <p>Processing specific to Apache FOP, Antenna House Formatter, and RenderX XEP has been separated into separate
+        plug-ins for each of those rendering engines. Customizations that extended this processing might need to extend
+        the new <codeph>org.dita.pdf2.fop</codeph>, <codeph>org.dita.pdf2.axf</codeph>, or
+          <codeph>org.dita.pdf2.xep</codeph> plug-ins.</p>
+      <p>PDF customizations that are not specific to a rendering engine can continue to extend the
+          <codeph>org.dita.pdf2</codeph> plug-in as before.</p>
+      <p>The default format for page numbers in the table of contents (<xmlelement>toc</xmlelement>) was switched to
+        roman to align with <xmlelement>preface</xmlelement> and ensure consistent numbering styles for all
+          <xmlelement>frontmatter</xmlelement> components in <xmlelement>bookmap</xmlelement>. This prevents numbering
+        from switching back and forth between styles in bookmaps where the Preface follows the table of contents.
+        Earlier versions of DITA-OT produced numbering sequences like <codeph>1,2,3,4,v,vi,7,8</codeph> in this use
+        case.</p>
+    </section>
+    <section>
+      <title>Deprecated properties</title>
+      <p>The following Ant properties have been deprecated:
+        <ul>
+          <li><parmname>user.input.file</parmname>, use <parmname>user.input.file.uri</parmname> instead to specify the
+            input file system path</li>
+          <li><parmname>user.input.dir</parmname>, use <parmname>user.input.dir.uri</parmname> instead to specify the
+            input directory system path</li>
+          <li><parmname>InputMapDir</parmname>, use <parmname>InputMapDir.uri</parmname> instead to specify the input
+            map directory system path</li>
+        </ul></p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-2.3.dita

@@ -0,0 +1,155 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-2.3">
+
+  <title>Migrating to release 2.3</title>
+  <titlealts>
+    <navtitle>To 2.3</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 2.3, <option>HTML5</option> table processing has been refactored to use HTML5 best practices and
+    improved CSS properties. In PDF output, table heads and key columns no longer include shading, and unused
+    localization variables have been deprecated. The template for generated error messages has been updated to use a
+    single <codeph>id</codeph> variable that contains the entire message ID.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>languages<indexterm>supported</indexterm></indexterm>
+        <indexterm>Chinese</indexterm>
+        <indexterm>English</indexterm>
+        <indexterm>Indonesian</indexterm>
+        <indexterm>Korean</indexterm>
+        <indexterm>I18N<indexterm>PDF processing</indexterm></indexterm>
+        <indexterm>metadata<indexterm>chunking, effect of</indexterm></indexterm>
+        <indexterm>tables<indexterm>HTML5</indexterm></indexterm>
+        <indexterm>tables<indexterm>PDF</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 2.3 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the <xref keyref="2.3-release-notes"/>.</note>
+    </section>
+    <section>
+      <title>HTML5</title>
+      <p>The <option>HTML5</option> table processing has been refactored to use valid HTML5 markup, HTML5 best
+        practices, and better CSS properties for styling. <xref href="https://en.bem.info/methodology/" format="html"
+          scope="external">BEM</xref>-style CSS classes are now generated with the name of the containing element, the
+        name of the attribute, and the value of the attribute. </p>
+      <p>Common CSS files are now generated using separate modules for each DITA domain, implemented as <xref
+          keyref="sass-lang"/> partials to better support extensions with CSS frameworks, custom plug-ins and future
+        toolkit versions.</p>
+    </section>
+    <section>
+      <title>HTML-based formats</title>
+      <div outputclass="div-index">
+        <indexterm><xmlelement>div</xmlelement><indexterm><codeph>div.shortdesc</codeph></indexterm></indexterm>
+        <indexterm><xmlelement>p</xmlelement></indexterm>
+        <indexterm><xmlelement>abstract</xmlelement></indexterm>
+        <indexterm><xmlelement>simpletable</xmlelement></indexterm>
+        <indexterm><xmlelement>properties</xmlelement></indexterm>
+        <indexterm><xmlelement>choicetable</xmlelement></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>tm-area</codeph> named template</indexterm></indexterm>
+      </div>
+      <p>The XSLT <codeph>tm-area</codeph> named template, which used to toggle rendering of trademark symbols in US
+        English and Asian languages (Japanese, Korean, and both Chinese) but ignore them in all other languages, has
+        been deprecated. Trademark symbols are now rendered uniformly for all languages and the template will be removed
+        in an upcoming release.</p>
+      <p id="2191">In previous releases, short descriptions in <xmlelement>abstract</xmlelement> elements were rendered
+        as division elements (<xmlelement>div</xmlelement>), rather than paragraphs (<xmlelement>p</xmlelement>).
+        Processing has been revised to ensure that short descriptions are consistently rendered as paragraphs,
+        regardless of whether they appear in <xmlelement>abstract</xmlelement> elements. Users who have previously
+        implemented custom CSS rules to style <codeph>div.shortdesc</codeph> like paragraphs should be able to remove
+        these rules.</p>
+    </section>
+    <section>
+      <title>PDF</title>
+      <div outputclass="div-index">
+        <indexterm>deprecated features<indexterm><codeph>tm-area</codeph> named template</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm>PDF localization variables</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>conreffile</parmname></indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>conref-check</parmname> target</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><parmname>coderef</parmname> target</indexterm></indexterm>
+      </div>
+      <p>The <codeph>antiquewhite</codeph> background color has been removed from table heads and key column contents in
+          <xmlelement>simpletable</xmlelement> and <xmlelement>properties</xmlelement> tables to synchronize
+        presentation with <xmlelement>choicetable</xmlelement> and provide a more uniform customization baseline between
+        PDF output and HTML-based formats.</p>
+      <p id="2179">PDF: The I18N Java and XSLT processing code has been merged into single task. This eliminated the
+        need for a <filepath>stage3.fo</filepath> file in the temporary directory; instead,
+          <filepath>topic.fo</filepath> is generated directly from <filepath>stage2.fo</filepath>. If custom plug-ins
+        were implemented to handle <filepath>stage3.fo</filepath>, they would need to be updated. </p>
+      <p>Localization variables that are no longer used in PDF processing have been deprecated and will be removed in an
+        upcoming release. PDF customization plug-ins that make use of these variables should plan to refactor
+        accordingly:
+        <ul>
+          <li>Back button title</li>
+          <li>Contents button title</li>
+          <li>Forward button title</li>
+          <li>Index button title</li>
+          <li>Index multiple entries separator</li>
+          <li>Main page button title</li>
+          <li>Next page button title</li>
+          <li>Online help prefix</li>
+          <li>Online Help Search Method And</li>
+          <li>Online Help Search Method Field</li>
+          <li>Online Help Search Method Or</li>
+          <li>Previous page button title</li>
+          <li>Search button title</li>
+          <li>Search Case Sensitive Switch</li>
+          <li>Search Excluded Stop Words Message</li>
+          <li>Search Highlight Switch</li>
+          <li>Search index button title</li>
+          <li>Search index field title</li>
+          <li>Search index next button title</li>
+          <li>Search Search Give No Results Message</li>
+          <li>Search Search in Progress Message</li>
+          <li>Search Stopped Message</li>
+          <li>Search text button title</li>
+          <li>Search text field title</li>
+          <li>Search title</li>
+          <li>Search Whole Words Switch</li>
+          <li>Untitled section</li>
+        </ul>
+      </p>
+      <note>Most of these variables were never used by the PDF process, and most were not supported (or localized) for
+        any language other than English.</note>
+    </section>
+    <section>
+      <title>Deprecated properties and targets</title>
+      <p>The following Ant properties have been deprecated:
+        <ul>
+          <li><parmname>conreffile</parmname></li>
+        </ul>
+      </p>
+      <p>The following preprocessing targets have been deprecated:
+        <ul>
+          <li><parmname>conref-check</parmname></li>
+          <li><parmname>coderef</parmname></li>
+        </ul>
+      </p>
+    </section>
+    <section>
+      <title>Pre-processing</title>
+      <p id="2207">The order of the <codeph>chunk</codeph> and <codeph>move-meta-entries</codeph> pre-processing stages
+        has been switched so that <codeph>chunk</codeph> comes first. This ensures that metadata is properly pulled or
+        pushed into the chunked version of DITA topics. </p>
+    </section>
+    <section>
+      <title>Generating error messages</title>
+      <p>Previously, the XSLT <codeph>output-message</codeph> named template for generating error messages combined a
+        global variable and two parameters to determine the actual message ID. This function has been updated to use a
+        single <codeph>id</codeph> variable that contains the entire message ID.</p>
+      <p>Plug-ins that make use of the <codeph>output-message</codeph> function should be updated to use the single
+          <codeph>id</codeph> variable, as
+        in:<codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;xsl:call-template name="output-message">
+  &lt;xsl:with-param name="id" select="'FULLMESSAGENUMBER'"/>
+  &lt;xsl:with-param name="msgparams">optional-message-parameters&lt;/xsl:with-param>
+&lt;/xsl:call-template></codeblock>
+      </p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-2.4.dita

@@ -0,0 +1,116 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-2.4">
+
+  <title>Migrating to release 2.4</title>
+  <titlealts>
+    <navtitle>To 2.4</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 2.4, the <option>HTML5</option> transformation was refactored as an independent plug-in that no
+    longer depends on the <option>XHTML</option> plug-in. </shortdesc>
+  
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>deprecated features<indexterm><codeph>.notetitle</codeph> classes</indexterm></indexterm>
+        <indexterm>GitHub</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 2.4 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the
+        <xref keyref="2.4-release-notes"/>.</note>
+    </section>
+    <section>
+      <title>HTML5</title>
+      <ul>
+        <li>
+          <div id="24-html5-split">
+            <p>The <option>HTML5</option> transformation introduced in release 2.0 as part of the <option>XHTML</option>
+              plug-in was moved to a separate <option>HTML5</option> plug-in in release 2.2, but that version of the
+                <option>HTML5</option> transformation still depended on the <option>XHTML</option> plug-in for certain
+              common processing.</p>
+            <p>In release 2.4, all dependencies between <option>HTML5</option> and <option>XHTML</option> have been
+              removed to ensure that HTML5 processing can be further refactored in the future without affecting XHTML
+              output, or other HTML-based transformations such as <option>eclipsehelp</option>,
+                <option>htmlhelp</option> or <option>javahelp</option>.</p>
+          </div>
+          <p>Customizations that extended the previous HTML5 output under the <option>XHTML</option> plug-in (as
+            provided in releases 2.0 and 2.1) or the <option>HTML5</option> plug-in that shipped with release 2.2 will
+            need to be refactored to build on the new HTML5 plug-in.</p></li>
+        <li>
+          <p>Note title processing was revised in release 2.2 to include a common <codeph>note__title</codeph> class for
+            note elements of all types. The legacy <codeph><varname>{$type}</varname>title</codeph> classes (such as
+              <codeph>.notetitle</codeph>, <codeph>.cautiontitle</codeph>, <codeph>.tiptitle</codeph>, etc.) were
+            included in release 2.2 for backwards compatibility, but have now been removed in release 2.4.</p>
+          <p>Stylesheets that apply formatting overrides to note titles should be revised to replace the deprecated
+            class selectors with the equivalent descendant selectors, for example:</p>
+          <ul>
+            <li><codeph>.note_note .note__title</codeph></li>
+            <li><codeph>.note_caution .note__title</codeph></li>
+            <li><codeph>.note_tip .note__title</codeph></li>
+          </ul>
+        </li>
+      </ul>
+    </section>
+    <section id="24-legacy-plugin-removal">
+      <title>Legacy plug-ins removed</title>
+      <div outputclass="div-index">
+        <indexterm>DocBook</indexterm>
+        <indexterm>Eclipse Content</indexterm>
+        <indexterm>OpenDocument Text</indexterm>
+        <indexterm>RTF</indexterm>
+        <indexterm>plug-ins<indexterm>DocBook</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>Eclipse Content</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>OpenDocument Text</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>RTF</indexterm></indexterm>        
+      </div>
+      <p>DITA-OT 2.4 no longer includes the following legacy transformation plug-ins in the default distribution:</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <title>Legacy plug-ins</title>
+        <tgroup cols="2">
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <thead>
+            <row>
+              <entry>Plug-in </entry>
+              <entry>Source code location</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry>DocBook</entry>
+              <entry>
+                <xref href="https://github.com/dita-ot/org.dita.docbook" format="html" scope="external"/></entry>
+            </row>
+            <row>
+              <entry>Eclipse Content</entry>
+              <entry>
+                <xref href="https://github.com/dita-ot/org.dita.eclipsecontent" format="html" scope="external"/></entry>
+            </row>
+            <row>
+              <entry>OpenDocument Text</entry>
+              <entry>
+                <xref href="https://github.com/dita-ot/org.dita.odt" format="odt" scope="external"/></entry>
+            </row>
+            <row>
+              <entry>Word RTF</entry>
+              <entry>
+                <xref href="https://github.com/dita-ot/org.dita.wordrtf" format="html" scope="external"/></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <note>If necessary, legacy plug-ins may be re-installed from earlier DITA-OT distributions, but they are no longer
+        actively maintained or supported by the core toolkit committers. The source code is available on GitHub for
+        anyone interested in maintaining the plug-ins for use with future toolkit versions.</note>
+    </section>
+
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-2.5.dita

@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-2.5">
+
+  <title>Migrating to release 2.5</title>
+  <titlealts>
+    <navtitle>To 2.5</navtitle>
+  </titlealts>
+
+  <shortdesc>In DITA-OT 2.5, several frequently-overridden legacy style settings were removed from the default PDF
+    plug-in. A separate plug-in can be used to restore the original settings.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>example</xmlelement></indexterm>
+        <indexterm>PDF<indexterm><codeph>org.dita.pdf2.legacy</codeph></indexterm></indexterm>
+        <indexterm>languages<indexterm>right-to-left</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 2.5 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the
+        <xref keyref="2.5-release-notes"/>.</note>
+    </section>
+    <!--<section>
+      <title>HTML5</title>
+      <ul>
+        <li/>
+      </ul>
+    </section>-->
+    <section id="25-pdf-changes">
+      <title>Default PDF style improvements</title>
+      <div outputclass="div-index">
+        <indexterm>tables<indexterm>indentation</indexterm></indexterm>
+      </div>
+      <p>Several legacy styles have been modified or removed in the default PDF plug-in <codeph>org.dita.pdf2</codeph>,
+        including the following:</p>
+      <p>
+        <ul>
+          <li>In task topics with only a single step, the step is now rendered as a simple block (rather than as a list
+            item without a label).</li>
+          <li>Table containers now inherit the initial indentation (<codeph>start-indent</codeph>) from the parent
+            elements.</li>
+          <li>Borders and indentation have been removed from <xmlelement>example</xmlelement> elements.</li>
+          <li>Links are no longer italicized.</li>
+          <li>Titles for related link lists have been standardized to use the <codeph>common.title</codeph> attribute
+            set (which applies the <codeph>sans-serif</codeph> font-family) and bold font weight.</li>
+          <li>Several remaining occurrences of left/right borders, margins, padding, and text alignment now use the
+            corresponding start/end equivalents to better support right-to-left languages.</li>
+        </ul>
+      </p></section>
+    <section id="25-legacy-pdf-plugin">
+      <title>External plug-in for legacy PDF styling</title>
+      <p>If you have a custom PDF plug-in that explicitly depends on the previous default settings for the
+        aforementioned styles, the <codeph>org.dita.pdf2.legacy</codeph> plug-in can be used to restore the pre–2.5
+        styles.</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <tgroup cols="2">
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <thead>
+            <row>
+              <entry>Plug-in </entry>
+              <entry>Source code location</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry><codeph>org.dita.pdf2.legacy</codeph></entry>
+              <entry>
+                <xref href="https://github.com/dita-ot/org.dita.pdf2.legacy" format="html" scope="external"/></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <p>To install the legacy PDF plug-in, run the following command:</p>
+      <codeblock><cmdname>dita</cmdname> <parmname>--install</parmname>=<filepath>https://github.com/dita-ot/org.dita.pdf2.legacy/archive/2.5.zip</filepath></codeblock>
+      <note type="attention">Only install the legacy PDF plug-in if you have a custom PDF plug-in that requires the
+        pre–2.5 styles. If your plug-in was designed for DITA-OT 2.4 and does not override these settings, there is no
+        need to install the legacy PDF plug-in.</note>
+    </section>
+
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-3.0.dita

@@ -0,0 +1,88 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-3.0">
+
+  <title>Migrating to release 3.0</title>
+  <titlealts>
+    <navtitle>To 3.0</navtitle>
+  </titlealts>
+
+  <shortdesc>DITA-OT 3.0 <ph id="summary">adds support for Markdown, normalized DITA output, and the alternative
+      authoring formats proposed for Lightweight DITA. The map-first preprocessing approach provides a modern
+      alternative to the default <codeph>preprocess</codeph> operation.</ph></shortdesc>
+  
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>Lightweight DITA</indexterm>
+        <indexterm>GitHub</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 3.0 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the
+        <xref keyref="3.0-release-notes"/>.</note>
+    </section>
+
+    <section conkeyref="reusable-components/use-xslt2"/>
+
+    <section id="30-legacy-plugin-removal">
+      <title>Legacy plug-ins removed</title>
+      <div outputclass="div-index">
+        <indexterm>JavaHelp</indexterm>
+        <indexterm>deprecated features<indexterm>JavaHelp plug-in</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>JavaHelp</indexterm></indexterm>
+      </div>
+      <p>DITA-OT 3.0 no longer includes the following legacy transformation plug-ins in the default distribution:</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <title>Legacy plug-ins</title>
+        <tgroup cols="2">
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <thead>
+            <row>
+              <entry>Plug-in </entry>
+              <entry>Source code location</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry>JavaHelp<indexterm>JavaHelp</indexterm></entry>
+              <entry>
+                <xref href="https://github.com/dita-ot/org.dita.javahelp" format="html" scope="external"/></entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+      <note>If necessary, legacy plug-ins may be re-installed from earlier DITA-OT distributions, but they are no longer
+        actively maintained or supported by the core toolkit committers. The source code is available on GitHub for
+        anyone interested in maintaining the plug-ins for use with future toolkit versions.</note>
+      <p>To re-install the JavaHelp plug-in, run the following command:</p>
+      <codeblock><cmdname>dita</cmdname> <parmname>--install</parmname>=<filepath>https://github.com/dita-ot/org.dita.javahelp/archive/2.5.zip</filepath></codeblock>
+    </section>
+
+    <section id="map-first">
+      <title>Map-first preprocessing</title>
+      <p><ph conref="../reference/map-first-preprocessing.dita#ID/map-first-preproc-desc"/></p>
+      <p conkeyref="reusable-components/no-internal-preprocess2-ext"/>
+      <note type="tip">See
+        <xref keyref="map-first-preproc"/> for information on how to use (or test) map-first preprocessing, or revert to
+        the default <codeph>preprocess</codeph> target.</note>
+    </section>
+
+    <section>
+      <title>New <codeph>ant.import</codeph> extension point</title>
+      <p>A new extension point has been added to make it easier to add new targets to the Ant processing pipeline.</p>
+      <p>Earlier versions of DITA-OT use the <codeph>dita.conductor.target.relative</codeph> to call a wrapper file with
+        a dummy task that imports the Ant project file. This approach is still supported for backwards compatibility,
+        but the simpler <codeph>ant.import</codeph> approach should be used for all new customizations. </p>
+      <note type="tip">See
+        <xref keyref="plugin-anttarget"/> for details.</note>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-3.1.dita

@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-3.1">
+
+  <title>Migrating to release 3.1</title>
+  <titlealts>
+    <navtitle>To 3.1</navtitle>
+  </titlealts>
+
+  <shortdesc>DITA-OT 3.1 includes <ph id="summary">support for DITA 1.3 SVG domain elements, enhanced
+        <xmlelement>codeblock</xmlelement> processing, and incremental improvements to Lightweight DITA processing and
+      PDF output</ph>.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>codeblock</xmlelement></indexterm>
+        <indexterm><xmlelement>param</xmlelement></indexterm>
+        <indexterm><xmlatt>if:set</xmlatt></indexterm>
+        <indexterm><xmlatt>unless:set</xmlatt></indexterm>
+        <indexterm><xmlatt>if</xmlatt></indexterm>
+        <indexterm><xmlatt>outputclass</xmlatt></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dost.class.path</codeph> property</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>xml.catalog.files</codeph> property</indexterm></indexterm>
+        <indexterm>deprecated features<indexterm><codeph>dost.class.path</codeph></indexterm></indexterm>
+        <indexterm>Lightweight DITA</indexterm>
+        <indexterm>XSLT<indexterm>Ant</indexterm></indexterm>
+        <indexterm>DITA 1.3<indexterm>SVG domain</indexterm></indexterm>
+        <indexterm>SVG</indexterm>
+        <indexterm>catalog<indexterm><codeph>xml.catalog.files</codeph></indexterm><indexterm><codeph>xml.catalog.path</codeph></indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 3.1 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the
+        <xref keyref="3.1-release-notes"/>.</note>
+    </section>
+
+    <section>
+      <title>Custom if/unless attributes in Ant scripts</title>
+      <p>Ant scripts for DITA-OT builds now make use of <xmlatt>if:set</xmlatt> and <xmlatt>unless:set</xmlatt>
+        attributes in the Ant namespace, which can be used to control whether parameters are passed to XSLT modules.
+        These attributes replace custom implementations of <codeph>if</codeph> and <codeph>unless</codeph> logic
+        introduced before Ant had this capability.</p>
+      <p>If your plug-ins include Ant scripts that use <xmlatt>if</xmlatt> or <xmlatt>unless</xmlatt> on
+          <xmlelement>param</xmlelement> elements that pass XSLT parameters, add the following namespace attributes to
+        the root project:
+        <ul>
+          <li><xmlnsname>xmlns:if</xmlnsname>=<codeph>"ant:if"</codeph></li>
+          <li><xmlnsname>xmlns:unless</xmlnsname>=<codeph>"ant:unless"</codeph></li>
+        </ul></p>
+      <p>In custom Ant build files and in any files that supply parameters to existing DITA-OT XSLT modules, replace all
+        occurrences of <codeph>if="property"</codeph> on <xmlelement>param</xmlelement> elements with
+            <codeph>if<b>:set</b>="property"</codeph> (and <codeph>unless</codeph> → <codeph>unless<b>:set</b></codeph>
+        respectively).</p>
+      <p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;root xmlns:if="ant:if" xmlns:unless="ant:unless">
+  &lt;param name="antProperty" expression="${antProperty}"
+         if<b>:set</b>="antProperty"/>
+&lt;/root></codeblock></p>
+      <p>For more information on passing parameters to existing XSLT steps, see
+        <xref keyref="plugin-extension-points-xslt-parameters"/>.</p>
+    </section>
+
+    <section>
+      <title>Deprecated properties</title>
+      <sectiondiv>
+        <!-- From plugin-javalib.dita -->
+        <p>As of DITA-OT 3.1, the Java class path is managed automatically, meaning you do not (and should not) use
+          explicit references to Java class paths in your build scripts. In particular, the old
+            <codeph>dost.class.path</codeph> property has been deprecated and should not be used. If you are migrating
+          older plug-ins that manage their class path directly, you should remove any explicit class path configuration.
+          If your plug-in was not already using the <codeph>dita.conductor.lib.import</codeph> extension point to
+          integrate its JAR dependencies you must add it.</p>
+        <p>The effective DITA-OT class path is the combination of the JAR files in the main <filepath>lib/</filepath>
+          directory and the plug-in-contributed JARs, which are listed in <filepath>config/env.sh</filepath>. The
+            <filepath>env.sh</filepath> file is updated automatically when plug-ins are installed or removed.</p>
+      </sectiondiv>
+      <p>The <codeph>xml.catalog.files</codeph> property has been deprecated and should not be used. Replace any such
+        references with the <codeph>xml.catalog.path</codeph> instead.</p>
+    </section>
+
+    <section id="pdf-line-numbers">
+      <title>PDF – Enabling line numbers in codeblocks </title>
+      <p>The <codeph>codeblock.generate-line-number</codeph> template mode default has been changed to check for the
+          <codeph>show-line-numbers</codeph> keyword in the <xmlatt>outputclass</xmlatt> attribute. Earlier versions of
+        DITA-OT required custom PDF plug-ins to override the template mode to return <codeph>true()</codeph>. </p>
+    </section>
+
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-3.2.dita

@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-3.2">
+
+  <title>Migrating to release 3.2</title>
+  <titlealts>
+    <navtitle>To 3.2</navtitle>
+  </titlealts>
+
+  <shortdesc>DITA-OT 3.2 includes <ph id="summary">new command-line options, support for RELAX NG parsing and
+      validation, preliminary processing for the XDITA authoring format proposed for Lightweight DITA, and a plug-in
+      registry that makes it easier to discover and install new plug-ins</ph>.</shortdesc>
+  
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>deprecated features<indexterm><parmname>configuration-jar</parmname> Ant target</indexterm></indexterm>
+        <indexterm>Lightweight DITA</indexterm>
+        <indexterm>command line<indexterm>RELAX NG parsing</indexterm></indexterm>
+        <indexterm>security</indexterm>
+        <indexterm>TLS</indexterm>
+        <indexterm>registry</indexterm>
+        <indexterm>targets<indexterm>deprecated</indexterm></indexterm>
+        <indexterm>classpath<indexterm><parmname>configuration-jar</parmname></indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 3.2 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the
+        <xref keyref="3.2-release-notes"/>.</note>
+    </section>
+
+    <section>
+      <title>Deprecated targets</title>
+      <p>The <parmname>configuration-jar</parmname> Ant target used during the plug-in integration process has been
+        deprecated and may be removed in an upcoming release. This was previously used to package additional
+        configuration files and properties into <filepath>lib/dost-configuration.jar</filepath>, but recent versions of
+        DITA-OT include the <filepath>config</filepath> directory in the classpath for this purpose, so the
+        configuration JAR is no longer necessary.</p>
+    </section>
+
+    <section>
+      <title>Secure connections to the plug-in registry</title>
+      <note type="attention">To ensure data integrity during the plug-in installation process, Transport Layer Security
+        (TLS) will soon be required to access the plug-in registry. If you are using DITA-OT 3.2 or 3.2.1 and are unable
+        to upgrade to the latest version, modify the <codeph>registry</codeph> key in the
+          <filepath>config/configuration.properties</filepath> file to switch the URI schema to
+          <codeph>http<b>s</b>://</codeph>, so the entry reads <codeph>https://plugins.dita-ot.org/</codeph>.</note>
+      <p>For more information, see
+        <xref keyref="plugins-registry"/>.</p>
+    </section>
+
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migrating-to-3.3.dita

@@ -0,0 +1,120 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="migrating-to-3.3">
+
+  <title>Migrating to release 3.3</title>
+  <titlealts>
+    <navtitle>To 3.3</navtitle>
+  </titlealts>
+
+  <shortdesc>DITA-OT 3.3 includes <ph id="summary">new attribute sets for HTML5 customization, support for custom
+      integration processing, rotated table cells in PDF output, and hazard statements in HTML output</ph>.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>security</indexterm>
+        <indexterm>TLS</indexterm>
+        <indexterm>registry</indexterm>
+        <indexterm>tables<indexterm>PDF</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section>
+      <note>This topic provides a summary of changes in DITA-OT 3.3 that may require modifications to custom stylesheets
+        or plug-ins. For more information on changes in this release, see the
+        <xref keyref="3.3-release-notes"/>.</note>
+    </section>
+
+    <section>
+      <title>Secure connections to the plug-in registry</title>
+      <note type="attention">To ensure data integrity during the plug-in installation process, Transport Layer Security
+        (TLS) will soon be required to access the plug-in registry. If you are using DITA-OT 3.3, 3.2, or 3.2.1 and are
+        unable to upgrade to the latest version, modify the <codeph>registry</codeph> key in the
+          <filepath>config/configuration.properties</filepath> file to switch the URI schema to
+          <codeph>http<b>s</b>://</codeph>, so the entry reads <codeph>https://plugins.dita-ot.org/</codeph>.</note>
+      <p>For more information, see
+        <xref keyref="plugins-registry"/>.</p>
+    </section>
+
+    <section>
+      <title>Base plug-in files moved to <filepath>plugins</filepath> directory</title>
+      <div outputclass="div-index">
+        <indexterm><xmlelement>xsl:include</xmlelement></indexterm>
+        <indexterm><xmlelement>xsl:import</xmlelement></indexterm>
+      </div>
+      <p>Various XSLT files and other resources have been moved from the root of the DITA-OT installation directory to
+        the base plug-in directory <filepath>plugins/org.dita.base</filepath>.</p>
+      <note type="attention">There is no longer an <filepath>xsl/</filepath> directory in the installation root.</note>
+      <p>If your plug-ins use the <codeph>plugin</codeph> URI scheme as recommended in the
+        <xref keyref="plugin-coding-conventions"/>, this change should not require any modifications to custom plug-in
+        code:</p>
+      <lq>
+        <p>In XSLT, use the <codeph>plugin</codeph> URI scheme in <xmlelement>xsl:import</xmlelement> and
+            <xmlelement>xsl:include</xmlelement> to reference files in other plug-ins.</p>
+        <p>Instead of:</p>
+        <p><codeblock outputclass="language-xml">&lt;xsl:import href="../../org.dita.base/xsl/common/output-message.xsl"/></codeblock></p>
+        <p>use:</p>
+        <p><codeblock outputclass="language-xml">&lt;xsl:import href="plugin:org.dita.base:xsl/common/output-message.xsl"/></codeblock></p>
+        <p>As with the plug-in directory property in Ant, this allows plug-ins to resolve to the correct directory even
+          when a plug-in moves to a new location. The plug-in is referenced using the syntax
+              <codeph>plugin:<varname>plugin-id</varname>:<varname>path/within/plugin/file.xsl</varname></codeph>.</p>
+      </lq>
+    </section>
+
+    <section>
+      <title>Relocated catalog</title>
+      <div outputclass="div-index">
+        <indexterm><xmlelement>nextCatalog</xmlelement></indexterm>
+        <indexterm>catalog<indexterm>location</indexterm></indexterm>
+      </div>
+      <p>
+        <ph id="catalog">Along with the other base plug-in files, the <filepath>catalog-dita.xml</filepath> file has
+          been moved from the root of the DITA-OT installation directory to <filepath>plugins/org.dita.base</filepath>.
+          External systems that rely on this catalog should be updated with the new location. Ant scripts and DITA-OT
+          plug-ins should use the plug-in directory property to refer to the file as
+            <codeph>${dita.plugin.org.dita.base.dir}/catalog-dita.xml</codeph>. A placeholder with a
+            <xmlelement>nextCatalog</xmlelement> entry is provided in the original location for backwards compatibility,
+          but this file may be removed in an upcoming release.</ph></p>
+      <fig>
+        <title>Legacy catalog placeholder content</title>
+        <codeblock outputclass="language-xml">&lt;nextCatalog catalog="plugins/org.dita.base/catalog-dita.xml"/></codeblock>
+      </fig>
+    </section>
+
+    <section>
+      <title>Deprecated properties</title>
+      <div outputclass="div-index">
+        <indexterm><xmlelement>template</xmlelement></indexterm>
+        <indexterm>deprecated features<indexterm><filepath>plugin.xml</filepath>, <codeph>templates</codeph>
+          key</indexterm></indexterm>
+      </div>
+      <p><ph id="templates">The <codeph>templates</codeph> key in configuration properties has been deprecated in favor
+          of the <xmlelement>template</xmlelement> element in <filepath>plugin.xml</filepath>.</ph></p>
+    </section>
+
+    <section>
+      <title>New attribute sets for HTML5 customization</title>
+      <div outputclass="div-index">
+        <indexterm>Bootstrap</indexterm>
+        <indexterm>CSS<indexterm>HTML5</indexterm></indexterm>
+        <indexterm>HTML5<indexterm>CSS</indexterm></indexterm>
+      </div>
+      <p id="html5-att-sets">A series of new attribute sets has been added to the default HTML5 transformation to
+        facilitate customization with additional ARIA roles, attributes, or CSS classes. Attribute sets are provided
+        for:
+        <ul>
+          <li><codeph>article</codeph></li>
+          <li><codeph>banner</codeph></li>
+          <li><codeph>footer</codeph></li>
+          <li><codeph>main</codeph></li>
+          <li><codeph>navigation</codeph></li>
+          <li><codeph>toc</codeph></li>
+        </ul>If you have previously copied XSL templates (or template modes) to custom plug-ins only to add classes
+        required by web frameworks such as Bootstrap or Foundation (or your company CSS), you may be able to simplify
+        your customizations by using the new attribute sets instead of overriding the default templates.</p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migration.dita

@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="ID">
+  <title>Migrating customizations</title>
+  <shortdesc>If you have XSL transformation overrides, plug-ins or other customizations written prior to DITA-OT
+      <keyword keyref="release"/>, you may need to make changes to ensure your overrides work properly with the latest
+    toolkit versions. </shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>upgrading<indexterm>plug-ins</indexterm></indexterm>
+        <!-- LE: Only first alphabetical index-see-also prints in the index -->
+        <indexterm>upgrading<index-see-also>migrating</index-see-also><index-see-also>installing</index-see-also></indexterm>
+        <indexterm>migrating</indexterm> <!-- LE: Build crash for the line above if this line does not exist even though
+        the line below does. Its existence causes duplicate page number to be emitted. Also, the line below does not generate a range. The @end is in migrating-to-1.5.4.dita. -->
+        <indexterm start="migrate">migrating</indexterm>
+        <indexterm>plug-ins<indexterm>upgrading</indexterm></indexterm>
+        <indexterm>installing</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section>
+      <p>In some cases, you may be able to remove old code that is no longer needed. In other cases, you may need to
+        refactor your code to point to the modified extension points, templates or modes in recent toolkit versions.</p>
+      <p>When migrating customizations, identify the version of the toolkit you're currently using (base version) and
+        the version of the toolkit you want to migrate to (target version). Then, review all of the migration changes
+        described in <i>all</i> of the versions from the base through the target. For instance, if you're currently on
+        2.2 and want to move to 3.3, you should review all of the changes in 2.3 through 3.3. You may want to start at
+        the oldest version and read forward so you can chronologically follow the changes, since it is possible that
+        files or topics have had multiple changes. </p>
+      <note><p conkeyref="conref-task/semver-info" conrefend="semver-plugins"/></note>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/migration.ditamap

@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <title>Migrating customizations</title>
+  <topicref keyref="migration">
+    <topicref keyref="migrating-to-3.3"/>
+    <topicref keyref="migrating-to-3.2"/>
+    <topicref keyref="migrating-to-3.1"/>
+    <topicref keyref="migrating-to-3.0"/>
+    <topicref keyref="migrating-to-2.5"/>
+    <topicref keyref="migrating-to-2.4"/>
+    <topicref keyref="migrating-to-2.3"/>
+    <topicref keyref="migrating-to-2.2"/>
+    <topicref keyref="migrating-to-2.1"/>
+    <topicref keyref="migrating-to-2.0"/>
+    <topicref keyref="migrating-to-1.8"/>
+    <topicref keyref="migrating-to-1.7">
+      <topicref rev="1.7" keyref="flagging-migration"/>
+    </topicref>
+    <topicref keyref="migrating-to-1.6"/>
+    <topicref keyref="migrating-to-1.5.4"/>
+  </topicref>
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/other-errors.dita

@@ -0,0 +1,56 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="troubleshooting" xml:lang="en-US">
+  <title>Other error messages</title>
+  <shortdesc>In addition to error messages that DITA Open Toolkit generates, you might also encounter error messages
+    generated by Java or other tools.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>logging</indexterm>
+        <indexterm>Java<indexterm>logging</indexterm></indexterm>
+        <indexterm>Java<indexterm>out of memory</indexterm></indexterm>
+        <indexterm>Java<indexterm>UnsupportedClassVersionError</indexterm></indexterm>
+        <indexterm>Java<indexterm>tools.jar</indexterm></indexterm>
+        <indexterm>tools.jar</indexterm>
+        <indexterm>XSLT<indexterm>errors</indexterm></indexterm>
+        <indexterm>preprocessing<indexterm>XSLT</indexterm></indexterm>
+        <indexterm>debugging<indexterm>generate-debug-attributes</indexterm></indexterm>
+        <indexterm>memory</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section id="out-of-memory-error">
+      <title>Out of Memory error</title>
+      <p>In some cases, you might receive a message stating the build has failed due to an <msgph>Out of Memory</msgph>
+        error. Try the following approaches to resolve the problem:</p>
+      <ol>
+        <li>Increase the memory available to Java.</li>
+        <li>Reduce memory consumption by setting the <option>generate-debug-attributes</option> option to
+            <codeph>false</codeph>. This option is set in the <filepath>lib/configuration.properties</filepath> file.
+          This will disable debug attribute generation (used to trace DITA-OT error messages back to source files) and
+          will reduce memory consumption.</li>
+        <li>Set <codeph>dita.preprocess.reloadstylesheet</codeph> Ant property to <codeph>true</codeph>. This will allow
+          the XSLT processor to release memory when converting multiple files.</li>
+        <li>Run the transformation again.</li>
+      </ol>
+    </section>
+    <section id="unsupported-class-version-error">
+      <title>UnsupportedClassVersionError</title>
+      <p>If you receive a <codeph>java.lang.UnsupportedClassVersionError</codeph> error message with an
+          <codeph>Unsupported major.minor version</codeph> and a list of Java classes, make sure your system meets the
+        minimum Java requirements as listed in the <cite>Release Notes</cite> and installation instructions.</p>
+    </section>
+    <section id="tools-jar-error">
+      <title>Unable to locate tools.jar</title>
+      <p>If a Java Runtime Environment (JRE) is used when building output via Ant, the <msgph>Unable to locate
+          tools.jar</msgph> error may appear. This message is safe to ignore, since DITA-OT does not rely on any of the
+        functions in this library. If a Java Development Kit (JDK) is also installed, setting the
+          <varname>JAVA_HOME</varname> environment variable to the location of the JDK will prevent this message from
+        appearing.</p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/output-formats.dita

@@ -0,0 +1,23 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="availabletransforms" xml:lang="en-US">
+  <title>DITA-OT transformations (output formats)</title>
+  <titlealts>
+    <navtitle>Output formats</navtitle>
+  </titlealts>
+  <shortdesc>DITA Open Toolkit ships with several core transformations that generate different output formats from DITA
+    content. Each transformation represents an implementation of the processing that is defined by OASIS in the DITA
+    specification.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>output formats</indexterm>
+        <indexterm>transformations</indexterm>
+        <indexterm>DITA specification</indexterm>
+        <indexterm>plug-ins<indexterm>default, list of</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-customization-approaches.dita

@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="pdf_customization_approaches">
+  <title>PDF customization approaches</title>
+  <shortdesc>Various methods may be used to customize the PDF output that DITA Open Toolkit produces. Each of these
+    approaches have advantages and shortcomings that should be considered when preparing a customization project. Some
+    of these methods are considered “anti-patterns” with disadvantages that outweigh their apparent appeal. In most
+    cases, you should create a custom PDF plug-in.</shortdesc>
+  
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>PDF<indexterm>customizing, best practices</indexterm></indexterm>
+        <indexterm>upgrading<indexterm>default plug-ins</indexterm></indexterm>
+        <indexterm>upgrading<indexterm>PDF</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <conbody>
+    <section id="why_not_edit_default_files">
+      <title>Why not edit default files?</title>
+      <p>When first experimenting with PDF customization, novice users are often tempted to simply edit the default
+          <filepath>org.dita.pdf2</filepath> files in place to see what happens.</p>
+      <p>As practical as this approach may seem, the DITA-OT project does not recommend changing any of the files in the
+          default plug-ins.</p>
+      <p>While this method yields quick results and can help users to determine which files and templates control
+        various aspects of PDF output, it quickly leads to problems, as any errors may prevent the toolkit from
+        generating PDF output.</p>
+      <note type="warning">Any changes made in this fashion would be overwritten when upgrading to newer versions of
+        DITA-OT, so users that have customized their toolkit installation in this way are often “stuck” on older
+        versions of the toolkit and unable to take advantage of improvements in recent versions of DITA-OT.</note>
+    </section>
+
+    <section id="the_customization_folder">
+      <title>Using the <filepath>Customization</filepath> folder</title>
+      <div outputclass="div-index">
+        <indexterm>deprecated features<indexterm><filepath>Customization</filepath> folder</indexterm></indexterm>
+        <indexterm>Customization directory</indexterm>
+      </div>
+      <p>The original Idiom plug-in used its own extension mechanism to provide overrides to the PDF transformation.
+        With this approach, a dedicated folder within the plug-in is used to store customized files.</p>
+      <p>Files in the <filepath>org.dita.pdf2/Customization</filepath> folder can override their default counterparts,
+        allowing users to adjust certain aspects of PDF output without changing any of the plug-in’s default files, or
+        specifying additional parameters when generating output.</p>
+      <note type="important">While this approach is slightly better than editing default files in place, it can still
+        cause problems when upgrading the toolkit to a new version. Since the <filepath>Customization</filepath> folder
+        is located within the <filepath>org.dita.pdf2</filepath> plug-in’s parent directory, users must be take care to
+        preserve the contents of this folder when upgrading to new toolkit versions.</note>
+      <p>Although recent versions of DITA-OT still support this mechanism to ensure backwards compatibility, this
+        practice is deprecated in favor of custom PDF plug-ins.</p>
+      <note type="tip">Users who have used the <filepath>Customization</filepath> folder to modify the default PDF
+        output are encouraged to create a custom PDF plug-in instead. In many cases, this may be as simple as copying
+        the contents of the <filepath>Customization</filepath> folder to a new subfolder in the
+          <filepath>plugins</filepath> folder and creating the necessary <filepath>plugin.xml</filepath> file and an Ant
+        script to define the transformation type as described in the following example.</note>
+    </section>
+
+    <section id="external_customization_directories">
+      <title>Specifying an external customization directory</title>
+      <p>To ensure that overrides in customization folders are not overwritten when upgrading DITA-OT to a new
+        release, an external customization directory can be specified at build time or in build scripts via the
+          <parmname>customization.dir</parmname> parameter.</p>
+      <p>This method is preferable to the use of the <filepath>org.dita.pdf2/Customization</filepath> folder, as the
+        contents of external folders are unaffected when upgrading DITA-OT. In distributed environments, users can use
+        local installations of DITA-OT, yet still take advantage of common customizations stored in a network location
+        available to the entire team, such as a shared drive.</p>
+      <p>It can also be useful in environments where corporate policy, CMS permissions, or network access rights prevent
+        changes to the toolkit installation, which may prohibit the installation of custom plug-ins.</p>
+      <note type="tip">Users who specify external customization directories via <parmname>customization.dir</parmname>
+        are encouraged to create a custom PDF plug-in if possible.</note>
+    </section>
+
+    <section id="plug_ins_and_customization_folders">
+      <title>Combining custom plug-ins &amp; customization directories</title>
+      <p>A common custom plug-in may be used to store base overrides that are applicable to all company publications,
+        and the <parmname>customization.dir</parmname> parameter can be passed at build time to override individual
+        settings as necessary for a given project or publication.</p>
+      <p>In this case, any settings in the customization directory will take precedence over their counterparts in the
+        custom plug-in or default <filepath>org.dita.pdf2</filepath> plug-in.</p>
+      <p>This approach allows a single custom plug-in to be shared between multiple publications or the entire company,
+        without the need to create additional plug-in dependencies per project.</p>
+      <p>However, the use of multiple customization mechanisms can make it difficult to debug the precedence cascade and
+        determine the origin of local formatting or processing overrides.</p>
+      <note type="tip">In most scenarios, the use of dedicated PDF customization plug-ins is preferable. Common
+        customizations can be bundled in one plug-in, and any project-specific overrides can be maintained in separate
+        plug-ins that build on the base branding or other settings in the common custom plug-in.</note>
+    </section>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-customization-example.dita

@@ -0,0 +1,121 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="dita2pdf-customization" xml:lang="en">
+  <title>Example: Creating a simple PDF plug-in</title>
+  <titlealts>
+    <navtitle>Simple PDF plug-in example</navtitle>
+  </titlealts>
+  <shortdesc>This scenario walks through the process of creating a very simple plug-in
+      (<codeph>com.example.print-pdf</codeph>) that creates a new transformation type: <option>print-pdf</option>. </shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>figure</xmlelement></indexterm>
+        <indexterm>PDF<indexterm>plug-in</indexterm></indexterm>
+        <indexterm>integrator.xml</indexterm>
+        <indexterm>catalog<indexterm>example</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>The <option>print-pdf</option> transformation has the following characteristics:</p>
+      <ul>
+        <li>Uses A4 paper </li>
+        <li>Renders figures with a title at the top and a description at the bottom</li>
+        <li>Use em dashes as the symbols for unordered lists</li>
+      </ul>
+    </context>
+    <steps>
+      <step>
+        <cmd>In the <filepath>plugins</filepath> directory, create a directory named
+            <filepath>com.example.print-pdf</filepath>.</cmd>
+      </step>
+      <step>
+        <cmd>In the new <filepath>com.example.print-pdf</filepath> directory, create a plug-in configuration file
+            (<filepath>plugin.xml</filepath>) that declares the new <option>print-pdf</option> transformation and its
+          dependencies.</cmd>
+        <info>
+          <fig>
+            <title><filepath>plugin.xml</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.print-pdf/plugin.xml"/></codeblock>
+          </fig>
+        </info>
+      </step>
+      <step>
+        <cmd>Add an Ant script (<filepath>integrator.xml</filepath>) to define the transformation type.</cmd>
+        <info>
+          <fig>
+            <title><filepath>integrator.xml</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.print-pdf/integrator.xml"/></codeblock>
+          </fig></info>
+      </step>
+      <step>
+        <cmd>In the new plug-in directory, add a <filepath>cfg/catalog.xml</filepath> file that specifies the custom
+          XSLT style sheets.</cmd>
+        <stepxmp>
+          <fig>
+            <title><filepath>cfg/catalog.xml</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.print-pdf/cfg/catalog.xml"/></codeblock>
+          </fig>
+        </stepxmp>
+      </step>
+      <step>
+        <cmd>Create the <filepath>cfg/fo/attrs/custom.xsl</filepath> file, and add attribute and variable overrides to
+          it.</cmd>
+        <stepxmp>For example, add the following variables to change the page size to A4.<fig>
+            <title><filepath>cfg/fo/attrs/custom.xsl</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.print-pdf/cfg/fo/attrs/custom.xsl"/></codeblock>
+          </fig></stepxmp>
+      </step>
+      <step>
+        <cmd>Create the <filepath>cfg/fo/xsl/custom.xsl</filepath> file, and add XSLT overrides to it.</cmd>
+        <stepxmp>For example, the following code changes the rendering of <xmlelement>figure</xmlelement> elements.<fig>
+            <title><filepath>cfg/fo/xsl/custom.xsl</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.print-pdf/cfg/fo/xsl/custom.xsl"/></codeblock>
+          </fig></stepxmp>
+      </step>
+      <step>
+        <cmd>Create an English-language variable-definition file (<filepath>cfg/common/vars/en.xml</filepath>) and make
+          any necessary modifications to it.</cmd>
+        <stepxmp>For example, the following code removes the period after the number for an ordered-list item; it also
+          specifies that the bullet for an unordered list item should be an em dash.<fig>
+            <title><filepath>cfg/common/vars/en.xml</filepath> file</title>
+            <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace"><coderef href="../samples/plugins/com.example.print-pdf/cfg/common/vars/en.xml"/></codeblock>
+          </fig></stepxmp>
+      </step>
+    </steps>
+    <result>
+      <note type="tip">The files for this sample plug-in are included in the DITA-OT installation directory under
+          <filepath>docsrc/samples/plugins/com.example.print-pdf/</filepath> and on
+        <xref href="https://github.com/dita-ot/docs/tree/develop/samples/plugins/com.example.print-pdf" format="html"
+          scope="external">GitHub</xref>.</note>
+      <p>The plug-in directory has the following layout and files:</p>
+      <codeblock>com.example.print-pdf
+├── cfg
+│   ├── catalog.xml
+│   ├── common
+│   │   └── vars
+│   │       └── en.xml
+│   └── fo
+│       ├── attrs
+│       │   └── custom.xsl
+│       └── xsl
+│           └── custom.xsl
+├── integrator.xml
+└── plugin.xml</codeblock>
+    </result>
+    <postreq>
+      <ol>
+        <li>Run <filepath conref="../resources/conref-task.dita#ID/dita-cmd"/>
+          <parmname>--install</parmname> to install the plug-in and make the <option>print-pdf</option> transformation
+          available.</li>
+        <li>Build output with the new transformation type to verify that the plug-in works as intended.
+          <codeblock><filepath conref="../resources/conref-task.dita#ID/dita-cmd"/> <parmname>--input</parmname>=<varname>my.ditamap</varname> <parmname>--format</parmname>=<option>print-pdf</option></codeblock>
+        </li>
+      </ol>
+    </postreq>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-customization-plugin-types.dita

@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="types-pdf-customization-plugins">
+  <title>Types of custom PDF plug-ins</title>
+  <shortdesc>There are two common types of plug-ins: A plug-in that simply sets the DITA-OT parameters to be used when a
+    PDF is generated, and a plug-in that overrides aspects of the base DITA-OT PDF transformation. A plug-in can, of
+    course, do both of these things.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>property</xmlelement></indexterm>
+        <indexterm>PDF<indexterm>plug-in</indexterm></indexterm>
+        <indexterm>PDF<indexterm>draft comments</indexterm></indexterm>
+        <indexterm>draft<indexterm>PDF</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <section>
+      <title>Plug-in that only provides DITA-OT parameters</title>
+      <p>You might want to build a transformation type that uses a transformation as-is; however, you might want ensure
+        that certain DITA-OT parameters are used. For example, consider the following scenario:</p>
+      <p>You want to ensure that PDFs generated for internal review have the following characteristics:</p>
+      <ul>
+        <li>Use company style sheets</li>
+        <li>Make draft comments visible to the reviewers, as they contain queries from the information developers</li>
+        <li>Print the file names of the graphics underneath figures, so that graphic artists can more quickly respond to
+          requested changes</li>
+      </ul>
+      <p>To accomplish this, you can create a new plug-in. In the Ant script that defines the transformation type,
+        specify the DITA-OT parameters. For example, to render draft comments and art labels, add
+          <xmlelement>property</xmlelement> elements to specify the DITA-OT parameters:</p>
+      <p>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version='1.0' encoding='UTF-8'?>
+&lt;project name="com.example.draft.pdf">
+  &lt;target name="dita2draft.pdf.init">
+    &lt;property name="customization.dir"
+              location="${dita.plugin.com.example.draft.pdf.dir}/cfg"/>
+    <b>&lt;property name="args.draft" value="yes"/></b>
+    <b>&lt;property name="args.artlbl" value="yes"/></b>
+  &lt;/target>
+  &lt;target name="dita2draft.pdf"
+          depends="dita2draft.pdf.init, dita2production.pdf,dita2pdf2"/>
+&lt;/project></codeblock>
+      </p>
+    </section>
+    <section>
+      <title>Plug-in that overrides the base PDF transformation</title>
+      <p>Production uses of DITA-OT typically rely on a custom PDF plug-in to render PDFs that are styled to match
+        corporate or organizational guidelines. Such customization plug-ins often override the following aspects of
+        DITA-OT default output:</p>
+      <ul>
+        <li>Generated text strings</li>
+        <li>XSL templates</li>
+        <li>XSL-FO attribute sets</li>
+      </ul>
+    </section>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-customization-resources.dita

@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="ID">
+  <title>Resources for custom PDF plug-ins</title>
+  <titlealts>
+    <navtitle>Custom PDF plug-in resources</navtitle>
+  </titlealts>
+  <shortdesc>There are several external resources that can help you generate and refine custom PDF plug-ins for DITA
+    Open Toolkit.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>RenderX<indexterm>plugin generator</indexterm></indexterm>
+        <indexterm>Antenna House<indexterm>plugin generator</indexterm></indexterm>
+        <indexterm>Apache FOP<indexterm>plugin generator</indexterm></indexterm>
+        <indexterm>Jarno Elovirta</indexterm>
+        <indexterm>PDF<indexterm>plugin generator</indexterm></indexterm>
+        <indexterm>fonts<indexterm>PDF plugin generator</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <refbody>
+    <section id="pdf-plugin-generator">
+      <title>PDF Plugin Generator</title>
+      <p>This online tool, developed and maintained by Jarno Elovirta, enables you to generate a PDF customization
+        plug-in automatically.</p>
+      <p>The application at <xref href="http://dita-generator.elovirta.com/" format="html" scope="external"
+          >dita-generator.elovirta.com</xref> walks you through the process of creating a custom PDF plug-in and allows
+        you to adjust a variety of settings for your PDF output. For example, you can:</p>
+      <ul>
+        <li>Define the target environment, selecting from the most current and two previous versions of DITA-OT</li>
+        <li>Select the XSL formatting engine (FOP, Antenna House Formatter, or RenderX XEP)</li>
+        <li>Specify page size, columns, and margins</li>
+        <li>Select from (limited) options for headers and footers</li>
+        <li>Specify layout options for chapters</li>
+        <li>Select formatting for the following publication components:
+          <ul>
+            <li>Normal text</li>
+            <li>Headings (levels one through four)</li>
+            <li>Titles for sections and examples</li>
+            <li>Tables and figures</li>
+            <li>Notes and examples</li>
+            <li>Lists (unordered, ordered, and definition)</li>
+            <li>Code blocks and pre-formatted text</li>
+            <li>Inline elements such as links and trademarks</li>
+          </ul><draft-comment author="Kristen Eberlein" time="13 February 2016">
+            <p>Given the technical level of our audience here, should we list DITA elements rather than the generic
+              categories?</p>
+          </draft-comment>
+          <p>For each component, you can specify: </p>
+          <ul>
+            <li>Font family, size, weight, and style</li>
+            <li>Color and background color</li>
+            <li>Alignment, indentation, spacing, and padding</li>
+          </ul></li>
+      </ul>
+      <note type="tip">The PDF Plugin Generator should be your first stop as you start developing a brand-new PDF
+        customization plug-in.</note>
+    </section>
+
+    <section conkeyref="reusable-components/dita-for-print"/>
+
+    <section conkeyref="reusable-components/dita-for-practitioners"/>
+
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-customization.dita

@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="customizing-pdf-output">
+  <title>Customizing PDF output</title>
+  <titlealts>
+    <navtitle>Customizing PDF</navtitle>
+  </titlealts>
+  <shortdesc>You can create custom DITA-OT plug-ins that build on the default DITA to PDF transformation. Plug-ins can
+    customize covers and page layouts, modify formatting, override logic of the default PDF plug-in, and much
+    more.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>transformations<indexterm start="pdf">PDF</indexterm></indexterm> <!-- LE: This is not generating a page range. -->
+        <indexterm>PDF</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-customization.ditamap

@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <title>Customizing PDF output</title>
+  <topicref keyref="pdf-customization">
+    <topicref keyref="pdf-customization-approaches"/>
+    <topicref keyref="pdf-customization-plugin-types"/>
+    <topicref keyref="pdf-plugin-structure" collection-type="family">
+      <topicref keyref="pdf-plugin-structure_common-artwork"/>
+      <topicref keyref="pdf-plugin-structure_common-index"/>
+      <topicref keyref="pdf-plugin-structure_common-vars"/>
+      <topicref keyref="pdf-plugin-structure_fo-attrs"/>
+      <topicref keyref="pdf-plugin-structure_fo-i18n"/>
+      <topicref keyref="pdf-plugin-structure_fo-xsl"/>
+    </topicref>
+    <topicref keyref="pdf-customization-example"/>
+    <topicref keyref="pdf-customization-resources"/>
+    <topicref keyref="pdf2-creating-change-bars"/>
+  </topicref>
+
+  <reltable>
+    <title>Bi-directional links</title>
+    <relrow>
+      <relcell>
+        <topicref keyref="pdf-customization"/>
+        <topicref keyref="pdf-customization-approaches"/>
+      </relcell>
+      <relcell>
+        <!-- Link formerly PDF-specific content to new location -->
+        <topicref keyref="plugin-best-practices"/>
+        <topicref keyref="plugin-coding-conventions"/>
+      </relcell>
+    </relrow>
+  </reltable>
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-plugin-structure.dita

@@ -0,0 +1,105 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="pdf-plugin-structure">
+  <title>PDF plug-in structure</title>
+  <shortdesc>In cases that require substantial customizations, it is often useful to organize the files in a folder
+    structure that mimics the hierarchy of the default PDF plug-in.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>languages<indexterm>adding support for</indexterm></indexterm>
+        <indexterm>I18N<indexterm>plug-in</indexterm></indexterm>
+        <indexterm>PDF<indexterm start="pdf-plugin">plug-in</indexterm></indexterm>
+        <indexterm>font-mappings.xml</indexterm>
+        <indexterm>fonts<indexterm>PDF</indexterm></indexterm>
+        <indexterm>PDF<indexterm>fonts</indexterm></indexterm>
+        <indexterm>index<indexterm>PDF</indexterm></indexterm>
+        <indexterm>Customization directory</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+
+  <conbody>
+    <note>For simpler customizations, you may want to structure your plug-in differently, but the information in this
+      topic may help you to locate the files you need to customize.</note>
+    <p>The original Idiom plug-in used its own extension mechanism to provide overrides to the PDF transformation. With
+      this approach, a dedicated <filepath>Customization</filepath> folder within the plug-in was used as a
+      customization layer to store files that override the default behavior.</p>
+    <p>While this method is no longer recommended, the same organization principles can be used in custom PDF plug-ins
+      to facilitate comparisons with the default settings in the base PDF plug-in and make it easier to migrate
+      customizations to new toolkit versions.</p>
+    <fig>
+      <title>Default <filepath>Customization</filepath> folder content</title>
+      <codeblock>.
+├── build.properties.orig
+├── catalog.xml.orig
+└── fo/
+    ├── attrs/
+    │   └── custom.xsl.orig
+    └── xsl/
+        └── custom.xsl.orig</codeblock>
+    </fig>
+    <p>To begin creating a new custom plug-in, you can copy the contents of the customization layer template in
+        <filepath>plugins/org.dita.pdf2/Customization</filepath> to a new folder that will serve as your new custom
+      plug-in folder, such as <filepath>plugins/com.company.pdf</filepath>.</p>
+    <p>To mimic the hierarchy of the default PDF plug-in, you may want to add a <filepath>cfg/</filepath> subfolder and
+      move the contents of the <filepath>fo/</filepath> folder to <filepath>cfg/fo/</filepath>.</p>
+    <p>DITA-OT provides template files that you can start with throughout the <filepath>Customization</filepath>
+      directory structure. These files end in the suffix <codeph>.orig</codeph> (for example,
+        <filepath>catalog.xml.orig</filepath>). To enable these files, remove the <codeph>.orig</codeph> suffix from the
+      copies in your new custom plug-in folder. (For example, rename <filepath>catalog.xml.orig</filepath> to
+        <filepath>catalog.xml</filepath>).</p>
+    <p>You can then make modifications to the copy in your custom plug-in folder, and copy any other files from the
+      default PDF plug-in that you need to override, such as the page layouts in
+      <filepath>layout-masters.xsl</filepath>, or the <filepath>font-mappings.xml</filepath> file that tells your PDF
+      renderer which fonts to use and where to find them.</p>
+    <note type="important"> Wherever possible, avoid copying entire XSL files from the PDF2 plug-in to your custom
+      plug-in. Instead, copy only the specific attribute sets and templates that you want to override. For details, see
+      <xref keyref="plugin-best-practices"/>.</note>
+    <p>Things you can currently override include:</p>
+    <ul>
+      <li>Custom XSL via <filepath>xsl/custom.xsl</filepath> and <filepath>attrs/custom.xsl</filepath></li>
+      <li>Layout overrides via <filepath>layout-masters.xsl</filepath></li>
+      <li>Font overrides via <filepath>font-mappings.xml</filepath></li>
+      <li>Per-locale variable overrides via <filepath>common/vars/[language].xml</filepath></li>
+      <li>I18N configuration via <filepath>i18n/[language].xml</filepath></li>
+      <li>Index configuration via <filepath>index/[language].xml</filepath></li>
+    </ul>
+    <p>When customizing any of these areas, modify the relevant file(s) in your custom plug-in folder. Then, to enable
+      the changes in the publishing process, you find the corresponding entry for each file you modified in the
+        <filepath>catalog.xml</filepath> file.</p>
+    <p>It should look like this:</p>
+    <codeblock outputclass="language-xml">&lt;!--uri name="cfg:fo/attrs/custom.xsl" uri="fo/attrs/custom.xsl"/--&gt;</codeblock>
+    <p>Remove the comment markers <codeph>!--</codeph> and <codeph>--</codeph> to enable the change:</p>
+    <codeblock outputclass="language-xml">&lt;uri name="cfg:fo/attrs/custom.xsl" uri="fo/attrs/custom.xsl"/&gt;</codeblock>
+    <p>Your customization should now be enabled as part of the publishing process.</p>
+    <fig>
+      <title>Sample custom plug-in structure</title>
+      <codeblock>.
+├── plugin.xml
+├── ant-include.xml
+└── cfg/
+    ├── catalog.xml
+    ├── common/
+    │   ├── artwork/
+    │   │   ├── logo.svg
+    │   └── vars/
+    │       ├── strings.xml
+    │       ├── en.xml
+    └── fo/
+        ├── attrs/
+        │   ├── custom.xsl
+        ├── font-mappings.xml
+        ├── layout-masters.xsl
+        └── xsl/
+            └── custom.xsl</codeblock>
+    </fig>
+    <p>When your custom plug-in is installed, the files in its subfolders will override the out-of-the-box settings from
+      their counterparts in <filepath>org.dita.pdf2/cfg/fo/attrs</filepath> and
+        <filepath>org.dita.pdf2/xsl/fo</filepath>.</p>
+    <p>The following topics describe the contents of the base PDF plug-in subfolders and provide additional information
+      on customizing various aspects of the default PDF output.</p>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-plugin-structure_common-artwork.dita

@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="custom_artwork_the_common_artwork_folder">
+  <title>Custom artwork</title>
+  <shortdesc>The <filepath>common/artwork</filepath> folder houses custom artwork files that override the standard icons
+    in <filepath>org.dita.pdf2/cfg/common/artwork</filepath>.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>note</xmlelement></indexterm>
+        <indexterm><xmlatt>type</xmlatt></indexterm>
+        <indexterm>locale</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>These files are used to graphically identify different types of DITA <xmlelement>note</xmlelement> element.</p>
+    <p>The mapping between <xmlelement>note</xmlelement> type and graphic is contained in the common variables file
+        <filepath>org.dita.pdf2/cfg/common/vars/commonvariables.xml</filepath>.</p>
+    <p>The variables that control <xmlelement>note</xmlelement> graphics all follow the form</p>
+    <codeblock outputclass="language-xml">&lt;variable id="<varname>{type}</varname> Note Image Path"&gt; <varname>{path to image file}</varname> &lt;/variable&gt;</codeblock>
+    <p>where <varname>{type}</varname> contains a possible value for the <xmlelement>note</xmlelement>
+      <xmlatt>type</xmlatt> attribute and <varname>{path to image file}</varname> is the path to the note icon
+      image.</p>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-plugin-structure_common-index.dita

@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="index_configuration_the_common_index_folder">
+  <title>Index configuration</title>
+  <shortdesc>The <filepath>common/index</filepath> folder houses custom index definition files that override the
+    standard definitions in <filepath>org.dita.pdf2/cfg/common/index</filepath>.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>index.group</xmlelement></indexterm>
+        <indexterm><xmlelement>char.set</xmlelement></indexterm>
+        <indexterm>languages<indexterm>ISO 639-1</indexterm></indexterm>
+        <indexterm>ISO 639-1</indexterm>
+        <indexterm>Portuguese</indexterm>
+        <indexterm>index<indexterm>PDF</indexterm></indexterm>
+        <indexterm>catalog<indexterm><filepath>catalog.xml</filepath></indexterm></indexterm>
+        <indexterm>catalog<indexterm>index configuration</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>Each file contains data for a single language, and should take that language’s ISO 639-1 language designator as
+      its name (for example, <filepath>pt.xml</filepath> for Portuguese). If necessary, locale-specific customizations
+      can be provided by adding a region designator to the file name (for example, <filepath>pt_BR.xml</filepath> for
+      Brazilian Portuguese).</p>
+    <p>The index files consist of <xmlelement>index.group</xmlelement> elements which contain sorting information on one
+      or more characters. Index groups are listed in sort order (“specials” before numbers, numbers before the letter
+      ‘A‘, etc), and the <xmlelement>char.set</xmlelement> entries they contain are also listed in sort order (uppercase
+      before lowercase).</p>
+    <p>The best way to start editing a custom index file is by making a copy of the original from
+        <filepath>org.dita.pdf2/cfg/common/index</filepath> and making changes as desired.</p>
+    <p>In order to apply a custom index definition to your publishing outputs, edit <filepath>catalog.xml</filepath> and
+      uncomment the appropriate entry in the “Index configuration override entries” section.</p>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-plugin-structure_common-vars.dita

@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="variable_overrides_the_common_vars_folder">
+  <title>Variable overrides</title>
+  <shortdesc>The <filepath>common/vars</filepath> folder houses custom variable definitions that override the standard
+    definitions in <filepath>org.dita.pdf2/cfg/common/vars</filepath>. </shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>variable</xmlelement></indexterm>
+        <indexterm><xmlelement>param</xmlelement></indexterm>
+        <indexterm><xmlatt>id</xmlatt><indexterm>variables, overriding</indexterm></indexterm>
+        <indexterm>languages<indexterm>adding support for</indexterm></indexterm>
+        <indexterm>languages<indexterm>ISO 639-1</indexterm></indexterm>
+        <indexterm>ISO 639-1</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>As with index configuration, each file contains data for a single language, and should take that language’s ISO
+      639-1 language designator as its name.</p>
+    <p>Variable files contain a set of <xmlelement>variable</xmlelement> elements, identified by their
+        <xmlatt>id</xmlatt> attribute. The variable definitions are used to store static text that is used as part of
+      the published outputs. For example, page headers, hyperlinks, etc. The id attribute for each variable should make
+      it clear how the variable text is being used.</p>
+    <p>Some variables contain <xmlelement>param</xmlelement> elements which indicate parameter values that are
+      substituted at publish time by the XSL. For example, a page number that is being generated as part of the
+      publishing process might be identified by &amp;lt;param ref-name="number"/&amp;gt; When editing or translating a
+      variable file, these should be included in the translation, though they can be moved and rearranged within the
+        <xmlelement>variable</xmlelement> content as needed.</p>
+    <p>The best way to start editing a custom variables file is by making a copy of the original from
+        <filepath>org.dita.pdf2/cfg/common/vars</filepath> and making changes as desired. When adding a new language,
+      start from an existing language’s list of variables and translate each entry as needed.</p>
+    <p>Note that unchanged <xmlelement>variable</xmlelement> elements can be omitted: the custom variables file need
+      only include those <xmlelement>variable</xmlelement> elements which you have modified. Variables not found in the
+      custom file will are taken from the standard variable files.</p>
+    <p>Applying a custom variable does not require modifying the <filepath>catalog.xml</filepath> file. The publishing
+      process will automatically use any custom variables definitions in place of the original ones.</p>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-plugin-structure_fo-attrs.dita

@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="custom_attributes_the_fo_attrs_folder">
+  <title>Custom attributes</title>
+  <shortdesc>The <filepath>fo/attrs</filepath> folder houses custom attribute configuration files that override the
+    standard attributes in <filepath>org.dita.pdf2/cfg/fo/attrs</filepath>.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>fonts<indexterm>PDF</indexterm></indexterm>
+        <indexterm>PDF<indexterm>fonts</indexterm><indexterm>index</indexterm><indexterm>tables</indexterm></indexterm>
+        <indexterm>index<indexterm>PDF</indexterm></indexterm>
+        <indexterm>tables<indexterm>tables.attr.xsl</indexterm></indexterm>
+        <indexterm>tables<indexterm>PDF</indexterm></indexterm>
+        <indexterm>index-attr.xsl</indexterm>
+        <indexterm>tables-attr.xsl</indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>These files define the appearance of different elements in XML assets when they are rendered to PDF output. The
+      different DITA elements are organized into files by element type – index-related definitions in
+        <filepath>index-attr.xsl</filepath>, table-related definitions in <filepath>tables-attr.xsl</filepath>, etc.</p>
+    <p>The XSL attribute sets defined in these files can be used to override the presentation of DITA elements,
+      including font size, color, spacing, etc.</p>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-plugin-structure_fo-i18n.dita

@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="internationalization_configuration_the_fo_i18n_folder">
+  <title>Internationalization configuration</title>
+  <titlealts>
+    <navtitle>Internationalization</navtitle>
+  </titlealts>
+  <shortdesc>The <filepath>fo/i18n</filepath> folder houses custom internationalization files that override the standard
+    configurations in <filepath>org.dita.pdf2/cfg/fo/i18n</filepath>.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>languages<indexterm>adding support for</indexterm></indexterm>
+        <indexterm>languages<indexterm>ISO 639-1</indexterm></indexterm>
+        <indexterm>ISO 639-1</indexterm>
+        <indexterm>I18N<index-see-also>languages</index-see-also></indexterm>
+        <indexterm>locale<index-see-also>languages</index-see-also><index-see-also>args.dita.locale</index-see-also></indexterm>
+        <indexterm>catalog<indexterm><filepath>catalog.xml</filepath></indexterm></indexterm>
+        <indexterm>catalog<indexterm>adding languages</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <body>
+    <p>As with index configuration and variable overrides, each file contains data for a single language, and should
+      take that language’s ISO 639-1 language designator as its name. </p>
+    <p>Each configuration file contains mappings of certain symbols to the Unicode codepoint which should be used to
+      represent them in the given locale.</p>
+    <p>The best way to start editing a custom configuration is by making a copy of the original from
+        <filepath>org.dita.pdf2/cfg/fo/i18n</filepath> and making changes as desired.</p>
+    <p>In order to apply a custom configuration to your publishing outputs, edit <filepath>catalog.xml</filepath> and
+      uncomment the appropriate entry in the “I18N configuration override entries” section.</p>
+  </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf-plugin-structure_fo-xsl.dita

@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<topic id="custom_stylesheets_the_fo_xsl_folder">
+    <title>Custom stylesheets</title>
+    <shortdesc>The <filepath>fo/xsl</filepath> folder houses custom stylesheet files that override the default
+        stylesheets in <filepath>org.dita.pdf2/xsl/fo</filepath>.</shortdesc>
+    <prolog>
+        <metadata>
+            <keywords>
+                <indexterm end="pdf-plugin"/>
+            </keywords>
+        </metadata>
+    </prolog>
+    <body>
+        <p>You can use custom stylesheets to implement additional processing routines or adjust the output generated by
+            the default toolkit processing.</p>
+    </body>
+</topic>

SE/stuff/dita-ot-3.3.3/docsrc/topics/pdf2-creating-change-bars.dita

@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="concept_gsc_vcf_vs">
+  <title>Generating revision bars</title>
+  <shortdesc>If you use Antenna House Formatter or RenderX XEP, you can generate revision bars in your PDF output by
+    using the <xmlatt>changebar</xmlatt> and <xmlatt>color</xmlatt> attributes of the DITAVAL
+      <xmlelement>revprop</xmlelement> element.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>revprop</xmlelement></indexterm>
+        <indexterm><xmlatt>changebar</xmlatt></indexterm>
+        <indexterm><xmlatt>color</xmlatt></indexterm>
+        <indexterm>DITAVAL<indexterm>change bars</indexterm></indexterm>
+        <indexterm>RenderX<indexterm>change bars</indexterm></indexterm>
+        <indexterm>Antenna House<indexterm>change bars</indexterm></indexterm>
+        <indexterm>Apache FOP<indexterm>change bars</indexterm></indexterm>
+        <indexterm>PDF<indexterm>change bars</indexterm></indexterm>
+        <indexterm>transformations<indexterm end="pdf"/></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <note>The Apache Formatting Objects Processor (FOP <keyword keyref="tool.fop.version"/>) bundled with DITA-OT does
+      not yet support the XSL <codeph>fo:change-bar</codeph> formatting object. A patch has been submitted to enable
+      this support in a future version of FOP.</note>
+    <p>The DITA specification for <xmlatt>changebar</xmlatt> simply says:<lq>
+        <dl>
+          <dlentry>
+            <dt><xmlatt>changebar</xmlatt></dt>
+            <dd>When flag has been set, specify a changebar color, style, or character, according to the changebar
+              support of the target output format. If flag has not been set, this attribute is ignored.</dd>
+          </dlentry>
+        </dl>
+      </lq></p>
+    <p>The current version of DITA Open Toolkit uses two <xmlelement>revprop</xmlelement> attribute values to define
+      revision bars:</p>
+    <ul>
+      <li>
+        <p>The <xmlatt>changebar</xmlatt> attribute value defines the style to use for the line. The list of possible
+          values is the same as for other XSL-FO rules (see <xref keyref="fo-spec.change-bar-style"/>). The default
+          value is <option>groove</option>.</p></li>
+      <li>
+        <p>The <xmlatt>color</xmlatt> attribute value specifies the change bar color using any color value recognized by
+          XSL-FO, including the usual color names or a hex color value. The default value is
+        <option>black</option>.</p></li>
+    </ul>
+    <fig>
+      <title>Sample revision bar configuration</title>
+      <codeblock outputclass="language-xml">&lt;revprop action="flag" changebar="solid" color="green"/></codeblock>
+    </fig>
+    <p>DITA-OT uses a default offset of 2 mm to place the revision bar near the edge of the text column. The offset,
+      placement and width are not currently configurable via attribute values.</p>
+    <!-- Doesn't look like there is any way to set the offset (defaults to `2mm2), placement, or width -->
+    <!-- https://github.com/dita-ot/dita-ot/pull/3111#issuecomment-431110715 -->
+    <!-- 
+    <parml>
+      <plentry>
+        <pt>offset</pt>
+        <pd>The space to offset the revision bar from the edge of the text column. You can use points (pt) or
+          millimeters (mm).</pd>
+      </plentry>
+      <plentry>
+        <pt>placement</pt>
+        <pd>The side of the text column on which to place the revision bar. The allowed values are
+            <option>start</option> (left side for left-to-right languages) and <option>end</option> (right side for
+          left-to-right languages). The default value is <option>start</option>.</pd>
+      </plentry>
+      <plentry>
+        <pt>width</pt>
+        <pd>The width of the rule as a measurement value. Typical values are <option>1pt</option> and
+            <option>0.5pt</option>, which renders a hairline rule.</pd>
+      </plentry>
+    </parml>
+    -->
+    <p>XSL-FO 1.1 does not provide for revision bars that are not rules, so there is no way to get text revision
+      indicators instead of rules, for example, using a number in place of a rule. Antenna House Formatter provides a
+      proprietary extension to enable this, but the DITA-OT PDF transformation does not take advantage of it.</p>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plug-ins.ditamap

@@ -0,0 +1,133 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" "map.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<map>
+  <title>Working with plug-ins</title>
+  <topicref keyref="custom-plugins">
+    <topicref keyref="plugins-installing"/>
+    <topicref keyref="plugins-removing"/>
+    <topicref keyref="plugins-registry"/>
+    <topicref keyref="plugin-configfile"/>
+    <topicref keyref="plugin-dependencies"/>
+    <topicref keyref="plugin-applications">
+      <topicref keyref="plugin-xmlcatalog"/>
+      <topicref keyref="plugin-anttarget"/>
+      <topicref keyref="plugin-antpreprocess"/>
+      <topicref keyref="plugin-newtranstype"/>
+      <topicref keyref="plugin-overridestyle"/>
+      <topicref keyref="using-plugin-URI-extension"/>
+      <topicref keyref="plugin-xsltparams"/>
+      <topicref keyref="plugin-javalib"/>
+      <topicref keyref="plugin-messages"/>
+      <topicref keyref="plugin-newextensions"/>
+      <topicref keyref="plugin-implement-saxon-customizations">
+        <topicref keyref="plugin-implement-saxon-extension-functions"/>
+        <topicref keyref="plugin-implement-saxon-collation-uri-resolvers"/>
+      </topicref>
+    </topicref>
+    <topicref keyref="plugin-sample"/>
+    <topicref keyref="plugin-best-practices"/>
+    <topicref keyref="plugin-coding-conventions"/>
+  </topicref>
+
+  <reltable>
+    <title>Bi-directional links</title>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-best-practices"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-coding-conventions"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugins-installing"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugins-registry"/>
+      </relcell>
+    </relrow>
+  </reltable>
+
+  <reltable>
+    <title>Source and target links</title>
+    <relheader>
+      <relcolspec linking="sourceonly"/>
+      <relcolspec linking="targetonly"/>
+    </relheader>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-xmlcatalog"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-extension-points-general"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-anttarget"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-extension-points-general"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-antpreprocess"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-extension-points-pre-processing"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-newtranstype"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-extension-points-general"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-overridestyle"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-extension-points-xslt-import"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-xsltparams"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-extension-points-xslt-parameters"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-javalib"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-extension-points-general"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-messages"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-extension-points-general"/>
+      </relcell>
+    </relrow>
+    <relrow>
+      <relcell>
+        <topicref keyref="plugin-configfile"/>
+      </relcell>
+      <relcell>
+        <topicref keyref="plugin-newextensions"/>
+      </relcell>
+    </relrow>
+  </reltable>
+</map>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-addgeneratedtext.dita

@@ -0,0 +1,130 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="plugin-addgeneratedtext" xml:lang="en-US">
+  <title>Customizing generated text</title>
+  <shortdesc>Generated text is the term for strings that are automatically added by the build, such as "Note" before the
+    contents of a <xmlelement>note</xmlelement> element.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>note</xmlelement></indexterm>
+        <indexterm><xmlatt>xml:lang</xmlatt></indexterm>
+        <indexterm>languages<indexterm>adding support for</indexterm></indexterm>
+        <indexterm>English</indexterm>
+        <indexterm>Icelandic</indexterm>
+        <indexterm>Russian</indexterm>
+        <indexterm>Vietnamese</indexterm>
+        <indexterm>Gaelic</indexterm>
+        <indexterm>strings</indexterm>
+        <indexterm>generated text</indexterm>
+        <indexterm>draft<indexterm>localizing generated text</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section>
+      <p>The generated text extension point is used to add new strings to the default set of generated text. There are
+        several reasons you may want to use this:
+        <ul>
+          <li>It can be used to add new text for your own processing extensions; for example, it could be used to add
+            localized versions of the string "User response" to aid in rendering troubleshooting information.</li>
+          <li>It can be used to override the default strings in the toolkit; for example, it could be used to reset the
+            English string "Figure" to "Fig".</li>
+          <li>It can be used to add support for new languages (for non-PDF transforms only; PDF requires more
+            complicated localization support). For example, it could be used to add support for Vietnamese or Gaelic; it
+            could also be used to support a new variant of a previously supported language, such as Australian
+            English.</li>
+        </ul></p>
+      <dl>
+        <dlentry>
+          <dt><codeph>dita.xsl.strings</codeph></dt>
+          <dd>Add new strings to generated text file. </dd>
+        </dlentry>
+      </dl>
+    </section>
+    <example>
+      <title>Example: adding new strings</title>
+      <p>First copy the file <filepath>xsl/common/strings.xml</filepath> to your plug-in, and edit it to contain the
+        languages that you are providing translations for ("en-US" must be present). For this sample, copy the file into
+        your plug-in as <filepath>xsl/my-new-strings.xml</filepath>. The new strings file will look something like
+        this:</p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version="1.0" encoding="utf-8"?>
+&lt;!-- Provide strings for my plug-in; this plug-in supports
+     English, Icelandic, and Russian. -->
+&lt;langlist>
+  &lt;lang xml:lang="en"     filename="mystring-en-us.xml"/>
+  &lt;lang xml:lang="en-US"  filename="mystring-en-us.xml"/>
+  &lt;lang xml:lang="is"     filename="mystring-is-is.xml"/>
+  &lt;lang xml:lang="is-IS"  filename="mystring-is-is.xml"/>
+  &lt;lang xml:lang="ru"     filename="mystring-ru-ru.xml"/>
+  &lt;lang xml:lang="ru-RU"  filename="mystring-ru-ru.xml"/>
+&lt;/langlist></codeblock>
+      <p>Next, copy the file <filepath>xsl/common/strings-en-us.xml</filepath> to your plug-in, and replace the content
+        with your own strings (be sure to give them unique name attributes). Do the same for each language that you are
+        providing a translation for. For example, the file <filepath>mystring-en-us.xml</filepath> might contain:</p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version="1.0" encoding="utf-8"?>
+&lt;strings xml:lang="en-US">
+  &lt;str name="String1">English generated text&lt;/str>
+  &lt;str name="Another String">Another String in English&lt;/str>
+&lt;/strings></codeblock>
+      <p>Use the following extension code to include your strings in the set of generated text: </p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;plugin id="com.example.strings">
+  &lt;feature extension="dita.xsl.strings" file="xsl/my-new-strings.xml"/>
+&lt;/plugin></codeblock>
+      <p>The string is now available to the "getVariable" template used in many DITA-OT XSLT files.
+        For example, if processing in a context where the xml:lang value is "en-US", the following
+        call would return "Another String in English":</p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;xsl:call-template name="getVariable">
+  &lt;xsl:with-param name="id" select="'Another String'"/>
+&lt;/xsl:call-template></codeblock>
+      <note>If two plug-ins define the same string, the results will be non-deterministic, so multiple plug-ins should
+        not try to create the same generated text string. One common way to avoid this problem is to ensure the name
+        attributes used to look up the string value are related to the ID or purpose of your plug-in.</note>
+    </example>
+    <example>
+      <title>Example: modifying existing strings</title>
+      <p>The process for modifying existing generated text is exactly the same as for adding new text, except that the
+        strings you provide override values that already exist. To begin, set up the
+          <filepath>xsl/my-new-strings.xml</filepath> file in your plug-in as in the previous example. </p>
+      <p>Next, copy the file <filepath>xsl/common/strings-en-us.xml</filepath> to your plug-in, and choose the strings
+        you wish to change (be sure to leave the name attribute unchanged, because this is the key used to look up the
+        string). Create a strings file for each language that needs to modify existing strings. For example, the new
+        file <filepath>mystring-en-us.xml</filepath> might contain:</p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version="1.0" encoding="utf-8"?>
+&lt;strings xml:lang="en-US">
+  &lt;str name="Figure">Fig&lt;/str>
+  &lt;str name="Draft comment">ADDRESS THIS DRAFT COMMENT&lt;/str>
+&lt;/strings></codeblock>
+      <p>To include the new strings, use the same method as above to add these strings to your
+          <filepath>plugin.xml</filepath> file. Once this plug-in is installed, where XHTML output previously generated
+        the term "Figure", it will now generate "Fig"; where it previously generated "Draft comment", it will now
+        generate "ADDRESS THIS DRAFT COMMENT". The same strings in other languages will not be modified unless you also
+        provide new versions for those languages.</p><note>If two plug-ins override the same string in the same
+        language, the results will be non-deterministic (either string may be used under different conditions). Multiple
+        plug-ins should not override the same generated text string for a single language.</note>
+    </example>
+    <example>
+      <title>Example: adding a new language</title>
+      <p>The process for adding a new language is exactly the same as for adding new text, except you are effectively
+        just translating an existing strings file. To begin, set up the <filepath>xsl/my-new-strings.xml</filepath> file
+        in your plug-in as in the previous examples. In this case, the only difference is that you are adding a mapping
+        to new languages; for example, the following file would be used to set up support for
+        Vietnamese:<codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version="1.0" encoding="utf-8"?>
+&lt;!-- Map languages with xml:lang="vi" or xml:lang="vi-vn"
+     to the translations in this plug-in. -->
+&lt;langlist>
+  &lt;lang xml:lang="vi"     filename="strings-vi.xml"/>
+  &lt;lang xml:lang="vi-VN"  filename="strings-vi.xml"/>
+&lt;/langlist></codeblock></p>
+      <p>Next, copy the file <filepath>xsl/common/strings-en-us.xml</filepath> to your plug-in, and rename it to match
+        the language you wish to add. For example, to support Vietnamese strings you may want to pick a name like
+          <filepath>strings-vi.xml</filepath>. In that file, change the <xmlatt>xml:lang</xmlatt> attribute on the root
+        element to match your new language.</p>
+      <p>Once the file is ready, translate the contents of each <xmlelement>str</xmlelement> element (be sure to leave
+        the name attribute unchanged). Repeat this process for each new language you wish to add.</p>
+      <p>To include the new languages, use the same method as above to add these strings to your
+          <filepath>plugin.xml</filepath> file. Once this plug-in is installed, non-PDF builds will include support for
+        Vietnamese; instead of generating the English word "Caution", the element <codeph>&lt;note type="caution"
+          xml:lang="vi"></codeph> may generate something like "<term xml:lang="vi">chú ý</term>".</p><note>If two
+        plug-ins add support for the same language using different values, the results will be non-deterministic
+        (translations from either plug-in may be picked up under different conditions).</note>
+    </example>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-antpreprocess.dita

@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="plugin-antpreprocess" xml:lang="en-US">
+  <title>Adding an Ant target to the pre-processing pipeline</title>
+  <shortdesc>You can add an Ant target to the pre-processing pipeline. This enables you to insert additional processing
+    before or after the pre-processing chain or a specific step in the pre-processing operation.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>plug-ins<indexterm>Ant</indexterm></indexterm>
+        <indexterm>Ant<indexterm>preprocessing</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>You can use the <codeph>depend.preprocess.pre</codeph> and <codeph>depend.preprocess.post</codeph> extension
+        points to run a target before or after the entire pre-processing operation. In addition, there are extension
+        points that enable you to run an Ant target before specific pre-processing steps.</p>
+      <note conref="../resources/conref-task.dita#ID/tip-extend-before-after-preprocessing"/>
+    </context>
+    <steps>
+      <step>
+        <cmd>Define and integrate the new Ant target.</cmd>
+      </step>
+      <step>
+        <cmd>Create the following <filepath>plugin.xml</filepath> file:</cmd>
+        <info><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;plugin id="<varname>plugin-id</varname>">
+  &lt;feature extension="<varname>extension-point</varname>" value="<varname>Ant-target</varname>"/>
+&lt;/plugin></codeblock>where
+          <ul>
+            <li><varname>plugin-id</varname> is the plug-in identifier.</li>
+            <li><varname>extension-point</varname> is a pre-processing extension point.</li>
+            <li><varname>Ant-target</varname> is the name of the Ant target.</li>
+          </ul></info>
+      </step>
+      <step>
+        <cmd>Install the plug-in.</cmd>
+      </step>
+    </steps>
+    <result>The new target is added to the Ant dependency list. The new target is now always run in conjunction with the
+      specified step in the pre-processing pipeline.</result>
+    <example>
+      <title>Example</title>
+      <p>The following <filepath>plugin.xml</filepath> file specifies that the
+          <parmname>myAntTargetBeforeChunk</parmname> target is always run before the <codeph>chunk</codeph> step in the
+        pre-processing stage.</p>
+      <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;plugin id="com.example.extendchunk">
+  &lt;feature extension="depend.preprocess.chunk.pre" 
+           value="myAntTargetBeforeChunk"/>
+&lt;/plugin></codeblock>
+      <p>It assumes that the <parmname>myAntTargetBeforeChunk</parmname> target has already been defined and
+        integrated.</p>
+      <note conref="../resources/conref-task.dita#ID/caution-extend-within-preprocessing"/>
+    </example>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-anttarget.dita

@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="plugin-anttarget" xml:lang="en-US">
+  <title>Adding a new target to the Ant build process</title>
+  <shortdesc>As of DITA-OT 3.0, the <codeph>ant.import</codeph> extension point can be used to make new targets
+    available to the Ant processing pipeline. This can be done as part of creating a new transformation, extending
+    pre-processing, or simply to make new Ant targets available to other plug-ins.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>plug-ins<indexterm>Ant</indexterm></indexterm>
+        <indexterm><codeph>ant.import</codeph></indexterm>
+        <indexterm>preprocessing</indexterm>
+        <indexterm>Ant<indexterm>targets</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <steps>
+      <step>
+        <cmd>Create an Ant project file that contains the new target(s).</cmd>
+      </step>
+      <step>
+        <cmd>Create the <filepath>plugin.xml</filepath> file:</cmd>
+        <stepxmp><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;plugin id="<varname>plugin-id</varname>">
+  &lt;feature extension="ant.import" file="<varname>build-file</varname>"/>
+&lt;/plugin></codeblock>where:
+          <ul>
+            <li><varname>plugin-id</varname> is the plug-in identifier, for example,
+              <codeph>com.example.ant</codeph>.</li>
+            <li><varname>build-file</varname> is the Ant project file that contains the new build target(s).</li>
+          </ul></stepxmp>
+      </step>
+      <step>
+        <cmd>Install the plug-in.</cmd>
+      </step>
+    </steps>
+    <result>
+      <p>The targets from the project (<varname>build-file</varname>) are copied into the <filepath>build.xml</filepath>
+        file, using the correct path. This makes the new Ant targets available to other processes.</p>
+      <note type="tip">Earlier versions of DITA-OT use the <codeph>dita.conductor.target.relative</codeph> to call a
+        wrapper file with a dummy task that imports the Ant project file. This approach is still supported for backwards
+        compatibility, but the simpler <codeph>ant.import</codeph> approach described above should be used for all new
+        customizations.</note>
+    </result>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-applications.dita

@@ -0,0 +1,16 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="plugins-overview">
+  <title>Plug-in applications</title>
+  <shortdesc>Plug-ins allow you to extend the functionality of DITA-OT. This might entail adding support for specialized
+    document types, integrating processing overrides, or defining new output transformations.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>plug-ins<indexterm start="plugin-ideas">ideas for</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-best-practices.dita

@@ -0,0 +1,60 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="best-practices-pdf-customization-plugins">
+  <title>Best practices for custom plug-ins</title>
+  <titlealts>
+    <navtitle>Best practices</navtitle>
+  </titlealts>
+  <shortdesc>Adhering to certain development practices will properly isolate your code from that of DITA Open Toolkit.
+    This will make it easier to you to upgrade to new versions of DITA-OT when they are released.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>plug-ins<indexterm>best practices</indexterm></indexterm>
+        <indexterm>upgrading<indexterm>best practices</indexterm></indexterm>
+        <indexterm>XSLT<indexterm>best practices</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <ul>
+      <li>
+        <p>Use a properly-constructed DITA-OT plug-in.</p></li>
+      <li>
+        <p>Use a version control system to store your code.</p></li>
+      <li>
+        <p>Never modify any of the core DITA-OT code.<note type="tip">You may want to set the permissions on default
+            plug-in directories such as <filepath>org.dita.pdf2</filepath> to “read-only” to ensure that you do not
+            accidentally modify the files within as you develop your customized plug-in.</note></p></li>
+      <li>
+        <p>Avoid copying entire DITA-OT files into your customization plug-in. When you only copy the attribute sets and
+          templates that you need to override, there is less risk of impact from new features or fixes in the base code,
+          making your code more stable and easier to upgrade between releases.</p></li>
+      <li>
+        <p>If you only need to change a few attribute sets and templates, you may prefer to store your overrides in
+            <filepath>custom.xsl</filepath> files, or a simple folder hierarchy within your custom plug-in.</p></li>
+      <li>
+        <p>In cases that require substantial customizations, you may prefer to organize the files in a folder structure
+          that mimics the hierarchy of the default plug-in you are customizing. This facilitates comparisons with the
+          default settings in the base plug-in and makes it easier to migrate your changes to new toolkit versions. See
+          <xref keyref="pdf-plugin-structure"/> for information on the files in the base PDF plug-in.</p></li>
+      <li>
+        <p>Upgrade your customization plug-in to new versions of DITA-OT regularly. Do not wait through several major
+          releases before upgrading.</p></li>
+      <li><div conkeyref="reusable-components/plugin.rnc"/></li>
+      <li>
+        <p>For XSLT customizations, use a custom namespace for any modified template modes, template names, attribute
+          sets, functions, and variables. This helps to clarify which portions of the code are specific to your
+          customizations, and serves to isolate your changes in the event that items with the same name are added to the
+          base plug-ins in the future.</p>
+        <p>For example, instead of creating a template named <codeph>searchbar</codeph>, use something like
+            <codeph>corp:searchbar</codeph> instead. This ensures that if future versions of DITA-OT add a
+            <codeph>searchbar</codeph> template, your custom version will be unaffected.</p>
+        <p>Instead of: <codeblock outputclass="language-xml">&lt;xsl:template name="searchbar"/></codeblock></p>
+        <p>use: <codeblock outputclass="language-xml">&lt;xsl:template name="corp:searchbar"/></codeblock></p>
+      </li>
+    </ul>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-coding-conventions.dita

@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="ID">
+  <title>Plug-in coding conventions</title>
+  <titlealts>
+    <navtitle>Coding conventions</navtitle>
+  </titlealts>
+  <shortdesc>To ensure custom plug-ins work well with the core toolkit code and remain compatible with future releases,
+    the DITA Open Toolkit project recommends that plug-ins use modern development practices and common coding
+    patterns.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm end="plugins"/>
+        <indexterm>plug-ins<indexterm>best practices</indexterm></indexterm>
+        <indexterm>XSLT<indexterm>best practices</indexterm></indexterm>
+        <indexterm>preprocessing<indexterm>XSLT</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <section conkeyref="reusable-components/use-xslt2"/>
+    <section>
+      <title>Use custom <xmlelement>pipeline</xmlelement> elements</title>
+      <div outputclass="div-index">
+        <indexterm>Ant<indexterm><xmlelement>pipeline</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>xslt</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>style</xmlelement></indexterm></indexterm>
+      </div>
+      <p>In Ant scripts, use the XSLT module from DITA-OT instead of Ant’s built-in <xmlelement>xslt</xmlelement> or
+          <xmlelement>style</xmlelement> tasks. </p>
+      <p>The XSLT module allows access to DITA-OT features like using the job configuration to select files in the
+        temporary folder based on file metadata and custom XSLT extension functions. </p>
+      <p>Instead of:</p>
+      <p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;xslt style="${dita.plugin.example.dir}/custom.xsl"
+      basedir="${dita.temp.dir}"
+      destdir="${dita.output.dir}"
+      includesfile="${dita.temp.dir}/${fullditatopicfile}"/></codeblock></p>
+      <p>use:</p>
+      <p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;pipeline>
+  &lt;xslt style="${dita.plugin.example.dir}/custom.xsl"
+        destdir="${dita.output.dir}">
+    &lt;ditafileset format="dita" />
+  &lt;/xslt>
+&lt;/pipeline></codeblock></p>
+    </section>
+
+    <section>
+      <title>Use the plug-in directory property</title>
+      <p>In Ant scripts, always refer to files in other plug-ins using the
+            <codeph>dita.plugin.<varname>plugin-id</varname>.dir</codeph> property.</p>
+      <p>Instead of:</p>
+      <p><codeblock outputclass="language-xml">&lt;property name="base" location="../example/custom.xsl"/></codeblock></p>
+      <p>use:</p>
+      <p><codeblock outputclass="language-xml">&lt;property name="base" location="${dita.plugin.example.dir}/custom.xsl"/></codeblock></p>
+      <p>This fixes cases where plug-ins are installed to custom plug-in directories or the plug-in folder name doesn’t
+        match the plug-in ID.</p>
+    </section>
+
+    <section>
+      <title>Use <xmlelement>ditafileset</xmlelement> to select files</title>
+      <div outputclass="div-index">
+        <indexterm>Ant<indexterm><xmlelement>ditafileset</xmlelement></indexterm></indexterm>
+        <indexterm><xmlelement>ditafileset</xmlelement></indexterm>
+        <indexterm>images<indexterm>selecting</indexterm></indexterm>
+        <indexterm>images<index-see-also>copy-files</index-see-also></indexterm>
+      </div>
+      <p>In Ant scripts, use <xmlelement>ditafileset</xmlelement> to select resources in the temporary directory.</p>
+      <p>For example, to select all images referenced by input DITA files, instead of:</p>
+      <p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;copy todir="${copy-image.todir}">
+  &lt;fileset dir="${user.input.dir}">
+    &lt;includes name="*.jpg"/>
+    &lt;includes name="*.jpeg"/>
+    &lt;includes name="*.png"/>
+    &lt;includes name="*.gif"/>
+    &lt;includes name="*.svg"/>
+  &lt;/fileset>
+&lt;/copy></codeblock></p>
+      <p>use:</p>
+      <p><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;copy todir="${copy-image.todir}">
+  &lt;ditafileset format="image" />
+&lt;/copy></codeblock>
+      </p>
+      <p>The <xmlelement>ditafileset</xmlelement> resource collection can be used to select different types of
+        files.</p>
+      <table outputclass="table-hover" frame="none" colsep="0" rowsep="1">
+        <title>Usage examples of <xmlelement>ditafileset</xmlelement></title>
+        <tgroup cols="2">
+          <colspec colwidth="1*"/>
+          <colspec colwidth="1*"/>
+          <thead>
+            <row>
+              <entry>Example</entry>
+              <entry>Description</entry>
+            </row>
+          </thead>
+          <tbody>
+            <row>
+              <entry><codeph>&lt;ditafileset format="dita"/></codeph></entry>
+              <entry>Selects all DITA topics in the temporary directory.</entry>
+            </row>
+            <row>
+              <entry><codeph>&lt;ditafileset format="ditamap"/></codeph></entry>
+              <entry>Selects all DITA maps in the temporary directory.</entry>
+            </row>
+            <row>
+              <entry><codeph>&lt;ditafileset format="image"/></codeph></entry>
+              <entry>Selects images of all known types in the temporary directory.</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+    </section>
+
+    <section>
+      <title>Use the <codeph>plugin</codeph> URI scheme</title>
+      <div outputclass="div-index">
+        <indexterm>Ant<indexterm><xmlelement>xsl:import</xmlelement></indexterm></indexterm>
+        <indexterm>Ant<indexterm><xmlelement>xsl:include</xmlelement></indexterm></indexterm>
+      </div>
+      <p>In XSLT, use the <codeph>plugin</codeph> URI scheme in <xmlelement>xsl:import</xmlelement> and
+          <xmlelement>xsl:include</xmlelement> to reference files in other plug-ins.</p>
+      <p>Instead of:</p>
+      <p><codeblock outputclass="language-xml">&lt;xsl:import href="../../org.dita.base/xsl/common/output-message.xsl"/></codeblock></p>
+      <p>use:</p>
+      <p><codeblock outputclass="language-xml">&lt;xsl:import href="plugin:org.dita.base:xsl/common/output-message.xsl"/></codeblock></p>
+      <p>As with the plug-in directory property in Ant, this allows plug-ins to resolve to the correct directory even
+        when a plug-in moves to a new location. The plug-in is referenced using the syntax
+            <codeph>plugin:<varname>plugin-id</varname>:<varname>path/within/plugin/file.xsl</varname></codeph>.</p>
+    </section>
+
+    <section conkeyref="reusable-components/validating-plugins"/>
+
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-configfile.dita

@@ -0,0 +1,357 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<reference id="plugin-configfile" xml:lang="en-US">
+  <title>Plug-in descriptor file</title>
+  <shortdesc>The plug-in descriptor file (<filepath>plugin.xml</filepath>) controls all aspects of a plug-in, making
+    each extension visible to the rest of the toolkit. The file uses pre-defined extension points to locate changes, and
+    then integrates those changes into the core DITA-OT code.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>plug-ins<indexterm>identfiers</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm><filepath>plugin.xml</filepath></indexterm></indexterm>
+        <indexterm>metadata<indexterm>plug-in</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <refbody>
+    <section conkeyref="reusable-components/validating-plugins"/>
+    <section>
+      <title>Plug-in identifiers</title>
+      <div outputclass="div-index">
+        <indexterm><xmlatt>id</xmlatt><indexterm>plug-in</indexterm></indexterm>
+      </div>
+      <p>Every DITA-OT plug-in must have a unique identifier composed of one or more dot-delimited tokens, for example,
+          <codeph>com.example.rss</codeph>. This identifier is used to identify the plug-in to the toolkit for
+        installation, processing, and when determining plug-in dependencies.</p>
+      <note>The default DITA-OT plug-ins use a reverse domain naming convention, as in <codeph>org.dita.html5</codeph>;
+        this is strongly recommended to avoid plug-in naming conflicts.</note>
+      <p id="tokendef">Each token can include only the following characters:
+        <ul>
+          <li>Lower-case letters (a-z)</li>
+          <li>Upper-case letters (A-Z)</li>
+          <li>Numerals (0-9)</li>
+          <li>Underscores (_)</li>
+          <li>Hyphens (-)</li>
+        </ul></p>
+    </section>
+    <section>
+      <title><xmlelement>plugin</xmlelement></title>
+      <p>The root element of the <filepath>plugin.xml</filepath> file is <xmlelement>plugin</xmlelement>, which has a
+        required <xmlatt>id</xmlatt> attribute set to the unique plug-in identifier.</p>
+      <fig>
+        <title>Sample <xmlelement>plugin</xmlelement> element</title>
+        <codeblock outputclass="language-xml"><coderef href="../samples/plugins/com.example.html5-javascript/plugin.xml#line=3,4"/></codeblock>
+      </fig>
+    </section>
+    <section>
+      <title>Plug-in elements</title>
+      <div outputclass="div-index">
+        <indexterm><xmlelement>plugin</xmlelement></indexterm>
+      </div>
+      <draft-comment author="Kristen Eberlein" time="13 May 2013">Perhaps all the following tables should have a Data
+        type column? That would match with the DITA spec; also, it seems as if some attributes must take a predefined
+        set of values.</draft-comment>
+      <p>The <xmlelement>plugin</xmlelement> element can contain the following child elements: </p>
+      <parml>
+        <plentry>
+          <pt><xmlelement>extension-point</xmlelement></pt>
+          <pd>
+            <indexterm><xmlelement>extension-point</xmlelement></indexterm>
+            <p>An optional element that defines a new extension point that can be used by other DITA-OT plug-ins.</p>
+            <p>The following attributes are supported:</p>
+            <simpletable keycol="1">
+              <sthead>
+                <stentry>Attribute</stentry>
+                <stentry>Description</stentry>
+                <stentry>Required?</stentry>
+              </sthead>
+              <strow>
+                <stentry>id</stentry>
+                <stentry>Extension point identifier</stentry>
+                <stentry>Yes</stentry>
+              </strow>
+              <strow>
+                <stentry>name</stentry>
+                <stentry>Extension point description</stentry>
+                <stentry>No</stentry>
+              </strow>
+            </simpletable>
+            <p id="extension-point-ids">Like plug-in identifiers, extension point identifiers are composed of one or
+              more dot-delimited tokens.</p>
+            <note id="entension-point-ids-note">Extension point identifiers should begin with the identifier of the
+              defining plug-in and append one or more tokens, for example, <codeph>org.dita.example.pre</codeph>.</note>
+            <fig>
+              <title>Sample <xmlelement>extension-point</xmlelement> element</title>
+              <codeblock outputclass="language-xml">&lt;extension-point id="dita.xsl.html5" name="HTML5 XSLT import"/></codeblock>
+            </fig>
+          </pd>
+        </plentry>
+        <plentry>
+          <pt><xmlelement>feature</xmlelement></pt>
+          <pd>
+            <indexterm><xmlelement>feature</xmlelement></indexterm>
+            <indexterm><xmlatt>value</xmlatt></indexterm>
+            <indexterm><xmlatt>file</xmlatt></indexterm>
+            <p>An optional element that supplies values to a DITA-OT extension point.</p>
+            <p>The following attributes are supported:</p>
+            <simpletable keycol="1">
+              <sthead>
+                <stentry>Attribute</stentry>
+                <stentry>Description</stentry>
+                <stentry>Required?</stentry>
+              </sthead>
+              <strow>
+                <stentry>extension</stentry>
+                <stentry>Identifier of the DITA-OT extension point</stentry>
+                <stentry>Yes</stentry>
+              </strow>
+              <strow>
+                <stentry>value</stentry>
+                <stentry>Comma separated string value of the extension</stentry>
+                <stentry>Either the <xmlatt>value</xmlatt> or <xmlatt>file</xmlatt> attribute must be
+                  specified</stentry>
+              </strow>
+              <strow>
+                <stentry>file</stentry>
+                <stentry>Name and path of a file containing data for the extension point.
+                  <p>Depending on the extension point, this might be specified as an absolute path, a path relative to
+                    the <filepath>plugin.xml</filepath> file, or a path relative to the DITA-OT root.</p></stentry>
+                <stentry>Either the <xmlatt>value</xmlatt> or <xmlatt>file</xmlatt> attribute must be
+                  specified</stentry>
+              </strow>
+              <strow>
+                <stentry>type</stentry>
+                <stentry>Type of the <xmlatt>value</xmlatt> attribute</stentry>
+                <stentry>No</stentry>
+              </strow>
+            </simpletable>
+            <fig>
+              <title>Sample <xmlelement>feature</xmlelement> elements</title>
+              <p>If more than one <xmlelement>feature</xmlelement> element supplies values to the same extension point,
+                the values are additive. For example, the following are equivalent:</p>
+              <codeblock outputclass="language-xml">&lt;feature extension="org.dita.example.extension-point" value="a,b,c"/></codeblock>
+              <codeblock outputclass="language-xml">&lt;feature extension="org.dita.example.extension-point" value="a"/>
+&lt;feature extension="org.dita.example.extension-point" value="b"/>
+&lt;feature extension="org.dita.example.extension-point" value="c"/></codeblock>
+            </fig>
+          </pd>
+        </plentry>
+        <plentry>
+          <pt><xmlelement>meta</xmlelement></pt>
+          <pd>
+            <indexterm><xmlelement>meta</xmlelement></indexterm>
+            <p>An optional element that defines metadata.</p>
+            <p>The following attributes are supported:</p>
+            <simpletable keycol="1">
+              <sthead>
+                <stentry>Attribute</stentry>
+                <stentry>Description</stentry>
+                <stentry>Required?</stentry>
+              </sthead>
+              <strow>
+                <stentry>type</stentry>
+                <stentry>Metadata name </stentry>
+                <stentry>Yes</stentry>
+              </strow>
+              <strow>
+                <stentry>value</stentry>
+                <stentry>Metadata value</stentry>
+                <stentry>Yes</stentry>
+              </strow>
+            </simpletable>
+            <fig>
+              <title>Sample <xmlelement>meta</xmlelement> element</title>
+              <codeblock outputclass="language-xml">&lt;meta type="foo" value="bar"/></codeblock>
+            </fig>
+          </pd>
+        </plentry>
+        <plentry>
+          <pt><xmlelement>require</xmlelement></pt>
+          <pd>
+            <indexterm><xmlelement>require</xmlelement></indexterm>
+            <p>An optional element that defines plug-in dependencies.</p>
+            <p>The following attributes are supported:</p>
+            <simpletable keycol="1">
+              <sthead>
+                <stentry>Attribute</stentry>
+                <stentry>Description</stentry>
+                <stentry>Required?</stentry>
+              </sthead>
+              <strow>
+                <stentry>plugin</stentry>
+                <stentry>The identifier of the required plug-in.
+                  <p>To specify alternative requirements, separate plug-in identifiers with a vertical
+                  bar.</p></stentry>
+                <stentry>Yes</stentry>
+              </strow>
+              <strow>
+                <stentry>importance</stentry>
+                <stentry>Identifies whether the plug-in is <codeph>required</codeph> (default) or
+                    <codeph>optional</codeph>. DITA-OT provides a warning if a required plug-in is not
+                  available.</stentry>
+                <stentry>No</stentry>
+              </strow>
+            </simpletable>
+            <fig>
+              <title>Sample <xmlelement>require</xmlelement> element</title>
+              <codeblock outputclass="language-xml normalize-space"><coderef href="../samples/plugins/com.example.html5-javascript/plugin.xml#line=4,5"/></codeblock>
+            </fig>
+          </pd>
+        </plentry>
+        <plentry>
+          <pt><xmlelement>template</xmlelement></pt>
+          <pd>
+            <indexterm><xmlelement>template</xmlelement></indexterm>
+            <indexterm><xmlelement>dita:extension</xmlelement></indexterm>
+            <p>An optional element that defines files that should be treated as templates.</p>
+            <p>Template files can be used to integrate DITA-OT extensions. Templates typically extend the default
+              transformation-type-specific build files via <xmlelement>dita:extension</xmlelement> elements. When the
+              plug-in installation process runs, template files are used to recreate build files, and the specified
+              extension points are replaced with references to the appropriate plug-ins.</p>
+            <p>The following attributes are supported:</p>
+            <simpletable keycol="1">
+              <sthead>
+                <stentry>Attribute</stentry>
+                <stentry>Description</stentry>
+                <stentry>Required?</stentry>
+              </sthead>
+              <strow>
+                <stentry>file</stentry>
+                <stentry>Name and path to the template file, relative to the <filepath>plugin.xml</filepath>
+                  file</stentry>
+                <stentry>Yes</stentry>
+              </strow>
+            </simpletable>
+            <fig>
+              <title>Sample <xmlelement>template</xmlelement> element</title>
+              <codeblock outputclass="language-xml">&lt;template file="build_dita2html5_template.xml"/></codeblock>
+            </fig>
+          </pd>
+        </plentry>
+        <plentry>
+          <pt><xmlelement>transtype</xmlelement></pt>
+          <pd>
+            <indexterm><xmlelement>transtype</xmlelement><indexterm><filepath>plugin.xml</filepath></indexterm></indexterm>
+            <p>An optional element that defines a new output format (transformation type).</p>
+            <p>The following attributes are supported:</p>
+            <simpletable keycol="1">
+              <sthead>
+                <stentry>Attribute</stentry>
+                <stentry>Description</stentry>
+                <stentry>Required?</stentry>
+              </sthead>
+              <strow>
+                <stentry>name</stentry>
+                <stentry>Transformation name</stentry>
+                <stentry>Yes</stentry>
+              </strow>
+              <strow>
+                <stentry>desc</stentry>
+                <stentry>Transformation type description</stentry>
+                <stentry>No</stentry>
+              </strow>
+              <strow>
+                <stentry>abstract</stentry>
+                <stentry>When <option>true</option>, sets the transformation type as <q>abstract</q>, meaning it can be
+                  extended by other plug-ins, but cannot be used directly.
+                  <p>For example, the <codeph>org.dita.base</codeph> plug-in defines an abstract <q>base</q>
+                    transformation type that is extended by other DITA-OT plug-ins.</p></stentry>
+                <stentry>No</stentry>
+              </strow>
+              <strow>
+                <stentry>extends</stentry>
+                <stentry>Specifies the name of the transformation type being extended</stentry>
+                <stentry>No</stentry>
+              </strow>
+            </simpletable>
+            <fig>
+              <title>Sample <xmlelement>transtype</xmlelement> element</title>
+              <codeblock outputclass="language-xml">&lt;transtype name="base" abstract="true" desc="Common">
+  &lt;!-- ⋮ -->
+  &lt;param name="link-crawl" 
+         desc="Specifies whether to crawl only topic links found in maps, or all discovered topic links."
+         type="enum">
+    &lt;val>map&lt;/val>
+    &lt;val default="true">topic&lt;/val>
+  &lt;/param>
+  &lt;!-- ⋮ -->
+&lt;/transtype>
+</codeblock>
+            </fig>
+            <p>The <xmlelement>transtype</xmlelement> element may define additional parameters for the transformation
+              type using the following child elements.</p>
+            <parml>
+              <plentry>
+                <pt><xmlelement>param</xmlelement></pt>
+                <pd>
+                  <indexterm><xmlelement>param</xmlelement></indexterm>
+                  <p>An optional element that specifies a parameter for the transformation type.</p>
+                  <p>The following parameter attributes are supported:</p>
+                  <simpletable keycol="1">
+                    <sthead>
+                      <stentry>Attribute</stentry>
+                      <stentry>Description</stentry>
+                      <stentry>Required?</stentry>
+                    </sthead>
+                    <strow>
+                      <stentry>name</stentry>
+                      <stentry>Parameter name</stentry>
+                      <stentry>Yes</stentry>
+                    </strow>
+                    <strow>
+                      <stentry>desc</stentry>
+                      <stentry>Parameter description</stentry>
+                      <stentry>No</stentry>
+                    </strow>
+                    <strow>
+                      <stentry>type</stentry>
+                      <stentry>Parameter type (<option>enum</option>, <option>file</option>,
+                        <option>string</option>)</stentry>
+                      <stentry>Yes</stentry>
+                    </strow>
+                    <strow>
+                      <stentry>deprecated</stentry>
+                      <stentry>When <option>true</option>, identifies this parameter as deprecated</stentry>
+                      <stentry>No</stentry>
+                    </strow>
+                    <strow>
+                      <stentry>required</stentry>
+                      <stentry>When <option>true</option>, identifies this parameter as required</stentry>
+                      <stentry>No</stentry>
+                    </strow>
+                  </simpletable></pd>
+              </plentry>
+              <plentry>
+                <pt><xmlelement>val</xmlelement></pt>
+                <pd>
+                  <indexterm><xmlelement>val</xmlelement></indexterm>
+                  <p>A child of <xmlelement>param</xmlelement> (when <xmlatt>type</xmlatt>=<option>enum</option>) that
+                    specifies an enumeration value.</p>
+                  <p>The following attributes are supported:</p>
+                  <simpletable keycol="1">
+                    <sthead>
+                      <stentry>Attribute</stentry>
+                      <stentry>Description</stentry>
+                      <stentry>Required?</stentry>
+                    </sthead>
+                    <strow>
+                      <stentry>default</stentry>
+                      <stentry>When <option>true</option>, sets the enumeration value as the default value of the parent
+                          <xmlelement>param</xmlelement></stentry>
+                      <stentry>Only for the default <xmlelement>val</xmlelement></stentry>
+                    </strow>
+                  </simpletable></pd>
+              </plentry>
+            </parml>
+          </pd>
+        </plentry>
+      </parml>
+      <p>Any extension that is not recognized by DITA-OT is ignored. Since DITA-OT version 1.5.3, you can combine
+        multiple extension definitions within a single <filepath>plugin.xml</filepath> file; in older versions, only the
+        last extension definition was used.</p>
+    </section>
+  </refbody>
+</reference>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-dependencies.dita

@@ -0,0 +1,63 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<concept id="plugin-dependencies" xml:lang="en-US">
+  <title>Plug-in dependencies</title>
+  <shortdesc>A DITA-OT plug-in can be dependent on other plug-ins. Prerequisite plug-ins are installed first, which
+    ensures that DITA-OT handles XSLT overrides correctly.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlelement>require</xmlelement></indexterm>
+        <indexterm>plug-ins<indexterm>prerequisites</indexterm><indexterm>dependencies</indexterm><indexterm>order</indexterm><indexterm><xmlelement>require</xmlelement></indexterm></indexterm>
+        <indexterm>XSLT<index-see-also>plug-ins</index-see-also></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <conbody>
+    <draft-comment author="Kristen Eberlein" time="24 February 2016">
+      <p>I'm not entirely happy with this topic as it currently is, but want to move forward with the overall
+        rework.</p>
+      <p>The original topic was quite a mixture of task, concept, and reference. While it could have been reworked as a
+        task topic, it really was about working with a <filepath>plugin.xml</filepath> file, not using an extension
+        point.</p>
+      <p>I still wonder whether this topic would be better of as a reference topic in the reference section for the
+        topic cluster.</p>
+    </draft-comment>
+    <section>
+      <p>The <xmlelement>require</xmlelement> element in the <filepath>plugin.xml</filepath> file specifies whether the
+        plug-in has dependencies. Use <xmlelement>require</xmlelement> elements to specify prerequisite plug-ins, in
+        order from most general to most specific.</p>
+      <p>If a prerequisite plug-in is missing, DITA-OT prints a warning during installation. To suppress the warning but
+        keep the installation order if both plug-ins are present, add <codeph>importance="optional"</codeph> to the
+          <xmlelement>require</xmlelement> element. </p>
+      <!--<p>If the current plug-in requires a plug-in with <codeph>id="plugin-id"</codeph> before it can be installed, it would include the following: </p><codeblock>&lt;require plugin="<i>plugin-id</i>"></codeblock>-->
+      <p>If a plug-in can depend on any one of several optional plug-ins, separate the plug-in IDs with a vertical bar.
+        This is most useful when combined with <codeph>importance="optional"</codeph>.</p>
+    </section>
+    <example>
+      <title>Example: Plug-in with a prerequisite plug-in</title>
+      <p>The following plug-in will only be installed if the plug-in with the ID <codeph>com.example.primary</codeph> is
+        available. If that plug-in is not available, a warning is generated and the installation operation fails.</p>
+      <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;plugin id="com.example.builds-on-primary">
+  &lt;!-- ... Extensions here -->
+  &lt;require plugin="com.example.primary"/>
+&lt;/plugin></codeblock>
+    </example>
+    <example>
+      <title>Example: Plug-in that has optional plug-ins</title>
+      <p>The following plug-in will only be installed if either the plug-in with the ID <codeph>pluginA</codeph> or the
+        plug-in with the ID <codeph>pluginB</codeph> is available. If neither of those plug-ins are installed, a warning
+        is generated but the installation operation is completed.</p>
+      <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;plugin id="pluginC">
+  &lt;!-- ...extensions here -->
+  &lt;require plugin="pluginA|pluginB" importance="optional"/>
+&lt;/plugin></codeblock>
+      <draft-comment author="Kristen Eberlein" time="24 February 2016">
+        <p>We need to check this example against the toolkit. Text in the original topic was wrong, but I have not
+          tested this.</p>
+      </draft-comment>
+    </example>
+  </conbody>
+</concept>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-javalib.dita

@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="plugin-javalib" xml:lang="en-US">
+  <title>Adding a Java library to the DITA-OT <parmname>classpath</parmname></title>
+  <titlealts>
+    <navtitle>Adding a Java library to the <parmname>classpath</parmname></navtitle>
+  </titlealts>
+  <shortdesc>You can use the <codeph>dita.conductor.lib.import</codeph> extension point to add an additional Java
+    library to the DITA-OT <parmname>classpath</parmname> parameter.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm>deprecated features<indexterm><codeph>dost.class.path</codeph> property</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>Java</indexterm></indexterm>
+        <indexterm>Java<indexterm>classpath</indexterm></indexterm>
+        <indexterm>classpath<indexterm>Java</indexterm></indexterm>
+        <indexterm>XSLT<indexterm>Java</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <context>
+      <p>As of DITA-OT 3.1, the Java class path is managed automatically, meaning you do not (and should not) use
+        explicit references to Java class paths in your build scripts. In particular, the old
+          <codeph>dost.class.path</codeph> property has been deprecated and should not be used. If you are migrating
+        older plug-ins that manage their class path directly, you should remove any explicit class path configuration.
+        If your plug-in was not already using the <codeph>dita.conductor.lib.import</codeph> extension point to
+        integrate its JAR dependencies you must add it.</p>
+      <p>The effective DITA-OT class path is the combination of the JAR files in the main <filepath>lib/</filepath>
+        directory and the plug-in-contributed JARs, which are listed in <filepath>config/env.sh</filepath>. The
+          <filepath>env.sh</filepath> file is updated automatically when plug-ins are installed or removed.</p>
+    </context>
+    <steps>
+      <step>
+        <cmd>If necessary, compile the Java code into a JAR file.</cmd>
+      </step>
+      <step>
+        <cmd>Create a <filepath>plugin.xml</filepath> file that contains the following code:</cmd>
+        <info><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;plugin id="<varname>plugin-id</varname>">
+  &lt;feature extension="dita.conductor.lib.import" file="<varname>file</varname>"/>
+&lt;/plugin></codeblock>where:
+          <ul>
+            <li><varname>plugin-id</varname> is the plug-in identifier, for example,
+              <codeph>com.example.addjar</codeph>.</li>
+            <li><varname>file</varname> is the name of the JAR file, for example,
+              <filepath>myJavaLibrary.jar</filepath>. </li>
+          </ul></info>
+      </step>
+      <step>
+        <cmd>Install the plug-in.</cmd>
+      </step>
+    </steps>
+    <result>The Ant or XSLT code now can make use of the Java code.</result>
+    <example>
+      <p>In the following extended example, the <filepath>myJavaLibrary.jar</filepath> file performs a validation step
+        during processing, and you want it to run immediately before the <codeph>conref </codeph>step.</p>
+      <p>To accomplish this, you will need to use several features:</p>
+      <ul>
+        <li>The JAR file must be added to the classpath.</li>
+        <li>The Ant target must be added to the dependency chain for conref.</li>
+        <li>An Ant target must be created that uses this class, and integrated into the code.</li>
+      </ul>
+      <p>The files might look like the following:</p>
+      <fig>
+        <title><filepath>plugin.xml</filepath> file</title>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version="1.0" encoding="UTF-8"?>
+&lt;plugin id="com.example.samplejava">
+  <i>&lt;!-- Add the JAR file to the DITA-OT CLASSPATH --></i>
+  <b>&lt;feature extension="dita.conductor.lib.import" 
+           file="com.example.sampleValidation.jar"/></b>
+  <i>&lt;!-- Integrate the Ant code --></i>
+  &lt;feature extension="ant.import" file="calljava-antcode.xml"/>
+  <i>&lt;!-- Define the Ant target to call, and when (before conref) --></i>
+  &lt;feature extension="depend.preprocess.conref.pre" 
+           value="validateWithJava"/>
+&lt;/plugin></codeblock>
+      </fig>
+      <fig>
+        <title><filepath>calljava-antcode.xml</filepath> file</title>
+        <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;?xml version="1.0" encoding="UTF-8"?>
+&lt;project default="validateWithJava">
+  &lt;target name="validateWithJava">
+    &lt;java classname="com.example.sampleValidation">
+      &lt;!-- The class was added to the DITA-OT classpath -->
+    &lt;/java>
+  &lt;/target>
+&lt;/project></codeblock>
+      </fig>
+    </example>
+  </taskbody>
+</task>

SE/stuff/dita-ot-3.3.3/docsrc/topics/plugin-messages.dita

@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
+<!--  This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license.  -->
+
+<task id="plugin-messages" xml:lang="en-US">
+  <title>Adding new diagnostic messages</title>
+  <shortdesc>Use the <codeph>dita.xsl.messages</codeph> extension point to add plug-in-specific messages to the
+    diagnostic messages that are generated by DITA-OT. These messages then can be used by any XSLT override.</shortdesc>
+  <prolog>
+    <metadata>
+      <keywords>
+        <indexterm><xmlatt>type</xmlatt></indexterm>
+        <indexterm><xmlatt>id</xmlatt><indexterm>diagnostic messages</indexterm></indexterm>
+        <indexterm>plug-ins<indexterm>troubleshooting</indexterm></indexterm>
+        <indexterm>troubleshooting<indexterm>plug-ins</indexterm></indexterm>
+        <indexterm>XSLT<indexterm>errors</indexterm></indexterm>
+        <indexterm>preprocessing<indexterm>XSLT</indexterm></indexterm>
+      </keywords>
+    </metadata>
+  </prolog>
+  <taskbody>
+    <steps>
+      <step id="step_create-message-xml">
+        <cmd>Create an XML file that contains the messages that you want to add. Be sure to use the following format for
+          the XML file:</cmd>
+        <info><codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;messages>
+  <i>&lt;!-- See resources/messages.xml for the details. --></i>
+  &lt;message id="<varname>Prefix</varname><varname>Number</varname><varname>Letter</varname>" type="<varname>error-severity</varname>">
+    &lt;reason>Message text&lt;/reason>
+    &lt;response>How to resolve&lt;/response>
+  &lt;/message>
+&lt;/messages></codeblock>where:
+          <ul>
+            <li><varname>Prefix</varname> is a sequence of four capital letters.<note>By convention, the toolkit
+                messages use <codeph>DOTX</codeph> but any sequence can be used by plug-in developers.</note></li>
+            <li><varname>Number</varname> is a three-digit integer.</li>
+            <li><varname>Letter</varname> is one of the following upper-case letters: I, W, E, F. It should match the
+              value that is specified for the <xmlatt>type</xmlatt> attribute.<note>As the <xmlatt>id</xmlatt> attribute
+                is used as a whole and not decomposed by recent versions of the toolkit, you could use any sequence as
+                the message identifier. Nevertheless, to facilitate reuse of the plug-in and make it more readable by
+                other users, we recommend following these guidelines.</note></li>
+            <li><varname>error-severity</varname> specifies the severity of the error. It must be one of the following
+              values:
+              <dl conkeyref="messages-push/severity-levels">
+                <dlentry>
+                  <dt/>
+                  <dd/>
+                </dlentry>
+              </dl><note>The <codeph>FATAL</codeph> value throws a fatal error message in XSLT and an exception in
+                Java.</note>
+              <note type="tip">If the <xmlatt>id</xmlatt> attribute of your message is equal to the <xmlatt>id</xmlatt>
+                of a default DITA-OT message, your message will override the default one.</note></li>
+          </ul></info>
+      </step>
+      <step>
+        <cmd>Create a <filepath>plugin.xml</filepath> file that contains the following content:</cmd>
+        <info>
+          <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;plugin id="<varname>plugin-id</varname>">
+  &lt;feature extension="dita.xsl.messages" file="<varname>file</varname>"/>
+&lt;/plugin></codeblock>
+          <p>where:</p>
+          <ul>
+            <li><varname>plugin-id</varname> is the plug-in identifier, for example,
+              <codeph>com.example.newmsg</codeph>.</li>
+            <li><varname>file</varname> is the name of the new XML file containing the messages created in step
+              <xref keyref="plugin-messages/step_create-message-xml"/>, for example,
+              <filepath>myMessages.xml</filepath>. </li>
+          </ul>
+        </info>
+      </step>
+      <step>
+        <cmd>Install the plug-in.</cmd>
+      </step>
+    </steps>
+    <postreq>
+      <p>Add the following call in XSLT modules to generate a message when a specific condition occurs:</p>
+      <codeblock outputclass="language-xml normalize-space show-line-numbers show-whitespace">&lt;xsl:call-template name="output-message">
+  &lt;xsl:with-param name="id"><varname>prefix</varname><varname>number</varname><varname>letter</varname>&lt;/xsl:with-param>
+  &lt;xsl:with-param name="msg">Message text and parameters.&lt;/xsl:with-param>
+&lt;/xsl:call-template></codeblock>
+      <p>Use the <codeph>ctx</codeph> parameter if calling from a function.</p>
+    </postreq>
+  </taskbody>
+</task>