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.
Each message ID is composed of a message prefix, a message number, and a letter that indicates the severity level (I, W, E, or F).
The toolkit uses the following severity scale:
- Info (I)
- Informational messages highlight the progress of transformation and call attention to conditions of which you should be aware. For example, draft comments are enabled and will be rendered in the output.
- Warning (W)
- The toolkit encountered a problem that should be corrected. Processing will continue, but the output might not be as expected.
- Error (E)
- The toolkit encountered a more severe problem, and the output is affected. For example, some content is missing or invalid, or the content is not rendered in the output
- Fatal (F)
- The toolkit encountered a severe condition, processing stopped, and no output is generated.
Plug-ins may be used to add additional messages to the toolkit; for more information, see Rebuilding the DITA-OT documentation.
| Message ID | Severity | Message text | Additional details |
|---|---|---|---|
| DOTA001F | Fatal | '%1' is not a recognized transformation type. Supported transformation types are dita, eclipsehelp, html5, htmlhelp, markdown, markdown_gitbook, markdown_github, pdf, pdf2, xhtml. | Default transformation types that ship with the toolkit include dita, eclipsehelp, html5, htmlhelp, markdown variants, pdf (or pdf2), and xhtml. Additional transformation types may be available if toolkit plug-ins are installed. |
| DOTA002F | Fatal | Input not specified, or specified using the wrong parameter. | The input parameter was not specified, so there is no DITA or DITAMAP file to transform. Ensure the parameter is set properly; see DITA-OT common parameters (args.input) if you are unsure how to specify the input file. |
| DOTA003F | Fatal | Cannot find the user-specified XSLT stylesheet '%1'. | An alternate stylesheet was specified to run in place of the default XSLT output process, but that stylesheet could not be loaded. Correct the parameter value to specify a valid stylesheet. |
| DOTA004F | Fatal | Invalid file name extension '%1'. The '.dita' and '.xml' file name extensions are supported for DITA topics. | This optional parameter is used to set an extension for DITA topic documents in the temporary processing directory. Only "dita", ".dita", "xml", or ".xml" are allowed. |
| DOTA006W | Warning | Absolute paths on the local file system are not supported for the CSSPATH parameter. Use a relative path or full URI instead. | If the CSSPATH uses an absolute
path, it should be one that can still be accessed after the files are moved to another system (such as
http://www.example.org/). Absolute paths on the local file system will be broken if the
content is moved to a new system. |
| DOTA007E | Error | Cannot find the running-footer file '%1'. Check the value to ensure it is specified correctly. | The running footer file, which contains content to be added to the bottom of each XHTML output topic, cannot be located or read. This is usually caused by a typo in the parameter value. You should also make sure the value is not specified with file: as a prefix. |
| DOTA008E | Error | Cannot find the running-header file '%1'. Check the value to ensure it is specified correctly. | The running header file, which contains content to be added to the top of each XHTML output topic, cannot be located or read. This is usually caused by a typo in the parameter value. You should also make sure the value is not specified with file: as a prefix. |
| DOTA009E | Error | Cannot find the specified heading file '%1'. Check the value to ensure it is specified correctly. | The running heading file, which
contains content to be added to the <head> section of each HTML output topic,
cannot be located or read. This is usually caused by a typo in the parameter value. You should also ensure
that the value is not specified with file: as a prefix. |
| DOTA011W | Warning | The '%1' argument is deprecated. This argument is no longer supported. | |
| DOTA012W | Warning | The '%1' argument is deprecated. Use the '%2' argument instead. | |
| DOTA013F | Fatal | Cannot find the specified DITAVAL file '%1'. | |
| DOTA014W | Warning | The @%1 attribute is deprecated. Use the @%2 attribute instead. | |
| DOTA015F | Fatal | The internal property '%1' may not be set directly. Use the '%2' property instead. | |
| DOTA066F | Fatal | Cannot find the user-specified XSLT stylesheet '%1'. | An alternate stylesheet was specified to run in place of the default XSL-FO output process, but that stylesheet could not be loaded. Correct the parameter value to specify a valid stylesheet. |
| DOTA067W | Warning | Ignoring <index-see> '%1' inside parent index entry '%2' because the parent term contains term children. | According to the OASIS DITA
Specification, the <index-see> element should be ignored if the parent
<indexterm> contains other <indexterm> children. |
| DOTA068W | Warning | Ignoring <index-see-also> '%1' inside parent index entry '%2' because the parent term contains term children. | According to the OASIS DITA
Specification, the <index-see-also> element should be ignored if the parent
<indexterm> contains other <indexterm> children. |
| DOTA069F | Fatal | The input resource '%1' cannot be located or read. Make sure '%1' exists and that you have permission to access it. | Make sure the input file path and file name were entered correctly. |
| DOTA069W | Warning | Target '%1' is deprecated. Remove references to this target from your custom XSLT or plug-ins. | |
| DOTJ005F | Fatal | Failed to create new instance for '%1'. Make sure '%1' exists and that you have permission to access it. | |
| DOTJ007E | Error | Duplicate condition in filter file for rule '%1'. Using the first condition found. | |
| DOTJ007I | Info | Duplicate condition in filter file for rule '%1'. Using the first condition found. | |
| DOTJ007W | Warning | Duplicate condition in filter file for rule '%1'. Using the first condition found. | |
| DOTJ009E | Error | Cannot overwrite the '%1' resource with '%2'. The modified result may not be available to the following transformation steps. Check if the resource is locked by some other application during the transformation process. | The transformation was unable to create certain files; results may not be as expected. |
| DOTJ012F | Fatal | Failed to parse the input resource '%1'. | This message may indicate an invalid input (such as a PDF accidentally specified as input rather than a DITA map file), an input file that uses elements that are not allowed, or a DITA file that has errors and cannot be parsed as XML. You could also be using a specialized DITA document type that needs external plug-ins to be parsed correctly. The message issued by the XML parser should provide additional information to help diagnose the cause. |
| DOTJ013E | Error | Failed to parse the referenced resource '%1'. | This message may indicate a reference to an invalid file (such as a PDF or unknown XML file referenced as if it was DITA), a file that uses elements that are not allowed, or a DITA file that has errors and cannot be parsed as XML. You could also be using a specialized DITA document type that needs external plug-ins to be parsed correctly. The message issued by the XML parser should provide additional information to help diagnose the cause. |
| DOTJ014W | Warning | Found an <indexterm> element with no content. Setting the term to '***'. | An empty
<indexterm> element was found, and will appear in the index as
***. This index term should be removed from the source. |
| DOTJ018I | Info | The '%1' log file was written to the '%2' directory. Any messages from the transformation process are available in the log; additional details about each message may be available in the documentation. | |
| DOTJ020W | Warning | The '%2' plug-in cannot be loaded because it requires at least one plug-in in '%1'. Make sure all prerequisite plug-ins are properly installed. | This message appears when one plug-in requires another to function correctly, but the required dependency is not found. The installed plug-in will be ignored. |
| DOTJ021E | Error | No output generated for '%1' because all content has been filtered out by DITAVAL 'exclude' conditions, or the resource is not valid DITA. Check the '%1' resource and the DITAVAL file to see if this is the intended result. | |
| DOTJ021W | Warning | No output generated for '%1' because all content has been filtered out by DITAVAL 'exclude' conditions, or the resource is not valid DITA. Check the '%1' resource and the DITAVAL file to see if this is the intended result. | This may appear if filter conditions on the root element of a topic cause the entire topic to be filtered out. To remove this message, move any filter conditions to the topic reference to prevent the build from accessing this resource. |
| DOTJ022F | Fatal | Failed to parse the input resource '%1' because all of its content has been filtered out. This can happen if the resource has filter conditions on the root element, and a DITAVAL file excludes all content based on those conditions. | To remove this message, update the filtering conditions in the input file or the DITAVAL file to permit access to the content, or move filter conditions to the topic reference to prevent the build from accessing this resource. |
| DOTJ023E | Error | The specified image file '%1' is not available. It is not included in the output. Make sure '%1' exists and that you have permission to access it. | Check whether the image exists in the source location or already exists in the output directory. |
| DOTJ025E | Error | The input to the 'topic merge' process cannot be found. Correct any earlier errors and try the build again, or see the documentation for additional details. | This message should only appear in
the following cases:
|
| DOTJ026E | Error | The 'topic merge' process did not generate any output. Correct any earlier errors and try the build again, or see the documentation for additional details. | This message should only appear if an Ant build or plug-in is directly calling the toolkit’s topic merge module, or if earlier errors resulted in problems with some of the content. If the topic merge module is called correctly, then this indicates a program error that should be reported to the DITA-OT development team via the GitHub issues tracker. |
| DOTJ028E | Error | No @format attribute was found on a reference to the '%1' resource, which does not appear to be DITA. If this is not a DITA resource, set the @format attribute to an appropriate value; otherwise set the @format attribute to 'dita'. | When referencing a non-DITA file,
the @format attribute should indicate the type of file referenced (such as
html for HTML topics or pdf for PDF files). Otherwise, the toolkit may
attempt to parse the referenced document as a DITA topic. |
| DOTJ029I | Info | No @domains attribute was found for the <%1> element. This generally indicates that the grammar files (such as DTDs or schemas) were not developed properly according to the DITA specification. | The @domains
attribute is used in specialized DITA documents to help determine which domain elements are legal. This
message will only appear if a DITA specialization was not defined properly. |
| DOTJ030I | Info | No @class attribute was found for the <%1> element. Processing as an unknown or non-DITA element. | All specialized DITA elements must
define a @class attribute to provide ancestry information. This message will only appear
if a specialized DITA element did not define a @class attribute, or if non-DITA elements
are included in a DITA context. |
| DOTJ031I | Info | No rule for '%1' was found in the DITAVAL file. Using the default action, or a parent prop action if specified. To remove this message, specify a rule for '%1' in the DITAVAL file. | This informational message is intended to help you catch filter conditions that may have been specified improperly; if the value is correct, no action is needed. |
| DOTJ033E | Error | No valid content found in the referenced resource '%1' during chunk processing. Specify an existing and valid topic for the topic reference. | |
| DOTJ034F | Fatal | Failed to parse the input resource '%1' (the content is not valid). If '%1' does not have a DOCTYPE declaration, make sure that all @class attributes are present. | DITA processing is based on
@class attributes defined for every element. Usually these are defaulted in the DTD or
schema; if no DTD or schema is used, the @class attributes must be explicitly included in
the map or topic. |
| DOTJ035F | Fatal | The '%1' resource is outside the scope of the input directory. To lower the severity level, use the Ant parameter 'outer.control', and set the value to 'warn' or 'quiet'. Otherwise, move the '%1' resource to the directory where the input map or topic is stored. | This message appears when a topic is outside the scope of the map; for example, if the main input map references "../other-directory/some.dita". The result would cause an output file to be created outside of the output directory. See DITA-OT common parameters (outer.control and generate.copy.outer) for details. |
| DOTJ036W | Warning | The '%1' resource is outside the scope of the input directory. | This message appears when a topic is outside the scope of the map; for example, if the main input map references "../other-directory/some.dita". The result would cause an output file to be created outside of the output directory. If you do not want to see the warning message, use the outer.control parameter and set the value to quiet. Otherwise, move the referenced file into the input directory. See DITA-OT common parameters (outer.control and generate.copy.outer) for details. |
| DOTJ037W | Warning | The XML schema and DTD validation function of the parser is turned off. For correct processing, make sure the input is normalized DITA with @class attributes included. | DITA processing is based on
@class attributes defined for every element. Usually these are defaulted in the DTD or
schema; if no DTD or schema is used, the @class attributes must be explicitly included in
the map or topic. |
| DOTJ038E | Error | The <%1> element is specialized from unrecognized metadata. Make sure that the <%1> element is specialized from an existing metadata element in the core DITA vocabulary. | This appears to indicate an error in creating specialized metadata elements. Check that the document type you are using is complete and complies with DITA specialization rules. |
| DOTJ039E | Error | There is no target specified for the conref push action 'pushafter'. Specify a @conref target and set the 'mark' @conaction on the element that precedes the current element. | See Conref Push in the DITA specification for details on expected syntax for this function. |
| DOTJ040E | Error | An element uses the conref push action 'pushreplace', but no @conref attribute is defined. Specify a @conref target with the ID of the content you want to replace. | See Conref Push in the DITA specification for details on expected syntax for this function. |
| DOTJ041E | Error | The @conref attribute value '%1' uses invalid syntax. The value must contain '#' followed by a topic or map ID, optionally followed by '/elemID' for a sub-topic element. | The @conref
attribute must be a URI reference to a DITA element. See
URI-based addressing in the DITA specification for details on the
expected syntax. |
| DOTJ042E | Error | Two elements both use conref push to replace the target '%1'. Delete one of the duplicate 'pushreplace' actions. | The conref push function was used
to replace a single element with two or more alternatives. Only one element may directly replace another
using conref push. For more information about the conref pushreplace action, see
The @conaction attribute in the DITA specification. |
| DOTJ043W | Warning | The conref push function is trying to replace an element <%1> that does not exist in the '%2' resource. Update the reference to refer to a valid target. | The target for a conref push action does not exist; make sure that the syntax is correct and that the target exists. See URI-based addressing in the DITA specification for details on the expected syntax. If the syntax is correct, it is possible that the target was filtered out of your build using a DITAVAL file. |
| DOTJ044W | Warning | There is a redundant conref push action 'pushbefore'. Make sure that 'mark' and 'pushbefore' occur in pairs. | For details on the expected
syntax for this function, see
The @conaction attribute in the DITA specification. |
| DOTJ045I | Info | The key '%1' is defined more than once in the same map. | This informational message is intended to help you catch catch duplicate key definitions; if the keys are defined as expected, no action is needed. |
| DOTJ046E | Error | The @conkeyref attribute value '%1' cannot be resolved because it does not contain a key or the key is not defined. Using the @conref attribute as fallback if it exists. | See the conkeyref definition for details on expected syntax and usage. |
| DOTJ047I | Info | Unable to find key definition for key reference '%1' in root scope. Using the @href attribute as fallback if it exists. | This message is intended to help you locate incorrectly specified keys; if the key was specified correctly, this message may be ignored. |
| DOTJ048I | Info | Unable to find key definition for key reference '%1' in scope '%2'. Using the @href attribute as fallback if it exists. | |
| DOTJ049W | Warning | The @%1 attribute value '%3' on the <%2> element does not comply with the specified subject scheme. According to the subject scheme map, the following values are valid for the @%1 attribute: '%4'. | A DITA Subject Scheme map was used to limit values that are available to the specified attribute. Correct the attribute value so that it uses one of the allowed values. |
| DOTJ050W | Warning | Found an <index-see> or <index-see-also> reference to the term '%1', but that term is not defined in the index. | The Eclipse index will contain a value such as "See also otherEntry", but otherEntry does not exist in this index. The index reference will be broken unless this plug-in is always loaded into Eclipse with another plug-in that defines otherEntry as an index term. |
| DOTJ051E | Error | Unable to load target for coderef '%1'. Make sure '%1' exists and that you have permission to access it. | The target for a
<coderef> element, which specifies an external text-based file, could not be
located or loaded. Make sure the reference is correct.
For security reasons, references to code samples outside of the scope of the map directory are not supported by default, as this could allow a reference to access and display any restricted or hidden file on the system. If you are certain that the path is valid and the file should be loaded, the current workaround is to set a parameter to allow these references. See DITA-OT common parameters (outer.control and generate.copy.outer) for details. |
| DOTJ052E | Error | Unsupported code reference charset '%1'. See the documentation for supported character set values on the @format attribute. | DITA-OT supports a special syntax
on <coderef> elements to specify the character set of the target document. See
Extended codeblock processing for details on the expected syntax. |
| DOTJ053W | Warning | The input resource '%1' is not a valid DITA filename. Check '%1' to see if it is correct. The '.dita' and '.xml' file name extensions are supported for DITA topics. | By default, DITA-OT supports the .dita and .xml file name extensions for DITA topics, as mandated by the DITA specification. Make sure your topics use one of these extensions, or configure the toolkit to allow additional extensions. |
| DOTJ054E | Error | Unable to parse invalid @%1 attribute value '%2'. | This message indicates that the
@href value specified in %1 does not use proper URI syntax. This may
occur when @href includes characters that should be escaped (such as the space character,
which should be %20 when in a URI). In strict processing mode this will cause a build
failure; in other processing modes the build will continue using the value in
%2. |
| DOTJ055E | Error | Invalid key name '%1'. Key names consist of URI characters and may not contain '{', '}', '[', ']', '/', '#', '?' or whitespace. | |
| DOTJ056E | Error | Invalid @xml:lang attribute value '%1'. Check the correct value for the target language. | |
| DOTJ057E | Error | The @id attribute value '%1' is not unique within the topic that contains it. | |
| DOTJ058E | Error | Both the @%1 and @%2 attributes are defined. A single element may not contain both generalized and specialized values for the same attribute. | |
| DOTJ059E | Error | Invalid key scope name '%1'. | |
| DOTJ060W | Warning | The '%1' key is used in a @conkeyref attribute but it is not bound to a DITA topic or map. Cannot resolve '%2' as a valid content key reference. | |
| DOTJ061E | Error | Topic reference target is a DITA map but the @format attribute has not been set. Set the @format attribute value to 'ditamap'. | |
| DOTJ062E | Error | Invalid @%1 attribute value '%2'. | |
| DOTJ063E | Error | The @cols attribute is set to '%1' but the number of <colspec> elements was '%2'. Check the number of columns in the table. | |
| DOTJ064W | Warning | The @chunk attribute uses both 'to-content' and 'by-topic' that conflict with each other. Ignoring the 'by-topic' token. | |
| DOTJ065I | Info | Branch filter generated topic '%1' is used more than once. Renaming '%1' to '%2'. | |
| DOTJ066E | Error | No @id attribute on topic type element '%1'. Using generated ID '%2'. | |
| DOTJ067E | Error | No @id attribute on topic type element '%1'. | |
| DOTJ068E | Error | Conref action 'mark' without conref target. | A conref mark
action has been used to mark a target element without a corresponding content reference target. This may
occur when the order of the marked element and the pushed element is reversed. |
| DOTJ069E | Error | Circular key definition '%1'. |
A circular reference was found in key definitions: a series of key references where the last key references the first. This may occur if a To resolve this issue, change the target of the |
| DOTJ070I | Info | An invalid @class attribute '%1' was found for the <%2> element. Processing as an unknown or non-DITA element. |
When a If this is a non-DITA element, it needs to be placed inside a |
| DOTJ071E | Error | Cannot find the specified DITAVAL file '%1'. | Make sure the DITAVAL file exists.
If more than one DITAVAL file is specified, ensure that the paths are delimited using the file path
separator character appropriate for your operating system (semicolon ‘;’ on Windows, or
colon ‘:’ on macOS or Linux). |
| DOTJ072E | Error | Email link without correct @format attribute. Using @format attribute value 'email'. | |
| DOTJ073E | Error | Email link without correct @scope attribute. Using @scope attribute value 'external'. | |
| DOTJ074W | Warning | The @rev attribute cannot be used with the <prop> filter. | |
| DOTJ075W | Warning | Absolute link '%1' without correct @scope attribute. Using @scope attribute value 'external'. | |
| DOTJ076W | Warning | Absolute link '%1' without correct @scope attribute. | |
| DOTJ077F | Fatal | Invalid @action attribute '%1' on DITAVAL property. | |
| DOTJ078F | Fatal | The input resource '%1' cannot be loaded. Make sure the grammar files (such as DTDs or schemas) for this document type are properly referenced and installed. | |
| DOTJ079E | Error | The '%1' resource cannot be loaded. Make sure the grammar files (such as DTDs or schemas) for this document type are properly referenced and installed. | |
| DOTJ080W | Warning | Integrator configuration '%1' has been deprecated. Use plug-in configuration '%1' instead. | |
| DOTJ081W | Warning | Ignoring empty @conref attribute. | |
| DOTJ082E | Error | Processing table cell failed. | |
| DOTJ083E | Error | The resource referenced as '%1' is capitalized differently on disk. | |
| DOTJ084E | Error | Cannot read '%1' with the '%2' character set. Save the file with '%2' encoding. | |
| DOTJ085E | Error | The '%1' parameter cannot be set with 'param' in project files. Use '%2' instead. | |
| DOTJ086W | Warning | Split @chunk attribute found on <%1> element that does not reference a topic. Ignoring chunk operation. | |
| DOTJ087W | Warning | Found @chunk attribute with value '%1' inside combine chunk. Ignoring chunk operation. | |
| DOTJ088E | Error | XML parsing error: %1 | |
| DOTX001W | Warning | No string named '%1' was found for language '%2'. Using the default language '%3'. Add a mapping between default language and desired language for the string '%1'. | This build uses generated text, such as the phrase “Related information” (which is generated above many link groups). The toolkit was unable to locate the string %1 for your specified language, so the text will appear in the default language. This generally indicates that the toolkit’s strings need to be updated to support your language, or that your language setting is incorrect. |
| DOTX002W | Warning | The @title attribute or element in the DITA map is required for Eclipse output. | The Eclipse help system requires a title in the project files generated from your map. Add a title to your input map to get valid Eclipse help output. |
| DOTX003I | Info | The @anchorref attribute should either reference another DITA map or an Eclipse XML TOC file. The value '%1' does not appear to reference either. | Eclipse uses anchor references to connect with other TOC files. For this to work in content generated from a DITA map, the anchorref element must reference either an existing Eclipse TOC XML file, or another DITA map (which will presumably also be converted to an Eclipse TOC). |
| DOTX004I | Info | Found a <navref> element that does not reference anything. The <navref> element should either reference another DITA map or an Eclipse XML TOC file. | Eclipse builds use DITA’s
<navref> element to pull in other Eclipse TOC files. The build found a
<navref> element that does not reference any other file; the element will be
ignored. |
| DOTX005E | Error | Unable to find navigation title for reference to '%1'. Using '%1' as the title in the Eclipse Table of Contents. | To remove this message, provide a navigation title for the referenced object in the map or topic, or make sure you are referencing a valid local DITA target. |
| DOTX006E | Error | Unknown file name extension in @href attribute value '%1'. References to non-DITA resources should set the @format attribute to match the resource (for example, 'txt', 'pdf', or 'html'). | Set the @format
attribute to identify the format of the file. If the reference is to a DITA document, make sure the
document uses a valid DITA extension. By default, DITA-OT supports the .dita and
.xml file name extensions for DITA topics, as mandated by the DITA
specification. |
| DOTX007I | Info | Only DITA topics, HTML files, and images may be included in the compiled CHM file. Ignoring reference to '%1'. To remove this message, set the @toc attribute to 'no' or the @processing-role attribute to 'resource-only' on the topic reference. | The HTML Help compiler will only include some types of information in the compiled CHM file; the current reference will not be included. |
| DOTX008E | Error | The resource '%1' cannot be loaded. Make sure '%1' exists and that you have permission to access it. | The name of the file in this message may have been changed to use a standard DITA topic file name extension (.dita or .xml) instead of the original extension used by the file; it may also include a path to the temporary directory rather than to the original. |
| DOTX008W | Warning | The resource '%1' cannot be loaded, and no navigation title is specified for the table of contents. | To fix the table of contents, specify a navigation title in your map or make sure the referenced file is local and can be accessed. The name of the file in this message may have been changed to use a standard DITA topic file name extension (.dita or .xml) instead of the original extension used by the file; it may also include a path to the temporary directory rather than to the original. |
| DOTX009W | Warning | Cannot retrieve a title from '%1'. Using '%2' instead. | No title was found in the specified topic, so the table of contents will use the indicated fallback value for this topic. |
| DOTX010E | Error | Unable to find the @conref target '%1'. Check '%1' to see if the target resource exists. | The @conref
attribute must be a URI reference to an existing DITA element. See
URI-based addressing in the DITA specification for details on the
expected syntax. The name of the file in this message may have been changed to
use a standard DITA topic file name extension (.dita or .xml)
instead of the original extension used by the file; it may also include a path to the temporary
directory rather than to the original.
If the target element exists in your source file, check to make sure it is not filtered out of the build with a DITAVAL file (which will remove the target before conref processing runs). This message may also appear if the path to either the source file or the content reference target exceeds the platform’s maximum path length in bytes. |
| DOTX011W | Warning | There is more than one possible target for the @conref attribute value '%1'. Using the first value found. Remove the duplicate ID in the referenced resource. | When pulling content with a
@conref attribute, you may only pull from a single element, but the target ID appears
twice in the referenced topic. The name of the file in this message may have been changed to
use a standard DITA topic file name extension (.dita or .xml)
instead of the original extension used by the file; it may also include a path to the temporary
directory rather than to the original. |
| DOTX012W | Warning | When you conref another topic or an item in another topic, the @domains attribute of the target topic must be equal to or a subset of the current topic's @domains attribute. Put the target under an appropriate domain. | This message is deprecated and should no longer appear in any logs. |
| DOTX013E | Error | An element with the @conref attribute set to '%1' indirectly includes itself, which results in an infinite loop. | This may appear if (for example)
you have a <ph> element that references another phrase, but that phrase itself
contains a reference to the original. The toolkit will stop following the conref trail when this is
detected; you will need to correct the reference in your source files. The name of the file in this message may have been changed to
use a standard DITA topic file name extension (.dita or .xml)
instead of the original extension used by the file; it may also include a path to the temporary
directory rather than to the original. |
| DOTX014E | Error | The @conref attribute value '%1' uses invalid syntax. Content references to a map element should contain '#' followed by an ID, such as 'mymap.ditamap#mytopicrefid'. | The @conref
attribute must be a URI reference to a DITA element. See
URI-based addressing in the DITA specification for details on the
expected syntax. |
| DOTX015E | Error | The @conref attribute value '%1' uses invalid syntax. The value must contain '#' followed by a topic or map ID, optionally followed by '/elemID' for a sub-topic element. | The @conref
attribute must be a URI reference to a DITA element. See
URI-based addressing in the DITA specification for details on the
expected syntax. The name of the file in this message may have been changed to
use a standard DITA topic file name extension (.dita or .xml)
instead of the original extension used by the file; it may also include a path to the temporary
directory rather than to the original. |
| DOTX016W | Warning | '%2' appears to reference a DITA document, but the @format attribute has inherited a value of '%1'. Processing as a non-DITA resource. To process as DITA, set the @format attribute to 'dita'. | This warning is intended to catch
instances where a non-DITA format setting unexpectedly cascades to a DITA topic, which will prevent the
topic from being processed. To remove this message, set the @format attribute directly on
the indicated reference. The name of the file in this message may have been changed to
use a standard DITA topic file name extension (.dita or .xml)
instead of the original extension used by the file; it may also include a path to the temporary
directory rather than to the original. |
| DOTX017E | Error | Found a link or cross reference with an empty @href attribute. Remove the empty @href attribute or provide a value. | Found a value such as
<xref href="">link text</xref>. The empty @href attribute value
is not serving a purpose and has caused problems with some tools in the past; you should remove the
attribute entirely or specify a value. |
| DOTX018I | Info | The @type attribute on a topicref was set to '%1', but the topicref references a more specific '%2' topic. Note that the @type attribute cascades in maps, so the value '%1' may come from an ancestor topicref. | The @type attribute
in DITA is intended to describe the type of the target; for example, a reference to a concept topic may
use type="concept". Generally, this attribute is optional, and the DITA-OT build will
automatically determine the value during processing. In this case, the @type attribute
lists a more general type than what is actually found. This is not an error, but links to this topic may
not be sorted as expected. |
| DOTX019W | Warning | The @type attribute on a topicref was set to '%1', but the topicref references a '%2' topic. This may cause links to sort incorrectly in the output. Note that the @type attribute cascades in maps, so the value '%1' may come from an ancestor topicref. | The @type attribute
in DITA is intended to describe the type of the target; for example, a reference to a concept topic may
use type="concept". Generally, this attribute is optional, and the DITA-OT build will
automatically determine the value during processing. In this case, the specified @type
value does not match the target, so links to this topic may not be sorted as expected. |
| DOTX020E | Error | Missing @navtitle attribute or element for peer topic '%1'. References must provide a navigation title when the target is not a local DITA resource. | DITA-OT is only able to dynamically retrieve titles when the target is a local (not peer or external) DITA resource. |
| DOTX021E | Error | Missing @navtitle attribute or element for non-DITA resource '%1'. References must provide a navigation title when the target is not a local DITA resource. | DITA-OT is only able to dynamically retrieve titles when the target is a local DITA resource. |
| DOTX022W | Warning | Unable to retrieve navtitle from target: '%1'. Using topicmeta linktext as the navigation title. | The build was unable to get a title
from the referenced topic; instead, a navigation title will be created based on the content of the
<linktext> element in <topicmeta>. |
| DOTX023W | Warning | Unable to retrieve navtitle from target: '%1'. | If the target is a local DITA
topic, make sure the reference is correct and the topic is available. Otherwise, provide a navigation
title, and ensure the @scope and @format attributes are set
appropriately. |
| DOTX024E | Error | Missing linktext and navtitle for peer topic '%1'. References must provide a navigation title when the target is not a local DITA resource. | DITA-OT can only retrieve titles and link text when the target is a local DITA resource (not a peer topic). |
| DOTX025E | Error | Missing linktext and navtitle for non-DITA resource '%1'. References must provide a navigation title when the target is not a local DITA resource. | DITA-OT can only retrieve titles and link text when the target is a local DITA resource (not peer or external). |
| DOTX026W | Warning | Unable to retrieve linktext from target: '%1'. Using navigation title as fallback. | The reference to this document did not specify any link text for generated map-based links; the navigation title will be used as fallback. |
| DOTX027W | Warning | Unable to retrieve linktext from target: '%1'. | The referenced file did not specify any link text for generated map-based links, and no fallback text could be located. Any links generated from this reference will have incorrect link text. |
| DOTX028E | Error | Link or cross reference must contain a valid @href or @keyref attribute; no link target is specified. | The link or cross reference has no target specified and will not generate a link. |
| DOTX029I | Info | The @type attribute on a <%1> element was set to '%3', but the reference is to a more specific '%4' '%2'. This may cause links to sort incorrectly in the output. | The @type attribute
in DITA is intended to describe the type of the target; for example, a reference to a concept topic may
use type="concept". Generally, this attribute is optional, and the DITA-OT build will
automatically determine the value during processing. In this case, the @type attribute
lists a more general type than what is actually found. This is not an error, but links to this topic may
not be sorted as expected. |
| DOTX030W | Warning | The @type attribute on a <%1> element was set to '%3', but the reference is to a '%4' '%2'. This may cause links to sort incorrectly in the output. | The @type attribute
in DITA is intended to describe the type of the target; for example, a reference to a concept topic may
use type="concept". Generally, this attribute is optional, and the DITA-OT build will
automatically determine the value during processing. In this case, the specified @type
value does not match the target, so links to this topic may not be sorted as expected. |
| DOTX031E | Error | The '%1' resource is not available to resolve link information. | The build attempted to access the specified file to retrieve a title or short description, but the file could not be found. If the file exists, it is possible that a DITAVAL file was used to remove the file’s contents from the build. Be aware that the path information above may not match the link in your topic. |
| DOTX032E | Error | Unable to retrieve link text from target: '%1'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference. | When a link or cross reference does
not have content, the build will attempt to pull the target’s title for use as link text. If the target is
unavailable, be sure to set the @scope attribute to an appropriate value. If the target
does not have a title (such as when linking to a paragraph), be sure to provide link text inside the cross
reference. |
| DOTX033E | Error | Unable to generate link text for a cross reference to a list item: '%1'. | An <xref>
element specifies type="li", which indicates a link to a list item, but the item number
could not be determined to use as link text. Specify link text inside the reference, or make sure you are
referencing an available list item. |
| DOTX034E | Error | Unable to generate link text for a cross reference to an unordered list item: '%1'. | The cross reference goes to a list item in an unordered list. The process could not automatically generate link text because the list item is not numbered. Provide link text within the cross reference. |
| DOTX035E | Error | Unable to generate the correct number for a cross reference to a footnote: '%1'. | An <xref>
element specifies type="fn", which indicates a link to a footnote, but the footnote
number could not be determined to use as link text. Specify link text inside the reference, or make sure
you are referencing an available footnote. |
| DOTX036E | Error | Unable to generate link text for a cross reference to a dlentry (the dlentry or term cannot be found): '%1'. | An <xref>
element specifies type="dlentry", which indicates a link to a definition list entry, but
the term could not be located to use as link text. Specify link text inside the reference, or make sure
you are referencing an available definition list entry. |
| DOTX037W | Warning | No title found for this document; using '***' as HTML page title. | No title was found for the current
document, so the HTML output file will set the <title> to ***.
This value generally appears in the title bar at the top of a browser. |
| DOTX038I | Info | Ignoring the @longdescref attribute on the <%1> element. Accessibility for object elements needs to be handled another way. | The <object>
element in HTML does not support @longdescref for accessibility. To make the object
accessible, you may need to add text before or after the element. You may also be able to handle it with a
<param> element inside the object. |
| DOTX039W | Warning | Required cleanup area found. To remove this message and hide the content, build without the DRAFT parameter. | This message is generated when creating draft output to help you locate all topics that need to be cleaned up; the cleanup items will appear in your output with styling that makes it stand out. The content will be hidden when the draft parameter is not active. |
| DOTX040I | Info | Draft comment area found. To remove this message and hide the comments, build without the DRAFT parameter. | This message is generated when creating draft output to help you locate all topics that have draft comments. Each comment will appear in your HTML output; the comments will be hidden when the draft parameter is not active. |
| DOTX041W | Warning | Found more than one <title> element in a <%1> element. Using the first one as the element title. | Because of the way XML and DITA are defined, it is generally not possible to prohibit adding a second title to a section during editing (or to force that title to come first). However, the DITA specification states that only one title should be used in a section. When multiple titles are found, only the first one will appear in the output. |
| DOTX042I | Info | DITAVAL-based flagging is not currently supported for inline phrases in XHTML; ignoring flag value on '%1' attribute. | If it is important to flag this piece of information, try placing a flag on the block element that contains your phrase. If you just want to have an image next to the phrase, you may place an image directly into the document. |
| DOTX043I | Info | The link to '%1' may appear more than once in '%2'. | DITA-OT is able to remove duplicate
links in most cases. However, if two links to the same resource use different attributes or link text, it
is possible for them to appear together. For example, if the same link shows up with
role="next" and again with no specified role, it may show up as both the “Next
topic” link and as a related link. Note that links generated from a
<reltable> in a DITA map will have the @role attribute set to
friend.
|
| DOTX044E | Error | The <area> element in an image map does not specify a link target. Add an <xref> element with a link target to the <area> element. | The <area>
element in an image map must provide a link target for the specified area. Add an
<xref> element as a child of <area> and make sure it
specifies a link target.
|
| DOTX045W | Warning | The <area> element in an image map should specify link text for better accessibility. Link text should be specified directly when the target is not a local DITA resource. | Cross reference text inside the
<area> element is used to provide accessibility for screen readers that can
identify different areas of an image map. If text cannot be retrieved automatically by referencing a DITA
element, it should be specified directly in the cross reference. |
| DOTX046W | Warning | Area shape should be one of: default, rect, circle, poly, or blank (no value). The value '%1' is not recognized. | The specified value was passed
as-is through to the <area> element in the HTML. |
| DOTX047W | Warning | Area coordinates are blank. Coordinate points for the shape need to be specified. | The <area>
element is intended to define a region in an image map; coordinates must be specified to define that
region. |
| DOTX048I | Info | To include the peer or external topic '%1' in your help file, you may need to recompile the CHM file after making the resource available. | The build will not look for peer or
external topics before compiling your CHM file, so they may not be included. If you are referencing an
actual HTML file that will not be available, it cannot be included in the project, and you should set the
@toc attribute to no on the <topicref> element.
Otherwise, make sure the HTML file was included in the CHM; if it was not, you will need to place it in
the correct location with your other output files and recompile.
|
| DOTX049I | Info | References to non-DITA files are ignored by the PDF, ODT, and RTF transformations. | The PDF, ODT, and RTF output processes cannot automatically convert non-DITA content into DITA to merge it with the rest of your content. The referenced items are ignored. |
| DOTX050W | Warning | The default ID 'org.sample.help.doc' is used for the Eclipse plug-in. To use your own plug-in ID, specify it using the @id attribute on the map. | Eclipse requires that an ID be specified when creating an Eclipse Help project; the toolkit expects to locate that ID on the root element of your input map. |
| DOTX052W | Warning | No string named '%1' was found when creating generated text; using the value '%1' in the output. | The toolkit is attempting to add generated text, such as the string “Related information” that appears above links. The requested string could not be found in any language. Your output may contain a meaningful string, or it may contain a code that was intended to map to a string. This likely indicates an error in a plug-in or XSL override; either the string was requested incorrectly, or you will need to provide a mapping for the string in all of the languages you require. |
| DOTX053E | Error | A element that references another map indirectly includes itself, which results in an infinite loop. The original map reference is to '%1'. | This will occur if a map references another map, and then that second map (or another further nested map) references the original map. Correct the chain of map references to remove circular references. |
| DOTX054W | Warning | Conflict text style is applied on the current element based on DITAVAL flagging rules. Check the DITAVAL and DITA source files to make sure there is no style conflict on the element that needs to be flagged. | This will occur when a DITAVAL file contains multiple styling rules that apply to the same element. |
| DOTX055W | Warning | A customized stylesheet uses the deprecated 'flagit' template. Conditional processing is no longer supported using this template. Update the stylesheet to use the 'start-flagit' template instead of the 'flagit' template. | The flagit named
template was deprecated in DITA-OT version 1.4, when the OASIS standard formalized the DITAVAL syntax. The
template was removed in DITA-OT 1.6. Any stylesheets that use this template must be updated. |
| DOTX056W | Warning | The '%1' resource is not available to resolve link information. | The build attempted to access the specified file to retrieve a title or short description, but the file could not be found. If the file exists, it is possible that a DITAVAL file was used to remove the file’s contents from the build. Another possibility is that the file is located outside of the scope of the main input directory, and was not available because the onlytopic.in.map parameter was specified. Be aware that the path information above may not match the link in your topic. |
| DOTX057W | Warning | The link or cross reference target '%1' cannot be found, which may cause errors in the output. | The link appears to use valid syntax to reference a DITA element, but that element cannot be found. Check that the element exists, and is not removed from the build by DITAVAL filtering. |
| DOTX058W | Warning | No glossary entry found for the '%1' key on the <%2> element. Check display text and hover text for terms and abbreviations. | Processing for terms, acronyms, or
abbreviated forms associates the key from the element’s @keyref attribute with a glossary
entry topic. This message appears if the key is defined, but not associated with a
<glossentry> element. The process will try to use the best available fallback
(usually the title of the referenced topic). |
| DOTX060W | Warning | The '%1' key is used in an <abbreviated-form> element, but the key is not associated with a glossary entry. Abbreviated-form should ONLY be used to reference a glossary entry. | Processing for abbreviated form
elements associates the key from the element’s @keyref attribute with a glossary entry
topic. This message appears if the key is defined, but not associated with a
<glossentry> element. This element is only supported with keys that are
associated with glossary topics; the element will not generate any output. Correct the reference, or use a
different element to reference your topic. |
| DOTX061W | Warning | The @href attribute value '%1' contains a fragment identifier, but it does not reference a topic element. The @href attribute on a <topicref> element should only reference topic-level elements. | According to the DITA
specification, references from maps should either point to DITA maps, DITA topics, or non-DITA resources.
References below the topic level should only be made via <xref> cross references
within topics. For details, see the @href attribute description in the
topicref element definition. |
| DOTX062I | Info | It appears that this document uses constraints, but the conref processor cannot validate that the target of a conref is valid. To enable constraint checking, upgrade to an XSLT 2.0 processor. | |
| DOTX063W | Warning | The DITA document '%1' is linked to from the content, but not referenced by a <topicref> element in the map. Include the topic in the map to avoid a broken link. | This message appears when generating PDF or ODT output that includes a link to a local topic, but the referenced topic is not part of the map itself. This will result in a broken link. You should include the topic in your map or remove the link from the build. |
| DOTX064W | Warning | The @copy-to attribute value '%1' uses the name of a resource that already exists, so this attribute is ignored. | Make sure that all
@copy-to attributes define unique names. |
| DOTX065W | Warning | Two unique source files each specify a @copy-to attribute value '%2', which results in a collision. Ignoring the @copy-to value associated with the @href value '%1'. | Two different topics are copied to
the same location using @copy-to attributes. To prevent data loss, only the first instance
will be applied. To create multiple copies, make sure that all @copy-to attributes define
unique names. |
| DOTX066W | Warning | The '%1' template is deprecated. Remove references to this template from the custom XSLT or plug-ins. | This message indicates that your custom XSLT or plug-ins rely on templates that will be removed in an upcoming release. Typically this occurs when a named template has been converted to a mode template; any code that uses the deprecated template should be updated. |
| DOTX067E | Error | No string named '%1' was found for language '%2'. Add a mapping for the string '%1'. | This PDF build uses generated text, such as the phrase “Related information” (which is generated above many link groups). The toolkit was unable to locate the string %1 for your specified language, so the text will appear in the default language. This generally indicates that the toolkit’s strings need to be updated to support your language, or that your language setting is incorrect. |
| DOTX068W | Warning | A <topicref> element that references a map contains child <topicref> elements. Ignoring child topic references. | |
| DOTX069W | Warning | The '%1' template mode is deprecated. Remove references to this template mode from custom XSLT or plug-ins. | |
| DOTX070W | Warning | The '%1' target is deprecated. Remove references to this target from custom Ant files. | |
| DOTX071E | Error | Unable to find conref range end element with ID '%1'. | |
| DOTX071W | Warning | The '%1' parameter on the '%2' template is deprecated. Use the '%3' parameter instead. | |
| DOTX072I | Info | Ignoring navtitle within topicgroup. | |
| DOTX073I | Info | Removing broken link to '%1'. | |
| DOTX074W | Warning | No formatting defined for unknown @class attribute value '%1'. | |
| DOTX075W | Warning | A content reference in a constrained document type is pulling content from an unconstrained document type. Resolving this reference may result in content that violates one of the document constraints in '%1'. | |
| DOTX076E | Error | A content reference in a constrained document type cannot be resolved because it would violate one of the document constraints '%1'. The current constrained document may only reuse content from documents with equivalent constraints. | |
| DOTX077I | Info | Resolving content references results in duplicate ID '%1'. Rewriting resolved version to '%2'. | |
| INDX001I | Info | Index entry '%1' will be sorted under the "Special characters" heading. | |
| INDX002E | Error | The PDF indexing process could not find the proper sort location for '%1', so the term has been dropped from the index. | |
| INDX003E | Error | The build failed due to problems encountered when sorting the PDF index. | |
| PDFJ001E | Error | The PDF indexing process cannot find the proper sort location for '%1', so the term has been dropped from the index. | |
| PDFJ002E | Error | The build failed due to problems encountered when sorting the PDF index. Address any messages located earlier in the log. | The PDF index process relies on pre-defined letter headings when sorting terms. The specified term does not begin with a character that can be mapped to an existing heading. Typically this term would be placed in a “Special characters” group, but the current language did not specify such a group when setting up the index sort process. |
| PDFJ003I | Info | Index entry '%1' will be sorted under the 'Special characters' heading. | The PDF index process relies on pre-defined letter headings when sorting terms. The specified term does not begin with a character that can be mapped to an existing heading, so it has been placed under a heading for terms that begin with special characters such as punctuation. If this term should be sorted under a new or existing letter heading, open an issue in the DITA-OT GitHub issues tracker to correct the sort. |
| PDFX001W | Warning | An index term range is specified with a @start attribute value of '%1', but there is no matching @end attribute. To end the range, add an index term in a valid location with the @end attribute set to '%1'. | |
| PDFX002W | Warning | There are multiple index terms specified with a @start attribute value of '%1', but there is only one term to end this range, or the ranges for this term overlap. Make sure that each term with this start value has a matching end value, and that the specified ranges for this value do not overlap. | |
| PDFX003W | Warning | Multiple index entries close the index range '%1'. Make sure that each index term with a @start attribute value of '%1' has only one matching term with a corresponding @end attribute value. | |
| PDFX004F | Error | Found a topic reference with an empty @href attribute value. Please specify a target or remove the @href attribute. | |
| PDFX005F | Error | The '%1' topic reference cannot be found. Please correct the @href attribute value, or set the @scope or @format attribute if the target is not a local DITA topic. | |
| PDFX007W | Warning | Found an index term with @end attribute value '%1', but no start term was found for this entry. | |
| PDFX008W | Warning | Font definition not found for the logical name or alias '%1'. | |
| PDFX009E | Error | Attribute set reflection cannot handle the XSLT element <%1>. | |
| PDFX011E | Error | The index term '%2' uses both an <index-see> element and an <%1> element. Convert the <index-see> element to <index-see-also>. | Found an
<index-see> element as a child of a term that also exists as a standalone index
term, or as a term that also uses <index-see-also>. When using
<index-see> with an index term, that term should not be used to create page
references and should not reference additional terms. Treating the <index-see> as
<index-see-also>. |
| PDFX012E | Error | Found a table row with more entries than allowed. Check the number of columns in the table. | |
| PDFX013F | Fatal | The PDF file '%1' cannot be generated. | |
| XEPJ001W | Warning | %1 | |
| XEPJ002E | Error | %1 | |
| XEPJ003E | Error | %1 |