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.
DITA content can be divided or merged into new output documents in different ways, depending on the value of
DITA-OT supports the following chunking methods:
When no chunk attribute values are given, no chunking is performed.
- When two tokens from the same category are used, no error or warning is thrown.
- When an unrecognized chunking method is used, no error or warning is thrown.
- When there are multiple
<revprop>elements with the same
@valattribute, no error or warning is thrown
- When multiple prop elements define a duplicate attribute and value combination, attribute default, or fall-back behavior, the DOTJ007E error is thrown.
The debug attributes are populated as follows:
- The XML trace filename is used to store the absolute system path of the original source document.
- The XML trace counter stores an element counter with the following format:
element-name ":" integer-counter ";" line-number ":" column-number
If both height and width attributes are given, the image is scaled non-uniformly.
If the scale attribute is not an unsigned integer, no error or warning is thrown during preprocessing.
<topicref> element that references a map contains child
<topicref> elements, the DOTX068W error is thrown and the child
<topicref> elements are ignored.
When the value of a hyperlink reference in the
@href attribute is not a valid URI reference,
the DOTJ054E error is thrown. Depending on the processing-mode setting, error recovery
may be attempted.
@copy-to attribute is specified on a
<topicref>, the content of
<shortdesc> element is not used to override the short description of the topic.
<coderef> elements are used within code blocks to reference external files with
literal code samples, the system default character set is used as the target file encoding unless a different
character set is explicitly defined via the mechanisms described under Character set definition.