| A | B | C | D | ||
|---|---|---|---|---|---|
1 | To edit this sheet, click View Only, then REQUEST EDIT ACCESS. | ||||
2 | Title | Shortdesc | Proposed Index Terms | Location | |
3 | Accessing help for the dita command | You can access a list of supported parameters for the dita command by issuing the -help parameter. | http://www.dita-ot.org/2.4/user-guide/dita-command-help.html | ||
4 | Adding a Java library to the DITA-OT classpathparameter | You can use the dita.conductor.lib.import extension point to add an additional Java library to the DITA-OT classpath parameter. | http://www.dita-ot.org/2.4/dev_ref/plugin-javalib.html | ||
5 | Adding a new target to the Ant build process | Use the Ant conductor extension point (dita.conductor.target.relative) to make new targets available to the Ant processing pipeline. This can be done as part of creating a new transformation, extending pre-processing, or simply to make new Ant targets available to other plug-ins. | http://www.dita-ot.org/2.4/dev_ref/plugin-anttarget.html | ||
6 | Adding a new transformation type | Plug-ins can add an entirely new transformation type. The new transformation type can be very simple, such as an XHTML build that creates an additional control file; it also can be very complex, adding any number of new processing steps. | http://www.dita-ot.org/2.4/dev_ref/plugin-newtranstype.html | ||
7 | Adding an Ant target to the pre-processing pipeline | You can add an Ant target to the pre-processing pipeline. This enables you to insert additional processing before or after the pre-processing chain or a specific step in the pre-processing operation. | http://www.dita-ot.org/2.4/dev_ref/plugin-antpreprocess.html | ||
8 | Adding custom CSS | To modify the appearance of the default HTML output generated by the DITA Open Toolkit, you can reference a custom Cascading Style Sheet (CSS) file with the typography and colors that define your corporate identity. | http://www.dita-ot.org/2.4/dev_ref/html-customization-css.html | ||
9 | Adding custom headers and footers | You add a custom header to include a publication title, company logo, or other common branding elements in HTML output. A custom footer can also be added with copyright information, legal boilerplate, or other fine print. | http://www.dita-ot.org/2.4/dev_ref/html-customization-header.html | ||
10 | Adding navigation to topics | In HTML5 output, you can set a parameter to include table-of-contents navigation in the <nav> element of each page. The navigation can be rendered in a sidebar or menu via CSS. | http://www.dita-ot.org/2.4/dev_ref/html-customization-navigation.html | ||
11 | Adding new diagnostic messages | Use the dita.xsl.messages extension point to add plug-in-specific messages to the diagnostic messages that are generated by the DITA-OT. These messages then can be used by any XSLT override. | http://www.dita-ot.org/2.4/dev_ref/plugin-messages.html | ||
12 | Adding parameters to existing XSLT steps | You can pass parameters from the Ant build to existing XSLT steps in both the pre-processing pipeline and certain DITA-OT transformations. This can be useful if you want to make the parameters available as global<xsl:param> values within XSLT overrides. | http://www.dita-ot.org/2.4/dev_ref/plugin-xsltparams.html | ||
13 | All DITA-OT extension points | The pre-defined extension points can be used to extend the functionality of the 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. | http://www.dita-ot.org/2.4/extension-points/all-extension-points.html | ||
14 | Ant | Ant is a Java-based, open-source tool that is provided by the Apache Foundation. It can be used to declare a sequence of build actions. It is well suited for both development and document builds. The toolkit ships with a copy of Ant. | http://www.dita-ot.org/2.4/user-guide/ant.html | ||
15 | Architecture of the DITA Open Toolkit | The DITA Open Toolkit is an open-source implementation of the OASIS specification for the Darwin Information Typing Architecture. The toolkit uses Ant, XSLT, and Java to transform DITA content (maps and topics) into different deliverable formats. | http://www.dita-ot.org/2.4/dev_ref/DITA-OTArchitecture.html | ||
16 | Arguments and options for the dita command | The dita command takes mandatory arguments to process DITA content, manage plug-ins, or print information about the command. Options can be used to modify the command behavior or specify additional configuration parameters. | http://www.dita-ot.org/2.4/parameters/dita-command-arguments.html | ||
17 | Benefits of plug-ins | Plug-ins permit users to extend the toolkit in a way that is consistent, easy-to-share, and possible to preserve through toolkit upgrades. | http://www.dita-ot.org/2.4/dev_ref/plugin-benefits.html | ||
18 | Best practices for custom PDF plug-ins | Adhering to certain development practices will properly isolate your code from that of the DITA Open Toolkit. This will make it easier to you to upgrade to new versions of the DITA-OT when they are released. | http://www.dita-ot.org/2.4/dev_ref/pdf-customization-best-practices.html | ||
19 | Branch filtering (branch-filter) | The branch-filter step filters topics using DITAVAL files defined in the map. | http://www.dita-ot.org/2.4/dev_ref/preprocess-branch-filter.html | ||
20 | Building output using Ant | You can build output by using an Ant build script to provide the DITA-OT parameters. | http://www.dita-ot.org/2.4/user-guide/building-with-ant.html | ||
21 | Building output using the dita command | You can generate output using the DITA Open Toolkit dita command-line tool. Build parameters can be specified on the command line or with .properties files. | http://www.dita-ot.org/2.4/getting-started/first-build-using-dita-command.html | ||
22 | Building output using the dita command | You can generate output using the DITA Open Toolkit dita command-line tool. Build parameters can be specified on the command line or with .properties files. | http://www.dita-ot.org/2.4/user-guide/build-using-dita-command.html | ||
23 | Building output using the dita command | You can generate output using the DITA Open Toolkit dita command-line tool. Build parameters can be specified on the command line or with .properties files. | http://www.dita-ot.org/2.4/user-guide/using-dita-command.html | ||
24 | Bundling CSS in a custom HTML plug-in | You can create a DITA-OT plug-in that provides a custom stylesheet with the typography and colors that define your corporate identity. Coworkers can install this plug-in to ensure consistent HTML output across projects without having to copy the stylesheet to each project. | http://www.dita-ot.org/2.4/dev_ref/html-customization-plugin-bundle-css.html | ||
25 | Checking the DITA-OT version | You can determine the version of the DITA Open Toolkit from a command prompt. | http://www.dita-ot.org/2.4/user-guide/determining-version-of-ditaot.html | ||
26 | Chunk topics (chunk) | The chunk step breaks apart and assembles referenced DITA content based on the @chunk attribute in maps. This step is implemented in Java. | http://www.dita-ot.org/2.4/dev_ref/preprocess-chunk.html | ||
27 | Common HTML-based processing | After the pre-processing operation runs, HTML-based builds each run a common series of Ant targets to generate HTML file. Navigation may be created before or after this set of common routines. | http://www.dita-ot.org/2.4/dev_ref/XhtmlCommon.html | ||
28 | Common parameters | Certain parameters apply to all transformations that are supported by the DITA Open Toolkit. | http://www.dita-ot.org/2.4/parameters/parameters-base.html | ||
29 | Configuration properties | The DITA-OT uses .properties files and internal properties that store configuration settings for the toolkit and its plug-ins. Configuration properties are available to both Ant and Java processes, but unlike argument properties, they cannot be set at run time. | http://www.dita-ot.org/2.4/parameters/configuration-properties.html | ||
30 | Conref (conref) | The conref step resolves conref attributes, processing only the DITA maps or topics that use the @conref attribute. This step is implemented in XSLT. | http://www.dita-ot.org/2.4/dev_ref/preprocess-conref.html | ||
31 | Conref push (conrefpush) | The conrefpush step resolves "conref push" references. This step only processes documents that use conref push or that are updated due to the push action. This step is implemented in Java. | http://www.dita-ot.org/2.4/dev_ref/preprocess-conrefpush.html | ||
32 | Conrefs for DITA-OT parameter topics | This shoudn't be generated as a topic (@resource-only) | http://www.dita-ot.org/2.4/parameters/conref-dita-ot-parameters.html | ||
33 | Copy related files (copy-files) | The copy-files step copies non-DITA resources to the output directory, such as HTML files that are referenced in a map or images that are referenced by a DITAVAL file. Which files are copied depends on the transformation type. | http://www.dita-ot.org/2.4/dev_ref/preprocess-copyfiles.html | ||
34 | Copy topics (copy-to) | The copy-to step makes a copy of original topic resources to new resources defined by the @copy-to attribute. | http://www.dita-ot.org/2.4/dev_ref/preprocess-copy-to.html | ||
35 | Creating a new plug-in extension point | If your plug-in needs to define its own extension point in an XML file, add the string "_template" to the filename before the file suffix. When the plug-in is installed, this file will be processed like the built-in DITA-OT templates. | http://www.dita-ot.org/2.4/dev_ref/plugin-newextensions.html | ||
36 | Creating an Ant build script | Instead of typing the DITA-OT parameters at the command prompt, you might want to create an Ant build script that contains all of the parameters. | http://www.dita-ot.org/2.4/user-guide/creating-an-ant-build-script.html | ||
37 | Creating plug-ins | You can use DITA-OT plug-ins to extend the DITA Open Toolkit. | http://www.dita-ot.org/2.4/dev_ref/plugin-creating.html | ||
38 | Custom HTML plug-ins | For more complex customizations, you can create custom DITA-OT plug-ins that build on the default XHTML and HTML5 transformations, bundle custom stylesheets, modify the HTML markup, or override other aspects of HTML processing. | http://www.dita-ot.org/2.4/dev_ref/html-customization-plugins.html | ||
39 | Customizing HTML output | There are several ways to customize the default HTML output. You can easily adjust the look and feel just by setting parameters and adding custom CSS, or create plug-ins for more complex customizations. | http://www.dita-ot.org/2.4/dev_ref/html-customization.html | ||
40 | Customizing HTML with a .properties file | You can also use a .properties file to reference a set of build parameters when building output with the dita command. The DITA-OT documentation uses a .properties file to include custom CSS, header branding, and table-of-contents navigation in the HTML5 output. | http://www.dita-ot.org/2.4/dev_ref/html-customization-properties-file.html | ||
41 | Customizing PDF output | You can create custom DITA-OT plug-ins that build on the default DITA to PDF transformation. Plug-ins can customize covers and page layouts, modify formatting, override logic of the default PDF plug-in, and much more. | http://www.dita-ot.org/2.4/dev_ref/pdf-customization.html | ||
42 | Debug and filter (debug-filter) | The debug-filter step processes all referenced DITA content and creates copies in a temporary directory. As the DITA content is copied, filtering is performed, debugging information is inserted, and table column names are adjusted. This step is implemented in Java. | http://www.dita-ot.org/2.4/dev_ref/preprocess-debugfilter.html | ||
43 | DITA 1.2 support | DITA Open Toolkit 2.4 supports the DITA 1.2 specification. Initial support for this specification was added in version 1.5 of the toolkit; versions 1.5.1 and 1.5.2 contain minor modifications to keep up with the latest drafts. The specification itself was approved at approximately the same time as DITA-OT 1.5.2, which contained the final versions of the DTD and Schemas. DITA-OT 1.6 updated the DITA 1.2 XSDs to address minor errata in the standard; the DTDs remain up to date. | http://www.dita-ot.org/2.4/user-guide/DITA_v1-2-support.html | ||
44 | DITA 1.3 support | DITA Open Toolkit 2.4 provides processing support for the OASIS DITA 1.3 specification. Initial preview support for this specification was added in version 2.0 of the toolkit; version 2.2 extends this foundation to support key scopes and branch filtering along with additional DITA 1.3 features. | http://www.dita-ot.org/2.4/user-guide/DITA_v1-3-support.html | ||
45 | DITA and DITA-OT resources | In addition to the DITA Open Toolkit documentation, there are other resources about DITA and the DITA-OT that you might find helpful. | http://www.dita-ot.org/2.4/user-guide/dita-and-dita-ot-resources.html | ||
46 | DITA features in the documentation | The DITA Open Toolkit uses various recent DITA features in the project documentation. | http://www.dita-ot.org/2.4/user-guide/DITA-features-in-docs.html | ||
47 | DITA Open Toolkit 2.4 | The DITA Open Toolkit, or DITA-OT for short, is a set of Java-based, open-source tools that provide processing for XML content authored in the Darwin Information Typing Architecture. | http://www.dita-ot.org/2.4/index.html | ||
48 | DITA Open Toolkit 2.4.3 Release Notes | DITA Open Toolkit 2.4.3 is a maintenance release that fixes issues reported in DITA-OT 2.4, which includes Apache FOP 2.1, a new long-form syntax for dita command options, and additional code referencing extensions. | http://www.dita-ot.org/2.4/release-notes/index.html | ||
49 | DITA Open Toolkit Developer Reference | The Developer Reference is designed to provide more advanced information about the DITA-OT. It is geared to an audience that needs information about the DITA-OT architecture, extending the DITA-OT, and creating DITA-OT plug-ins. | http://www.dita-ot.org/2.4/dev_ref/index.html | ||
50 | DITA Open Toolkit License Information | DITA Open Toolkit is released under the Apache License, Version 2.0. | http://www.dita-ot.org/2.4/license/index.html | ||
51 | DITA Open Toolkit Parameter Reference | The Parameter Reference is designed to help users to locate information easily and quickly. It includes documentation for dita command arguments and options, DITA-OT parameters, and configuration properties. | http://www.dita-ot.org/2.4/parameters/index.html | ||
52 | DITA Open Toolkit User Guide | The User Guide is designed to provide basic information about using the DITA-OT. It is geared for an audience that needs information about running the toolkit, generating output, and troubleshooting builds. | http://www.dita-ot.org/2.4/user-guide/index.html | ||
53 | DITA specification support | DITA Open Toolkit 2.4 supports all versions of the OASIS DITA specification, including 1.0, 1.1, 1.2, and 1.3. | http://www.dita-ot.org/2.4/user-guide/DITA_spec-support.html | ||
54 | DITA to Eclipse help | The eclipsehelp transformation generates XHTML output, CSS files, and the control files that are needed for Eclipse help. | http://www.dita-ot.org/2.4/user-guide/dita2eclipsehelp.html | ||
55 | DITA to HTML Help (CHM) | The htmlhelp transformation generates HTML output, CSS files, and the control files that are needed to produce a Microsoft HTML Help file. | http://www.dita-ot.org/2.4/user-guide/dita2htmlhelp.html | ||
56 | DITA to HTML5 | The html5 transformation generates HTML5 output and a table of contents (TOC) file. | http://www.dita-ot.org/2.4/user-guide/dita2html5.html | ||
57 | DITA to Java Help | The javahelp transformation will generate Java Help output, along with the control files needed to compile the project. | http://www.dita-ot.org/2.4/user-guide/dita2javahelp.html | ||
58 | DITA to PDF (PDF2) | The pdf (or pdf2) transformation generates PDF output. | http://www.dita-ot.org/2.4/user-guide/dita2pdf.html | ||
59 | DITA to TocJS | The tocjs transformation generates XHTML output, a frameset, and a JavaScript-based table of contents with expandable and collapsible entries. The transformation was originally created by Shawn McKenzie as a plug-in and was added to the default distribution in DITA-OT release 1.5.4. | http://www.dita-ot.org/2.4/user-guide/dita2tocjs.html | ||
60 | DITA to troff | The troff transformation produces output for use with the troff viewer on Unix-style platforms, particularly for programs such as the man page viewer. | http://www.dita-ot.org/2.4/user-guide/dita2troff.html | ||
61 | DITA to XHTML | The xhtml transformation generates XHTML output and a table of contents (TOC) file. This was the first transformation created for the DITA Open Toolkit, and originally served as the basis for all HTML-based transformations. | http://www.dita-ot.org/2.4/user-guide/dita2xhtml.html | ||
62 | DITA-OT error messages | This topic lists each error message generated by the toolkit and provides additional information that might be helpful in understanding and resolving the error condition. If your toolkit installation includes custom plug-ins that define additional messages, you can add to this list by rebuilding the DITA-OT documentation. | http://www.dita-ot.org/2.4/user-guide/DITA-messages.html | ||
63 | DITA-OT parameters | Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Some parameters apply only to specific transformation types. These parameters can be passed as options to the dita command using the --parameter=value syntax or included in build scripts as Ant properties. | http://www.dita-ot.org/2.4/parameters/parameters_intro.html | ||
64 | DITA-OT transformations (output formats) | The DITA Open Toolkit ships with several core transformations that generate different output formats from DITA content. Each transformation represents an implementation of the processing that is defined by OASIS in the DITA specification. | http://www.dita-ot.org/2.4/user-guide/AvailableTransforms.html | ||
65 | Eclipse Help parameters | Certain parameters are specific to the Eclipse help transformation. | http://www.dita-ot.org/2.4/parameters/parameters-eclipsehelp.html | ||
66 | Eclipse help processing | The eclipsehelp transformation generates XHTML-based output and files that are needed to create an Eclipse Help system plug-in. Once the normal XHTML process has run, the dita.map.eclipse target is used to create a set of control files and navigation files. | http://www.dita-ot.org/2.4/dev_ref/XhtmlEclipse.html | ||
67 | Enabling debug mode | When the debug mode is enabled, additional diagnostic information is written to the log file. This information, which includes environment variables and stack trace data, can help you determine the root cause of a problem. | http://www.dita-ot.org/2.4/user-guide/enabling-debug-mode.html | ||
68 | Error messages and troubleshooting | This section contains information about problems that you might encounter and how to resolve them. | http://www.dita-ot.org/2.4/user-guide/troubleshooting-overview.html | ||
69 | Example plugin.xml file | The following is a sample of a plugin.xml file. This file adds support for a new set of specialized DTDs, and includes an override for the XHTML output processor. | http://www.dita-ot.org/2.4/dev_ref/plugin-sample.html | ||
70 | Example: Creating a simple PDF plug-in | This scenario walks through the process of creating a very simple plug-in (com.example.print-pdf) that creates a new transformation type: print-pdf. | http://www.dita-ot.org/2.4/dev_ref/pdf-customization-example.html | ||
71 | Extended code reference processing | DITA-OT provides additional code reference processing support beyond that which is mandated by the DITA specification. These extensions can be used to define character encodings or line ranges for use in code blocks. | http://www.dita-ot.org/2.4/user-guide/extended-functionality.html | ||
72 | Extending an XML catalog file | You can update either the main DITA-OT XML catalog or the XML catalog that is used by the PDF plug-in. This enables the DITA-OT to support new specializations and document-type shells. | http://www.dita-ot.org/2.4/dev_ref/plugin-xmlcatalog.html | ||
73 | Extending the DITA Open Toolkit | There are several methods that can be used to extend the toolkit; not all of them are recommended or supported. The best way to create most extensions is with a plug-in; extended documentation for creating plug-ins is provided in the next section. | http://www.dita-ot.org/2.4/dev_ref/extending-the-ot.html | ||
74 | Extension points | The DITA Open Toolkit provides a series of extension points that can be used to integrate changes into the core code. Extension points are defined in the plugin.xml file for each plug-in. When plug-ins are installed, the DITA-OT makes each extension visible to the rest of the toolkit. | http://www.dita-ot.org/2.4/extension-points/plugin-extension-points.html | ||
75 | Extension points by plug-in | The default plug-ins that ship with the DITA Open Toolkit include a series of extension points that can be used to modify various aspects of toolkit processing. | http://www.dita-ot.org/2.4/extension-points/extension-points-by-plugin.html | ||
76 | Extension points in org.dita.base | The org.dita.base plug-in provides common extension points that are available to extend processing in all transformations that are supported by the DITA Open Toolkit. | http://www.dita-ot.org/2.4/extension-points/extension-points-in-org.dita.base.html | ||
77 | Extension points in org.dita.eclipsehelp | Certain extension points are specific to the Eclipse Help transformation. | http://www.dita-ot.org/2.4/extension-points/extension-points-in-org.dita.eclipsehelp.html | ||
78 | Extension points in org.dita.html5 | In addition to the extension points provided by common processing and those shared by with other HTML-based transformations, theorg.dita.html5 plug-in provides extension points that are specific to the HTML5 transformation. | http://www.dita-ot.org/2.4/extension-points/extension-points-in-org.dita.html5.html | ||
79 | Extension points in org.dita.htmlhelp | Certain extension points are specific to the HTML Help transformation. | http://www.dita-ot.org/2.4/extension-points/extension-points-in-org.dita.htmlhelp.html | ||
80 | Extension points in org.dita.pdf2 | Certain extension points are specific to the PDF transformation (formerly known as “PDF2”). | http://www.dita-ot.org/2.4/extension-points/extension-points-in-org.dita.pdf2.html | ||
81 | Extension points in org.dita.troff | Certain extension points are specific to the troff transformation, which produces output for use with the troff viewer on Unix-style platforms, particularly for programs such as the man page viewer. | http://www.dita-ot.org/2.4/extension-points/extension-points-in-org.dita.troff.html | ||
82 | Extension points in org.dita.xhtml | The org.dita.xhtml plug-in provides shared extension points that can be used to modify processing in HTML-based transformation types such as Eclipse help, HTML Help, JavaHelp, TocJS, and XHTML. | http://www.dita-ot.org/2.4/extension-points/extension-points-in-org.dita.xhtml.html | ||
83 | Filter conditional content (profile) | The profile step removes content from topics and maps based on the rules in DITAVAL files or the @print attribute setting. Output can differ based on when filtering is done. | http://www.dita-ot.org/2.4/dev_ref/preprocess-profile.html | ||
84 | Flagging (flag-module) | Beginning with DITA-OT 1.7, flagging support is implemented as a common flag-module preprocessing step. The module evaluates the DITAVAL against all flagging attributes, and adds DITA-OT–specific hints to the topic when flags are active. Any extended transformation type may use these hints to support flagging without adding logic to interpret the DITAVAL. | http://www.dita-ot.org/2.4/dev_ref/preprocess-flagging.html | ||
85 | General extension points | These extension points enable you to extend the DITA-OT. You can add Ant targets or imports; add a Java library to the classpath parameter; add a new transformation type; extend a catalog file; add new diagnostic messages, and more. | http://www.dita-ot.org/2.4/extension-points/plugin-extension-points-general.html | ||
86 | Generate lists (gen-list) | The gen-list step examines the input files and creates lists of topics, images, document properties, or other content. These lists are used by later steps in the pipeline. This step is implemented in Java. | http://www.dita-ot.org/2.4/dev_ref/preprocess-genlist.html | ||
87 | generate.copy.outer parameter | Elaboration on how the generate.copy.outer parameter functions. | http://www.dita-ot.org/2.4/parameters/generate-copy-outer.html | ||
88 | Generating revision bars | If you use Antenna House Formatter or RenderX XEP, you can generate revision bars in your PDF output by using the @changebar attribute of the DITAVAL <revprop> element. | http://www.dita-ot.org/2.4/user-guide/pdf2-creating-change-bars.html | ||
89 | Getting Started with the DITA Open Toolkit | Getting Started provides a guided exploration of the DITA Open Toolkit. It is geared for an audience that has little or no knowledge of build scripts or DITA-OT parameters. It walks the novice user through installing the toolkit and building output. | http://www.dita-ot.org/2.4/getting-started/index.html | ||
90 | Globalization support offered by the DITA-OT | The DITA Open Toolkit offers globalization support in the following areas: Generated text, index sorting, and bi-directional text. | http://www.dita-ot.org/2.4/user-guide/globalization-supported-in-dita-ot.html | ||
91 | Globalizing DITA content | The DITA standard supports content that is written in or translated to any language. In general, the DITA Open Toolkit passes content through to the output format unchanged. The DITA-OT uses the values for the @xml:lang and @dir attributes that are set in the source content to provide globalization support. | http://www.dita-ot.org/2.4/user-guide/DITA-globalization.html | ||
92 | History of the PDF transformation | The DITA Open Toolkit PDF transformation was originally based on a third-party contribution by Idiom Technologies, and is commonly known as the “pdf2” plug-in. | http://www.dita-ot.org/2.4/dev_ref/pdf-transformation-history.html | ||
93 | HTML Help processing | The htmlhelp transformation creates HTML Help control files. If the build runs on a system that has the HTML Help compiler installed, the control files are compiled into a CHM file. | http://www.dita-ot.org/2.4/dev_ref/XhtmlCHM.html | ||
94 | HTML-based output parameters | Certain parameters apply to all the HTML-based transformation types: Eclipse help, HTML5, HTML Help, JavaHelp, TocJS, and XHTML. | http://www.dita-ot.org/2.4/parameters/parameters-base-html.html | ||
95 | HTML-based processing modules | The DITA-OT ships with several varieties of HTML output, each of which follows roughly the same path through the processing pipeline. All HTML-based transformation begin with the same call to the pre-processing module, after which they generate HTML files and then branch to create the transformation-specific navigation files. | http://www.dita-ot.org/2.4/dev_ref/XhtmlWithNavigation.html | ||
96 | HTML5 parameters | The HTML5 transformation shares common parameters with other HTML-based transformations and provides additional parameters that are specific to HTML5 output. | http://www.dita-ot.org/2.4/parameters/parameters-html5.html | ||
97 | HTML5 processing | After the HTML5 files are generated by the common routine, the dita.map.xhtml target is called by the html5 transformation. This target generates a TOC file called index.html, which can be loaded into a frameset. | http://www.dita-ot.org/2.4/dev_ref/html5.html | ||
98 | HTMLHelp parameters | Certain parameters are specific to the HTML Help transformation. | http://www.dita-ot.org/2.4/parameters/parameters-htmlhelp.html | ||
99 | Implementation-dependent features | For certain features, the DITA specification allows conforming processors to choose between different implementation alternatives. In these cases, there may be differences in behavior when DITA content is handled by different processors. DITA-OT supports implementation-specific features by applying one or more of the permissible processing approaches. | http://www.dita-ot.org/2.4/user-guide/implementation-dependent-features.html | ||
100 | Increasing Java memory allocation | If you are working with large documents with extensive metadata or key references, you will need to increase the memory allocation for the Java process. You can do this from the command-line prompt for a specific session, or you can increase the value of the ANT_OPTS environment variable. | http://www.dita-ot.org/2.4/user-guide/increasing-the-jvm.html | ||