apb/code-srv-test
apb/code-srv-test
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity Actions

from code-server

Browse source
This commit is contained in:
Andy Bunce 2021-03-23 22:38:58 +00:00
parent eda5c02fe9
commit 5ef8bdba47
2652 changed files with 528235 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
dita-ot-3.6/docsrc/resources/common-resources.ditamap Normal file
View file

@ -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 processing-role="resource-only">
<title>Common Resources</title>
<topicref keyref="conref-task"/>
<topicref keyref="reusable-components"/>
<mapref href="key-definitions.ditamap"/>
<mapref href="reltable.ditamap"/>
<mapref href="subjectscheme.ditamap" type="subjectScheme"/>
<topicref keyref="error-messages-details"/>
</map>

52
dita-ot-3.6/docsrc/resources/common-toc.ditamap Normal file
View file

@ -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 xml:lang="en-US">
<title>DITA Open Toolkit <keyword keyref="release"/></title>
<topicref keyref="landing-page"/>
<topicref keyref="release-notes">
<topicref keyref="release-history"/>
</topicref>
<topicref keyref="installing-client">
<mapref href="../topics/installing.ditamap"/>
</topicref>
<topicref keyref="building-output">
<mapref href="../topics/publishing.ditamap"/>
</topicref>
<topicref keyref="input-formats" collection-type="family">
<mapref href="../topics/input-formats.ditamap"/>
</topicref>
<topicref keyref="output-formats">
<mapref href="../topics/transformations.ditamap"/>
</topicref>
<topicref keyref="parameters">
<mapref href="../parameters/parameters.ditamap"/>
</topicref>
<topicref keyref="html-customization" collection-type="family">
<mapref href="../topics/html-customization.ditamap"/>
</topicref>
<topicref keyref="pdf-customization">
<mapref href="../topics/pdf-customization.ditamap"/>
</topicref>
<topicref keyref="adding-plugins">
<mapref href="../topics/using-plugins.ditamap"/>
</topicref>
<topicref keyref="custom-plugins">
<mapref href="../topics/creating-plugins.ditamap"/>
</topicref>
<topicref keyref="troubleshooting-overview">
<mapref href="../topics/troubleshooting.ditamap"/>
</topicref>
<topicref keyref="reference">
<mapref href="../reference/reference.ditamap"/>
</topicref>
<topicref keyref="dita-and-dita-ot-resources">
<mapref href="../topics/dita-resources.ditamap" toc="no"/>
<mapref href="../topics/dita-ot-day-videos.ditamap"/>
</topicref>
<topicgroup processing-role="resource-only">
<mapref href="common-resources.ditamap"/>
</topicgroup>
</map>

155
dita-ot-3.6/docsrc/resources/conref-task.dita Normal file
View file

@ -0,0 +1,155 @@
<?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="ID">
<title>Conref file for tasks</title>
<taskbody>
<context>
<p id="semver-info">DITA-OT releases follow
<xref keyref="semver"/> guidelines. Version numbers use the
<codeph><varname>major</varname>.<varname>minor</varname>.<varname>patch</varname></codeph> syntax, where
<varname>major</varname> versions may include incompatible API changes, <varname>minor</varname> versions add
functionality in a backwards-compatible manner and <varname>patch</varname> versions are maintenance releases
that include backwards-compatible bug fixes.</p>
<p id="semver-plugins">Custom plug-ins developed for a previous <varname>major</varname> version may require
changes to work correctly with recent toolkit versions. Most plug-ins should be compatible with subsequent
<varname>minor</varname> and <varname>patch</varname> versions of the <varname>major</varname> release for
which they were originally developed.</p>
<dl>
<dlentry>
<dt>Standard Path / Directory Names</dt>
<dd><filepath id="ot-dir"><varname>dita-ot-dir</varname></filepath></dd>
<dd><filepath id="dita-cmd"><cmdname>dita</cmdname></filepath></dd>
<dd><filepath id="docsrc-dir"><varname>dita-ot-dir</varname>/docsrc</filepath></dd>
<dd><filepath id="samples-dir"><varname>dita-ot-dir</varname>/docsrc/samples</filepath></dd>
<dd><filepath id="samples-absolute"><varname
>/absolute/path/to/dita-ot-dir</varname>/docsrc/samples</filepath></dd>
</dlentry>
<dlentry>
<dt>Plug-In Info</dt>
<dd>
<ul>
<li id="plug-in-id"><filepath><varname>&lt;plug-in-id&gt;</varname></filepath> is the unique ID of the
plug-in, as defined in the plug-in’s configuration file (<filepath>plugin.xml</filepath>).</li>
<li id="plug-in-zip"><filepath><varname>plug-in-zip</varname></filepath> is the
<varname>filename</varname> or <varname>URL</varname> of the plug-in’s distribution ZIP file
(optional).</li>
<li id="plug-in">the optional <filepath><varname>&lt;plug-in&gt;</varname></filepath> argument is one of
the following:
<ul>
<li>the unique <varname>ID</varname> of the plug-in as defined in the plug-in registry at
<xref keyref="site-plugin-registry"/> (or a local registry)</li>
<li>the remote <varname>URL</varname> of the plug-in’s distribution ZIP file</li>
<li>the name of a local ZIP <varname>file</varname></li>
</ul>
</li>
<li><ph id="plugin-integrate-all">If no <varname>ID</varname>, <varname>URL</varname>, or
<varname>file</varname> argument is provided, the installation process reloads the current set of
plug-ins from the <filepath>plugins</filepath> directory (or any custom locations defined via the
<parmname>pluginsdir</parmname> property in the <filepath>configuration.properties</filepath> file
in the <filepath>config</filepath> directory). This approach can be used to add or remove multiple
plug-ins at once, or any individual plug-ins you have already copied to (or removed from) the plug-in
directories. Any plug-ins added or removed in the process will be listed by their plug-in
ID.</ph></li>
<li><note id="plugin-remove-subdir" type="attention">The <cmdname>uninstall</cmdname> subcommand also
removes the corresponding plug-in directory from the <filepath>plugins</filepath> folder.
<indexterm>uninstalling</indexterm></note></li>
<li><note>
<ph id="pre-subcommands-2-4-ph">In earlier versions of DITA-OT (2.4–3.4), use the double-hyphen option
syntax <cmdname>dita</cmdname></ph>
<parmname>--uninstall</parmname>. <ph id="pre-subcommands-2-0-ph">In DITA-OT 2.0–2.3, use the
single-hyphen form: <cmdname>dita</cmdname></ph>
</note></li>
</ul>
</dd>
</dlentry>
</dl>
</context>
<steps>
<step>
<cmd>
<!-- Used in installation topic & Release Notes -->
<ph id="download-ot">Download the <filepath>dita-ot-<keyword keyref="maintenance-version"/>.zip</filepath>
package from the project website at
<xref keyref="download.dita-ot"/>.</ph>
</cmd>
</step>
<step>
<cmd id="open-terminal">Open a command prompt or terminal session.</cmd>
<info>
<ul id="basic-variables">
<li id="novice-variables"><varname>input-file</varname> is the DITA map or DITA file that you want to
process.</li>
<!-- ↓ excerpt-variables ↓ -->
<li id="novice-variables-last" audience="novice">
<p id="common-format-info">
<varname>format</varname> is the output format (transformation type). This argument corresponds to the
common parameter <parmname>transtype</parmname>. Use the same values as for the
<parmname>transtype</parmname> build parameter, for example <option>html5</option> or
<option>pdf</option>.</p>
</li>
<!-- ↑ end-excerpt ↑ -->
<li id="expert-variables-last" audience="expert">
<p conref="#ID/common-format-info"/>
<p id="transtypes">You can create plug-ins to add new output formats; by default, the following values are
available:
<indexterm>transtype
<indexterm>list</indexterm></indexterm>
<ul>
<li><option>dita</option></li>
<li><option>eclipsehelp</option></li>
<li><option>html5</option></li>
<li platform="windows"><option>htmlhelp</option></li>
<li><option>markdown</option>, <option>markdown_gitbook</option>, and
<option>markdown_github</option></li>
<li><option>pdf</option></li>
<li><option>xhtml</option></li>
</ul>
<note type="tip">See
<xref keyref="output-formats"/> for sample command line syntax and more information on each
transformation. </note>
</p>
</li>
<li id="options">[<varname>options</varname>] include the following optional build parameters:
<parml conkeyref="dita-command-arguments/dita_build_options">
<plentry>
<pt/>
<pd/>
</plentry>
</parml></li>
</ul>
</info>
<stepresult id="running-ditaot-results">
<p>If processing is successful, nothing is printed in the terminal window. The built output is written to the
specified output directory (by default, in the <filepath>out</filepath> subdirectory of the current
directory).</p>
</stepresult>
</step>
<step>
<cmd>Extending pre-processing</cmd>
<info>
<note id="tip-extend-before-after-preprocessing" type="tip">For maximum compatibility with future versions of
DITA-OT, most plug-ins should use the extension points that run <b>before</b> or <b>after</b>
pre-processing.</note>
<note id="caution-extend-within-preprocessing" type="caution">The internal order of preprocessing steps is
subject to change between versions of DITA-OT. New versions may remove, reorder, combine, or add steps to
the process, so the extension points <b>within</b> the preprocessing stage should only be used if absolutely
necessary.</note>
</info>
</step>
</steps>
<postreq>
<note type="tip" id="template-properties">Copy <filepath conref="#ID/samples-dir"/><filepath
>/properties/template.properties</filepath>; this template describes each of the properties you can
set.</note>
<note type="tip" id="pass-input-dir">If you are building in different environments where the location of the input
files is not consistent, set <option>args.input.dir</option> with the <cmdname>dita</cmdname> command and
reference its value with <codeph>${args.input.dir}</codeph> in your <filepath>.properties</filepath> file.
<indexterm><cmdname>dita</cmdname> command
<indexterm><option>args.input.dir</option></indexterm>
<indexterm>.properties file</indexterm></indexterm>
<indexterm>args.input.dir</indexterm>
</note>
</postreq>
</taskbody>
</task>

12
dita-ot-3.6/docsrc/resources/dita-ot-day-video-keys.ditamap Normal file
View file

@ -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>DITA-OT Day Videos Keys</title>
<mapref href="ditaotdaykeys/dita-ot-day-2014-keys.ditamap" format="ditamap"/>
<mapref href="ditaotdaykeys/dita-ot-day-2015-keys.ditamap" format="ditamap"/>
<mapref href="ditaotdaykeys/dita-ot-day-2016-keys.ditamap" format="ditamap"/>
<mapref href="ditaotdaykeys/dita-ot-day-2017-keys.ditamap" format="ditamap"/>
<mapref href="ditaotdaykeys/dita-ot-day-2018-keys.ditamap" format="ditamap"/>
<mapref href="ditaotdaykeys/dita-ot-day-2019-keys.ditamap" format="ditamap"/>
</map>

322
dita-ot-3.6/docsrc/resources/dita-ot-doc.css Normal file
View file

