plugin-configfile.html 26 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326
  1. <!DOCTYPE html
  2. SYSTEM "about:legacy-compat">
  3. <html lang="en-us"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2019"><meta name="DC.rights.owner" content="(C) Copyright 2019"><meta name="DC.type" content="reference"><meta name="description" content="The plug-in descriptor file (plugin.xml) 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."><meta name="DC.subject" content="plug-ins, identfiers, plugin.xml, metadata, plug-in"><meta name="keywords" content="plug-ins, identfiers, plugin.xml, metadata, plug-in"><meta name="DC.relation" scheme="URI" content="../topics/custom-plugins.html"><meta name="DC.relation" scheme="URI" content="../topics/plugin-newextensions.html"><meta name="DC.relation" scheme="URI" content="../topics/plugin-newtranstype.html"><meta name="DC.relation" scheme="URI" content="../topics/plugin-sample.html"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="plugin-configfile"><meta name="DC.language" content="en-US"><link rel="stylesheet" type="text/css" href="../css/commonltr.css"><link rel="stylesheet" type="text/css" href="../css/dita-ot-doc.css"><title>Plug-in descriptor file</title></head><body id="plugin-configfile"><header role="banner"><div class="header">
  4. <p>DITA Open Toolkit</p>
  5. <hr>
  6. </div></header><nav role="toc"><ul><li><a href="../index.html">DITA Open Toolkit 3.3</a></li><li><a href="../release-notes/index.html">Release Notes</a></li><li><a href="../topics/installing-client.html">Installing DITA-OT</a></li><li><a href="../topics/alternative-input-formats.html">Authoring formats</a></li><li><a href="../topics/building-output.html">Building output</a></li><li><a href="../parameters/index.html">Setting parameters</a></li><li><a href="../topics/customizing.html">Customizing DITA-OT</a><ul><li><a href="../topics/html-customization.html">Customizing HTML</a></li><li><a href="../topics/pdf-customization.html">Customizing PDF</a></li><li><a href="../topics/custom-plugins.html">Working with plug-ins</a><ul><li><a href="../topics/plugins-installing.html">Installing plug-ins</a></li><li><a href="../topics/plugins-removing.html">Removing plug-ins</a></li><li><a href="../topics/plugins-registry.html">Plug-in registry</a></li><li class="active"><a href="../topics/plugin-configfile.html">Plug-in descriptor file</a></li><li><a href="../topics/plugin-dependencies.html">Plug-in dependencies</a></li><li><a href="../topics/plugin-applications.html">Plug-in applications</a></li><li><a href="../topics/plugin-sample.html">Example plugin.xml file</a></li><li><a href="../topics/plugin-best-practices.html">Best practices</a></li><li><a href="../topics/plugin-coding-conventions.html">Coding conventions</a></li></ul></li><li><a href="../extension-points/plugin-extension-points.html">Extension points</a></li><li><a href="../topics/migration.html">Migrating customizations</a></li><li><a href="../topics/globalization.html">Globalizing DITA content</a></li><li><a href="../topics/rebuilding-docs.html">Rebuilding documentation</a></li></ul></li><li><a href="../topics/troubleshooting-overview.html">Troubleshooting</a></li><li><a href="../reference/index.html">Reference</a></li><li><a href="../topics/dita-and-dita-ot-resources.html">Resources</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1">
  7. <h1 class="title topictitle1" id="ariaid-title1">Plug-in descriptor file</h1>
  8. <div class="body refbody"><p class="shortdesc">The plug-in descriptor file (<span class="ph filepath">plugin.xml</span>) controls all aspects of a plug-in, making
  9. each extension visible to the rest of the toolkit. The file uses pre-defined extension points to locate changes, and
  10. then integrates those changes into the core DITA-OT code.</p>
  11. <section class="section"><h2 class="title sectiontitle">Validating plug-ins</h2>
  12. <div class="div" id="plugin-configfile__d29e92">
  13. <p class="p">DITA-OT includes a RELAX NG schema file that can be used to validate the <span class="ph filepath">plugin.xml</span>
  14. files that define the capabilities of each plug-in.
  15. </p>
  16. <p class="p">To ensure the syntax of your custom plug-in is correct, include an <code class="keyword markupname xmlpi">&lt;?xml-model?&gt;</code> processing
  17. instruction at the beginning of the <span class="ph filepath">plugin.xml</span> file, immediately after the XML
  18. prolog:</p>
  19. <p class="p"><code class="keyword markupname xmlpi">&lt;?xml-model href="dita-ot/plugin.rnc" type="application/relax-ng-compact-syntax"?&gt;</code></p>
  20. <p class="p">If your authoring environment does not apply this schema automatically, point your editor to <span class="ph filepath" id="plugin-configfile__d29e123"><var class="keyword varname">dita-ot-dir</var>/resources/plugin.rnc</span> to associate the schema with
  21. your plug-in file.</p>
  22. </div>
  23. </section>
  24. <section class="section"><h2 class="title sectiontitle">Plug-in identifiers</h2>
  25. <div class="div div-index">
  26. </div>
  27. <p class="p">Every DITA-OT plug-in must have a unique identifier composed of one or more dot-delimited tokens, for example,
  28. <code class="ph codeph">com.example.rss</code>. This identifier is used to identify the plug-in to the toolkit for
  29. installation, processing, and when determining plug-in dependencies.</p>
  30. <div class="note note note_note"><span class="note__title">Note:</span> The default DITA-OT plug-ins use a reverse domain naming convention, as in <code class="ph codeph">org.dita.html5</code>;
  31. this is strongly recommended to avoid plug-in naming conflicts.</div>
  32. <div class="p" id="plugin-configfile__tokendef">Each token can include only the following characters:
  33. <ul class="ul">
  34. <li class="li">Lower-case letters (a-z)</li>
  35. <li class="li">Upper-case letters (A-Z)</li>
  36. <li class="li">Numerals (0-9)</li>
  37. <li class="li">Underscores (_)</li>
  38. <li class="li">Hyphens (-)</li>
  39. </ul></div>
  40. </section>
  41. <section class="section"><h2 class="title sectiontitle"><code class="keyword markupname xmlelement">&lt;plugin&gt;</code></h2>
  42. <p class="p">The root element of the <span class="ph filepath">plugin.xml</span> file is <code class="keyword markupname xmlelement">&lt;plugin&gt;</code>, which has a
  43. required <code class="keyword markupname xmlatt">@id</code> attribute set to the unique plug-in identifier.</p>
  44. <figure class="fig fignone"><figcaption><span class="fig--title-label">Figure 1. </span>Sample <code class="keyword markupname xmlelement">&lt;plugin&gt;</code> element</figcaption>
  45. <pre class="pre codeblock language-xml"><code>&lt;plugin id="com.example.html5-javascript"&gt;</code></pre>
  46. </figure>
  47. </section>
  48. <section class="section"><h2 class="title sectiontitle">Plug-in elements</h2>
  49. <div class="div div-index">
  50. </div>
  51. <p class="p">The <code class="keyword markupname xmlelement">&lt;plugin&gt;</code> element can contain the following child elements: </p>
  52. <dl class="dl parml">
  53. <dt class="dt pt dlterm"><code class="keyword markupname xmlelement">&lt;extension-point&gt;</code></dt>
  54. <dd class="dd pd">
  55. <p class="p">An optional element that defines a new extension point that can be used by other DITA-OT plug-ins.</p>
  56. <p class="p">The following attributes are supported:</p>
  57. <table class="simpletable"><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead><tr class="sthead">
  58. <th class="stentry" scope="col">Attribute</th>
  59. <th class="stentry" scope="col">Description</th>
  60. <th class="stentry" scope="col">Required?</th>
  61. </tr></thead><tbody><tr class="strow">
  62. <th scope="row" class="stentry">id</th>
  63. <td class="stentry">Extension point identifier</td>
  64. <td class="stentry">Yes</td>
  65. </tr><tr class="strow">
  66. <th scope="row" class="stentry">name</th>
  67. <td class="stentry">Extension point description</td>
  68. <td class="stentry">No</td>
  69. </tr></tbody></table>
  70. <p class="p" id="plugin-configfile__extension-point-ids">Like plug-in identifiers, extension point identifiers are composed of one or
  71. more dot-delimited tokens.</p>
  72. <div class="note note note_note" id="plugin-configfile__entension-point-ids-note"><span class="note__title">Note:</span> Extension point identifiers should begin with the identifier of the
  73. defining plug-in and append one or more tokens, for example, <code class="ph codeph">org.dita.example.pre</code>.</div>
  74. <figure class="fig fignone"><figcaption><span class="fig--title-label">Figure 2. </span>Sample <code class="keyword markupname xmlelement">&lt;extension-point&gt;</code> element</figcaption>
  75. <pre class="pre codeblock language-xml"><code>&lt;extension-point id="dita.xsl.html5" name="HTML5 XSLT import"/&gt;</code></pre>
  76. </figure>
  77. </dd>
  78. <dt class="dt pt dlterm"><code class="keyword markupname xmlelement">&lt;feature&gt;</code></dt>
  79. <dd class="dd pd">
  80. <p class="p">An optional element that supplies values to a DITA-OT extension point.</p>
  81. <p class="p">The following attributes are supported:</p>
  82. <table class="simpletable"><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead><tr class="sthead">
  83. <th class="stentry" scope="col">Attribute</th>
  84. <th class="stentry" scope="col">Description</th>
  85. <th class="stentry" scope="col">Required?</th>
  86. </tr></thead><tbody><tr class="strow">
  87. <th scope="row" class="stentry">extension</th>
  88. <td class="stentry">Identifier of the DITA-OT extension point</td>
  89. <td class="stentry">Yes</td>
  90. </tr><tr class="strow">
  91. <th scope="row" class="stentry">value</th>
  92. <td class="stentry">Comma separated string value of the extension</td>
  93. <td class="stentry">Either the <code class="keyword markupname xmlatt">@value</code> or <code class="keyword markupname xmlatt">@file</code> attribute must be
  94. specified</td>
  95. </tr><tr class="strow">
  96. <th scope="row" class="stentry">file</th>
  97. <td class="stentry">Name and path of a file containing data for the extension point.
  98. <p class="p">Depending on the extension point, this might be specified as an absolute path, a path relative to
  99. the <span class="ph filepath">plugin.xml</span> file, or a path relative to the DITA-OT root.</p></td>
  100. <td class="stentry">Either the <code class="keyword markupname xmlatt">@value</code> or <code class="keyword markupname xmlatt">@file</code> attribute must be
  101. specified</td>
  102. </tr><tr class="strow">
  103. <th scope="row" class="stentry">type</th>
  104. <td class="stentry">Type of the <code class="keyword markupname xmlatt">@value</code> attribute</td>
  105. <td class="stentry">No</td>
  106. </tr></tbody></table>
  107. <figure class="fig fignone"><figcaption><span class="fig--title-label">Figure 3. </span>Sample <code class="keyword markupname xmlelement">&lt;feature&gt;</code> elements</figcaption>
  108. <p class="p">If more than one <code class="keyword markupname xmlelement">&lt;feature&gt;</code> element supplies values to the same extension point,
  109. the values are additive. For example, the following are equivalent:</p>
  110. <pre class="pre codeblock language-xml"><code>&lt;feature extension="org.dita.example.extension-point" value="a,b,c"/&gt;</code></pre>
  111. <pre class="pre codeblock language-xml"><code>&lt;feature extension="org.dita.example.extension-point" value="a"/&gt;
  112. &lt;feature extension="org.dita.example.extension-point" value="b"/&gt;
  113. &lt;feature extension="org.dita.example.extension-point" value="c"/&gt;</code></pre>
  114. </figure>
  115. </dd>
  116. <dt class="dt pt dlterm"><code class="keyword markupname xmlelement">&lt;meta&gt;</code></dt>
  117. <dd class="dd pd">
  118. <p class="p">An optional element that defines metadata.</p>
  119. <p class="p">The following attributes are supported:</p>
  120. <table class="simpletable"><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead><tr class="sthead">
  121. <th class="stentry" scope="col">Attribute</th>
  122. <th class="stentry" scope="col">Description</th>
  123. <th class="stentry" scope="col">Required?</th>
  124. </tr></thead><tbody><tr class="strow">
  125. <th scope="row" class="stentry">type</th>
  126. <td class="stentry">Metadata name </td>
  127. <td class="stentry">Yes</td>
  128. </tr><tr class="strow">
  129. <th scope="row" class="stentry">value</th>
  130. <td class="stentry">Metadata value</td>
  131. <td class="stentry">Yes</td>
  132. </tr></tbody></table>
  133. <figure class="fig fignone"><figcaption><span class="fig--title-label">Figure 4. </span>Sample <code class="keyword markupname xmlelement">&lt;meta&gt;</code> element</figcaption>
  134. <pre class="pre codeblock language-xml"><code>&lt;meta type="foo" value="bar"/&gt;</code></pre>
  135. </figure>
  136. </dd>
  137. <dt class="dt pt dlterm"><code class="keyword markupname xmlelement">&lt;require&gt;</code></dt>
  138. <dd class="dd pd">
  139. <p class="p">An optional element that defines plug-in dependencies.</p>
  140. <p class="p">The following attributes are supported:</p>
  141. <table class="simpletable"><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead><tr class="sthead">
  142. <th class="stentry" scope="col">Attribute</th>
  143. <th class="stentry" scope="col">Description</th>
  144. <th class="stentry" scope="col">Required?</th>
  145. </tr></thead><tbody><tr class="strow">
  146. <th scope="row" class="stentry">plugin</th>
  147. <td class="stentry">The identifier of the required plug-in.
  148. <p class="p">To specify alternative requirements, separate plug-in identifiers with a vertical
  149. bar.</p></td>
  150. <td class="stentry">Yes</td>
  151. </tr><tr class="strow">
  152. <th scope="row" class="stentry">importance</th>
  153. <td class="stentry">Identifies whether the plug-in is <code class="ph codeph">required</code> (default) or
  154. <code class="ph codeph">optional</code>. DITA-OT provides a warning if a required plug-in is not
  155. available.</td>
  156. <td class="stentry">No</td>
  157. </tr></tbody></table>
  158. <figure class="fig fignone"><figcaption><span class="fig--title-label">Figure 5. </span>Sample <code class="keyword markupname xmlelement">&lt;require&gt;</code> element</figcaption>
  159. <pre class="pre codeblock language-xml normalize-space"><code>&lt;require plugin="org.dita.html5"/&gt;</code></pre>
  160. </figure>
  161. </dd>
  162. <dt class="dt pt dlterm"><code class="keyword markupname xmlelement">&lt;template&gt;</code></dt>
  163. <dd class="dd pd">
  164. <p class="p">An optional element that defines files that should be treated as templates.</p>
  165. <p class="p">Template files can be used to integrate DITA-OT extensions. Templates typically extend the default
  166. transformation-type-specific build files via <code class="keyword markupname xmlelement">&lt;dita:extension&gt;</code> elements. When the
  167. plug-in installation process runs, template files are used to recreate build files, and the specified
  168. extension points are replaced with references to the appropriate plug-ins.</p>
  169. <p class="p">The following attributes are supported:</p>
  170. <table class="simpletable"><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead><tr class="sthead">
  171. <th class="stentry" scope="col">Attribute</th>
  172. <th class="stentry" scope="col">Description</th>
  173. <th class="stentry" scope="col">Required?</th>
  174. </tr></thead><tbody><tr class="strow">
  175. <th scope="row" class="stentry">file</th>
  176. <td class="stentry">Name and path to the template file, relative to the <span class="ph filepath">plugin.xml</span>
  177. file</td>
  178. <td class="stentry">Yes</td>
  179. </tr></tbody></table>
  180. <figure class="fig fignone"><figcaption><span class="fig--title-label">Figure 6. </span>Sample <code class="keyword markupname xmlelement">&lt;template&gt;</code> element</figcaption>
  181. <pre class="pre codeblock language-xml"><code>&lt;template file="build_dita2html5_template.xml"/&gt;</code></pre>
  182. </figure>
  183. </dd>
  184. <dt class="dt pt dlterm"><code class="keyword markupname xmlelement">&lt;transtype&gt;</code></dt>
  185. <dd class="dd pd">
  186. <p class="p">An optional element that defines a new output format (transformation type).</p>
  187. <p class="p">The following attributes are supported:</p>
  188. <table class="simpletable"><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead><tr class="sthead">
  189. <th class="stentry" scope="col">Attribute</th>
  190. <th class="stentry" scope="col">Description</th>
  191. <th class="stentry" scope="col">Required?</th>
  192. </tr></thead><tbody><tr class="strow">
  193. <th scope="row" class="stentry">name</th>
  194. <td class="stentry">Transformation name</td>
  195. <td class="stentry">Yes</td>
  196. </tr><tr class="strow">
  197. <th scope="row" class="stentry">desc</th>
  198. <td class="stentry">Transformation type description</td>
  199. <td class="stentry">No</td>
  200. </tr><tr class="strow">
  201. <th scope="row" class="stentry">abstract</th>
  202. <td class="stentry">When <span class="keyword option">true</span>, sets the transformation type as <q class="q">abstract</q>, meaning it can be
  203. extended by other plug-ins, but cannot be used directly.
  204. <p class="p">For example, the <code class="ph codeph">org.dita.base</code> plug-in defines an abstract <q class="q">base</q>
  205. transformation type that is extended by other DITA-OT plug-ins.</p></td>
  206. <td class="stentry">No</td>
  207. </tr><tr class="strow">
  208. <th scope="row" class="stentry">extends</th>
  209. <td class="stentry">Specifies the name of the transformation type being extended</td>
  210. <td class="stentry">No</td>
  211. </tr></tbody></table>
  212. <figure class="fig fignone"><figcaption><span class="fig--title-label">Figure 7. </span>Sample <code class="keyword markupname xmlelement">&lt;transtype&gt;</code> element</figcaption>
  213. <pre class="pre codeblock language-xml"><code>&lt;transtype name="base" abstract="true" desc="Common"&gt;
  214. &lt;!-- ⋮ --&gt;
  215. &lt;param name="link-crawl"
  216. desc="Specifies whether to crawl only topic links found in maps, or all discovered topic links."
  217. type="enum"&gt;
  218. &lt;val&gt;map&lt;/val&gt;
  219. &lt;val default="true"&gt;topic&lt;/val&gt;
  220. &lt;/param&gt;
  221. &lt;!-- ⋮ --&gt;
  222. &lt;/transtype&gt;
  223. </code></pre>
  224. </figure>
  225. <p class="p">The <code class="keyword markupname xmlelement">&lt;transtype&gt;</code> element may define additional parameters for the transformation
  226. type using the following child elements.</p>
  227. <dl class="dl parml">
  228. <dt class="dt pt dlterm"><code class="keyword markupname xmlelement">&lt;param&gt;</code></dt>
  229. <dd class="dd pd">
  230. <p class="p">An optional element that specifies a parameter for the transformation type.</p>
  231. <p class="p">The following parameter attributes are supported:</p>
  232. <table class="simpletable"><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead><tr class="sthead">
  233. <th class="stentry" scope="col">Attribute</th>
  234. <th class="stentry" scope="col">Description</th>
  235. <th class="stentry" scope="col">Required?</th>
  236. </tr></thead><tbody><tr class="strow">
  237. <th scope="row" class="stentry">name</th>
  238. <td class="stentry">Parameter name</td>
  239. <td class="stentry">Yes</td>
  240. </tr><tr class="strow">
  241. <th scope="row" class="stentry">desc</th>
  242. <td class="stentry">Parameter description</td>
  243. <td class="stentry">No</td>
  244. </tr><tr class="strow">
  245. <th scope="row" class="stentry">type</th>
  246. <td class="stentry">Parameter type (<span class="keyword option">enum</span>, <span class="keyword option">file</span>,
  247. <span class="keyword option">string</span>)</td>
  248. <td class="stentry">Yes</td>
  249. </tr><tr class="strow">
  250. <th scope="row" class="stentry">deprecated</th>
  251. <td class="stentry">When <span class="keyword option">true</span>, identifies this parameter as deprecated</td>
  252. <td class="stentry">No</td>
  253. </tr><tr class="strow">
  254. <th scope="row" class="stentry">required</th>
  255. <td class="stentry">When <span class="keyword option">true</span>, identifies this parameter as required</td>
  256. <td class="stentry">No</td>
  257. </tr></tbody></table></dd>
  258. <dt class="dt pt dlterm"><code class="keyword markupname xmlelement">&lt;val&gt;</code></dt>
  259. <dd class="dd pd">
  260. <p class="p">A child of <code class="keyword markupname xmlelement">&lt;param&gt;</code> (when <code class="keyword markupname xmlatt">@type</code>=<span class="keyword option">enum</span>) that
  261. specifies an enumeration value.</p>
  262. <p class="p">The following attributes are supported:</p>
  263. <table class="simpletable"><colgroup><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"><col style="width:33.33333333333333%"></colgroup><thead><tr class="sthead">
  264. <th class="stentry" scope="col">Attribute</th>
  265. <th class="stentry" scope="col">Description</th>
  266. <th class="stentry" scope="col">Required?</th>
  267. </tr></thead><tbody><tr class="strow">
  268. <th scope="row" class="stentry">default</th>
  269. <td class="stentry">When <span class="keyword option">true</span>, sets the enumeration value as the default value of the parent
  270. <code class="keyword markupname xmlelement">&lt;param&gt;</code></td>
  271. <td class="stentry">Only for the default <code class="keyword markupname xmlelement">&lt;val&gt;</code></td>
  272. </tr></tbody></table></dd>
  273. </dl>
  274. </dd>
  275. </dl>
  276. <p class="p">Any extension that is not recognized by DITA-OT is ignored. Since DITA-OT version 1.5.3, you can combine
  277. multiple extension definitions within a single <span class="ph filepath">plugin.xml</span> file; in older versions, only the
  278. last extension definition was used.</p>
  279. </section>
  280. </div>
  281. <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/custom-plugins.html" title="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.">Working with plug-ins</a></div></div><div class="linklist relinfo reltasks"><strong>Related tasks</strong><br><ul class="linklist"><li class="linklist"><a class="link" href="../topics/plugin-newtranstype.html" title="Plug-ins can add an entirely new transformation type. The new transformation type can be very simple, such as an HTML build that creates an additional control file; it also can be very complex, adding any number of new processing steps.">Adding a new transformation type</a></li></ul></div><div class="linklist relinfo relref"><strong>Related reference</strong><br><ul class="linklist"><li class="linklist"><a class="link" href="../topics/plugin-newextensions.html" title="If your plug-in needs to define its own extension point in an XML file, add the string &#34;_template&#34; to the filename before the file suffix. When the plug-in is installed, this file will be processed like the built-in DITA-OT templates.">Creating a new plug-in extension point</a></li><li class="linklist"><a class="link" href="../topics/plugin-sample.html" title="The following is a sample of a plugin.xml file. This file adds support for a new set of specialized DTDs, and includes an override for the XHTML output processor.">Example plugin.xml file</a></li></ul></div></nav></article></main></body></html>