Edit online

This list includes the most common customization parameters that are available in the DITA Map PDF - based on HTML5 & CSS transformation scenario. Other standard DITA-OT parameters were omitted for clarity, but they are still supported.

args.css You can use this to specify a list of CSS URLs to be used in addition to those specified in the dita.css.list parameter or publishing template. The files must have URL syntax and be separated using semicolons.
args.css.param.* You can use this parameter pattern to set attributes on the root of the merged map. This means you can activate specific CSS rules from your custom CSS using custom attributes. For examples, see: Styling Through Custom Parameters.
args.css.param.numbering You can use this parameter to change the numbering of the chapters and sections. Allowed values:
  • shallow - Only the topics from the first level will be numbered (chapters).
  • deep - All the topics from the map will be numbered (chapters and sections).
  • deep-chapter-scope - Similar to deep, but in addition, the page numbers, figures, and table numbers are reset at the start of each chapter. The table and figure titles (and the links to them) are prefixed with the chapter numbers. The generic cross reference links contain both the chapter numbers and the page numbers to avoid ambiguity. This parameter value is only available for the DITA Map PDF - based on HTML5 & CSS transformation scenario.
  • deep-chapter-scope-no-page-reset - Similar to deep-chapter-scope, but the page numbers do not reset at the start of each chapter. The generic cross reference links contain only the page number. This parameter value is only available for the DITA Map PDF - based on HTML5 & CSS transformation scenario.

For more details, see Numbering Types.

args.draft

Specifies whether or not the content of <draft-comment> and <required-cleanup> elements is included in the output.

Allowed values:
  • no - No draft information is shown in the output. This is the default.
  • yes - The draft information is shown in the output.
args.figurelink.style
Specifies how cross references to figures are styled in output. Allowed values:
  • NUMBER - Only the number of the figures will be shown in links.
  • TITLE - Only the title of the figures will be shown in links.
  • NUMTITLE (default) - Both the title and number of the figures will be shown in links.
args.chapter.layout

Specifies whether chapter level TOCs are generated for bookmaps. When set to MINITOC, a small section with links is added at the beginning of each chapter. The default is BASIC. For details, see: Table of Contents for Chapters (Mini TOC).

Allowed values:

  • BASIC - No chapter TOC is created.
  • MINITOC - A chapter level TOC will be generated.
args.gen.task.lbl

Specifies whether or not to generate headings for sections within task topics. Allowed values: YES or NO (default). When set to yes, headings like "About this task", "Procedure", or "What to do next", are shown in the task contents.

args.input Specifies the master DITA map file for your documentation project.
args.output.base Specifies the name of the output file without a file extension. By default, the name of the PDF file is derived from the name of the DITA map file. This parameter allows you to override it.
args.tablelink.style
Specifies how cross references to tables are styled in output. Allowed values:
  • NUMBER - Only the number of the tables will be shown in links.
  • TITLE - Only the title of the tables will be shown in links.
  • NUMTITLE (default) - Both the title and number of the tables will be shown in links.
clean.temp Specifies whether the DITA-OT deletes the files in the temporary directory after it finishes a build. Allowed values: yes (default) / no
css.processor.path.antenna-house Path to the Antenna House executable file that needs to be run to generate the PDF (for example, C:\path\to\AHFCmd.exe on Windows).
css.processor.path.chemistry Path to the Oxygen PDF Chemistry executable file that needs to be run to generate the PDF (for example, C:\path\to\chemistry.bat on Windows). If this parameter is not set, the plugin will use the system's PATH environment variable to locate and start Oxygen PDF Chemistry.
css.processor.path.prince Path to the Prince executable file that needs to be run to generate the PDF (for example, C:\path\to\prince.exe on Windows).
css.processor.type Specifies the processor to use for the transformation. Allowed values: chemistry (default) / antenna-house / prince.
default.language Specifies the default language for source documents. Examples: fr, de, zh, etc. Depending on the transformation type, the actual number of supported languages can vary, see: Localization.
editlink.remote.ditamap.url Use this parameter in conjunction with editlink.web.author.url to add an Edit link next to the topic title in the PDF output. When a user clicks the link, the topic is opened in Oxygen XML Web Author where they can make changes that can be saved to a file server. The value should be set as the custom URL of the main DITA map. For example, a GitHub custom URL might look like this: https://getFileContent/oxyengxml/userguide/master/UserGuide.ditamap.
editlink.web.author.url This parameter needs to be used in conjunction with editlink.remote.ditamap.url to add an Edit link next to the topic title in the PDF output. When a user clicks the link, the topic is opened in Oxygen XML Web Author where they can make changes that can be saved to a file server. The value should be set as the URL of the Web Author installation. For example: https://www.oxygenxml.com/oxygen-xml-web-author/.
figure.title.placement Controls the title placement of the figures, relative to the image. Possible values include top (default) and bottom.
generate.named.destinations When set to yes (default), the @id attributes from the DITA content are used as PDF named destinations
hide.frontpage.toc.index.glossary When set to yes, the generated structures (table of contents, index list, front page, etc.) are removed from the output. The default is no.
show.changes.and.comments

When set to yes, the user comments, colored highlights and track-changes are shown in the output.

show.changes.and.comments.as.pdf.sticky.notes When set to yes (default) and the show.changes.and.comments parameter is also set to yes, the user comments and tracked changes are shown in the PDF output as stick note annotations. When set to no, the comments and tracked changes are left in the document model and are styled by the default CSS rules as footnotes. You can override this from your customization CSS.
The following parameters can be used to specify a publishing template:
pdf.publishing.template Specifies the path to the folder containing the custom PDF template.
pdf.publishing.template.descriptor Specifies the name of the descriptor to be loaded from the PDF template folder or package. If it is not specified, the first encountered descriptor will be loaded.