@ -0,0 +1,322 @@
/* DITA Open Toolkit documentation style */
/****************************************
Basic fonts and typography
****************************************/
body {
background: white;
background: linear-gradient(to right, #eee 0%, #fff 300px);
color: #212529;
margin: 0;
padding: 1em;
}
/* ↓ header-coderef ↓ */
.header {
font-size: 18pt;
margin: 0;
padding: 0 12px;
}
.header p {
color: #1d365d;
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;
line-height: 1.3;
margin: 0;
}
.header hr {
border: 0;
border-bottom: 1px solid #eee;
height: 0;
}
/* ↑ end-header-ref ↑ */
body {
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-size: 1rem;
}
code,
pre,
samp,
.cmdname,
.codeph,
.filepath,
.msgnum,
.option,
.parmname {
color: #6c757d;
font-family: SFMono-Regular, Menlo, Monaco, Consolas, 'Liberation Mono', 'Courier New', monospace;
font-size: 90%;
}
.codeblock .cmdname,
.codeblock .filepath,
.codeblock .msgnum,
.codeblock .option,
.codeblock .parmname,
.codeblock .varname,
pre code {
font-size: inherit;
}
/****************************************
Headings
****************************************/
h1,
h2,
h3 {
color: #1d365d;
font-size: 12pt;
font-weight: bold;
margin-bottom: 0.75em;
margin-left: 0;
margin-right: 0;
margin-top: 1em;
padding: 0;
}
h1 .filepath,
h2 .filepath,
h3 .filepath {
font-family: 'Helvetica Neue', Helvetica, Arial, sans-serif;
font-weight: bold;
}
h1 .filepath {
color: #1d365d;
}
.sectiontitle {
color: #1d365d;
font-weight: bold;
}
.topictitle1 {
margin-top: 1em;
}
/****************************************
Basic identation, padding, and margins
****************************************/
main {
margin-left: 300px;
}
blockquote,
li,
p {
line-height: 125%;
margin-bottom: 0.75em;
margin-left: 0;
margin-right: 0;
margin-top: 0.75em;
padding: 0;
}
dd {
line-height: 125%;
margin-bottom: 0.75em;
margin-top: 0.75em;
}
dl {
line-height: 125%;
margin-bottom: 0.75em;
margin-left: 2em;
margin-right: 0;
margin-top: 0.75em;
padding: 0;
}
ol,
ul {
margin-bottom: 0.75em;
margin-left: 2em;
margin-right: 0;
margin-top: 0.75em;
padding: 0;
}
pre {
margin: 10px 0;
padding: 0;
}
/****************************************
Block elements
****************************************/
.codeblock,
.screen {
background-color: #f5f5f5;
border: 1px solid #ccc;
border-radius: 4px;
padding: 6px;
}
/****************************************
Figures
****************************************/
figcaption {
font-style: italic;
}
/****************************************
In-line elements
****************************************/
.cmdname,
.msgnum {
font-weight: bold;
}
/****************************************
Links
****************************************/
a:link {
color: #3563ab;
text-decoration: none;
}
a:visited {
color: #3563ab;
}
a:active,
a:hover {
color: #1d365d;
text-decoration: underline;
}
.related-links {
color: #555;
}
.linklist {
margin-top: 1em;
}
/****************************************
Notes
****************************************/
.note {
line-height: 125%;
margin-left: 2em;
margin-right: 0;
padding: 0;
}
.caution {
font-weight: bold;
}
/****************************************
Tables
****************************************/
table,
.table {
border-color: #dee2e6;
border-style: solid;
border-width: 1px;
font-size: 90%;
margin-bottom: 1em;
margin-top: 1em;
padding: 0.5rem;
}
tr {
border-color: #dee2e6;
padding: 0.5rem;
}
td {
border-color: #dee2e6;
padding: 0.5rem;
}
th {
background-color: #f5f5f5;
padding: 0.5rem;
text-align: left;
}
caption,
figcaption {
color: #6c757d;
padding: 1em 0;
text-align: left;
}
/****************************************
Navigation
****************************************/
/* ↓ nav-coderef ↓ */
nav[role='toc'] {
float: left;
width: 300px;
}
nav[role='toc'] li.active > a {
font-weight: bold;
}
/* ↑ end-nav-ref ↑ */
nav[role='toc'] > ul {
margin-right: 2em;
}
nav[role='toc'] > ul li {
margin-bottom: 0.5em;
margin-top: 0.5em;
}
nav[role='toc'] > ul > li ul {
margin-bottom: 0.5em;
margin-left: 1.2em;
margin-top: 0.5em;
}
/****************************************
Glossary
****************************************/
.glossAbbreviation,
.glossAcronym {
color: #555;
font-size: 90%;
font-style: italic;
font-weight: normal;
margin-left: 2em;
}
.glossAbbreviation::before,
.glossAcronym::before {
content: 'Abbreviation: “';
}
.glossAbbreviation::after,
.glossAcronym::after {
content: '”';
}
/* Append video icon to DITA-OT Day links in related links and link lists (but not in page footers) */
a.link[href*='dita-ot_day']::after,
.link a[href*='dita-ot_day']::after {
display: inline;
content: '    ';
background-image: url('data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 16" width="16" height="16"><path fill="%233563ab" fill-rule="evenodd" d="M16 3.75a.75.75 0 00-1.136-.643L11 5.425V4.75A1.75 1.75 0 009.25 3h-7.5A1.75 1.75 0 000 4.75v6.5C0 12.216.784 13 1.75 13h7.5A1.75 1.75 0 0011 11.25v-.675l3.864 2.318A.75.75 0 0016 12.25v-8.5zm-5 5.075l3.5 2.1v-5.85l-3.5 2.1v1.65zM9.5 6.75v-2a.25.25 0 00-.25-.25h-7.5a.25.25 0 00-.25.25v6.5c0 .138.112.25.25.25h7.5a.25.25 0 00.25-.25v-4.5z"></path></svg>');
background-position: bottom;
background-repeat: no-repeat;
background-size: contain;
margin-left: 6px;
}

5
dita-ot-3.6/docsrc/resources/ditaotdaykeys/all-conferences.ditaval Normal file
View file

@ -0,0 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<val>
<prop action="exclude"/>
</val>

191
dita-ot-3.6/docsrc/resources/ditaotdaykeys/dita-ot-day-2014-keys.ditamap Normal file
View file

@ -0,0 +1,191 @@
<?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>
<!-- This file was generated from dita-ot-day-ditamap-keys.py found at https://gist.github.com/lief-erickson/4019b6ddf09c154164d4830b0fd6e7e8. -->
<title>DITA-OT Day 2014</title>
<keydef
keys="quovadis-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#Quo_vadis"
format="html"
scope="external"
>
<topicmeta>
<linktext>Quo vadis?</linktext>
<shortdesc>Discussion about the present and the future of the DITA-OT project.</shortdesc>
<author>Panel moderated by George Bina</author>
</topicmeta>
</keydef>
<keydef
keys="providingdesignersaflexi-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#Providing_designers_a_flexible_way_to_publish_DITA_content_into_Adobe_InDesign"
format="html"
scope="external"
>
<topicmeta>
<linktext>Providing Designers a Flexible Way to Publish DITA Content into Adobe InDesign</linktext>
<shortdesc>This presentation shows how Mekon have implemented a plugin that provides an approach to publishing
into InDesign, providing designers the flexibility they require.</shortdesc>
<author>Mark Poston</author>
</topicmeta>
</keydef>
<keydef
keys="publishingditacontentre--2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#Publishing_DITA_content_re-used_in_different_context"
format="html"
scope="external"
>
<topicmeta>
<linktext>Publishing DITA Content Re-Used in Different Context in EPUB and Eclipse Infocenter by Using
DITA-OT</linktext>
<shortdesc>On the example of ice hockey rule books, we show how easy content can be re-used by creating new
context variants and how it can be published to EPUB or into an Eclipse help infocenter.</shortdesc>
<author>Gunthilde Sohn</author>
</topicmeta>
</keydef>
<keydef
keys="scormwrapperforditatosco-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#SCORM_wrapper_for_DITA_to_SCORM"
format="html"
scope="external"
>
<topicmeta>
<linktext>SCORM Wrapper for DITA to SCORM</linktext>
<shortdesc>Hal Trent of Comtech will present a SCORM wrapper developed for learning and training output, which
could be potentially donated to the DITA-OT. The wrapper incorporates the current DITA to SCORM output and adds
a layer of JavaScript with the SCORM API to integrate the output generated from the DITA-OT into an LMS. The
wrapper passes test completion status to and from the LMS and provides a much needed output for the learning and
training implementation.</shortdesc>
<author>Hal Trent</author>
</topicmeta>
</keydef>
<keydef
keys="ditaopentoolkitpdfgenera-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#DITA_Open_Toolkit_PDF_generation_with_CSS"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA Open Toolkit PDF Generation with CSS</linktext>
<shortdesc>How about producing and styling PDFs only by using CSS? Join Radu for an overview of a new, innovative,
open-source DITA-OT plugin, which produces PDF from DITA content using CSS and an XML+CSS to PDF engine such as
the Prince XML or Antenna House engines.</shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="ditaopentoolkitpdfplugin-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#DITA_Open_Toolkit_PDF_plugins_without_fuss_muss_or_writing_XSL-FO"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA Open Toolkit PDF Plugins Without Fuss, Muss, or Writing XSL-FO</linktext>
<shortdesc>Did you know that you can create customized PDF plugins using an easy online tool? Join Jarno for an
overview of his plugin generator, what it produces, and his work developing the dynamic Web
interface.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="pdfsfromtheditaopentoolk-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#PDFs_from_the_DITA_Open_Toolkit"
format="html"
scope="external"
>
<topicmeta>
<linktext>PDFs from the DITA Open Toolkit: The Easy and the Not-so-Easy</linktext>
<shortdesc>With a few simple changes, it's possible to give the DITA-OT's default PDF output much of your own look
and feel. If you need to develop a DITA proof of concept for your organization, these changes might be all you
need to get the ball rolling. Join Leigh to find out what's easy to do, what's not quite so easy to do, and
where the real heavy lifting is.</shortdesc>
<author>Leigh White</author>
</topicmeta>
</keydef>
<keydef
keys="dita2rdffromtreestotripl-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#dita2rdf_from_trees_to_triples"
format="html"
scope="external"
>
<topicmeta>
<linktext>dita2rdf: from trees to triples</linktext>
<shortdesc>The dita2rdf plugin is meant to extract metadata from DITA content and produce an RDF/XML output, which
is a serialization of the W3C RDF standard. The final objective is to get insights from the DITA content by
querying its metadata as a graph, not as a tree-like in XML. It also potentially enables the connection of the
DITA metadata with other types of entities such as products, people, events, etc.</shortdesc>
<author>Colin Maudry</author>
</topicmeta>
</keydef>
<keydef
keys="extendingtheditaopentool-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#Extending_the_DITA_Open_Toolkit"
format="html"
scope="external"
>
<topicmeta>
<linktext>Extending the DITA Open Toolkit: How crazy can you get?</linktext>
<shortdesc>DITA-OT includes extension points that let you do any number of things. This session will cover what's
available, what you should or shouldn't extend, and give out sample plugins to slice and dice your
content.</shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="rngtodtdandxsdusingthedi-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#RNG_to_DTD_and_XSD_using_the_DITA_Open_Toolkit"
format="html"
scope="external"
>
<topicmeta>
<linktext>RNG to DTD and XSD using the DITA Open Toolkit</linktext>
<shortdesc>The new version of DITA, version 1.3, will use Relax NG as the normative grammar to express the DITA
content models. George proposed this idea and provided a working prototype under the DITA-NG open source project
and Eliot took this further making it an official proposal for DITA 1.3 and finalized its implementation. See
how Relax NG simplifies the way DITA content models and specializations are defined and what other benefits it
brings to DITA 1.3.</shortdesc>
<author>Eliot Kimber</author>
</topicmeta>
</keydef>
<keydef
keys="contributingtothetoolkit-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#Contributing_to_the_Toolkit_via_GitHub"
format="html"
scope="external"
>
<topicmeta>
<linktext>Contributing to the Toolkit via GitHub</linktext>
<shortdesc>Now that the toolkit is hosted on GitHub, it's easier than ever to contribute changes to the DITA-OT
code. Roger will demonstrate how to fork the repository, create a new branch, change the necessary files and
submit a pull request.</shortdesc>
<author>Roger Fienhold Sheen</author>
</topicmeta>
</keydef>
<keydef
keys="lookingunderthehoodofthe-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#Looking_under_the_hood_of_the_DITA_Open_Toolkit"
format="html"
scope="external"
>
<topicmeta>
<linktext>Looking under the hood of the DITA Open Toolkit</linktext>
<shortdesc>Participate in a deeper, more technical dive with the primary DITA-OT developer. This session will
cover the pre-processing architecture of the DITA-OT and information about the output
transformations.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="overviewoftheditaopentoo-2014"
href="https://www.oxygenxml.com/events/2014/dita-ot_day.html#Overview_of_the_DITA_Open_Toolkit"
format="html"
scope="external"
>
<topicmeta>
<linktext>Overview of the DITA Open Toolkit</linktext>
<shortdesc>Are you new to the DITA-OT? Come and get an overview of what it is, how it works, its history, and the
people involved. This will be an excellent start to DITA-OT day for novices.</shortdesc>
<author>Kristen James Eberlein</author>
</topicmeta>
</keydef>
</map>

238
dita-ot-3.6/docsrc/resources/ditaotdaykeys/dita-ot-day-2015-keys.ditamap Normal file
View file

@ -0,0 +1,238 @@
<?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>
<!-- This file was generated from dita-ot-day-ditamap-keys.py found at https://gist.github.com/lief-erickson/4019b6ddf09c154164d4830b0fd6e7e8. -->
<title>DITA-OT Day 2015</title>
<keydef
keys="dita-otdocumentationupda-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#DITA_OT_Documentation_Update"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT documentation update</linktext>
<shortdesc> This talk provides an overview of recent changes to the DITA-OT documentation, points out open issues,
highlights ideas for future improvements, and closes with room for suggestions from the community and a call for
contributions.</shortdesc>
<author>Roger Fienhold Sheen</author>
</topicmeta>
</keydef>
<keydef
keys="multipleotwithgit-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Multiple_OT_With_Git"
format="html"
scope="external"
>
<topicmeta>
<linktext>Multiple OT with Git</linktext>
<shortdesc> If you need to maintain multiple configurations of the OT for day-to-day or minute-by-minute changes
to the OT for different projects, clients, etc., you can use git to do it. There are some tricks and gotchas but
it does work.</shortdesc>
<author>Eliot Kimber</author>
</topicmeta>
</keydef>
<keydef
keys="sellingditawithdemodata-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Selling_DITA_With_Demo_Data"
format="html"
scope="external"
>
<topicmeta>
<linktext>Selling DITA with demo data</linktext>
<shortdesc> Over a couple of years, the Gnostyx team has been preparing and refining a DITA Demonstration Data
Set. It's purpose is to provide members of the community a functionally realistic data set with which to
demonstrate DITA based applications. It was made available publicly in early 2015 and has since been adopted and
used by several members of the DITA Community. This talk is really a demonstration of some of the business use
cases that we use to convince business stakeholders that DITA demands serious attention. People will learn a
little about the DITA Demonstration Data Set and some of the sales pitches that they might want to use, and to
demonstrate, in the future.</shortdesc>
<author>Joe Gollner</author>
</topicmeta>
</keydef>
<keydef
keys="publishingwithdita-ot-th-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Publishing_With_DITA_OT_The_CMS_Perspective"
format="html"
scope="external"
>
<topicmeta>
<linktext>Publishing with DITA-OT - the CMS perspective</linktext>
<shortdesc> Publishing from a CMS imposes specific requirements on the DITA-OT. We will review these requirements
while showing how IXIASOFT integrated the DITA-OT into their Output Generator.</shortdesc>
<author>Jean-François Ameye</author>
</topicmeta>
</keydef>
<keydef
keys="parametersannotationsfor-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Parameters_Annotations_For_DITA_OT_Plugins"
format="html"
scope="external"
>
<topicmeta>
<linktext>Parameters annotations for DITA-OT plugins</linktext>
<shortdesc> Each DITA-OT plugin provides a set of parameters that can be configured to customize the publishing
process. As these need to be made available to users it is important to have an automated way of discovering
these parameters and additional information about them - what they represent, what values are possible, etc.
DITA-OT makes this possible by allowing parameters to be annotated.</shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="howtorundita-ot-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#How_To_Run_DITA_OT"
format="html"
scope="external"
>
<topicmeta>
<linktext>How to run DITA-OT</linktext>
<shortdesc> There are multiples ways to run DITA-OT and some of them are good, some are bad, and some are just
plain ugly. This presentation goes through different interfaces to DITA-OT and when to use them.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="creatingdita-otconstrain-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Creating_DITA_OT_constraint_specialisation_plugins"
format="html"
scope="external"
>
<topicmeta>
<linktext>Creating DITA-OT constraint/specialisation plugins</linktext>
<shortdesc>This presentation will address the problem of creating DITA constraints/specialisations to customize
DITA to meet your specific needs. We will identify a problem, create a Relax NG constraint/specialization to
solve it and convert that to DTD. All these will be packaged as a DITA-OT plugin.</shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="ditacommunity-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#DITA_Community"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA Community</linktext>
<shortdesc> The DITA Community GitHub organization serves as a general place for people to contribute DITA Open
Toolkit plugins and other DITA-related tools and utilities that are not maintained by DITA-OT or other projects.
This presentation provides an overview of the DITA Community organization, what's there today, and how you can
contribute. </shortdesc>
<author>Eliot Kimber</author>
</topicmeta>
</keydef>
<keydef
keys="pdf5-mlplug-in-featuresf-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#PDF5-ML_Plug-in"
format="html"
scope="external"
>
<topicmeta>
<linktext>PDF5-ML Plug-in - features for practical use</linktext>
<shortdesc>Demonstrates the following features of PDF5-ML Multiple language in one documentConditional variable
&amp; style definitionFree format cover pages</shortdesc>
<author>Toshihiko Makita</author>
</topicmeta>
</keydef>
<keydef
keys="dita-otreloaded-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#DITA-OT_reloaded"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT ... reloaded!</linktext>
<shortdesc>Professional writing can require several features that the present DITA-OT (2.1.1) has not implemented.
There are several expensive plugins available as commercial products to improve that situation. Helmut Scherzer
presents a match to highly professional DITA-OT extensions which contains a list of more than 20 new powerful
features to PDF2 – offered to become part of the public DITA-OT.</shortdesc>
<author>Helmut Scherzer</author>
</topicmeta>
</keydef>
<keydef
keys="dita-otinsidetheblackbox-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Inside_the_black_box"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT: Inside the black box</linktext>
<shortdesc>When creating a product, a good design is critical; in many cases, this rule applies not only to the
outside, but also to the parts inside that normal users will not see. Unfortunately, to those who looked, the
inner workings of the early toolkit seemed to have almost no design at all. In this session, we'll talk about
how Jarno has cleaned up the hidden inner workings of the toolkit -- and how everyone benefits from these
changes to things they might never see.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="pdfgenerationwithcss-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#PDF_Generation_With_CSS"
format="html"
scope="external"
>
<topicmeta>
<linktext>PDF generation with CSS</linktext>
<shortdesc>Presenting new updates made to the DITA-OT plugin which can now be used to generate PDF from DITA and
CSS using either Prince XML or Antenna House. </shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="markdownplugin-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Markdown_plugin"
format="html"
scope="external"
>
<topicmeta>
<linktext>Markdown plugin</linktext>
<shortdesc>This talk introduces Jarno Elovirta’s DITA-OT Markdown plugins, which extend the DITA Open Toolkit so
you can use Markdown files directly in topic references and export existing DITA content in Markdown format for
use in other publishing systems. This makes it easier for people to contribute content to DITA publications,
enables mobile authoring workflows, facilitates review processes with less technical audiences and expands the
range of publishing options to workflows based on Markdown.</shortdesc>
<author>Roger Fienhold Sheen</author>
</topicmeta>
</keydef>
<keydef
keys="whystartcmdisnotyourfrie-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Why_startcmd_is_not_your_friend"
format="html"
scope="external"
>
<topicmeta>
<linktext>Why "startcmd" is not your friend</linktext>
<shortdesc>The startcmd batch script made it possible for many to easily use DITA-OT, but whether you realize it
or not, it's no longer really necessary. I'll briefly explain where it came from, why it was always more of a
kludge than a Feature, and how better DITA-OT designs mean it's no longer needed.</shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="dita-otpatternsandanti-p-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#DITA-OT_Patterns_and_Anti-patterns"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT Patterns and Anti-patterns</linktext>
<shortdesc>What might often seem like a good way to use or extend DITA-OT, but likely result in trouble later?
What is the alternative? This session will cover known traps that organizations have fallen into when using
DITA-OT, and suggest how to avoid those issues or (perhaps with difficulty) recover from the mistakes. The
session will leave time for discussion about other traps that audience members may have fallen into.</shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="whatsnewindita-ot-2015"
href="https://www.oxygenxml.com/events/2015/dita-ot_day.html#Whats_new_in_DITA-OT"
format="html"
scope="external"
>
<topicmeta>
<linktext>What's new in DITA-OT</linktext>
<shortdesc>What's new in DITA-OT? We'll cover major changes in both 2.1 and 2.2, with a focus on support for new
DITA 1.3 features.</shortdesc>
<author>Kristen James Eberlein</author>
</topicmeta>
</keydef>
</map>

221
dita-ot-3.6/docsrc/resources/ditaotdaykeys/dita-ot-day-2016-keys.ditamap Normal file
View file

@ -0,0 +1,221 @@
<?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>
<!-- This file was generated from dita-ot-day-ditamap-keys.py found at https://gist.github.com/lief-erickson/4019b6ddf09c154164d4830b0fd6e7e8. -->
<title>DITA-OT Day 2016</title>
<keydef
keys="panel-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#DITA_2016_Panel_Quo_Vadis"
format="html"
scope="external"
>
<topicmeta>
<linktext>Panel</linktext>
<shortdesc/>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="longtermdita-otplanning-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#Long_term_DITA-OT_planning"
format="html"
scope="external"
>
<topicmeta>
<linktext>Long term DITA-OT planning</linktext>
<shortdesc>Kris and Robert will discuss the long term future of DITA-OT: what can we all do to ensure the
continued health of this critical piece of the overall DITA infrastructure? </shortdesc>
<author>Kristen Eberlein</author>
</topicmeta>
</keydef>
<keydef
keys="theuse-casesforaditatore-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#DITA_to_resolved_DITA_transformation"
format="html"
scope="external"
>
<topicmeta>
<linktext>The use-cases for a "DITA to resolved DITA" transformation</linktext>
<shortdesc>A DITA to simplified/resolved DITA transformation provides a solution for some of the possible issues
with translating DITA. There are also other advantages, especially in connection to the increased dynamics in
DITA-OT development. Join me to discover how a DITA to resolved DITA can help you! </shortdesc>
<author>George Bina</author>
</topicmeta>
</keydef>
<keydef
keys="ditaterminologymanagemen-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#DITA_terminology_management_checking"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA terminology management and checking</linktext>
<shortdesc>I'd like to present how we manage and check terminology using the org.doctales.terminology
plugin.</shortdesc>
<author>Stefan Eike</author>
</topicmeta>
</keydef>
<keydef
keys="codeblockqualityassuranc-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#Codeblock_Quality_Assurance_instead_of_Errata"
format="html"
scope="external"
>
<topicmeta>
<linktext>Codeblock Quality Assurance instead of Errata</linktext>
<shortdesc>Fixing errors during authoring stage is cheap in both technical communication and software development;
fixing errors after publishing is expensive. In this talk I demonstrate a QA method for software documentation
in DITA.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="testingindita-ot-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#Testing_in_DITA-OT"
format="html"
scope="external"
>
<topicmeta>
<linktext>Testing in DITA-OT</linktext>
<shortdesc>Jarno and Robert will discuss how the DITA-OT is tested, get feedback and talk about where we want to
go.</shortdesc>
<author>Jarno Elovirta, Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="largescaleproductionusin-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#Large_Scale_Production_Using_Project_Maps"
format="html"
scope="external"
>
<topicmeta>
<linktext>Large Scale Production Using Project Maps</linktext>
<shortdesc>This presentation will show how SAP has integrated the DITA Open Toolkit to create a large scale
production infrastructure able to create daily builds producing 50 000+ outputs for all SAP Product
documentation. This covers the end-to-end process from getting the DITA content from the CMS to publishing the
produced outputs to the appropriate delivery channels, using so-called project maps as a key ingredient.
Advanced features like peer linking across outputs will be shown, as part of the overall implementation. </shortdesc>
<author>Youssef BENNANI</author>
</topicmeta>
</keydef>
<keydef
keys="usingtheopentoolkitthrou-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#Using_the_Open_Toolkit_Through_Docker_Containers"
format="html"
scope="external"
>
<topicmeta>
<linktext>Using the Open Toolkit Through Docker Containers</linktext>
<shortdesc>Docker containers make it easy to package and use different configurations of software components.
Docker containers can also provide the dependencies needed to run a given piece of software. For the Open
Toolkit, you can use Docker containers to easily provision and run the Open Toolkit without worrying about the
local Java configuration or other dependencies. Docker also makes it easy to set up custom configurations of the
Open Toolkit or use different versions. This presentation shows how to use Docker-based Open Toolkit
packages.</shortdesc>
<author>Eliot Kimber</author>
</topicmeta>
</keydef>
<keydef
keys="gotchaupgradingpdfplugin-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#Upgrading_PDF_plugins_to_DITA_OT_2.x"
format="html"
scope="external"
>
<topicmeta>
<linktext>Gotcha! Upgrading PDF plugins to DITA-OT 2.x</linktext>
<shortdesc>There are some significant changes to DITA-OT 2.x that can make upgrading PDF plugins written for
earlier versions of the OT a challenge. Having just upgraded several plugins, and released a new edition of
"DITA For Print," Leigh will share a few of the major things to look out for.</shortdesc>
<author>Leigh White</author>
</topicmeta>
</keydef>
<keydef
keys="documentationdevelopment-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#How_the_docs_are_done"
format="html"
scope="external"
>
<topicmeta>
<linktext>Documentation Development(s)</linktext>
<shortdesc>This talk provides an overview of recent changes to the DITA-OT documentation, points out open issues,
highlights ideas for future improvements, and closes with room for suggestions from the community, a call for
contributions and a brief demonstration of the pull request approval process that is applied when people submit
changes to the development documentation via the /Edit this Page/ links. </shortdesc>
<author>Roger Fienhold Sheen</author>
</topicmeta>
</keydef>
<keydef
keys="simplifiedcontributionpr-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#Simplified_contribution_process_for_the_DITA-OT_documentation"
format="html"
scope="external"
>
<topicmeta>
<linktext>Simplified contribution process for the DITA-OT documentation</linktext>
<shortdesc>Now it is very easy to contribute to the DITA-OT documentation - just read the developer docs and use
the "Edit" button to open the source topic from GitHub for editing. Save will automate all the contribution
process, sending a pull request with your proposed changes.</shortdesc>
<author>George Bina</author>
</topicmeta>
</keydef>
<keydef
keys="dita-otinternalsandfutur-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#DITA-OT_internals_and_future_development_plans"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT internals and future development plans</linktext>
<shortdesc>The internals of DITA-OT are in perpetual motion and most of these changes are not visible to end
users. In this talk we go through changes in the black box and describe future development plans.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="sevenopen-sourcedita-otp-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#Seven_Open-Source_DITA-OT_plugins"
format="html"
scope="external"
>
<topicmeta>
<linktext>Seven open-source DITA-OT plugins developed by Oxygen</linktext>
<shortdesc> This session shows 7 DITA Open Toolkit open source plugins that the developers of Oxygen XML have
created or updated this year including: DITA + CSS = PDF - This pre-existing plugin now was updated to add
support for showing Oxygen track changes and comments. DITA Classic PDF Review - This plugin adds support for
showing Oxygen track changes and comments in the classic PDF output. Media Support Plugin - Plugin which adds
the possibility to embed videos (including YouTube videos) and audio resources in DITA topics and publish to
HTML and PDF. DITA Merged - Plugin which produces a single merged XML file from the entire DITA content. DITA
Relax NG Defaults - Plugin which adds support to a DITA-OT distribution to process Relax NG-based topics and
maps. </shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="internationalizationandt-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#DITA-OT_Who_does_what"
format="html"
scope="external"
>
<topicmeta>
<linktext>Internationalization and the DITA-OT: Who does what?</linktext>
<shortdesc>While tools can be used to simplify many things, localization can still be scary. In this session,
we'll go over how the toolkit is set up to handle publishing in multiple languages: what comes out of the box?
What should you expect to do on your own? And how has this changed over the last few releases? Also: stories of
panic from the past!</shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="newdita-ot24releaseannou-2016"
href="https://www.oxygenxml.com/events/2016/dita-ot_day.html#New_DITA-OT_2.4_Release_Announcement"
format="html"
scope="external"
>
<topicmeta>
<linktext>New DITA-OT 2.4 Release Announcement</linktext>
<shortdesc/>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
</map>

226
dita-ot-3.6/docsrc/resources/ditaotdaykeys/dita-ot-day-2017-keys.ditamap Normal file
View file

@ -0,0 +1,226 @@
<?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>
<!-- This file was generated from dita-ot-day-ditamap-keys.py found at https://gist.github.com/lief-erickson/4019b6ddf09c154164d4830b0fd6e7e8. -->
<title>DITA-OT Day 2017</title>
<keydef
keys="panelwhatsnextfordita-ot-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#DITA_2017_Panel"
format="html"
scope="external"
>
<topicmeta>
<linktext>Panel: What's next for DITA-OT?</linktext>
<shortdesc/>
<author>Jarno Elovirta, Robert Anderson, Roger Fienhold Sheen, George Bina</author>
</topicmeta>
</keydef>
<keydef
keys="whatarewemissingwherewou-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#What_are_we_missing"
format="html"
scope="external"
>
<topicmeta>
<linktext>What are we missing? Where would you like to see us go?</linktext>
<shortdesc>This is a feedback session where we want to hear from you! One problem with DITA-OT development is that
we don't usually know what our customers like most, what they're using, and (almost as important) what they're
not using. It's also likely that in some cases, we're not sure what to ask. In this session we'll discuss
potential ways of getting this feedback, related issues such as data privacy, and ideally take suggestions from
the audience for improved communication.</shortdesc>
<author>Jarno Elovirta and Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="dcql-theditacascadingque-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#DCQL"
format="html"
scope="external"
>
<topicmeta>
<linktext>DCQL - the Dita Cascading Query Language</linktext>
<shortdesc>Short overview of the DCQL attribute domain and accompanying code that allows pulling DITA content in
from SQL or XML databases at publish time or runtime, and even keeping the data link alive on interactive media. </shortdesc>
<author>Jang Graat</author>
</topicmeta>
</keydef>
<keydef
keys="locale-awaresortingandte-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#Open_Toolkit"
format="html"
scope="external"
>
<topicmeta>
<linktext>Locale-Aware Sorting and Text Handling in the Open Toolkit</linktext>
<shortdesc>Presents the DITA Community i18n Plugin, which provides an integration with the ICU4J libraries. The
i18n plugin provides support for locale-specific grouping and sorting, including dictionary-based Simplified
Chinese, as well as facilities for doing locale-specific word and line breaking. </shortdesc>
<author>Eliot Kimber</author>
</topicmeta>
</keydef>
<keydef
keys="automaticallycreatetarge-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#Review_Docs"
format="html"
scope="external"
>
<topicmeta>
<linktext>Automatically Create Targeted Review Docs for your SMEs</linktext>
<shortdesc>This presentation illustrates how an OT plugin can leverage CMS status information to create a PDF for
review that includes only the content SMEs need to look at, or alternatively, include everything for full
context but highlight the specific content that needs reviewing. This presentation demonstrates how to quickly
create a PDF that includes material for a specific reviewer, and how to create a PDF intended for multiple
reviewers with their names assigned to each topic.</shortdesc>
<author>Leigh White</author>
</topicmeta>
</keydef>
<keydef
keys="bootstrappingdita-custom-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#Bootstrapping_DITA"
format="html"
scope="external"
>
<topicmeta>
<linktext>Bootstrapping DITA - Customizing HTML output for modern web frameworks</linktext>
<shortdesc> Web developers often use CSS frameworks, HTML5 boilerplate or component libraries like Bootstrap or
Foundation to quickly build robust, responsive sites. With custom HTML plug-ins, DITA-OT can be extended to
produce HTML5 output that makes use of these common templates so that generated documents can build on existing
front-end solutions. This talk will outline the process, using the DITA-OT project website at dita-ot.org as an
example.</shortdesc>
<author>Roger Fienhold Sheen</author>
</topicmeta>
</keydef>
<keydef
keys="usingcsstostylethepdfout-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#Using_CSS_to_style_the_PDF_output"
format="html"
scope="external"
>
<topicmeta>
<linktext>Using CSS to style the PDF output</linktext>
<shortdesc> Using CSS to produce PDF from DITA content is way easier than writing plugins and customizing XSLT
stylesheet and will probably become in the future the most used way to produce a PDF. We will go over the
existing solutions for producing PDF from DITA using CSS and maybe try to show a little bit of the CSS
pagination standard: change the front matter and backmatter, change headers and footers, change some colors and
styles, change the paper type and orientation.</shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="markdownsupportinside-ou-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#Markdown_support_inside-out"
format="html"
scope="external"
>
<topicmeta>
<linktext>Markdown support inside-out</linktext>
<shortdesc>Description of how Markdown support was added to DITA-OT to make Markdown a first-class file format for
DITA content. Focus is on the implementation details and goals instead of Markdown author
perspective.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="dita-otdocsdevelopments-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#DITA-OT_Docs_Development"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT Docs Development(s)</linktext>
<shortdesc>This talk provides an overview of DITA-OT documentation usage metrics and highlights recent changes to
the docs and ideas for future improvements. We’ll close with room for suggestions from the community and a call
for contributions with information on the browser-based workflow for suggesting changes.</shortdesc>
<author>Roger Fienhold Sheen</author>
</topicmeta>
</keydef>
<keydef
keys="managingalargescalebuild-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#Managing_a_large_scale_build_environment"
format="html"
scope="external"
>
<topicmeta>
<linktext>Managing a large scale build environment with 50+ custom plugins</linktext>
<shortdesc>Tips and tricks, mistakes made, and lessons learned: how IBM manages a single build environment for
hundreds of authors with 50+ plugins -- including new doctypes, new transform types, and externally contributed
plugins -- while keeping up with the latest DITA-OT releases. </shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="generatingsvgsyntaxdiagr-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#Generating_SVG_syntax_diagrams"
format="html"
scope="external"
>
<topicmeta>
<linktext>Generating SVG syntax diagrams with plugins for all output formats</linktext>
<shortdesc>DITA includes a lot of markup for syntax diagrams, but it's not particularly useful without a way to
render the diagrams. Many years ago Deborah Pickett wrote a group of plugins to render those diagrams as SVG,
but they were tied to the "html+" transform type and required an obsolete version of DITA-OT. Last year IBM
extracted the SVG diagram feature from those plugins, brought it up to date, and made it usable by other formats
(including PDF and EPUB). This session will give an overview of Deborah's original plugins, and explain how
anybody can use the updated versions with the latest DITA-OT.</shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="ditavalidationandspell-c-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#DITA_Validation_and_spell-checking"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA Validation and spell-checking</linktext>
<shortdesc> Jason will discuss and demonstrate how HERE Technologies extends DITA-OT using open-sourced plugins to
continuously validate and build technical documentation. See: https://github.com/heremaps/dita-ot-plugins for
more details. The discussion will cover the design and evolution of the plugins, interaction with end users and
how you can integrate the plugins in your own workflows, as well as expected future developments. </shortdesc>
<author>Jason Fox</author>
</topicmeta>
</keydef>
<keydef
keys="accessibilityindita-ot-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#Accessibility_DITA-OT"
format="html"
scope="external"
>
<topicmeta>
<linktext>Accessibility in DITA-OT</linktext>
<shortdesc> Not only is accessible content often mandatory, it's also just a good idea -- assuming you want your
content available to as many readers as possible. This session provides an overview of the accessibility
features in output generated by the DITA-OT. While many features are automated thanks to the semantic nature of
DITA elements, others rely on you to make sure your content includes everything it needs to. While going over
these features, we will explain how DITA-OT handles your content, while also giving tips for how to ensure your
content reaches users on all sorts of devices. </shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="weshallcallitpreprocess2-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#preprocess_2"
format="html"
scope="external"
>
<topicmeta>
<linktext>We shall call it preprocess2</linktext>
<shortdesc>Overview of preprocess2, the replacement module for the original preprocessing routines. This session
explains the new approach, why we developed it, and why should you care.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="dita-ot-2017"
href="https://www.oxygenxml.com/events/2017/dita-ot_day.html#DITA_Announcement"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT</linktext>
<shortdesc>A quick announcement about the DITA-OT project.</shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
</map>

260
dita-ot-3.6/docsrc/resources/ditaotdaykeys/dita-ot-day-2018-keys.ditamap Normal file
View file

@ -0,0 +1,260 @@
<?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>
<!-- This file was generated from dita-ot-day-ditamap-keys.py found at https://gist.github.com/lief-erickson/4019b6ddf09c154164d4830b0fd6e7e8. -->
<title>DITA-OT Day 2018</title>
<keydef
keys="whatsnextfordita-ot-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#DITA_2018_Panel"
format="html"
scope="external"
>
<topicmeta>
<linktext>What's next for DITA-OT?</linktext>
<shortdesc/>
<author>Robert Anderson, Roger Sheen, Jarno Elovirta, George Bina</author>
</topicmeta>
</keydef>
<keydef
keys="whoareyoucallingstale-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#who_are_you_calling"
format="html"
scope="external"
>
<topicmeta>
<linktext>Who are you calling “stale” ‽</linktext>
<shortdesc>The DITA-OT issue tracker contains a backlog of open issues, many of which have not been updated in
several years, and may no longer apply to recent versions. This session will discuss options for removing
outdated issues from the backlog to help focus resources on issues that are most important to users.</shortdesc>
<author>Robert Anderson, Roger Sheen, Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="twistedxslttricksmakingc-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#twisted_xslt_tricks"
format="html"
scope="external"
>
<topicmeta>
<linktext>Twisted XSLT Tricks: Making Column Switching Work for FOP</linktext>
<shortdesc>Switching from single column to two-column layout is almost impossible using the PDF2 transform and FOP
because FOP enforces XSL-FO's rule that only direct children of fo:flow can change the column spanning.
Likewise, splitting page sequences to change from portrait to landscape is hard to do with the PDF2 transform
because it provides no easy way to change the page sequence within the context of a topic's body (e.g., to put
rotated tables on landscape pages). This talk presents a general XSLT technique for splitting a single tree into
multiple trees, enabling changing column spanning and splitting page sequences with a minimum of rework of
normal templates.</shortdesc>
<author>Eliot Kimber</author>
</topicmeta>
</keydef>
<keydef
keys="dita-otanddocops-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#DITA-OT_and_docOps"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT and DocOps</linktext>
<shortdesc>Developing documentation concurrent with the software using DITA-OT in VSTS environment at
Shell.</shortdesc>
<author>Quick van Rijt</author>
</topicmeta>
</keydef>
<keydef
keys="validationmeetspublicati-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#apply_your_style_guide_rules_during_the_publication"
format="html"
scope="external"
>
<topicmeta>
<linktext>Validation meets publication - Apply your style guide rules during the publication</linktext>
<shortdesc>DITA-OT warns about technical issues in the input. Why not warn about style guide violations? This talk
shows how Schematron can be used to check topics and maps after the preprocessing phase and stop the build if
content does not pass the defined quality gates.</shortdesc>
<author>Stefan Eike</author>
</topicmeta>
</keydef>
<keydef
keys="afastpathforbuildingdata-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#fast_path_for_building_data_assets_from_DITA"
format="html"
scope="external"
>
<topicmeta>
<linktext>A fast path for building data assets from DITA</linktext>
<shortdesc>Structured content can save the day when product complexity gets in the way. Let's see how DITA content
fits into an external database using the org.dita.normalize transformation as base. DITA-OT can be packaged in
different ways to prepare dev/test environment setups for IT and developer contributors.</shortdesc>
<author>François Violette</author>
</topicmeta>
</keydef>
<keydef
keys="overviewofdita-semiaopen-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#overview_of_dita-semia_open-source_plugins_for_DITA-OT"
format="html"
scope="external"
>
<topicmeta>
<linktext>Overview of dita-semia open-source plugins for DITA-OT</linktext>
<shortdesc>I have created some DITA-OT plugins that are available as open-source (github.com/dita-semia). And I'd
like to give an overview of them: 1) postprocessing: Zip the output or set the pdf filename dynamically
depending on some content. 2) topic-num: Add numbers to topics, figures and tables (especially for HTML output).
3) image-convert: Convert images for compatibility (e.g. SVG to PNG for HTML output). 4) pdf: Yet another pdf
layout working with FOP. 5) diff: Compare two versions of a document and highlight the differences.resolver:
Resolve custom attributes (usually set as defaults be the schema) to standard DITA content, e.g. by applying an
XSLT transformation to some content, add static text content or resolve identifiers to cross
references.</shortdesc>
<author>Patrik Stellmann</author>
</topicmeta>
</keydef>
<keydef
keys="unittestingdita-otplugin-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#unit_testing_DITA-OT_plugin_extensions"
format="html"
scope="external"
>
<topicmeta>
<linktext>Unit Testing DITA-OT Plugin Extensions</linktext>
<shortdesc>I have created a Unit Testing Framework for DITA-OT Plugins
https://github.com/jason-fox/fox.jason.unit-test - This is a DITA-OT Plugin to test DITA-OT Plugins. The
complete functionality would include HTML and command line test results, ANT script profiling, XSL template code
coverage, e automated CI testing - integration with Travis, and how to write maintainable tests swiftly and
painlessly.</shortdesc>
<author>Jason Fox</author>
</topicmeta>
</keydef>
<keydef
keys="stepbystepimplementation-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#step_by_step_implementation_of_a_DITA"
format="html"
scope="external"
>
<topicmeta>
<linktext>Step by step implementation of a DITA Open Toolkit plugin</linktext>
<shortdesc>There are lots of DITA-OT extension points, maybe list some of the most common ones, then based on 3-4
use cases implement small plugins which use those extension points. For example: a plugin which changes the
default label value for "Note"a plugin which adds an XHTML customization matching a DITA element with a certain
@status attribute value and producing a certain HTML spana plugin which customizes the PDF processing in some
waya plugin which adds a specialization DTD with an XML catalog</shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="metaditasamplestestingar-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#meta_DITA_samples"
format="html"
scope="external"
>
<topicmeta>
<linktext>Meta DITA samples: testing around the edge cases</linktext>
<shortdesc>Over the past few years I've developed a number of test cases that are exhaustive but on very specific
features. The sample files are not well suited for automated testing, but can often be used to manually test
custom plugins. In this lightning talk, I'll describe the samples that exist today, and also solicit feedback on
other similar test sets that might prove useful.</shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="plug-ininstallationmadee-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#plug-in_installation_made_easier"
format="html"
scope="external"
>
<topicmeta>
<linktext>Plug-in installation made easier</linktext>
<shortdesc>Description and a demo of the new DITA-OT plug-in repository.</shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="installingdita-otonmacos-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#installing_DITA-OT_on_macOS_via_homebrew"
format="html"
scope="external"
>
<topicmeta>
<linktext>Installing DITA-OT on macOS via Homebrew</linktext>
<shortdesc>A new alternative installation method can now be used to install DITA-OT on macOS via the platform's
most popular open-source package manager. This talk explains the benefits of this approach, highlights key
differences to the default installation via .zip archive and demonstrates the new installation
process.</shortdesc>
<author>Roger Sheen</author>
</topicmeta>
</keydef>
<keydef
keys="comparisonbetweenthedocb-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#comparison_between_the_DocBook_and_DITA"
format="html"
scope="external"
>
<topicmeta>
<linktext>Comparison between the DocBook and DITA publishing systems</linktext>
<shortdesc>Let's compare side by side look at how the Docbook and DITA publishing systems work. This could give us
some ideas about future directions for DITA publishing. The presentation could be structured like this: Main
target audiences for Docbook and DITA vocabularies. Maybe initially discuss a little the Docbook and DITA
vocabularies, the ways in which Docbook handled new versions, how DITA tried to have all versions backward
compatible, the choice not to have a namespace for DITA elements. Show how Docbook solved the problem with
supporting both Docbook 4 and Docbook 5 standards. The Docbook @version attribute. 1) Pure XSLT-based processing
versus the melange of ANT + Java + XSLT which is the DITA Open Toolkit. How parameters can be discovered and
set. Also discuss how many parameters are available by default to be set for Docbook. Maybe ask people if they
want more params available by default for DITA processing. Show some examples with how a simple XSLT
customization for the HTML output can be accomplished in both systems. Also discuss disadvantages of pure XSLT
based publishing approaches, impossibility of copying resources (images for example) to an output folder for
example. 2) Adding new elements/attributes to Docbook and DITA. If you change Docbook in any way, it can no
longer be named Docbook 3) User's guides. A very decent user's manual structured a bit like a tutorial binding
together the Docbook specs, extending the vocabulary + publishing part:. The DITA-OT documentation only contains
documentation about the publishing part. 4) Profiling (filtering content). For example Docbook allows you to
filter content based on any attribute (even on xml:lang). 5) Discuss new ideas to be implemented in DITA, after
they were originally used in the DocBook publishing system:a) Index pages creating when using Apache FOP b) The
Docbook WebHelp project (Javascript-based search). c) Syntax highlight in code blocks d) Olinks (linking between
publications) e) You can add xlink:href on any Docbook element converting it to a link. f) Custom Processing
instructions which can change the publishing.</shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="ditagradleandgitasmallte-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#DITA_gradle_and_git"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA, Gradle and Git: a small team approach to publishing</linktext>
<shortdesc>At L-Acoustics we adopted an open source toolchain to automate our publishing process. With the CI
capabilities of GitLab and the dita-ot-gradle and saxon-gradle plugins developed by Eero Helenius, we have
created a comprehensive publishing solution suited to the needs of our small teams. One important feature of our
system is the handling of DITA-OT plugin dependencies. This architecture has facilitated the use of DITA by our
SMEs and marketing writers since from their point of view they just have to produce content and the output
"magically" appears.</shortdesc>
<author>Lionel Moizeau</author>
</topicmeta>
</keydef>
<keydef
keys="dita-otwebsitesurveyresu-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#DITA_website_survey_results"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT Website Survey Results</linktext>
<shortdesc>This session presents the results of a survey of www.dita-ot.org website users conducted in summer
2018. Topic areas included user happiness with the current website, how often and how the site is used, in what
formats users desire the DITA-OT documentation, etc.</shortdesc>
<author>Lief Erickson</author>
</topicmeta>
</keydef>
<keydef
keys="highlightsinrecentdita-o-2018"
href="https://www.oxygenxml.com/events/2018/dita-ot_day.html#highlights_in_recent_DITA"
format="html"
scope="external"
>
<topicmeta>
<linktext>Highlights in recent DITA-OT versions</linktext>
<shortdesc>The core developers present an overview of the changes in DITA Open Toolkit within the past year and
highlight new features that may be of particular interest to users.</shortdesc>
<author>Robert Anderson/Jarno Elovirta</author>
</topicmeta>
</keydef>
</map>

