The configuration.properties file
The configuration.properties file controls certain common properties, as well as some properties that control PDF processing.
The contents of the config/configuration.properties file are added to the DITA-OT
configuration in the
dost-configuration.jar file when the plug-in integration process runs. The
following properties are typically set in this file:
Specifies the processing default value for the DITA 1.3
@cascadeattribute, which determines how map-level metadata attributes are applied to the children of elements where the attributes are specified. DITA-OT uses the merge value by default for backwards compatibility with DITA 1.2 and earlier.Warning: This property can only be set in configuration.properties and should not be modified.
This setting specifies the name of the Java class that defines how the source URL of a topic is mapped to the URL of the temporary file name. The current default method uses a 1:1 mapping, though future implementations may use alternative approaches such as hashes or full absolute paths as file names.Warning: This property can only be set in configuration.properties and should not be modified.
Specifies whether the dita command prints colored output on the command line console. When set to true, error messages in dita command output will appear in red on terminals that support ANSI escape codes, such as on Linux or macOS. Set to false to disable the color. (Colored output is not supported on Windows consoles such as cmd.exe or PowerShell).
- A semicolon-separated list of directory paths that DITA-OT searches for plug-ins to install; any relative paths are resolved against the DITA-OT base directory. Any immediate subdirectory that contains a plugin.xml file is installed.
- A semicolon-separated list of directory names to be ignored during plug-in installation; any relative paths are resolved against the DITA-OT base directory.
- Defines the order in which plug-ins are processed. In XML catalog files, the order of imports is significant. If multiple plug-ins define the same thing (differently), the first catalog entry “wins”. DITA-OT uses this property to define the order in which catalog entries are written. This mechanism is currently used to ensure that DITA 1.3 grammar files take precedence over their DITA 1.2 equivalents.
- Defines the list (and order) of plug-in repositories that are searched for available plug-ins during the
installation process. In addition to the main plug-in registry at
dita-ot.org/plugins, you can create a registry of your own to store the custom plug-ins
for your company or organization. To add a new entry, append the URL for your custom registry directory to
registrykey value, separating each entry with a space. For more information, see Adding plug-ins via the registry.
Enables internationalization (I18N) font processing to provide per-character font selection for FO renderers that do not support the
font-selection-strategyproperty (such as Apache FOP).
When this feature is enabled, DITA-OT uses a font mapping process that takes the content language into consideration. The mapping process uses configuration files for each language to define characters that should be rendered with certain logical fonts, and font mappings that associate each logical font to physical font files.
The following values are allowed:
Tip: If you don’t use custom character mappings, turning off font mapping makes it easier to define custom fonts simply by changing font names in the XSL attributes files of your custom PDF plug-in. For details, see Font configuration in PDF2.
- true (default) — Enables font mapping
- false — Disables font mapping
- As of DITA-OT 3.3, the default character set for code references can be changed by specifying one of the character set values supported by the Java Charset class.