| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE html
|
|---|
| 3 | PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|---|
| 4 | <html xml:lang="en-us" lang="en-us">
|
|---|
| 5 | <head>
|
|---|
| 6 | <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
|
|---|
| 7 | <meta name="copyright" content="(C) Copyright 2005"/>
|
|---|
| 8 | <meta name="DC.rights.owner" content="(C) Copyright 2005"/>
|
|---|
| 9 | <meta name="DC.Type" content="reference"/>
|
|---|
| 10 | <meta name="DC.Title" content="Extending the XML Catalog"/>
|
|---|
| 11 | <meta name="abstract" content="The XML Catalogs extension point is used to update the XML Catalogs used to resolve DTD or Schema document types, or to add URI mappings. This is required in order to support DITA specializations or new DITA document type shells."/>
|
|---|
| 12 | <meta name="description" content="The XML Catalogs extension point is used to update the XML Catalogs used to resolve DTD or Schema document types, or to add URI mappings. This is required in order to support DITA specializations or new DITA document type shells."/>
|
|---|
| 13 | <meta name="DC.Relation" scheme="URI" content="../dev_ref/plugins-overview.html"/>
|
|---|
| 14 | <meta name="DC.Format" content="XHTML"/>
|
|---|
| 15 | <meta name="DC.Identifier" content="plugin-xmlcatalog"/>
|
|---|
| 16 | <meta name="DC.Language" content="en-us"/>
|
|---|
| 17 | <link rel="stylesheet" type="text/css" href="../commonltr.css"/>
|
|---|
| 18 | <link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
|
|---|
| 19 | <title>Extending the XML Catalog</title>
|
|---|
| 20 | </head>
|
|---|
| 21 | <body id="plugin-xmlcatalog">
|
|---|
| 22 |
|
|---|
| 23 |
|
|---|
| 24 | <h1 class="title topictitle1">Extending the XML Catalog</h1>
|
|---|
| 25 |
|
|---|
| 26 |
|
|---|
| 27 | <div class="body refbody"><p class="shortdesc">The XML Catalogs extension point is used to update the
|
|---|
| 28 | XML Catalogs used to resolve DTD or Schema document types, or to add
|
|---|
| 29 | URI mappings. This is required in order to support DITA specializations
|
|---|
| 30 | or new DITA document type shells.</p>
|
|---|
| 31 |
|
|---|
| 32 | <div class="section"> <p class="p">To do this, first create a catalog with only
|
|---|
| 33 | your new values, using the OASIS Catalog format, and place that
|
|---|
| 34 | in your plug-in. Local file references in the catalog should be relative
|
|---|
| 35 | to the location of the catalog. The following extension points are
|
|---|
| 36 | available to work with catalogs.</p>
|
|---|
| 37 | <dl class="dl">
|
|---|
| 38 | <dt class="dt dlterm"><samp class="ph codeph">dita.specialization.catalog.relative</samp></dt>
|
|---|
| 39 |
|
|---|
| 40 | <dt class="dt dlterm"><samp class="ph codeph">dita.specialization.catalog</samp></dt>
|
|---|
| 41 |
|
|---|
| 42 | <dd class="dd"> <p class="p">Adds the content of the catalog file defined in <samp class="ph codeph">file</samp> attribute
|
|---|
| 43 | to main DITA-OT catalog file.</p>
|
|---|
| 44 | <div class="note remember"><span class="remembertitle">Remember:</span> The <samp class="ph codeph">dita.specialization.catalog</samp> extension
|
|---|
| 45 | is deprecated. Use <samp class="ph codeph">dita.specialization.catalog.relative</samp> instead.</div>
|
|---|
| 46 |
|
|---|
| 47 | </dd>
|
|---|
| 48 |
|
|---|
| 49 |
|
|---|
| 50 | <dt class="dt dlterm"><samp class="ph codeph">org.dita.pdf2.catalog.relative</samp></dt>
|
|---|
| 51 |
|
|---|
| 52 | <dd class="dd"> <p class="p">Adds the content of the catalog file defined in <samp class="ph codeph">file</samp> attribute
|
|---|
| 53 | to main PDF plug-in catalog file.</p>
|
|---|
| 54 | </dd>
|
|---|
| 55 |
|
|---|
| 56 | </dl>
|
|---|
| 57 | </div>
|
|---|
| 58 |
|
|---|
| 59 | <div class="example"><h2 class="title sectiontitle">Example</h2><p class="p">This example assumes that "<span class="ph filepath">catalog-dita.xml</span>"
|
|---|
| 60 | contains an OASIS catalog for any DTDs or Schemas inside this plug-in.
|
|---|
| 61 | The catalog entries inside of <span class="ph filepath">catalog-dita.xml</span> are
|
|---|
| 62 | relative to the catalog itself; when the plug-in is integrated, they
|
|---|
| 63 | will be added to the core DITA-OT catalog (with the correct path).</p>
|
|---|
| 64 | <pre class="pre codeblock"><plugin id="com.example.catalog">
|
|---|
| 65 | <feature extension="dita.specialization.catalog.relative" file="catalog-dita.xml"/>
|
|---|
| 66 | </plugin></pre>
|
|---|
| 67 | </div>
|
|---|
| 68 |
|
|---|
| 69 | </div>
|
|---|
| 70 |
|
|---|
| 71 | <div class="related-links">
|
|---|
| 72 | <div class="familylinks">
|
|---|
| 73 | <div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../dev_ref/plugins-overview.html" title="The DITA Open Toolkit comes with a built in mechanism for adding in extensions through plug-ins. These plug-ins may do a wide variety of things, such as adding support for specialized DITA DTDs or Schemas, integrating processing overrides, or even providing entirely new output transforms. Plug-ins are the best way to extend the toolkit in a way that is consistent, easily sharable, and easy to preserve through toolkit upgrades.">Creating DITA-OT plug-ins</a></div>
|
|---|
| 74 | </div>
|
|---|
| 75 | </div>
|
|---|
| 76 |
|
|---|
| 77 | </body>
|
|---|
| 78 | </html>
|
|---|