225
dita-ot-3.6/docsrc/resources/ditaotdaykeys/dita-ot-day-2019-keys.ditamap Normal file
View file

@ -0,0 +1,225 @@
<?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>
<!-- This file was generated from dita-ot-day-ditamap-keys.py found at https://gist.github.com/lief-erickson/4019b6ddf09c154164d4830b0fd6e7e8. -->
<title>DITA-OT Day 2019</title>
<keydef
keys="dita-otshoptalk-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#dita_ot_shop_talk"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA-OT Shop Talk</linktext>
<shortdesc>Join us for an inside view of the DITA Open Toolkit project workshop: Who’s on duty; what’s on the
workbench; shavings, chips, and sawdust on the cutting room floor; management negotiations with union
representatives; annual guild membership drive, and a few ideas for what comes next.</shortdesc>
<author>Robert Anderson, Roger Sheen, Jarno Elovirta, George Bina</author>
</topicmeta>
</keydef>
<keydef
keys="easyaspiepdfcustomizatio-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#easy_as_pie_pdf_customizations_using_css"
format="html"
scope="external"
>
<topicmeta>
<linktext>Easy as pie PDF customizations using CSS</linktext>
<shortdesc> CSS can be used to produce quality PDF and using CSS to style the PDF output is much easier than using
XSLT stylesheets. We'll explore various scenarios (changing fonts, changing the paper size, rotating pages,
flagging content) and see how easily this can be done using CSS. </shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="generatingmetricsfromyou-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#generating_metrics"
format="html"
scope="external"
>
<topicmeta>
<linktext>Generating metrics from your DITA project</linktext>
<shortdesc> The DITA Map Metrics Report plugin can be used to generate all kinds of interesting metrics from your
DITA project. We'll explore what the plugin can offer and then use the plugin to build graphics which show
metrics evolve between various versions of the user's manual. </shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="casestudyoftaxonomyandse-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#case_study_of_taxonomy_and_search"
format="html"
scope="external"
>
<topicmeta>
<linktext>Case Study of Taxonomy and Search for DITA-OT</linktext>
<shortdesc> The DITA-OT website was the case study organization for my master's thesis. In this session we'll talk
about what data and metrics influenced the taxonomy used to create the index, how Subject Scheme is used to
control @outputclass values, how Algolia DocSearch is causing findability problems, and recommendations for
improvements. </shortdesc>
<author>Lief Erickson</author>
</topicmeta>
</keydef>
<keydef
keys="documentationdevelopment-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#documentation_developments"
format="html"
scope="external"
>
<topicmeta>
<linktext>Documentation Developments</linktext>
<shortdesc> This talk provides an overview of recent changes to the DITA-OT documentation and project website,
points out open issues, highlights ideas for future improvements, and closes with room for suggestions from the
community and a call for contributions. </shortdesc>
<author>Roger Fienhold Sheen</author>
</topicmeta>
</keydef>
<keydef
keys="theartofdoingnothing-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#the_art_of_doing_nothing"
format="html"
scope="external"
>
<topicmeta>
<linktext>The Art of doing nothing</linktext>
<shortdesc> Standard DITA-OT pre-processing assumes that all input files are of a processable format (e.g. DITA
topics, lwDITA, hDITA etc). This session demonstrates the use of a series of DITA-OT pass-through plugins, which
avoid DITA-OT pre-processing and extend possible input formats for chapters and topics to a wider range of
standard documentation formats used by developers and non-technical experts (e.g. Word documents, Swagger
specifications, Postman collections etc.):1) fox.jason.passthrough, 2) fox.jason.passthrough.pandoc, 3)
fox.jason.passthrough.swagger</shortdesc>
<author>Jason Fox</author>
</topicmeta>
</keydef>
<keydef
keys="allthecoolkidsareusingth-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#all_the_cool_kids_are_using_the_cloud"
format="html"
scope="external"
>
<topicmeta>
<linktext>All the cool kids are using the Cloud</linktext>
<shortdesc> Demonstration of two new DITA-OT transforms showing how to create novel XML-based intermediate outputs
and consume cloud-based services. The two new transforms cover DITA-to-speech and intelligent natural language
translation of text based on semantic DITA markup:1) fox.jason.audiobook, 2)
fox.jason.translate.xliff</shortdesc>
<author>Jason Fox</author>
</topicmeta>
</keydef>
<keydef
keys="allthecoolkidsareusingja-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#all_the_cool_kids_are_using_javascript"
format="html"
scope="external"
>
<topicmeta>
<linktext>All the cool kids are using JavaScript</linktext>
<shortdesc> Demonstration of a series of DITA-OT plugins combining the use of JavaScript with ANT and XSLT. An
architectural discussion on how to design, test and integrate JavaScript-based functions within DITA-OT Plugins
and how to split the code between different programming languages and appropriate use of extension points. The
plugins include a syntax-highlighter and a DITA prettifier:1) fox.jason.splash, 2) fox.jason.prismjs, 3)
fox.jason.readthedocs, 4) fox.jason.pretty-dita</shortdesc>
<author>Jason Fox</author>
</topicmeta>
</keydef>
<keydef
keys="editingditaopentoolkitpr-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#editing_dita_open_toolkit_project_files"
format="html"
scope="external"
>
<topicmeta>
<linktext>Editing DITA Open Toolkit Project files</linktext>
<shortdesc> DITA Open Toolkit project files can store the entire set of main DITA Maps, output formats and
parameters necessary for publishing your DITA project. We'll explore how an XML editing tool can provide
editing, validation and publishing support for the project file. </shortdesc>
<author>George Bina</author>
</topicmeta>
</keydef>
<keydef
keys="onefiletorulethemalldita-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#one_file_to_rule"
format="html"
scope="external"
>
<topicmeta>
<linktext>One file to rule them all (DITA Project)</linktext>
<shortdesc> DITA-OT 3.4 introduces support for project files to define reusable input context and publications. We
discuss why the feature was developed, how to use them and in the darkness bind them. </shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="ah-wmldita-to-wordplug-i-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#ah_wml_dita_to_word_plug-in"
format="html"
scope="external"
>
<topicmeta>
<linktext>AH-WML DITA-to-Word Plug-in</linktext>
<shortdesc>AH-WML is a DITA-OT plug-in that generates Microsoft Word Document (.docx) from DITA contents. It is a
work in progress, but it already supports multiple image formats (GIF, PNG, JPEG, TIFF, EMF, SVG (Word 2016 or
later)), CALS table rendering, and several standard DITA elements (&lt;p&gt;, &lt;ul&gt;, &lt;ol&gt;,
&lt;dl&gt;, &lt;pre&gt;). </shortdesc>
<author>Tony Graham</author>
</topicmeta>
</keydef>
<keydef
keys="varioususefulopensourcep-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#various_useful_open_source_plugins"
format="html"
scope="external"
>
<topicmeta>
<linktext>Various useful Open source plugins to enhance DITA publishing</linktext>
<shortdesc> The DITA Open Toolkit publishing engine has support for plugins which can be installed to customize or
enhance the publishing process. In time Syncro Soft (the company which produces Oxygen XML Editor) has developed
and made open source lots of small plugins which can be installed in the publishing engine. I will be presenting
small examples in order to show case what each plugin in the Oxygen XML GitHub organization does and maybe give
you ideas about how you could use these open source plugins on your side. </shortdesc>
<author>Radu Coravu</author>
</topicmeta>
</keydef>
<keydef
keys="runningonsomeoneelsescom-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#running_on_someone_else_computer"
format="html"
scope="external"
>
<topicmeta>
<linktext>Running on someone else’s computer</linktext>
<shortdesc> Description and demo of how to deploy DITA-OT on AWS, using Batch, Lambda, DynamoDB, and API Gateway
to run the process and orchestrate the deployment with CDK. </shortdesc>
<author>Jarno Elovirta</author>
</topicmeta>
</keydef>
<keydef
keys="trimyourtoolkitwiththiso-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#trim_your_toolkit"
format="html"
scope="external"
>
<topicmeta>
<linktext>Trim your toolkit with this one weird trick!</linktext>
<shortdesc> DITA-OT has now been under development for over fifteen years. If you started customizing DITA-OT with
the first release to support plug-ins, even those plug-ins could be over a decade old. So what should we all be
doing to keep our tools clean? In this session, we will talk about how DITA-OT has grown: a brief history of how
we got where we are, past efforts to handle technical debt, what we all might do to help make it easier to
manage (or get rid of) that debt. </shortdesc>
<author>Robert Anderson</author>
</topicmeta>
</keydef>
<keydef
keys="newsandannouncements-2019"
href="https://www.oxygenxml.com/events/2019/dita-ot_day.html#news_and_announcements"
format="html"
scope="external"
>
<topicmeta>
<linktext>News and Announcements</linktext>
<shortdesc/>
<author>DITA-OT Day team</author>
</topicmeta>
</keydef>
</map>

6
dita-ot-3.6/docsrc/resources/expert.ditaval Executable file
View file

@ -0,0 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<val>
<prop action="include" att="audience" val="expert"/>
<prop action="exclude" att="audience" val="novice"/>
</val>

169
dita-ot-3.6/docsrc/resources/extension-points.xsl Normal file
View file

@ -0,0 +1,169 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="xs"
version="2.0">
<xsl:output doctype-public="-//OASIS//DTD DITA Reference//EN"
doctype-system="reference.dtd"/>
<xsl:strip-space elements="*"/>
<xsl:param name="output-dir.url"/>
<xsl:template match="/">
<xsl:call-template name="all"/>
<xsl:call-template name="separate"/>
</xsl:template>
<xsl:template name="all">
<xsl:comment> Generated from plugin source, do not edit! </xsl:comment>
<reference id="all-extension-points">
<title id="title" outputclass="generated">All DITA-OT extension points</title>
<titlealts>
<navtitle>All extension points</navtitle>
</titlealts>
<shortdesc id="shortdesc">The pre-defined extension points can be used to add new functionality to DITA-OT. If
your toolkit installation includes custom plug-ins that define additional extension points, you can add to this
list by rebuilding the DITA-OT documentation.</shortdesc>
<refbody>
<section>
<dl>
<xsl:apply-templates select="//extension-point" mode="reuse">
<xsl:sort select="@name"/>
</xsl:apply-templates>
</dl>
</section>
</refbody>
</reference>
</xsl:template>
<xsl:template name="separate">
<!--xsl:for-each select="//transtype/param"-->
<xsl:for-each select="//plugin">
<xsl:variable name="id" select="@id"/>
<xsl:message>Writing <xsl:value-of select="$output-dir.url"/>extension-points-in-<xsl:value-of select="$id"/>.dita</xsl:message>
<xsl:result-document href="{$output-dir.url}/extension-points-in-{$id}.dita"
doctype-public="-//OASIS//DTD DITA Reference//EN"
doctype-system="reference.dtd">
<xsl:comment> Generated from plugin source, do not edit! </xsl:comment>
<reference id="{$id}-ext">
<title outputclass="generated">
<xsl:text>Extension points in </xsl:text>
<codeph><xsl:value-of select="@id"/></codeph>
</title>
<titlealts>
<navtitle id="navtitle">
<xsl:value-of select="(transtype/@desc)[1]"/>
</navtitle>
</titlealts>
<shortdesc id="shortdesc">The <codeph><xsl:value-of select="@id"/></codeph> plug-in provides extension points
to modify <xsl:value-of select="(transtype/@desc)[1]"/> processing.</shortdesc>
<refbody>
<section>
<dl>
<xsl:apply-templates select="extension-point">
<xsl:sort select="@id"/>
</xsl:apply-templates>
</dl>
</section>
</refbody>
</reference>
</xsl:result-document>
</xsl:for-each>
</xsl:template>
<!--xsl:template match="transtype" mode="inherit" as="element(param)*">
<xsl:sequence select="param"/>
<xsl:variable name="extends" as="xs:string?">
<xsl:choose>
<xsl:when test="@name = 'base'"/>
<xsl:when test="@extends">
<xsl:value-of select="@extends"/>
</xsl:when>
<xsl:otherwise>base</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:if test="exists($extends)">
<xsl:apply-templates select="//transtype[tokenize(@name, '\s+') = $extends]" mode="inherit"/>
</xsl:if>
</xsl:template-->
<xsl:template match="extension-point">
<dlentry id="{@id}">
<xsl:if test="@deprecated = 'true'">
<xsl:attribute name="importance">deprecated</xsl:attribute>
</xsl:if>
<xsl:if test="@required = 'true'">
<xsl:attribute name="importance">required</xsl:attribute>
</xsl:if>
<dt>
<parmname>
<xsl:value-of select="@id"/>
</parmname>
<ph>
<indexterm>
<parmname><xsl:value-of select="@id"/></parmname>
</indexterm>
<indexterm>extension points<indexterm>
<parmname><xsl:value-of select="@id"/></parmname>
</indexterm></indexterm>
</ph>
<xsl:if test="parent::*[@deprecated = 'true']">
<ph>
<indexterm>deprecated features<indexterm>extension points<indexterm>
<parmname><xsl:value-of select="@id"/></parmname>
</indexterm></indexterm>
</indexterm>
</ph>
</xsl:if>
</dt>
<dd id="{@id}.desc">
<xsl:value-of select="@name"/>
</dd>
</dlentry>
</xsl:template>
<xsl:template match="extension-point" mode="reuse">
<xsl:variable name="containing-plugin" select="ancestor::plugin/@id"/>
<dlentry id="{@id}">
<xsl:if test="@deprecated = 'true'">
<xsl:attribute name="importance">deprecated</xsl:attribute>
</xsl:if>
<xsl:if test="@required = 'true'">
<xsl:attribute name="importance">required</xsl:attribute>
</xsl:if>
<dt>
<parmname>
<xsl:value-of select="@id"/>
</parmname>
<ph>
<indexterm>
<parmname><xsl:value-of select="@id"/></parmname>
</indexterm>
<indexterm>extension points<indexterm>
<parmname><xsl:value-of select="@id"/></parmname>
</indexterm></indexterm>
</ph>
<xsl:if test="parent::*[@deprecated = 'true']">
<ph>
<indexterm>deprecated features<indexterm>extension points<indexterm>
<parmname><xsl:value-of select="@id"/></parmname>
</indexterm></indexterm>
</indexterm>
</ph>
</xsl:if>
</dt>
<!-- Changing the keyref to "extension-points-in-{$containing-plugin}/{@id}" would link to the exact parameter. -->
<dd>Defined in plug-in
<xref keyref="extension-points-in-{$containing-plugin}">
<codeph><xsl:value-of select="$containing-plugin"/></codeph>
</xref>.
</dd>
<dd conkeyref="extension-points-in-{$containing-plugin}/{@id}.desc" id="{@id}.desc"/>
</dlentry>
</xsl:template>
</xsl:stylesheet>

943
dita-ot-3.6/docsrc/resources/external-links.ditamap Normal file
View file

@ -0,0 +1,943 @@
<?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>External links</title>
<!-- Key definitions for external web resources -->
<topicset id="dita-ot-github">
<topicmeta>
<navtitle>DITA-OT GitHub Project</navtitle>
</topicmeta>
<keydef
keys="dita-ot-issues"
href="https://github.com/dita-ot/dita-ot/issues"
scope="external"
format="html"
>
<topicmeta>
<linktext>GitHub issues tracker</linktext>
</topicmeta>
</keydef>
<keydef
keys="contributions"
href="https://github.com/dita-ot/dita-ot/graphs/contributors"
scope="external"
format="html"
>
<topicmeta>
<linktext>code contributions</linktext>
</topicmeta>
</keydef>
<keydef
keys="docs-contributions"
href="https://github.com/dita-ot/docs/graphs/contributors"
scope="external"
format="html"
>
<topicmeta>
<linktext>documentation contributions</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-issues"
href="https://github.com/dita-ot/dita-ot/issues?q=label%3A%22DITA+1.3%22"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA 1.3 label</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita20-issues"
href="https://github.com/dita-ot/dita-ot/issues?q=label%3A%22DITA+2.0%22"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA 2.0 label</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita-ot-gradle"
href="https://github.com/eerohele/dita-ot-gradle"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT Gradle Plugin</linktext>
</topicmeta>
</keydef>
<keydef
keys="registry-repo"
href="https://github.com/dita-ot/registry"
scope="external"
format="html"
>
<topicmeta>
<linktext>github.com/dita-ot/registry</linktext>
</topicmeta>
</keydef>
<keydef
keys="pull-request"
href="https://help.github.com/articles/about-pull-requests/"
scope="external"
format="html"
>
<topicmeta>
<linktext>pull request</linktext>
</topicmeta>
</keydef>
<keydef
keys="plugin-dublin-core"
href="https://github.com/dita-ot/org.dita.html5.dublin-core/"
scope="external"
format="html"
>
<topicmeta>
<linktext>org.dita.html5.dublin-core</linktext>
</topicmeta>
</keydef>
</topicset>
<topicset id="dita-ot-rn">
<topicmeta>
<navtitle>DITA-OT Release Notes</navtitle>
</topicmeta>
<keydef
keys="2.0-release-notes"
href="https://www.dita-ot.org/2.0/readme/changes/rel2.0.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 2.0 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="2.1-release-notes"
href="https://www.dita-ot.org/2.1/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 2.1 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="2.2-release-notes"
href="https://www.dita-ot.org/2.2/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 2.2 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="2.3-release-notes"
href="https://www.dita-ot.org/2.3/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 2.3 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="2.4-release-notes"
href="https://www.dita-ot.org/2.4/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 2.4 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="2.5-release-notes"
href="https://www.dita-ot.org/2.5/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 2.5 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="3.0-release-notes"
href="https://www.dita-ot.org/3.0/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 3.0 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="3.1-release-notes"
href="https://www.dita-ot.org/3.1/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 3.1 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="3.2-release-notes"
href="https://www.dita-ot.org/3.2/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 3.2 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="3.3-release-notes"
href="https://www.dita-ot.org/3.3/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 3.3 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="3.4-release-notes"
href="https://www.dita-ot.org/3.4/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 3.4 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="3.5-release-notes"
href="https://www.dita-ot.org/3.5/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 3.5 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="3.6-release-notes"
href="https://www.dita-ot.org/3.6/release-notes/"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA-OT 3.6 Release Notes</linktext>
</topicmeta>
</keydef>
</topicset>
<topicset id="downloads">
<topicmeta>
<navtitle>Download links</navtitle>
</topicmeta>
<keydef
keys="download.ant"
href="https://ant.apache.org"
scope="external"
format="html"
>
<topicmeta>
<linktext>ant.apache.org</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.dita-ot"
href="https://www.dita-ot.org/download"
scope="external"
format="html"
>
<topicmeta>
<linktext>dita-ot.org/download</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.fop"
href="https://xmlgraphics.apache.org/fop/download.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>xmlgraphics.apache.org/fop</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.html-help-workshop"
href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms669985%28v=vs.85%29.aspx"
scope="external"
format="html"
>
<topicmeta>
<linktext>msdn.microsoft.com</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.icu4j"
href="http://site.icu-project.org/download"
scope="external"
format="html"
>
<topicmeta>
<linktext>icu-project.org/download</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.openjdk"
href="https://adoptopenjdk.net"
scope="external"
format="html"
>
<topicmeta>
<linktext>adoptopenjdk.net</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.openjdk.azul"
href="https://www.azul.com/downloads/zulu/"
scope="external"
format="html"
>
<topicmeta>
<linktext>Azul Zulu</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.openjdk.corretto"
href="https://aws.amazon.com/corretto/"
scope="external"
format="html"
>
<topicmeta>
<linktext>Amazon Corretto</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.openjdk.redhat"
href="https://developers.redhat.com/products/openjdk/download"
scope="external"
format="html"
>
<topicmeta>
<linktext>Red Hat</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.oracle-jdk"
href="http://www.oracle.com/technetwork/java/javase/downloads"
scope="external"
format="html"
>
<topicmeta>
<linktext>oracle.com/technetwork/java</linktext>
</topicmeta>
</keydef>
<keydef
keys="download.saxon"
href="http://saxon.sourceforge.net"
scope="external"
format="html"
>
<topicmeta>
<linktext>saxon.sourceforge.net</linktext>
</topicmeta>
</keydef>
</topicset>
<topicset id="fop">
<topicmeta>
<navtitle>FOP links</navtitle>
</topicmeta>
<keydef
keys="fop-20-rn"
href="https://xmlgraphics.apache.org/fop/2.0/releaseNotes_2.0.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>Apache FOP 2.0 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="fop-21-rn"
href="https://xmlgraphics.apache.org/fop/2.1/releaseNotes_2.1.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>Apache FOP 2.1 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="fop-23-rn"
href="https://xmlgraphics.apache.org/fop/2.3/releaseNotes_2.3.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>Apache FOP 2.3 Release Notes</linktext>
</topicmeta>
</keydef>
<keydef
keys="fop-accessibility"
href="https://xmlgraphics.apache.org/fop/trunk/accessibility.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>Apache FOP Accessibility</linktext>
</topicmeta>
</keydef>
</topicset>
<topicset id="specs">
<topicmeta>
<navtitle>Specs and RFC links</navtitle>
</topicmeta>
<topicset id="dita13spec">
<keydef
keys="dita13-spec"
href="http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-part0-overview.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA 1.3 specification</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-all-inclusive"
href="http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-part3-all-inclusive.html"
scope="external"
format="html"
>
<topicmeta>
<linktext
>DITA 1.3 Part 3 latest errata version: All-Inclusive Edition (HTML)</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-all-inclusive-pdf"
href="http://docs.oasis-open.org/dita/dita/v1.3/dita-v1.3-part3-all-inclusive.pdf"
scope="external"
format="pdf"
>
<topicmeta>
<linktext
>DITA 1.3 Part 3 latest errata version: All-Inclusive Edition (PDF)</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-source"
href="http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part3-all-inclusive/dita-v1.3-errata01-os-part3-all-inclusive-complete-dita.zip"
scope="external"
format="zip"
>
<topicmeta>
<linktext
>DITA Version 1.3 Errata 01 (Distribution ZIP of the DITA source)</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-metadata-cascade"
href="http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part1-base/archSpec/base/cascading-in-a-ditamap.html#cascading-in-a-ditamap"
scope="external"
format="html"
>
<topicmeta>
<linktext
>DITA 1.3 specification: Cascading of metadata attributes in a DITA map</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-metadata-cascade-example"
href="http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part1-base/archSpec/base/example-how-cascade-att-functions.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>Example: How the @cascade attribute functions</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-keyscopes"
href="http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part1-base/archSpec/base/keyScopes.html"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA 1.3 specification: Scoped keys</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-branch-filter"
href="http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part1-base/archSpec/base/branch-filtering.html"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA 1.3 specification: Branch filtering</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-conaction"
href="http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part1-base/langRef/attributes/theconactionattribute.html"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA 1.3 specification: The <xmlatt
>conaction</xmlatt> attribute</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-profile-groups"
href="http://docs.oasis-open.org/dita/dita/v1.3/errata01/os/complete/part1-base/archSpec/base/usage-of-conditional-processing-attributes.html"
format="html"
scope="external"
>
<topicmeta>
<linktext
>DITA 1.3 specification: Groups within profiling attributes</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita13-spec-revprop"
href="http://docs.oasis-open.org/dita/dita/v1.3/errata02/os/complete/part3-all-inclusive/langRef/ditaval/ditaval-revprop.html#ditaval-revprop"
format="html"
scope="external"
>
<topicmeta>
<linktext>DITA 1.3 specification: The <xmlelement
>revprop</xmlelement> element</linktext>
</topicmeta>
</keydef>
</topicset>
<topicset id="dita12">
<keydef
keys="dita12-xhtml"
href="http://docs.oasis-open.org/dita/v1.2/spec/DITA1.2-spec.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>DITA 1.2 Specification (XHTML)</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita12-pdf"
href="http://docs.oasis-open.org/dita/v1.2/spec/DITA1.2-spec.pdf"
scope="external"
format="pdf"
>
<topicmeta>
<linktext>DITA 1.2 Specification (PDF)</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita12-source"
href="http://docs.oasis-open.org/dita/v1.2/spec/DITA1.2-spec.zip"
scope="external"
format="zip"
>
<topicmeta>
<linktext>DITA 1.2 Specification (DITA source)</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita12-spec-chunking"
href="http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/chunking.html"
format="html"
scope="external"
>
<topicmeta>
<linktext>Chunking definition in the DITA 1.2 specification</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita12-spec-l10n"
href="http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/translation.html"
format="html"
scope="external"
>
<topicmeta>
<linktext>Localization overview in the OASIS DITA standard</linktext>
</topicmeta>
</keydef>
</topicset>
<keydef
keys="dublin-core"
href="https://dublincore.org/specifications/dublin-core/dcmi-terms"
format="html"
scope="external"
>
<topicmeta>
<linktext>Dublin Core Metadata Element Set</linktext>
</topicmeta>
</keydef>
<keydef keys="json" href="https://json.org" scope="external" format="html">
<topicmeta>
<linktext>JSON</linktext>
</topicmeta>
</keydef>
<keydef
keys="html5-code-highlighting"
href="https://www.w3.org/TR/html52/textlevel-semantics.html#the-code-element"
scope="external"
format="html"
>
<topicmeta>
<linktext>HTML5-compliant syntax highlighting</linktext>
</topicmeta>
</keydef>
<topicset id="lightweight-dita">
<keydef
keys="lwdita"
href="http://docs.oasis-open.org/dita/LwDITA/v1.0/cn01/LwDITA-v1.0-cn01.pdf"
scope="external"
format="pdf"
>
<topicmeta>
<linktext>Lightweight DITA</linktext>
</topicmeta>
</keydef>
</topicset>
<keydef
keys="fo-spec.change-bar-begin"
scope="external"
format="html"
href="http://www.w3.org/TR/xsl/#fo_change-bar-begin"
>
<topicmeta>
<linktext>XSL-FO fo:change-bar-begin element</linktext>
</topicmeta>
</keydef>
<keydef
keys="fo-spec.change-bar-style"
scope="external"
format="html"
href="http://www.w3.org/TR/xsl/#change-bar-style"
>
<topicmeta>
<linktext>@change-bar-style</linktext>
</topicmeta>
</keydef>
<keydef
keys="rfc3986"
href="https://tools.ietf.org/html/rfc3986"
scope="external"
format="html"
>
<topicmeta>
<linktext>RFC 3986</linktext>
</topicmeta>
</keydef>
<keydef
keys="rfc5147"
href="http://tools.ietf.org/html/rfc5147"
scope="external"
format="html"
>
<topicmeta>
<linktext>RFC 5147</linktext>
</topicmeta>
</keydef>
<keydef keys="yaml" href="https://yaml.org" scope="external" format="html">
<topicmeta>
<linktext>YAML</linktext>
</topicmeta>
</keydef>
</topicset>
<topicset id="licenses">
<topicmeta>
<navtitle>Third-party licenses</navtitle>
</topicmeta>
<keydef
keys="license-apache-2"
href="https://www.apache.org/licenses/LICENSE-2.0"
scope="external"
format="html"
>
<topicmeta>
<linktext>Apache License 2.0</linktext>
</topicmeta>
</keydef>
<keydef
keys="license-EPL"
href="http://www.eclipse.org/legal/epl-v10.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>Eclipse Public License 1.0</linktext>
</topicmeta>
</keydef>
<keydef
keys="license-LGPL"
href="https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>GNU Lesser General Public License 2.1</linktext>
</topicmeta>
</keydef>
<keydef
keys="license-ICU"
href="http://source.icu-project.org/repos/icu/icu/tags/release-57-1/LICENSE"
scope="external"
format="html"
>
<topicmeta>
<linktext>ICU License</linktext>
</topicmeta>
</keydef>
<keydef
keys="license-MIT"
href="https://opensource.org/licenses/mit-license.php"
scope="external"
format="html"
>
<topicmeta>
<linktext>MIT License</linktext>
</topicmeta>
</keydef>
<keydef
keys="license-MPL"
href="https://www.mozilla.org/media/MPL/1.1/index.0c5913925d40.txt"
scope="external"
format="html"
>
<topicmeta>
<linktext>Mozilla Public License 1.0</linktext>
</topicmeta>
</keydef>
<keydef
keys="license-W3C"
href="https://www.w3.org/Consortium/Legal/2002/copyright-documents-20021231"
scope="external"
format="html"
>
<topicmeta>
<linktext>W3C Document License</linktext>
</topicmeta>
</keydef>
</topicset>
<topicset id="websites">
<topicmeta>
<navtitle>Other Websites</navtitle>
</topicmeta>
<keydef
keys="ant-manual"
href="http://ant.apache.org/manual"
scope="external"
format="html"
>
<topicmeta>
<linktext>Apache Ant documentation</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita-tc"
href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita"
format="html"
scope="external"
>
<topicmeta>
<linktext>OASIS DITA Technical Committee</linktext>
</topicmeta>
</keydef>
<keydef
keys="dita-adoption-tc"
href="https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=dita-adoption"
scope="external"
format="html"
>
<topicmeta>
<linktext>OASIS DITA Adoption Technical Committee</linktext>
</topicmeta>
</keydef>
<keydef
keys="eclipse-website"
href="http://www.eclipse.org"
scope="external"
format="html"
>
<topicmeta>
<linktext>Official Eclipse website</linktext>
</topicmeta>
</keydef>
<keydef
keys="docker"
href="https://www.docker.com"
scope="external"
format="html"
>
<topicmeta>
<linktext>Docker</linktext>
</topicmeta>
</keydef>
<keydef
keys="sass-lang"
href="http://sass-lang.com"
scope="external"
format="html"
>
<topicmeta>
<linktext>Sass</linktext>
</topicmeta>
</keydef>
<keydef
keys="jelovirt-on-pdf2-i18n"
href="http://www.elovirta.com/2016/02/18/font-configuration-in-pdf2.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>Font configuration in PDF2</linktext>
</topicmeta>
</keydef>
<keydef
keys="markdown"
href="https://daringfireball.net/projects/markdown/"
scope="external"
format="html"
>
<topicmeta>
<linktext>Markdown</linktext>
</topicmeta>
</keydef>
<keydef
keys="commonmark"
href="http://commonmark.org"
scope="external"
format="html"
>
<topicmeta>
<linktext>CommonMark</linktext>
</topicmeta>
</keydef>
<keydef
keys="gfm-spec"
href="https://github.github.com/gfm/"
scope="external"
format="html"
>
<topicmeta>
<linktext>GitHub-Flavored Markdown</linktext>
</topicmeta>
</keydef>
<keydef
keys="semver"
href="https://semver.org"
scope="external"
format="html"
>
<topicmeta>
<linktext>semantic versioning</linktext>
</topicmeta>
</keydef>
<keydef
keys="gradle"
href="https://gradle.org"
scope="external"
format="html"
>
<topicmeta>
<linktext>Gradle</linktext>
</topicmeta>
</keydef>
<keydef
keys="gradle-daemon"
href="https://docs.gradle.org/current/userguide/gradle_daemon.html"
scope="external"
format="html"
>
<topicmeta>
<linktext>Gradle Daemon</linktext>
</topicmeta>
</keydef>
<keydef
keys="homebrew"
href="https://brew.sh"
scope="external"
format="html"
>
<topicmeta>
<linktext>Homebrew</linktext>
</topicmeta>
</keydef>
<keydef
keys="noto-sans-font"
href="https://fonts.google.com/specimen/Noto+Sans"
scope="external"
format="html"
>
<topicmeta>
<linktext>Noto Sans</linktext>
</topicmeta>
</keydef>
<keydef
keys="saxon-java-extensions-impl"
href="http://www.saxonica.com/html/documentation9.8/extensibility/integratedfunctions"
scope="external"
format="html"
>
<topicmeta>
<linktext>Integrated extension functions</linktext>
</topicmeta>
</keydef>
<keydef
keys="site-plugin-registry"
href="https://www.dita-ot.org/plugins"
scope="external"
format="html"
>
<topicmeta>
<linktext>dita-ot.org/plugins</linktext>
</topicmeta>
</keydef>
<keydef
keys="signoff"
href="https://www.dita-ot.org/DCO"
scope="external"
format="html"
>
<topicmeta>
<linktext>signing your work</linktext>
</topicmeta>
</keydef>
<keydef
keys="PATH"
href="https://en.wikipedia.org/wiki/PATH_(variable)"
scope="external"
format="html"
>
<topicmeta>
<linktext><varname>PATH</varname> environment variable</linktext>
</topicmeta>
</keydef>
<keydef
keys="prismjs"
href="https://prismjs.com"
scope="external"
format="html"
>
<topicmeta>
<linktext>prism.js</linktext>
</topicmeta>
</keydef>
</topicset>
<mapref href="dita-ot-day-video-keys.ditamap" format="ditamap"/>
</map>

6
dita-ot-3.6/docsrc/resources/fact.hs Normal file
View file

@ -0,0 +1,6 @@
-- START-FACT
fact :: Int -> Int
fact 0 = 1
fact n = n * fact (n-1)
-- END-FACT
main = print $ fact 7

4
dita-ot-3.6/docsrc/resources/header.xml Normal file
View file

@ -0,0 +1,4 @@
<div class="header">
<p>DITA Open Toolkit</p>
<hr/>
</div>

6
dita-ot-3.6/docsrc/resources/html.ditaval Normal file
View file

@ -0,0 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<val>
<prop action="include" att="deliveryTarget" val="html"/>
<prop action="exclude" att="deliveryTarget" val="pdf"/>
</val>

149
dita-ot-3.6/docsrc/resources/key-definitions.ditamap Normal file
View file

@ -0,0 +1,149 @@
<?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 id="keydefs">
<title>Key definitions (variables)</title>
<!-- Submap with key definitions for external web resources -->
<mapref href="external-links.ditamap"/>
<!-- Submap with key definitions for each topic -->
<mapref href="source-files.ditamap"/>
<!--VERSION NUMBERS: DITA-OT-->
<!-- DITA-OT: Major & minor release version (2 digits) -->
<keydef keys="release">
<topicmeta>
<keywords>
<keyword>3.6</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- DITA-OT: Latest maintenance version (normally 3 digits, 2 for initial minor release) -->
<!-- ↓ excerpt-version ↓ -->
<keydef keys="maintenance-version">
<topicmeta>
<keywords>
<keyword>3.6</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- ↑ end-excerpt ↑ -->
<!--VERSION NUMBERS: OTHER APPLICATIONS-->
<!-- Ant: Bundled version-->
<keydef keys="tool.ant.version">
<topicmeta>
<keywords>
<keyword>1.10.9</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- Apache Commons Codec: Bundled version -->
<keydef keys="tool.codec.version">
<topicmeta>
<keywords>
<keyword>1.10</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- Apache Commons IO: Bundled version -->
<keydef keys="tool.io.version">
<topicmeta>
<keywords>
<keyword>2.8.0</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- Guava: Bundled version -->
<keydef keys="tool.guava.version">
<topicmeta>
<keywords>
<keyword>25.1-jre</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- ICU for Java: Bundled version -->
<keydef keys="tool.icu4j.version">
<topicmeta>
<keywords>
<keyword>61.1</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- Java-->
<keydef keys="tool.java.version">
<topicmeta>
<keywords>
<keyword>8u101</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- Logback Classic Module used by OT Java API -->
<keydef keys="tool.logback.version">
<topicmeta>
<keywords>
<keyword>1.2.3</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- Simple Logging Facade for Java (SLF4J) used by OT Java API -->
<keydef keys="tool.SLF4J.version">
<topicmeta>
<keywords>
<keyword>1.7.25</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- Xerces: Bundled version-->
<keydef keys="tool.xerces.version">
<topicmeta>
<keywords>
<keyword>2.12.0</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- FOP: Bundled version -->
<keydef keys="tool.fop.version">
<topicmeta>
<keywords>
<keyword>2.5</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- XML APIs: Bundled version-->
<keydef keys="tool.xmlapis.version">
<topicmeta>
<keywords>
<keyword>1.4.01</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- XML Resolver: Bundled version-->
<keydef keys="tool.resolver.version">
<topicmeta>
<keywords>
<keyword>1.2</keyword>
</keywords>
</topicmeta>
</keydef>
<!-- Saxon: Bundled version -->
<keydef keys="tool.saxon.edition">
<topicmeta>
<keywords>
<keyword>Saxon-HE</keyword>
</keywords>
</topicmeta>
</keydef>
<keydef keys="tool.saxon.version">
<topicmeta>
<keywords>
<keyword>9.9.1.4</keyword>
</keywords>
</topicmeta>
</keydef>
</map>

95
dita-ot-3.6/docsrc/resources/messages.xsl Normal file
View file

@ -0,0 +1,95 @@
<?xml version="1.0" encoding="UTF-8"?><!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<xsl:stylesheet version="2.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="no" doctype-public="-//OASIS//DTD DITA Reference//EN" doctype-system="reference.dtd"/>
<xsl:template match="/">
<xsl:comment> This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. </xsl:comment>
<xsl:comment> This file is generated based on the message information shipped with DITA-OT, as defined in the file DITA-OT/config/messages.xml To regenerate this topic, run the following command: DITA-OT/docsrc/gradlew messages
Alternatively, you may use that same build file to create a PDF, HTML5, or HTML Help version of the documentation, which will update the topic as part of the build. To rebuild PDF and HTML5, just run the command DITA-OT/docsrc/gradlew
To build only one output format, run that same build command, followed by either "html", "pdf", or "htmlhelp". For example, this command will rebuild the HTML documentation (including the updated messages topic): DITA-OT/docsrc/gradlew html </xsl:comment> <!-- The title, shortdesc, and overview section in this topic will all
be overwritten with "conref push", as long as it is built
with the full userguide.ditamap. The text here is provided as
a default in case the topic is generated on its own. -->
<reference id="msgs">
<title id="title" outputclass="generated">Error messages</title>
<shortdesc id="shortdesc">This topic defines all error messages generated by the DITA-OT.</shortdesc>
<prolog>
<metadata>
<keywords>
<indexterm>error messages</indexterm>
</keywords>
</metadata>
</prolog>
<refbody>
<section id="overview">
<p>Plug-ins may be used to add additional error messages into the toolkit; for more information, see <cite>Customizing DITA-OT</cite>.
</p>
</section>
<simpletable>
<xsl:attribute name="relcolwidth">1.5* 1.5* 3* 4*</xsl:attribute>
<sthead>
<stentry>Message&#xA0;ID</stentry>
<stentry>Severity</stentry>
<stentry>Message text</stentry>
<stentry>Additional details</stentry>
</sthead>
<xsl:for-each select="/*/message">
<xsl:sort select="@id"/>
<strow id="{@id}">
<stentry>
<msgnum>
<xsl:value-of select="@id"/>
</msgnum>
<indexterm>
<msgnum>
<xsl:value-of select="@id"/>
</msgnum>
</indexterm>
</stentry>
<stentry>
<xsl:choose>
<xsl:when test="@type='INFO'">Info</xsl:when>
<xsl:when test="@type='WARN'">Warning</xsl:when>
<xsl:when test="@type='ERROR'">Error</xsl:when>
<xsl:when test="@type='FATAL'">Fatal</xsl:when>
<xsl:otherwise>
<xsl:value-of select="@type"/>
</xsl:otherwise>
</xsl:choose>
</stentry>
<stentry>
<xsl:call-template name="format-message">
<xsl:with-param name="text" select="string(reason)"/>
</xsl:call-template>
<xsl:text></xsl:text>
<xsl:call-template name="format-message">
<xsl:with-param name="text" select="string(response)"/>
</xsl:call-template>
</stentry>
<stentry id="{@id}-extra">&#xA0;</stentry>
</strow>
</xsl:for-each>
</simpletable>
</refbody>
</reference>
</xsl:template>
<xsl:template name="format-message">
<xsl:param name="text"/>
<xsl:choose>
<xsl:when test="contains($text, '%') and not(number(substring(substring-after($text, '%'), 1, 1)) = number('NaN'))">
<xsl:value-of select="substring-before($text, '%')"/>
<varname>
<xsl:text>%</xsl:text>
<xsl:value-of select="substring(substring-after($text, '%'), 1, 1)"/>
</varname>
<xsl:call-template name="format-message">
<xsl:with-param name="text" select="substring(substring-after($text, '%'), 2)"/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$text"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template> <!-- To create each as a nested topic --> <!--
<xsl:for-each select="/*/message"><reference id="{@id}"><title><xsl:value-of select="@id"/></title><shortdesc><xsl:value-of select="reason"/></shortdesc><refbody><section><title>User response</title><p><xsl:value-of select="response"/></p></section></refbody></reference></xsl:for-each>
--></xsl:stylesheet>

6
dita-ot-3.6/docsrc/resources/novice.ditaval Executable file
View file

@ -0,0 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<val>
<prop action="include" att="audience" val="novice"/>
<prop action="exclude" att="audience" val="expert"/>
</val>

197
dita-ot-3.6/docsrc/resources/params.xsl Normal file
View file

@ -0,0 +1,197 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
exclude-result-prefixes="xs"
version="2.0">
<xsl:output doctype-public="-//OASIS//DTD DITA Reference//EN"
doctype-system="reference.dtd"/>
<xsl:strip-space elements="*"/>
<xsl:param name="output-dir.url"/>
<xsl:template match="/">
<xsl:call-template name="all"/>
<xsl:call-template name="separate"/>
</xsl:template>
<xsl:template name="all">
<xsl:comment> Generated from plugin source, do not edit! </xsl:comment>
<reference id="parameters">
<title outputclass="generated">DITA-OT parameters</title>
<reference id="all">
<title>All DITA-OT parameters</title>
<refbody>
<section>
<parml>
<xsl:for-each select="//transtype/param">
<xsl:sort select="@name"/>
<!--xsl:variable name="props" as="xs:string*">
<xsl:variable name="params" as="element(param)*">
<xsl:apply-templates select=".." mode="inherit"/>
</xsl:variable>
<xsl:for-each select="$params/../@name">
<xsl:sequence select="tokenize(., '\s+')"/>
</xsl:for-each>
</xsl:variable-->
<xsl:apply-templates select=".">
<!--xsl:with-param name="props" select="string-join(distinct-values($props), ' ')"/-->
</xsl:apply-templates>
</xsl:for-each>
</parml>
</section>
</refbody>
</reference>
</reference>
</xsl:template>
<xsl:template name="separate">
<!--xsl:for-each select="//transtype/param"-->
<xsl:for-each-group select="//transtype" group-by="@name">
<xsl:variable name="id" select="current-grouping-key()"/>
<xsl:message>Writing <xsl:value-of select="$output-dir.url"/>parameters-<xsl:value-of select="$id"/>.dita</xsl:message>
<xsl:result-document href="{$output-dir.url}/parameters-{$id}.dita"
doctype-public="-//OASIS//DTD DITA Reference//EN"
doctype-system="reference.dtd">
<xsl:comment> Generated from plugin source, do not edit! </xsl:comment>
<reference id="{$id}">
<title outputclass="generated">
<xsl:value-of select="current-group()[1]/@desc"/>
<xsl:text> parameters</xsl:text>
</title>
<titlealts>
<navtitle>
<xsl:value-of select="current-group()[1]/@desc"/>
</navtitle>
</titlealts>
<shortdesc id="shortdesc"/>
<refbody>
<section>
<parml>
<xsl:variable name="params" as="element(param)*">
<xsl:sequence select="(current-group() | //transtype[@extends = current-grouping-key()])/param"/>
<!--xsl:apply-templates select="." mode="inherit"/-->
</xsl:variable>
<xsl:for-each-group select="$params" group-by="@name">
<xsl:sort select="@name"/>
<xsl:apply-templates select="current-group()[1]">
<xsl:with-param name="params" select="current-group()"/>
</xsl:apply-templates>
</xsl:for-each-group>
</parml>
</section>
</refbody>
</reference>
</xsl:result-document>
</xsl:for-each-group>
</xsl:template>
<!--xsl:template match="transtype" mode="inherit" as="element(param)*">
<xsl:sequence select="param"/>
<xsl:variable name="extends" as="xs:string?">
<xsl:choose>
<xsl:when test="@name = 'base'"/>
<xsl:when test="@extends">
<xsl:value-of select="@extends"/>
</xsl:when>
<xsl:otherwise>base</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:if test="exists($extends)">
<xsl:apply-templates select="//transtype[tokenize(@name, '\s+') = $extends]" mode="inherit"/>
</xsl:if>
</xsl:template-->
<xsl:template match="param">
<xsl:param name="params" select="."/>
<xsl:param name="props" select="tokenize(../@name, '\s+')" as="xs:string*"/>
<plentry id="{@name}">
<xsl:if test="not($props = 'base')">
<!--xsl:attribute name="props" select="concat('transtype(', string-join($props, ' '), ')')"/-->
<xsl:attribute name="props" select="string-join($props, ' ')"/>
</xsl:if>
<xsl:if test="@deprecated = 'true'">
<xsl:attribute name="importance">deprecated</xsl:attribute>
</xsl:if>
<xsl:if test="@required = 'true'">
<xsl:attribute name="importance">required</xsl:attribute>
</xsl:if>
<pt>
<parmname>
<xsl:value-of select="@name"/>
</parmname>
<ph>
<indexterm>
<parmname><xsl:value-of select="@name"/></parmname>
</indexterm>
<indexterm>parameters<indexterm>
<parmname><xsl:value-of select="@name"/></parmname>
</indexterm></indexterm>
</ph>
<xsl:if test="@deprecated = 'true'">
<ph>
<indexterm>deprecated features<indexterm>parameters<indexterm>
<parmname><xsl:value-of select="@name"/></parmname>
</indexterm></indexterm>
</indexterm>
</ph>
</xsl:if>
</pt>
<pd id="{@name}.desc">
<xsl:value-of select="@desc"/>
<xsl:choose>
<xsl:when test="@type = 'enum' and $params/val/@desc">
<xsl:text> The following values are supported:</xsl:text>
<ul>
<xsl:for-each select="$params/val">
<li>
<option>
<xsl:value-of select="."/>
</option>
<xsl:if test="@default = 'true'">
<xsl:text> (default)</xsl:text>
</xsl:if>
<xsl:text> – </xsl:text>
<xsl:value-of select="@desc"/>
</li>
</xsl:for-each>
</ul>
</xsl:when>
<xsl:when test="@type = 'enum' and $params/val">
<xsl:text> The allowed values are </xsl:text>
<xsl:choose>
<xsl:when test="count($params/val) gt 2">
<xsl:for-each select="$params/val">
<xsl:if test="position() ne 1">, </xsl:if>
<xsl:if test="position() eq last()">and </xsl:if>
<option>
<xsl:value-of select="."/>
</option>
</xsl:for-each>
</xsl:when>
<xsl:otherwise>
<xsl:for-each select="$params/val">
<xsl:if test="position() ne 1"> and </xsl:if>
<option>
<xsl:value-of select="."/>
</option>
</xsl:for-each>
</xsl:otherwise>
</xsl:choose>
<xsl:if test="$params/val[@default = 'true']">
<xsl:text>; the default value is </xsl:text>
<option>
<xsl:value-of select="$params/val[@default = 'true']"/>
</option>
</xsl:if>
<xsl:text>.</xsl:text>
</xsl:when>
</xsl:choose>
</pd>
</plentry>
</xsl:template>
</xsl:stylesheet>

6
dita-ot-3.6/docsrc/resources/pdf.ditaval Normal file
View file

@ -0,0 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<val>
<prop action="exclude" att="deliveryTarget" val="html"/>
<prop action="include" att="deliveryTarget" val="pdf"/>
</val>

165
dita-ot-3.6/docsrc/resources/properties-file.xsl Normal file
View file

@ -0,0 +1,165 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:fn="http://example.com/namespace"
exclude-result-prefixes="xs fn"
version="2.0">
<xsl:output method="text"/>
<xsl:strip-space elements="*"/>
<xsl:variable name="wrapCol" select="80"/>
<xsl:variable name="indentSize" select="20"/>
<xsl:variable name="crlf" select="codepoints-to-string((13,10))"/>
<xsl:variable name="comment" select="concat($crlf,'# ')"/>
<xsl:variable name="divBar" select="concat('# ',fn:padIt('=',$wrapCol - 4),' #')"/>
<xsl:variable name="sctn-start" select="concat($crlf,$crlf,'##### ')"/>
<xsl:variable name="sctn-end" select="concat(' PROPERTIES #####',$crlf)"/>
<xsl:variable name="indentSpaces" select="fn:padIt(' ',$indentSize)"/>
<xsl:function name="fn:padIt" as="xs:string">
<xsl:param name="string" as="xs:string"/>
<xsl:param name="len" as="xs:integer"/>
<xsl:variable name="seq">
<xsl:for-each select="1 to $len">
<xsl:value-of select="$string"/>
</xsl:for-each>
</xsl:variable>
<xsl:value-of select="string-join($seq,'')"/>
</xsl:function>
<xsl:function name="fn:breakAfter">
<xsl:param name="string" as="xs:string"/>
<xsl:param name="breakpoint" as="xs:integer"/>
<xsl:variable name="matchExpr" select="concat('^.{1,',$breakpoint,'}(\s|$)')"/>
<xsl:variable name="rest" select="replace($string,$matchExpr,'')"/>
<xsl:variable name="start" select="substring-before($string,$rest)"/>
<xsl:choose>
<xsl:when test="$start=''">
<start><xsl:value-of select="$string"/></start>
<rest></rest>
</xsl:when>
<xsl:otherwise>
<start><xsl:value-of select="$start"/></start>
<rest><xsl:value-of select="$rest"/></rest>
</xsl:otherwise>
</xsl:choose>
</xsl:function>
<xsl:function name="fn:wrapAndIndent" as="xs:string">
<xsl:param name="name" as="xs:string"/>
<xsl:param name="description" as="xs:string"/>
<xsl:variable name="step1"
select="fn:breakAfter(concat(normalize-space($name),$indentSpaces,normalize-space($description)),$indentSize - 1)"/>
<xsl:variable name="step2"
select="fn:breakAfter(concat($step1[1],normalize-space($step1[2])),$wrapCol)"/>
<xsl:choose>
<xsl:when test="string-length($step2[2]) gt 0">
<xsl:value-of select="concat($comment,$step2[1],fn:wrapAndIndent('',$step2[2]))"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="concat($comment,$step2[1])"/>
</xsl:otherwise>
</xsl:choose>
</xsl:function>
<xsl:template match="/">
<xsl:call-template name="all"/>
</xsl:template>
<xsl:template name="all">
<xsl:text>
# ============================================================================ #
#
# GENERATED PROPERTIES FILE FOR USE WITH THE DITA COMMAND
#
# Lines in this file that start with a number sign '#' are comments.
#
# To set a build parameter, remove the commenting '#' at the start of the line
# and specify the value for the parameter after the '=' sign, for example,
#
# args.filter = my-filter.ditaval
#
# Use the `dita` command with the `--propertyfile` option to use the build
# parameters specified in a properties file, for example:
#
# dita --input=my.ditamap --format=html5 --propertyfile=my.properties
#
# Build parameters in this file are grouped by transformation type.
# Supported parameter values are listed in brackets [] after each description,
# with an asterisk (*) indicating the default value where appropriate.
#
# ============================================================================ #
</xsl:text>
<xsl:for-each-group select="//transtype[param]" group-by="@desc">
<xsl:sort select="@desc"/>
<xsl:variable name="padsize" select="(ceiling( (($wrapCol - string-length(@desc)) div 2 ) ) - 2) cast as xs:integer"/>
<xsl:variable name="descpad" select="fn:padIt(' ',$padsize)"/>
<xsl:value-of
select="upper-case(concat($crlf,$crlf,$divBar,$crlf,'#',$descpad,@desc,$crlf,$divBar))"/>
<xsl:for-each-group select="current-group()/param" group-by="@name">
<xsl:sort select="@name"/>
<xsl:call-template name="param"/>
</xsl:for-each-group>
</xsl:for-each-group>
</xsl:template>
<xsl:template name="param">
<xsl:param name="params" select="current-group()"/>
<xsl:param name="desc_pre" as="xs:string*">
<xsl:if test="@required = 'true'">(REQUIRED) </xsl:if>
</xsl:param>
<xsl:param name="desc_post" as="xs:string*">
<xsl:if test="not(./@type = 'enum') and $params/val/@default='true'">
<xsl:value-of select="concat(' Default value: ',distinct-values($params/val[@default='true']),'.')"/>
</xsl:if>
</xsl:param>
<xsl:choose>
<xsl:when test="@name = 'args.input' or @name = 'transtype' or @deprecated = 'true'">
<!-- don’t output these as they shouldn’t be used in properties file -->
</xsl:when>
<xsl:otherwise>
<xsl:variable name="exampleval">
<xsl:choose>
<xsl:when test="$params/val/@default='true'">
<xsl:value-of select="distinct-values($params/val[@default='true'])"/>
</xsl:when>
<xsl:when test="./@type = 'enum'">
<xsl:value-of select="distinct-values($params/val[1])"/>
</xsl:when>
<xsl:otherwise></xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:value-of select="concat($crlf,$comment,@name,' = ',$exampleval)"/>
<xsl:value-of select="fn:wrapAndIndent('',concat($desc_pre,@desc,$desc_post))"/>
<xsl:choose>
<xsl:when test="@type = 'enum' and $params/val">
<xsl:for-each-group select="$params/val" group-by="text()">
<xsl:sort select="current-grouping-key()"/>
<xsl:choose>
<xsl:when test="@desc and @default = 'true'">
<xsl:value-of select="fn:wrapAndIndent('',concat('[ ',.,' ]* - ',@desc))"/>
</xsl:when>
<xsl:when test="@desc">
<xsl:value-of select="fn:wrapAndIndent('',concat('[ ',.,' ] - ',@desc))"/>
</xsl:when>
<xsl:when test="@default='true'">
<xsl:value-of select="fn:wrapAndIndent('',concat('[ ',.,' ]*'))"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="fn:wrapAndIndent('',concat('[ ',.,' ]'))"/>
</xsl:otherwise>
</xsl:choose>
</xsl:for-each-group>
</xsl:when>
</xsl:choose>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet>

388
dita-ot-3.6/docsrc/resources/reltable.ditamap Normal file
View file

@ -0,0 +1,388 @@
<?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 id="reltable">
<title>Relationship tables</title>
<reltable>
<relrow>
<relcell>
<topicref keyref="plugin-addgeneratedtext">
<topicmeta>
<linktext>How to add support for new languages in HTML</linktext>
</topicmeta>
</topicref>
</relcell>
<relcell>
<topicref keyref="globalization-languages">
<topicmeta>
<linktext>Languages supported by the core toolkit</linktext>
</topicmeta>
</topicref>
</relcell>
</relrow>
</reltable>
<reltable>
<title>CTR: Ant topics</title>
<relheader>
<relcolspec type="concept"/>
<relcolspec type="task"/>
<relcolspec type="reference"/>
</relheader>
<relrow>
<relcell>
<topicref keyref="ant"/>
</relcell>
<relcell>
<topicgroup collection-type="family">
<topicref keyref="building-with-ant"/>
<topicref keyref="creating-an-ant-build-script"/>
</topicgroup>
</relcell>
<relcell>
<topicref keyref="parameters_intro" linking="targetonly"/>
<topicref keyref="ant-manual">
<topicmeta>
<linktext>Apache Ant documentation</linktext>
</topicmeta>
</topicref>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2eclipsehelp">
<topicmeta>
<linktext>Eclipse help transformation</linktext>
</topicmeta>
</topicref>
</relcell>
<relcell/>
<relcell>
<topicref keyref="parameters-base"/>
<topicref keyref="parameters-base-html"/>
<topicref keyref="parameters-eclipsehelp"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2htmlhelp" platform="windows">
<topicmeta>
<linktext>HTML help transformation</linktext>
</topicmeta>
</topicref>
</relcell>
<relcell/>
<relcell>
<topicref keyref="parameters-base"/>
<topicref keyref="parameters-base-html"/>
<topicref keyref="parameters-htmlhelp"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2pdf">
<topicmeta>
<linktext>PDF transformation</linktext>
</topicmeta>
</topicref>
</relcell>
<relcell/>
<relcell>
<topicref keyref="parameters-base"/>
<topicref keyref="parameters-pdf"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2xhtml">
<topicmeta>
<linktext>XHTML transformation</linktext>
</topicmeta>
</topicref>
</relcell>
<relcell>
<topicref keyref="html-customization-parameters"/>
</relcell>
<relcell>
<topicref keyref="parameters-base"/>
<topicref keyref="parameters-base-html"/>
<topicref keyref="parameters-xhtml"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2html5">
<topicmeta>
<linktext>HTML5 transformation</linktext>
</topicmeta>
</topicref>
</relcell>
<relcell>
<topicref keyref="html-customization-parameters"/>
</relcell>
<relcell>
<topicref keyref="parameters-base"/>
<topicref keyref="parameters-base-html"/>
<topicref keyref="parameters-html5"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2markdown" type="topic">
<topicmeta>
<linktext>Markdown transformations</linktext>
</topicmeta>
</topicref>
</relcell>
<relcell/>
<relcell>
<topicref keyref="parameters-base"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2dita" type="topic">
<topicmeta>
<linktext>Normalized DITA transformations</linktext>
</topicmeta>
</topicref>
</relcell>
<relcell/>
<relcell>
<topicref keyref="parameters-base"/>
</relcell>
</relrow>
<relrow>
<relcell/>
<relcell>
<topicref keyref="html-customization-plugin-bundle-css"/>
</relcell>
<relcell>
<topicref keyref="parameters-base-html"/>
</relcell>
</relrow>
<relrow>
<relcell/>
<relcell>
<topicref keyref="html-customization-plugin-webfont"/>
<topicref keyref="html-customization-plugin-javascript"/>
</relcell>
<relcell>
<topicref keyref="parameters-base-html"/>
</relcell>
</relrow>
<relrow>
<relcell/>
<relcell>
<topicref keyref="increasing-the-jvm" linking="targetonly"/>
</relcell>
<relcell>
<topicref keyref="parameters-other"/>
<topicref keyref="other-errors"/>
</relcell>
</relrow>
</reltable>
<reltable>
<title>Source and target</title>
<relheader>
<relcolspec linking="sourceonly"/>
<relcolspec linking="targetonly"/>
</relheader>
<relrow>
<relcell>
<topicref keyref="parameters-eclipsehelp"/>
<topicref keyref="parameters-htmlhelp"/>
<topicref keyref="parameters-pdf"/>
<topicref keyref="parameters-xhtml"/>
</relcell>
<relcell>
<topicref keyref="parameters-base"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2eclipsehelp"/>
<topicref keyref="dita2html5"/>
<topicref keyref="dita2htmlhelp"/>
<topicref keyref="dita2xhtml"/>
</relcell>
<relcell>
<topicref keyref="generate-copy-outer"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="dita2pdf"/>
</relcell>
<relcell>
<topicref keyref="pdf2-creating-change-bars"/>
</relcell>
</relrow>
</reltable>
<reltable>
<title>Reference to reference: Bi-directional links</title>
<relheader>
<relcolspec type="reference"/>
<relcolspec type="reference"/>
</relheader>
<relrow>
<relcell>
<topicref keyref="parameters-base-html"/>
</relcell>
<relcell>
<topicref keyref="parameters-eclipsehelp"/>
<topicref keyref="parameters-html5"/>
<topicref keyref="parameters-htmlhelp"/>
<topicref keyref="parameters-xhtml"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="other-errors"/>
</relcell>
<relcell>
<topicref keyref="parameters-other"/>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="extension-points-in-org.dita.base"/>
</relcell>
<relcell>
<topicref keyref="plugin-extension-points-pre-processing"/>
<topicref keyref="plugin-extension-points-support"/>
<topicref keyref="plugin-extension-points-general"/>
</relcell>
</relrow>
</reltable>
<reltable>
<title>Task to task: Bi-directional links</title>
<relheader>
<relcolspec type="task"/>
<relcolspec type="task"/>
</relheader>
<relrow>
<relcell>
<topicref keyref="html-customization-css"/>
</relcell>
<relcell>
<topicref keyref="html-customization-plugin-bundle-css"/>
</relcell>
</relrow>
</reltable>
<reltable>
<title>External resources</title>
<relrow>
<relcell>
<topicref keyref="dita2eclipsehelp"/>
</relcell>
<relcell>
<topicref keyref="eclipse-website">
<topicmeta>
<linktext>Official Eclipse website</linktext>
</topicmeta>
</topicref>
</relcell>
</relrow>
<relrow>
<relcell>
<topicref keyref="globalization"/>
</relcell>
<relcell>
<topicref keyref="dita12-spec-l10n" type="reference">
<topicmeta>
<linktext>Localization overview in the OASIS DITA standard</linktext>
</topicmeta>
</topicref>
</relcell>
</relrow>
</reltable>
<reltable>
<title>Plugins</title>
<relheader>
<relcolspec type="reference"/>
<relcolspec type="reference"/>
</relheader>
<relrow>
<relcell>
<topicref keyref="plugin-configfile"/>
</relcell>
<relcell>
<topicref keyref="plugin-newtranstype" type="task"/>
</relcell>
</relrow>
</reltable>
<reltable>
<title>Plugins</title>
<relheader>
<relcolspec type="task"/>
<relcolspec linking="targetonly" type="task"/>
</relheader>
<relrow>
<relcell>
<topicref keyref="pdf-customization-example"/>
<topicref keyref="plugin-antpreprocess"/>
<topicref keyref="plugin-anttarget"/>
<topicref keyref="plugin-javalib"/>
<topicref keyref="plugin-messages"/>
<topicref keyref="plugin-newtranstype"/>
<topicref keyref="plugin-overridestyle"/>
<topicref keyref="plugin-xmlcatalog"/>
<topicref keyref="plugin-xsltparams"/>
</relcell>
<relcell>
<topicref keyref="plugins-installing"/>
</relcell>
</relrow>
</reltable>
<reltable>
<title>Source and target: Troubleshooting topics</title>
<relheader>
<relcolspec linking="sourceonly"/>
<relcolspec linking="targetonly"/>
</relheader>
<relrow>
<relcell>
<topicref keyref="other-errors"/>
</relcell>
<relcell>
<topicref keyref="release-notes"/>
<topicref keyref="installing-client"/>
</relcell>
</relrow>
</reltable>
<reltable>
<title>Release history</title>
<relheader>
<relcolspec linking="sourceonly"/>
<relcolspec linking="targetonly"/>
</relheader>
<relrow>
<relcell>
<topicref keyref="release-history"/>
</relcell>
<relcell>
<topicref keyref="migration"/>
<topicref keyref="3.5-release-notes"/>
<topicref keyref="3.4-release-notes"/>
<topicref keyref="3.3-release-notes"/>
<topicref keyref="3.2-release-notes"/>
<topicref keyref="3.1-release-notes"/>
<topicref keyref="3.0-release-notes"/>
<topicref keyref="2.5-release-notes"/>
<topicref keyref="2.4-release-notes"/>
<topicref keyref="2.3-release-notes"/>
<topicref keyref="2.2-release-notes"/>
<topicref keyref="2.1-release-notes"/>
<topicref keyref="2.0-release-notes"/>
<topicref format="html" href="http://dita-archive.xml.org/wiki/the-dita-open-toolkit" scope="external">
<topicmeta>
<linktext>DITA-OT 1.8 - 1.0 Release Notes</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>
</relcell>
</relrow>
</reltable>
</map>

181
dita-ot-3.6/docsrc/resources/reusable-components.dita Normal file
View file

@ -0,0 +1,181 @@
<?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>Re-usable components</title>
<shortdesc>Warehouse topic used to store re-usable content for concept topics or other constructs that would not be
valid in the existing warehouse task <filepath>conref-task.dita</filepath>.</shortdesc>
<prolog>
<metadata>
<keywords>
<indexterm><!-- This file contains reusable content. Index entries are in each <section>. --></indexterm>
</keywords>
</metadata>
</prolog>
<conbody>
<section id="use-xslt2">
<title>Upgrade stylesheets to XSLT 2.0</title>
<indexterm>upgrading</indexterm>
<indexterm>Saxon</indexterm>
<indexterm>XSLT
<indexterm>1.0</indexterm></indexterm>
<indexterm>XSLT
<indexterm>2.0</indexterm></indexterm>
<indexterm>plug-ins
<indexterm>upgrading</indexterm></indexterm>
<p>The Saxon project has announced plans to remove XSLT 1.0 support from the Saxon-HE library that ships with
DITA-OT:</p>
<lq href="https://www.xml.com/news/release-saxon-98/" format="html" scope="external">…we’re dropping XSLT 1.0
backwards compatibility mode from Saxon-HE, and hope to eliminate it entirely in due course.</lq>
<p>DITA-OT 3.0 and 3.0.1 included Saxon-HE 9.8.0.5, which rejects XSLT stylesheets that specify
<codeph>version="1.0"</codeph>. Plug-ins with XSLT templates specifying version 1.0 will fail with the message
“<msgph>XSLT 1.0 compatibility mode is not available in this configuration</msgph>.”</p>
<p>To resolve this issue, change any occurrences of <codeph>&lt;xsl:stylesheet version="1.0"></codeph> in custom
plug-in stylesheets to at least <codeph>&lt;xsl:stylesheet version="2.0"></codeph>.</p>
<note type="tip">DITA-OT 3.0.2 includes Saxon-HE 9.8.0.7, which restores XSLT 1.0 backwards-compatibility mode,
but the DITA Open Toolkit project recommends upgrading all stylesheets to XSLT 2.0 to ensure plug-ins remain
compatible with future versions of DITA-OT and Saxon-HE.</note>
</section>
<section id="validating-plugins">
<title>Validating plug-ins</title>
<div id="plugin.rnc">
<p>DITA-OT includes a RELAX NG schema file that can be used to validate the <filepath>plugin.xml</filepath>
files that define the capabilities of each plug-in.
<indexterm>schema
<indexterm>RELAX NG</indexterm></indexterm>
<indexterm>validate</indexterm>
</p>
<p>To ensure the syntax of your custom plug-in is correct, include an <xmlpi>xml-model</xmlpi> processing
instruction at the beginning of the <filepath>plugin.xml</filepath> file, immediately after the XML
prolog:</p>
<p><xmlpi>xml-model href="dita-ot/plugin.rnc" type="application/relax-ng-compact-syntax"</xmlpi></p>
<p>If your authoring environment does not apply this schema automatically, point your editor to <filepath
id="samples-dir"
><varname>dita-ot-dir</varname>/resources/plugin.rnc</filepath> to associate the schema with
your plug-in file.</p>
</div>
</section>
<section id="dita-for-print">
<title><cite>DITA for Print: A DITA Open Toolkit Workbook</cite> (Second Edition, 2017)</title>
<indexterm>Leigh White</indexterm>
<indexterm>DITA for Print</indexterm>
<p>Authored by Leigh W. White, DITA Specialist at IXIASOFT, and published by XML Press, <cite>DITA for
Print</cite> walks readers through developing a PDF customization from scratch. </p>
<p>Here is an excerpt from the back cover:</p>
<lq><cite>DITA for Print</cite> is for anyone who wants to learn how to create PDFs using the DITA Open Toolkit
without learning everything there is to know about XSL-FO, XSLT, or XPath, or even about the DITA Open Toolkit
itself. <cite>DITA for Print</cite> is written for non-programmers, by a non-programmer, and although it is
written for people who have a good understanding of the DITA standard, you don’t need a technical background to
get custom PDFs up and running quickly.</lq>
<p>This is an excellent, long-needed resource that was initially developed in 2013 for DITA-OT 1.8.</p>
<p>The second edition has been revised to cover DITA Open Toolkit Version 2, including customizing the DITA 1.3
troubleshooting topic type, localization strings, bookmarks, and the new back-cover functionality.</p>
<note type="important">
<p>The first edition of <cite>DITA for Print</cite> recommended copying entire files from the PDF2 plug-in to
your custom plug-in. The DITA-OT project — and the second edition of the book — do not recommend this
practice.</p>
<p>Instead, you should copy only the specific attribute sets and templates that you want to override. Following
this practice will more cleanly isolate your customizations from the DITA-OT code, which will make it easier
for you to update your plug-ins to work with future versions of DITA-OT.</p></note>
</section>
<section id="dita-for-practitioners">
<title><cite>DITA for Practitioners: Volume 1, Architecture and Technology</cite> (2012)</title>
<indexterm>Eliot Kimber</indexterm>
<indexterm>DITA for Practitioners: Volume 1, Architecture and Technology</indexterm>
<p>Authored by Eliot Kimber and published by XML Press, this seminal resource contains a chapter dedicated to DITA
Open Toolkit: “Running, Configuring, and Customizing the Open Toolkit”. In addition to a robust overview of
DITA-OT customization and extension, the chapter contains a detailed example of customizing a PDF plug-in to
specify 7" × 10" paper size and custom fonts for body text and headers.</p>
<p>The DITA-OT chapter in <cite>DITA for Practitioners: Volume 1</cite> was written for DITA-OT 1.5.4, which was
the latest stable version at the time it was written.</p>
</section>
<section id="java">
<title>Supported Java versions</title>
<p id="java-clients">DITA-OT is designed to run on Java version <keyword keyref="tool.java.version"/> or later and
built and tested with the Open Java Development Kit (OpenJDK). Compatible Java distributions are available from
multiple sources:
<indexterm>Java
<indexterm>versions</indexterm></indexterm>
<indexterm>Amazon Corretto</indexterm>
<indexterm>OpenJDK</indexterm>
<indexterm>Oracle JDK</indexterm>
<ul>
<li>You can download the Oracle JRE or JDK from
<xref keyref="download.oracle-jdk"/> under commercial license.</li>
<li>OpenJDK is a free open-source implementation of Java available from
<xref keyref="download.openjdk"/>.</li>
<li>Free OpenJDK distributions are also available from other vendors, including
<xref keyref="download.openjdk.corretto"/>,
<xref keyref="download.openjdk.azul"/>, and
<xref keyref="download.openjdk.redhat"/>.</li>
</ul>
</p>
</section>
<section id="preprocess2">
<title>Limitations of map-first pre-processing</title>
<p id="no-internal-preprocess2-ext">The internal extension points that run before or after individual steps in the
original <codeph>preprocess</codeph> pipeline (<codeph>preprocess.*.pre/preprocess.*.post</codeph>) are not
available in the newer map-first preprocessing pipeline (<codeph>preprocess2</codeph>), which is used in the PDF
and HTML Help transformations as of DITA-OT 3.0.</p>
</section>
<section id="legacy-plugins">
<title>Unbundled plug-ins</title>
<note id="legacy-plugins-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>
<section id="subcommands">
<title>New subcommands in 3.5</title>
<dl id="3.5-subcommands">
<dlentry>
<dt><cmdname>dita deliverables</cmdname></dt>
<dd>Prints the list of deliverables in a project <varname>file</varname></dd>
</dlentry>
<dlentry id="install-subcommand">
<dt><cmdname>dita install</cmdname></dt>
<dd>Installs or reloads plug-ins (replaces <cmdname>dita</cmdname>
<parmname>--install</parmname>)</dd>
</dlentry>
<dlentry>
<dt><cmdname>dita plugins</cmdname></dt>
<dd>Prints a list of installed plug-ins (replaces <cmdname>dita</cmdname>
<parmname>--plugins</parmname>)</dd>
</dlentry>
<dlentry>
<dt><cmdname>dita transtypes</cmdname></dt>
<dd>Prints a list of installed transformation types, or <i>output formats</i> (replaces
<cmdname>dita</cmdname>
<parmname>--transtypes</parmname>)</dd>
</dlentry>
<dlentry>
<dt><cmdname>dita uninstall</cmdname></dt>
<dd>Removes and deletes a plug-in (replaces <cmdname>dita</cmdname>
<parmname>--uninstall</parmname>)</dd>
</dlentry>
<dlentry id="version-subcommand">
<dt><cmdname>dita version</cmdname></dt>
<dd>Prints version information and exits (replaces <cmdname>dita</cmdname>
<parmname>--version</parmname>)</dd>
</dlentry>
</dl>
</section>
<section id="dita-ot-migration-tip">
<title>Recommendations for upgrading DITA-OT customizations</title>
<p id="migration-recommendation">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>
</section>
</conbody>
</concept>

7
dita-ot-3.6/docsrc/resources/site.ditaval Normal file
View file

@ -0,0 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<val>
<prop action="include" att="deliveryTarget" val="html"/>
<prop action="exclude" att="deliveryTarget" val="pdf"/>
<prop action="passthrough" att="platform"/>
</val>

218
dita-ot-3.6/docsrc/resources/source-files.ditamap Normal file
View file

@ -0,0 +1,218 @@
<?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>Source File Key Definitions</title>
<topicmeta>
<shortdesc>Provides key definitions for each DITA topic in the repository.</shortdesc>
</topicmeta>
<keydef keys="adding-plugins" href="../topics/adding-plugins.dita"/>
<keydef keys="ant" href="../topics/ant.dita"/>
<keydef keys="ant-parameters-details" href="../parameters/ant-parameters-details.dita"/>
<keydef keys="architecture" href="../reference/architecture.dita"/>
<keydef keys="books" href="../reference/books.dita"/>
<keydef keys="building-output" href="../topics/building-output.dita"/>
<keydef keys="building-with-ant" href="../topics/building-with-ant.dita"/>
<keydef keys="common-html-processing" href="../reference/common-html-processing.dita"/>
<keydef keys="configuration-properties" href="../parameters/configuration-properties.dita"/>
<keydef keys="configuration-properties-file" href="../parameters/configuration-properties-file.dita"/>
<keydef keys="conref-task" href="../resources/conref-task.dita"/>
<keydef keys="creating-an-ant-build-script" href="../topics/creating-an-ant-build-script.dita"/>
<keydef keys="creating-docker-images" href="../topics/creating-docker-images.dita"/>
<keydef keys="custom-plugins" href="../topics/custom-plugins.dita"/>
<keydef keys="customizing" href="../topics/customizing.dita"/>
<keydef keys="determining-version-of-ditaot" href="../topics/determining-version-of-ditaot.dita"/>
<keydef keys="dita-and-dita-ot-resources" href="../topics/dita-and-dita-ot-resources.dita"/>
<keydef keys="dita-command-arguments" href="../parameters/dita-command-arguments.dita"/>
<keydef keys="dita-command-help" href="../topics/dita-command-help.dita"/>
<keydef keys="dita-ot-day-videos" href="../topics/dita-ot-day-videos.dita"/>
<keydef keys="dita-ot-day-videos-intro-2014" href="../topics/dita-ot-day-videos-intro-2014.dita"/>
<keydef keys="dita-ot-day-videos-intro-2015" href="../topics/dita-ot-day-videos-intro-2015.dita"/>
<keydef keys="dita-ot-day-videos-intro-2016" href="../topics/dita-ot-day-videos-intro-2016.dita"/>
<keydef keys="dita-ot-day-videos-intro-2017" href="../topics/dita-ot-day-videos-intro-2017.dita"/>
<keydef keys="dita-ot-day-videos-intro-2018" href="../topics/dita-ot-day-videos-intro-2018.dita"/>
<keydef keys="dita-ot-day-videos-intro-2019" href="../topics/dita-ot-day-videos-intro-2019.dita"/>
<keydef keys="dita-spec-support" href="../reference/dita-spec-support.dita"/>
<keydef keys="dita-v1-2-support" href="../reference/dita-v1-2-support.dita"/>
<keydef keys="dita-v1-3-support" href="../reference/dita-v1-3-support.dita"/>
<keydef keys="dita-v2-0-support" href="../reference/dita-v2-0-support.dita"/>
<keydef keys="dita-xml-input" href="../topics/dita-xml-input.dita"/>
<keydef keys="dita2dita" href="../topics/dita2dita.dita"/>
<keydef keys="dita2eclipsehelp" href="../topics/dita2eclipsehelp.dita"/>
<keydef keys="dita2html5" href="../topics/dita2html5.dita"/>
<keydef keys="dita2htmlhelp" href="../topics/dita2htmlhelp.dita"/>
<keydef keys="dita2markdown" href="../topics/dita2markdown.dita"/>
<keydef keys="dita2pdf" href="../topics/dita2pdf.dita"/>
<keydef keys="dita2xhtml" href="../topics/dita2xhtml.dita"/>
<keydef keys="docs-dita-features" href="../reference/docs-dita-features.dita"/>
<keydef keys="eclipsehelp-processing" href="../reference/eclipsehelp-processing.dita"/>
<keydef keys="enabling-debug-mode" href="../topics/enabling-debug-mode.dita"/>
<keydef keys="error-messages messages" href="../topics/error-messages.xml"/>
<keydef keys="error-messages-details messages-push" href="../topics/error-messages-details.xml"/>
<keydef keys="extended-functionality" href="../reference/extended-functionality.dita"/>
<keydef keys="extension-points-by-plugin" href="../extension-points/extension-points-by-plugin.dita"/>
<keydef keys="extension-points-details" href="../extension-points/extension-points-details.dita"/>
<keydef keys="flagging-migration" href="../reference/flagging-migration.dita"/>
<keydef keys="generate-copy-outer" href="../parameters/generate-copy-outer.dita"/>
<keydef keys="globalization" href="../topics/globalization.dita"/>
<keydef keys="globalization-languages" href="../topics/globalization-languages.dita"/>
<keydef keys="globalization-support" href="../topics/globalization-support.dita"/>
<keydef keys="glossary" href="../reference/glossary.dita"/><!-- Glossary keys are defined in glossary.ditamap -->
<keydef keys="html-based-processing" href="../reference/html-based-processing.dita"/>
<keydef keys="html-customization" href="../topics/html-customization.dita"/>
<keydef keys="html-customization-css" href="../topics/html-customization-css.dita"/>
<keydef keys="html-customization-header" href="../topics/html-customization-header.dita"/>
<keydef keys="html-customization-navigation" href="../topics/html-customization-navigation.dita"/>
<keydef keys="html-customization-parameters" href="../topics/html-customization-parameters.dita"/>
<keydef keys="html-customization-plugin-bundle-css" href="../topics/html-customization-plugin-bundle-css.dita"/>
<keydef keys="html-customization-plugin-javascript" href="../topics/html-customization-plugin-javascript.dita"/>
<keydef keys="html-customization-plugin-webfont" href="../topics/html-customization-plugin-webfont.dita"/>
<keydef keys="html-customization-plugins" href="../topics/html-customization-plugins.dita"/>
<keydef keys="html-customization-properties-file" href="../topics/html-customization-properties-file.dita"/>
<keydef keys="html5-processing" href="../reference/html5-processing.dita"/>
<keydef keys="htmlhelp-processing" href="../reference/htmlhelp-processing.dita"/>
<keydef keys="implementation-dependent-features" href="../reference/implementation-dependent-features.dita"/>
<keydef keys="increasing-the-jvm" href="../topics/increasing-the-jvm.dita"/>
<keydef keys="input-formats" href="../topics/input-formats.dita"/>
<keydef keys="installing-client" href="../topics/installing-client.dita"/>
<keydef keys="installing-via-homebrew" href="../topics/installing-via-homebrew.dita"/>
<keydef keys="internal-ant-properties" href="../parameters/internal-ant-properties.dita"/>
<keydef keys="java-api" href="../reference/java-api.dita"/>
<keydef keys="landing-page" href="../index.dita"/>
<keydef keys="license" href="../reference/license.dita"/>
<keydef keys="local-properties-file" href="../parameters/local-properties-file.dita"/>
<keydef keys="logging" href="../topics/logging.dita"/>
<keydef keys="lwdita-input" href="../topics/lwdita-input.dita"/>
<keydef keys="map-first-preproc" href="../reference/map-first-preprocessing.dita"/>
<keydef keys="markdown-dita-syntax-reference" href="../topics/markdown-dita-syntax-reference.dita"/>
<keydef keys="markdown-input" href="../topics/markdown-input.dita"/>
<keydef keys="migrating-ant-to-dita" href="../topics/migrating-ant-to-dita.dita"/>
<keydef keys="migrating-to-1.5.4" href="../topics/migrating-to-1.5.4.dita"/>
<keydef keys="migrating-to-1.6" href="../topics/migrating-to-1.6.dita"/>
<keydef keys="migrating-to-1.7" href="../topics/migrating-to-1.7.dita"/>
<keydef keys="migrating-to-1.8" href="../topics/migrating-to-1.8.dita"/>
<keydef keys="migrating-to-2.0" href="../topics/migrating-to-2.0.dita"/>
<keydef keys="migrating-to-2.1" href="../topics/migrating-to-2.1.dita"/>
<keydef keys="migrating-to-2.2" href="../topics/migrating-to-2.2.dita"/>
<keydef keys="migrating-to-2.3" href="../topics/migrating-to-2.3.dita"/>
<keydef keys="migrating-to-2.4" href="../topics/migrating-to-2.4.dita"/>
<keydef keys="migrating-to-2.5" href="../topics/migrating-to-2.5.dita"/>
<keydef keys="migrating-to-3.0" href="../topics/migrating-to-3.0.dita"/>
<keydef keys="migrating-to-3.1" href="../topics/migrating-to-3.1.dita"/>
<keydef keys="migrating-to-3.2" href="../topics/migrating-to-3.2.dita"/>
<keydef keys="migrating-to-3.3" href="../topics/migrating-to-3.3.dita"/>
<keydef keys="migrating-to-3.4" href="../topics/migrating-to-3.4.dita"/>
<keydef keys="migrating-to-3.5" href="../topics/migrating-to-3.5.dita"/>
<keydef keys="migrating-to-3.6" href="../topics/migrating-to-3.6.dita"/>
<keydef keys="migration" href="../topics/migration.dita"/>
<keydef keys="other-errors" href="../topics/other-errors.dita"/>
<keydef keys="output-formats" href="../topics/output-formats.dita"/>
<keydef keys="parameters" href="../parameters/index.dita"/>
<keydef keys="parameters-other" href="../parameters/parameters-other.dita"/>
<keydef keys="parameters_intro" href="../parameters/parameters_intro.dita"/>
<keydef keys="pdf-customization" href="../topics/pdf-customization.dita"/>
<keydef keys="pdf-customization-approaches" href="../topics/pdf-customization-approaches.dita"/>
<keydef keys="pdf-customization-example" href="../topics/pdf-customization-example.dita"/>
<keydef keys="pdf-customization-plugin-types" href="../topics/pdf-customization-plugin-types.dita"/>
<keydef keys="pdf-customization-plugins" href="../topics/pdf-customization-plugins.dita"/>
<keydef keys="pdf-customization-resources" href="../topics/pdf-customization-resources.dita"/>
<keydef keys="pdf-plugin-structure" href="../topics/pdf-plugin-structure.dita"/>
<keydef keys="pdf-plugin-structure_common-artwork" href="../topics/pdf-plugin-structure_common-artwork.dita"/>
<keydef keys="pdf-plugin-structure_common-index" href="../topics/pdf-plugin-structure_common-index.dita"/>
<keydef keys="pdf-plugin-structure_common-vars" href="../topics/pdf-plugin-structure_common-vars.dita"/>
<keydef keys="pdf-plugin-structure_fo-attrs" href="../topics/pdf-plugin-structure_fo-attrs.dita"/>
<keydef keys="pdf-plugin-structure_fo-i18n" href="../topics/pdf-plugin-structure_fo-i18n.dita"/>
<keydef keys="pdf-plugin-structure_fo-xsl" href="../topics/pdf-plugin-structure_fo-xsl.dita"/>
<keydef keys="pdf-transform" href="../reference/pdf-transform.dita"/>
<keydef keys="pdf-transformation-history" href="../reference/pdf-transformation-history.dita"/>
<keydef keys="pdf2-creating-change-bars" href="../topics/pdf2-creating-change-bars.dita"/>
<keydef keys="plugin-addgeneratedtext" href="../topics/plugin-addgeneratedtext.dita"/>
<keydef keys="plugin-antpreprocess" href="../topics/plugin-antpreprocess.dita"/>
<keydef keys="plugin-anttarget" href="../topics/plugin-anttarget.dita"/>
<keydef keys="plugin-benefits" href="../topics/plugin-benefits.dita"/>
<keydef keys="plugin-coding-conventions" href="../topics/plugin-coding-conventions.dita"/>
<keydef keys="plugin-configfile" href="../topics/plugin-configfile.dita"/>
<keydef keys="plugin-dependencies" href="../topics/plugin-dependencies.dita"/>
<keydef keys="plugin-extension-points" href="../extension-points/plugin-extension-points.dita"/>
<keydef keys="plugin-extension-points-general" href="../extension-points/plugin-extension-points-general.dita"/>
<keydef keys="plugin-extension-points-pre-processing" href="../extension-points/plugin-extension-points-pre-processing.dita"/>
<keydef keys="plugin-extension-points-support" href="../extension-points/plugin-extension-points-support.dita"/>
<keydef keys="plugin-extension-points-xslt-import" href="../extension-points/plugin-extension-points-xslt-import.dita"/>
<keydef keys="plugin-extension-points-xslt-parameters" href="../extension-points/plugin-extension-points-xslt-parameters.dita"/>
<keydef keys="plugin-implement-saxon-collation-uri-resolvers" href="../topics/implement-saxon-collation-uri-resolvers.dita"/>
<keydef keys="plugin-implement-saxon-customizations" href="../topics/implement-saxon-customizations.dita"/>
<keydef keys="plugin-implement-saxon-extension-functions" href="../topics/implement-saxon-extension-functions.dita"/>
<keydef keys="plugin-javalib" href="../topics/plugin-javalib.dita"/>
<keydef keys="plugin-messages" href="../topics/plugin-messages.dita"/>
<keydef keys="plugin-newextensions" href="../topics/plugin-newextensions.dita"/>
<keydef keys="plugin-newtranstype" href="../topics/plugin-newtranstype.dita"/>
<keydef keys="plugin-overridestyle" href="../topics/plugin-overridestyle.dita"/>
<keydef keys="plugin-properties-file" href="../parameters/plugin-properties-file.dita"/>
<keydef keys="plugin-rewrite-rules" href="../topics/plugin-rewrite-rules.dita"/>
<keydef keys="plugin-set-parameters" href="../topics/plugin-set-parameters.dita"/>
<keydef keys="plugin-use-cases" href="../topics/plugin-use-cases.dita"/>
<keydef keys="plugin-xmlcatalog" href="../topics/plugin-xmlcatalog.dita"/>
<keydef keys="plugin-xsltparams" href="../topics/plugin-xsltparams.dita"/>
<keydef keys="plugins-installing" href="../topics/plugins-installing.dita"/>
<keydef keys="plugins-registry" href="../topics/plugins-registry.dita"/>
<keydef keys="plugins-removing" href="../topics/plugins-removing.dita"/>
<keydef keys="preprocess-branch-filter" href="../reference/preprocess-branch-filter.dita"/>
<keydef keys="preprocess-chunk" href="../reference/preprocess-chunk.dita"/>
<keydef keys="preprocess-clean-map" href="../reference/preprocess-clean-map.dita"/>
<keydef keys="preprocess-conref" href="../reference/preprocess-conref.dita"/>
<keydef keys="preprocess-conrefpush" href="../reference/preprocess-conrefpush.dita"/>
<keydef keys="preprocess-copy-to" href="../reference/preprocess-copy-to.dita"/>
<keydef keys="preprocess-copyfiles" href="../reference/preprocess-copyfiles.dita"/>
<keydef keys="preprocess-debugfilter" href="../reference/preprocess-debugfilter.dita"/>
<keydef keys="preprocess-flagging" href="../reference/preprocess-flagging.dita"/>
<keydef keys="preprocess-genlist" href="../reference/preprocess-genlist.dita"/>
<keydef keys="preprocess-keyref" href="../reference/preprocess-keyref.dita"/>
<keydef keys="preprocess-maplink" href="../reference/preprocess-maplink.dita"/>
<keydef keys="preprocess-mapref" href="../reference/preprocess-mapref.dita"/>
<keydef keys="preprocess-metadata" href="../reference/preprocess-metadata.dita"/>
<keydef keys="preprocess-profile" href="../reference/preprocess-profile.dita"/>
<keydef keys="preprocess-topic-fragment" href="../reference/preprocess-topic-fragment.dita"/>
<keydef keys="preprocess-topicpull" href="../reference/preprocess-topicpull.dita"/>
<keydef keys="preprocessing" href="../reference/preprocessing.dita"/>
<keydef keys="prerequisite-software" href="../topics/prerequisite-software.dita"/>
<keydef keys="processing-order" href="../reference/processing-order.dita"/>
<keydef keys="processing-pipeline-modules" href="../reference/processing-pipeline-modules.dita"/>
<keydef keys="processing-structure" href="../reference/processing-structure.dita"/>
<keydef keys="project-files-json" href="../topics/project-files-json.dita"/>
<keydef keys="project-files-xml" href="../topics/project-files-xml.dita"/>
<keydef keys="project-files-yaml" href="../topics/project-files-yaml.dita"/>
<keydef keys="publishing-with-ant" href="../topics/publishing-with-ant.dita"/>
<keydef keys="rebuilding-docs" href="../topics/rebuilding-docs.dita"/>
<keydef keys="reducing-processing-time" href="../topics/reducing-processing-time.dita"/>
<keydef keys="reference" href="../reference/index.dita"/>
<keydef keys="referencing-other-plugins" href="../topics/referencing-other-plugins.dita"/>
<keydef keys="release-history" href="../topics/release-history.dita"/>
<keydef keys="release-notes" href="../release-notes/index.dita"/>
<keydef keys="reusable-components" href="../resources/reusable-components.dita"/>
<keydef keys="store-api" href="../reference/store-api.dita"/>
<keydef keys="third-party-software" href="../reference/third-party-software.dita"/>
<keydef keys="troubleshooting-overview" href="../topics/troubleshooting-overview.dita"/>
<keydef keys="using-dita-command" href="../topics/using-dita-command.dita"/>
<keydef keys="using-dita-properties-file" href="../topics/using-dita-properties-file.dita"/>
<keydef keys="using-docker-images" href="../topics/using-docker-images.dita"/>
<keydef keys="using-project-files" href="../topics/using-project-files.dita"/>
<keydef keys="web-based-resources" href="../topics/web-based-resources.dita"/>
<keydef keys="xhtml-processing" href="../reference/xhtml-processing.dita"/>
<!-- Generated topics; this list should probably be generated automatically when all targets are valid -->
<keydef keys="all-extension-points" href="../extension-points/all-extension-points.dita"/>
<keydef keys="extension-points-in-org.dita.base" href="../extension-points/extension-points-in-org.dita.base.dita"/>
<keydef keys="extension-points-in-org.dita.eclipsehelp" href="../extension-points/extension-points-in-org.dita.eclipsehelp.dita"/>
<keydef keys="extension-points-in-org.dita.html5" href="../extension-points/extension-points-in-org.dita.html5.dita"/>
<keydef keys="extension-points-in-org.dita.htmlhelp" href="../extension-points/extension-points-in-org.dita.htmlhelp.dita"/>
<keydef keys="extension-points-in-org.dita.pdf2" href="../extension-points/extension-points-in-org.dita.pdf2.dita"/>
<keydef keys="extension-points-in-org.dita.xhtml" href="../extension-points/extension-points-in-org.dita.xhtml.dita"/>
<keydef keys="parameters-base" href="../parameters/parameters-base.dita"/>
<keydef keys="parameters-base-html" href="../parameters/parameters-base-html.dita"/>
<keydef keys="parameters-eclipsehelp" href="../parameters/parameters-eclipsehelp.dita"/>
<keydef keys="parameters-html5" href="../parameters/parameters-html5.dita"/>
<keydef keys="parameters-htmlhelp" href="../parameters/parameters-htmlhelp.dita"/>
<keydef keys="parameters-pdf" href="../parameters/parameters-pdf.dita"/>
<keydef keys="parameters-xhtml" href="../parameters/parameters-xhtml.dita"/>
</map>

60
dita-ot-3.6/docsrc/resources/subjectscheme-deliverytarget.ditamap Normal file
View file

@ -0,0 +1,60 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE subjectScheme PUBLIC "-//OASIS//DTD DITA Subject Scheme Map//EN" "subjectScheme.dtd">
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<subjectScheme>
<subjectHead>
<subjectHeadMeta>
<navtitle>Controlled values for the @deliveryTarget attribute</navtitle>
<shortdesc>Provides a set of values for use with the @deliveryTarget conditional-processing attribute.</shortdesc>
</subjectHeadMeta>
</subjectHead>
<subjectdef keys="deliveryTarget-values">
<topicmeta>
<navtitle>Values for @deliveryTarget attributes</navtitle>
</topicmeta>
<subjectdef keys="print">
<topicmeta>
<navtitle>Print-primary deliverables</navtitle>
</topicmeta>
<subjectdef keys="pdf">
<topicmeta>
<navtitle>PDF</navtitle>
</topicmeta>
</subjectdef>
<subjectdef keys="css-print">
<topicmeta>
<navtitle>CSS for print</navtitle>
</topicmeta>
</subjectdef>
</subjectdef>
<subjectdef keys="online">
<topicmeta>
<navtitle>Online deliverables</navtitle>
</topicmeta>
<subjectdef keys="html-based">
<topicmeta>
<navtitle>HTML-based deliverables</navtitle>
</topicmeta>
<subjectdef keys="html">
<topicmeta>
<navtitle>HTML</navtitle>
</topicmeta>
<subjectdef keys="html5">
<topicmeta>
<navtitle>HTML5</navtitle>
</topicmeta>
</subjectdef>
<subjectdef keys="site">
<topicmeta>
<navtitle>Project website: dita-ot.org</navtitle>
</topicmeta>
</subjectdef>
</subjectdef>
</subjectdef>
</subjectdef>
</subjectdef>
<enumerationdef>
<attributedef name="deliveryTarget"/>
<subjectdef keyref="deliveryTarget-values"/>
</enumerationdef>
</subjectScheme>

165
dita-ot-3.6/docsrc/resources/subjectscheme-outputclass.ditamap Normal file
View file

@ -0,0 +1,165 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE subjectScheme PUBLIC "-//OASIS//DTD DITA Subject Scheme Map//EN" "subjectScheme.dtd">
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<subjectScheme>
<subjectHead>
<subjectHeadMeta>
<navtitle>Controlled values for @outputclass on certain elements</navtitle>
</subjectHeadMeta>
</subjectHead>
<subjectdef keys="bootstrap-classes">
<topicmeta>
<navtitle>Bootstrap–specific classes </navtitle>
<shortdesc>Used to pick up Bootstrap formatting in site output.</shortdesc>
</topicmeta>
<subjectdef keys="table-outputclass">
<topicmeta>
<navtitle>Tables</navtitle>
<shortdesc>Highlight rows on hover</shortdesc>
</topicmeta>
<subjectdef keys="table-hover"/>
</subjectdef>
<subjectdef keys="ph-outputclass">
<topicmeta>
<navtitle>Phrases</navtitle>
</topicmeta>
<subjectdef keys="mark"/>
<subjectdef keys="small"/>
<subjectdef keys="text-muted"/>
</subjectdef>
</subjectdef>
<subjectdef keys="codeblock-outputclass">
<topicmeta>
<navtitle>Codeblocks</navtitle>
</topicmeta>
<subjectdef keys="codeblock-dita-ot-extensions">
<topicmeta>
<navtitle>DITA-OT Processing Extensions</navtitle>
<shortdesc>https://www.dita-ot.org/dev/reference/extended-functionality.html</shortdesc>
</topicmeta>
<subjectdef keys="normalize-space"/>
<subjectdef keys="show-line-numbers"/>
<subjectdef keys="show-whitespace"/>
</subjectdef>
<subjectdef keys="codeblock-syntax-highlights">
<topicmeta>
<navtitle>Syntax Highlights</navtitle>
<shortdesc>Used to trigger syntax highlighting via https://prismjs.com.</shortdesc>
</topicmeta>
<subjectdef keys="language-bash"/>
<subjectdef keys="language-clike"/>
<subjectdef keys="language-css"/>
<subjectdef keys="language-dockerfile"/>
<subjectdef keys="language-haskell"/>
<subjectdef keys="language-html"/>
<subjectdef keys="language-java"/>
<subjectdef keys="language-javascript"/>
<subjectdef keys="language-json"/>
<subjectdef keys="language-markdown"/>
<subjectdef keys="language-markup"/>
<subjectdef keys="language-mathml"/>
<subjectdef keys="language-properties"/>
<subjectdef keys="language-svg"/>
<subjectdef keys="language-xml"/>
<subjectdef keys="language-yaml"/>
</subjectdef>
<subjectdef keys="codeblock-syntax">
<topicmeta>
<navtitle>Code language</navtitle>
<shortdesc>Used to define the programming language code in codeblocks.</shortdesc>
</topicmeta>
<subjectdef keys="syntax-bash"/>
<subjectdef keys="syntax-batch"/>
</subjectdef>
</subjectdef>
<subjectdef keys="codeph-outputclass">
<topicmeta>
<navtitle>Code phrases</navtitle>
<shortdesc>&lt;codeph&gt; is used semantically three unique ways in the OT docs. Rather than using element
specialization this limits @outputclass on &lt;codeph&gt;, effectively creating semantic specialization without
needing to modify DTDs or schemas. How &lt;codeph&gt; is used:
https://github.com/dita-ot/docs/wiki/coding-guidelines#plug-ins</shortdesc>
</topicmeta>
<subjectdef keys="ant-target"/>
<subjectdef keys="plugin-name"/>
<subjectdef keys="preprocess"/>
</subjectdef>
<subjectdef keys="filepath-outputclass">
<topicmeta>
<navtitle>Filepath</navtitle>
<shortdesc>Control multi-platform processing</shortdesc>
</topicmeta>
<subjectdef keys="preserve-separator"/>
</subjectdef>
<subjectdef keys="multi-platform-outputclass">
<topicmeta>
<navtitle>Multi-platform examples</navtitle>
<shortdesc>Enable multi-platform tabs in site output</shortdesc>
</topicmeta>
<subjectdef keys="multi-platform"/>
</subjectdef>
<subjectdef keys="title-outputclass">
<topicmeta>
<navtitle>Titles</navtitle>
<shortdesc>Added by automated processes; not to be manually added by authors.</shortdesc>
</topicmeta>
<subjectdef keys="generated"/>
</subjectdef>
<!-- Bind an attribute to a tree of related values -->
<enumerationdef>
<elementdef name="choicetable"/>
<attributedef name="outputclass"/>
<subjectdef keyref="multi-platform-outputclass"/>
</enumerationdef>
<enumerationdef>
<elementdef name="codeblock"/>
<attributedef name="outputclass"/>
<subjectdef keyref="codeblock-dita-ot-extensions"/>
<subjectdef keyref="codeblock-syntax-highlights"/>
<subjectdef keyref="codeblock-syntax"/>
<subjectdef keyref="multi-platform-outputclass"/>
</enumerationdef>
<enumerationdef>
<elementdef name="codeph"/>
<attributedef name="outputclass"/>
<subjectdef keyref="codeph-outputclass"/>
<subjectdef keyref="codeblock-syntax"/>
</enumerationdef>
<enumerationdef>
<elementdef name="filepath"/>
<attributedef name="outputclass"/>
<subjectdef keyref="filepath-outputclass"/>
</enumerationdef>
<enumerationdef>
<elementdef name="ph"/>
<attributedef name="outputclass"/>
<subjectdef keyref="ph-outputclass"/>
</enumerationdef>
<enumerationdef>
<elementdef name="simpletable"/>
<attributedef name="outputclass"/>
<subjectdef keyref="table-outputclass"/>
</enumerationdef>
<enumerationdef>
<elementdef name="steps"/>
<attributedef name="outputclass"/>
<subjectdef keyref="multi-platform-outputclass"/>
</enumerationdef>
<enumerationdef>
<elementdef name="table"/>
<attributedef name="outputclass"/>
<subjectdef keyref="table-outputclass"/>
</enumerationdef>
<enumerationdef>
<elementdef name="title"/>
<attributedef name="outputclass"/>
<subjectdef keyref="title-outputclass"/>
</enumerationdef>
</subjectScheme>

31
dita-ot-3.6/docsrc/resources/subjectscheme.ditamap Normal file
View file

@ -0,0 +1,31 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE subjectScheme PUBLIC "-//OASIS//DTD DITA Subject Scheme Map//EN" "subjectScheme.dtd">
<!-- This file is part of the DITA Open Toolkit project. See the accompanying LICENSE file for applicable license. -->
<subjectScheme>
<!-- Outputclass Controlled Values -->
<!-- ↓ excerpt-outputclass ↓ -->
<schemeref href="subjectscheme-outputclass.ditamap"/>
<!-- ↓ excerpt-audience ↓ -->
<subjectdef keys="audience">
<subjectdef keys="novice"/>
<subjectdef keys="expert"/>
<subjectdef keys="xslt-customizer"/>
</subjectdef>
<!-- ↑ end-excerpt ↑ -->
<subjectdef keys="os">
<subjectdef keys="windows"/>
<subjectdef keys="unix">
<subjectdef keys="mac"/>
<subjectdef keys="linux"/>
</subjectdef>
</subjectdef>
<enumerationdef>
<attributedef name="audience"/>
<subjectdef keyref="audience"/>
</enumerationdef>
<enumerationdef>
<attributedef name="platform"/>
<subjectdef keyref="os"/>
</enumerationdef>
<schemeref href="subjectscheme-deliverytarget.ditamap"/>
</subjectScheme>