410 lines
No EOL
132 KiB
HTML
410 lines
No EOL
132 KiB
HTML
<!DOCTYPE html
|
||
SYSTEM "about:legacy-compat">
|
||
<html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2020"><meta name="generator" content="DITA-OT"><meta name="description" content="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."><meta name="keywords" content="error messages"><link rel="stylesheet" type="text/css" href="../css/commonltr.css"><link rel="stylesheet" type="text/css" href="../css/dita-ot-doc.css"><title>DITA-OT error messages</title></head><body id="msgs"><header role="banner"><div class="header">
|
||
<p>DITA Open Toolkit</p>
|
||
<hr>
|
||
</div></header><nav role="toc"><ul><li><a href="../index.html">DITA Open Toolkit 3.6</a></li><li><a href="../release-notes/index.html">Release Notes</a></li><li><a href="../topics/installing-client.html">Installing DITA-OT</a></li><li><a href="../topics/building-output.html">Building output</a></li><li><a href="../topics/input-formats.html">Authoring formats</a></li><li><a href="../topics/output-formats.html">Output formats</a></li><li><a href="../parameters/index.html">Parameters</a></li><li><a href="../topics/html-customization.html">Customizing HTML</a></li><li><a href="../topics/pdf-customization.html">Customizing PDF</a></li><li><a href="../topics/adding-plugins.html">Adding plug-ins</a></li><li><a href="../topics/custom-plugins.html">Creating plug-ins</a></li><li><a href="../topics/troubleshooting-overview.html">Troubleshooting</a><ul><li><a href="../topics/logging.html">Logging</a></li><li><a href="../topics/enabling-debug-mode.html">Enabling debug mode</a></li><li class="active"><a href="../topics/error-messages.html">DITA-OT error messages</a></li><li><a href="../topics/other-errors.html">Other error messages</a></li><li><a href="../topics/dita-command-help.html">Command line help</a></li><li><a href="../topics/increasing-the-jvm.html">Increasing Java memory</a></li><li><a href="../topics/reducing-processing-time.html">Speeding up builds</a></li></ul></li><li><a href="../reference/index.html">Reference</a></li><li><a href="../topics/dita-and-dita-ot-resources.html">Resources</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="msgs__title"><h1 class="title topictitle1" id="msgs__title">DITA-OT error messages</h1><div class="body refbody"><p class="shortdesc">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.</p><section class="section" id="msgs__overview">
|
||
<p class="p">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). </p>
|
||
<p class="p">The toolkit uses the following severity scale:</p>
|
||
<dl class="dl" id="msgs__severity-levels">
|
||
|
||
<dt class="dt dlterm">Info (I)</dt>
|
||
<dd class="dd">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.</dd>
|
||
|
||
|
||
<dt class="dt dlterm">Warning (W)</dt>
|
||
<dd class="dd">The toolkit encountered a problem that should be corrected. Processing will continue, but the output might
|
||
not be as expected.</dd>
|
||
|
||
|
||
<dt class="dt dlterm">Error (E)</dt>
|
||
<dd class="dd">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</dd>
|
||
|
||
|
||
<dt class="dt dlterm">Fatal (F)</dt>
|
||
<dd class="dd">The toolkit encountered a severe condition, processing stopped, and no output is generated.</dd>
|
||
|
||
</dl>
|
||
<p class="p">Plug-ins may be used to add additional messages to the toolkit; for more information, see
|
||
<a class="xref" href="rebuilding-docs.html" title="When you add or remove plug-ins, you can rebuild the documentation to update the information on the extension points, messages, and parameters that are available in your environment.">Rebuilding the DITA-OT documentation</a>.</p>
|
||
</section><table class="simpletable"><colgroup><col style="width:15%"><col style="width:15%"><col style="width:30%"><col style="width:40%"></colgroup><thead><tr class="sthead"><th class="stentry" scope="col" id="msgs__stentry__1">Message ID</th><th class="stentry" scope="col" id="msgs__stentry__2">Severity</th><th class="stentry" scope="col" id="msgs__stentry__3">Message text</th><th class="stentry" scope="col" id="msgs__stentry__4">Additional details</th></tr></thead><tbody><tr class="strow" id="msgs__DOTA001F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA001F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">"<var class="keyword varname">%1</var>" is not a recognized transformation type. Supported transformation types are dita, eclipsehelp, html5, htmlhelp, markdown, markdown_gitbook, markdown_github, pdf, pdf2, xhtml.</td><td class="stentry" id="msgs__DOTA001F-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTA002F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA002F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Input file is not specified, or is specified using the wrong parameter. </td><td class="stentry" id="msgs__DOTA002F-extra" headers="msgs__stentry__4">The input parameter was not
|
||
specified, so there is no DITA or DITAMAP file to transform. Ensure the parameter is set properly; see
|
||
<a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">DITA-OT common parameters (args.input)</a> if you are unsure how to specify
|
||
the input file.
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTA003F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA003F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Cannot find the user specified XSLT stylesheet '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTA003F-extra" headers="msgs__stentry__4">An alternate stylesheet was specified
|
||
to run in place of the default XSLT output process, but that stylesheet could not be loaded. Please correct
|
||
the parameter to specify a valid stylesheet.
|
||
</td></tr><tr class="strow" id="msgs__DOTA004F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA004F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Invalid DITA topic extension '<var class="keyword varname">%1</var>'. Supported values are '.dita' and '.xml'.</td><td class="stentry" id="msgs__DOTA004F-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTA006W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA006W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Absolute paths on the local file system are not supported for the CSSPATH parameter. Please use a relative path or full URI instead.</td><td class="stentry" id="msgs__DOTA006W-extra" headers="msgs__stentry__4">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
|
||
<code class="ph codeph">http://www.example.org/</code>). Absolute paths on the local file system will be broken if the
|
||
content is moved to a new system.</td></tr><tr class="strow" id="msgs__DOTA007E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA007E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Cannot find the running-footer file "<var class="keyword varname">%1</var>". Please double check the value to ensure it is specified correctly.</td><td class="stentry" id="msgs__DOTA007E-extra" headers="msgs__stentry__4">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 ensure that the value is not specified with
|
||
"file:" as a prefix.</td></tr><tr class="strow" id="msgs__DOTA008E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA008E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Cannot find the running-header file "<var class="keyword varname">%1</var>". Please double check the value to ensure it is specified correctly.</td><td class="stentry" id="msgs__DOTA008E-extra" headers="msgs__stentry__4">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 ensure that the value is not specified with "file:"
|
||
as a prefix.</td></tr><tr class="strow" id="msgs__DOTA009E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA009E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Cannot find the specified heading file "<var class="keyword varname">%1</var>". Please double check the value to ensure it is specified correctly.</td><td class="stentry" id="msgs__DOTA009E-extra" headers="msgs__stentry__4">The running heading file, which
|
||
contains content to be added to the <code class="keyword markupname xmlelement"><head></code> 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.</td></tr><tr class="strow" id="msgs__DOTA011W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA011W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Argument "<var class="keyword varname">%1</var>" is deprecated. This argument is no longer supported in the toolkit.</td><td class="stentry" id="msgs__DOTA011W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTA012W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA012W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Argument "<var class="keyword varname">%1</var>" is deprecated. Please use the argument "<var class="keyword varname">%2</var>" instead.</td><td class="stentry" id="msgs__DOTA012W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTA013F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA013F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Cannot find the specified DITAVAL '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTA013F-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTA014W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA014W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Attribute @<var class="keyword varname">%1</var> is deprecated. Use attribute @<var class="keyword varname">%2</var> instead.</td><td class="stentry" id="msgs__DOTA014W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTA066F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA066F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Cannot find the user specified XSLT stylesheet '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTA066F-extra" headers="msgs__stentry__4">An alternate stylesheet was specified
|
||
to run in place of the default XSL-FO output process, but that stylesheet could not be loaded. Please correct
|
||
the parameter to specify a valid stylesheet.</td></tr><tr class="strow" id="msgs__DOTA067W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA067W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Ignoring index-see '<var class="keyword varname">%1</var>' inside parent index entry '<var class="keyword varname">%2</var>' because the parent indexterm contains indexterm children. </td><td class="stentry" id="msgs__DOTA067W-extra" headers="msgs__stentry__4">According to the OASIS DITA
|
||
Specification, the <code class="keyword markupname xmlelement"><index-see></code> element should be ignored if the parent
|
||
<code class="keyword markupname xmlelement"><indexterm></code> contains other <code class="keyword markupname xmlelement"><indexterm></code> children.</td></tr><tr class="strow" id="msgs__DOTA068W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA068W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Ignoring index-see-also '<var class="keyword varname">%1</var>' inside parent index entry '<var class="keyword varname">%2</var>' because the parent indexterm contains indexterm children. </td><td class="stentry" id="msgs__DOTA068W-extra" headers="msgs__stentry__4">According to the OASIS DITA
|
||
Specification, the <code class="keyword markupname xmlelement"><index-see-also></code> element should be ignored if the parent
|
||
<code class="keyword markupname xmlelement"><indexterm></code> contains other <code class="keyword markupname xmlelement"><indexterm></code> children.</td></tr><tr class="strow" id="msgs__DOTA069F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA069F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Input file '<var class="keyword varname">%1</var>' cannot be located or read. Ensure that file was specified properly and that you have permission to access it.</td><td class="stentry" id="msgs__DOTA069F-extra" headers="msgs__stentry__4">Please ensure that the input file
|
||
path and file name were entered correctly.</td></tr><tr class="strow" id="msgs__DOTA069W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTA069W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Target "<var class="keyword varname">%1</var>" is deprecated. Remove references to this target from your custom XSLT or plug-ins.</td><td class="stentry" id="msgs__DOTA069W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ005F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ005F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Failed to create new instance for '<var class="keyword varname">%1</var>'. Please ensure that '<var class="keyword varname">%1</var>' exists and that you have permission to access it.</td><td class="stentry" id="msgs__DOTJ005F-extra" headers="msgs__stentry__4"></td></tr><tr class="strow" id="msgs__DOTJ007E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ007E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Duplicate condition in filter file for rule '<var class="keyword varname">%1</var>'. The first encountered condition will be used.</td><td class="stentry" id="msgs__DOTJ007E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ007I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ007I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Duplicate condition in filter file for rule '<var class="keyword varname">%1</var>'. The first encountered condition will be used.</td><td class="stentry" id="msgs__DOTJ007I-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ007W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ007W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Duplicate condition in filter file for rule '<var class="keyword varname">%1</var>'. The first encountered condition will be used.</td><td class="stentry" id="msgs__DOTJ007W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ009E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ009E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Cannot overwrite file '<var class="keyword varname">%1</var>' with file '<var class="keyword varname">%2</var>'. The modified result may not be consumed by the following steps in the transform pipeline. Check to see whether the file is locked by some other application during the transformation process.</td><td class="stentry" id="msgs__DOTJ009E-extra" headers="msgs__stentry__4">The transform was unable to create
|
||
files properly during the transform; results may not be as expected.</td></tr><tr class="strow" id="msgs__DOTJ012F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ012F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Failed to parse the input file '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTJ012F-extra" headers="msgs__stentry__4">This message may indicate an invalid
|
||
input file (such as accidentally specifying a PDF file as input rather than a DITA map file), an input file
|
||
that uses elements which are not allowed, are not part 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 in order to be
|
||
parsed correctly. The message issued by the XML parser should provide additional information to help diagnose
|
||
the cause.</td></tr><tr class="strow" id="msgs__DOTJ013E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ013E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Failed to parse the referenced file '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTJ013E-extra" headers="msgs__stentry__4">This message may indicate a reference
|
||
to an invalid file (such as accidentally referencing a PDF or unknown XML file as if it was DITA), a
|
||
referenced file that uses elements which are not allowed, or a referenced 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 in
|
||
order to be parsed correctly. The message issued by the XML parser should provide additional information to
|
||
help diagnose the cause.</td></tr><tr class="strow" id="msgs__DOTJ014W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ014W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Found an indexterm element with no content. Setting the term to ***.</td><td class="stentry" id="msgs__DOTJ014W-extra" headers="msgs__stentry__4">An empty
|
||
<code class="keyword markupname xmlelement"><indexterm></code> element was found, and will appear in the index as ***. This index term
|
||
should be removed from the source.</td></tr><tr class="strow" id="msgs__DOTJ018I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ018I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Log file '<var class="keyword varname">%1</var>' was generated successfully in directory '<var class="keyword varname">%2</var>'. Any messages from the transformation process are available in the log file; additional details about each message are available in the DITA-OT documentation.</td><td class="stentry" id="msgs__DOTJ018I-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ020W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ020W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">At least one plug-in in '<var class="keyword varname">%1</var>' is required by plug-in '<var class="keyword varname">%2</var>'. Plug-in '<var class="keyword varname">%2</var>' cannot be loaded. Check and see whether all prerequisite plug-ins are installed in toolkit.</td><td class="stentry" id="msgs__DOTJ020W-extra" headers="msgs__stentry__4">This will appear when one installed
|
||
plug-in requires another in order to function correctly, but the required plug-in is not found. The installed
|
||
plug-in will be ignored.</td></tr><tr class="strow" id="msgs__DOTJ021E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ021E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">File '<var class="keyword varname">%1</var>' will not generate output because because all content has been filtered out by DITAVAL "exclude" conditions, or because the file is not valid DITA. </td><td class="stentry" id="msgs__DOTJ021E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ021W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ021W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">File '<var class="keyword varname">%1</var>' will not generate output since it is invalid or all of its content has been filtered out by the ditaval file. Please check the file '<var class="keyword varname">%1</var>' and the ditaval file to see if this is the intended result.</td><td class="stentry" id="msgs__DOTJ021W-extra" headers="msgs__stentry__4">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, you could
|
||
place any filter conditions on the reference to this file, which will prevent the build from accessing this
|
||
file.</td></tr><tr class="strow" id="msgs__DOTJ022F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ022F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Failed to parse the input file '<var class="keyword varname">%1</var>' because all of its content has been filtered out. This will happen if the input file has filter conditions on the root element, and a ditaval excludes all content based on those conditions.</td><td class="stentry" id="msgs__DOTJ022F-extra" headers="msgs__stentry__4">Either the input file or the ditaval
|
||
file should change, otherwise your build is explicitly excluding all content.</td></tr><tr class="strow" id="msgs__DOTJ023E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ023E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Failed to get the specified image file '<var class="keyword varname">%1</var>', so it will not be included with your output. </td><td class="stentry" id="msgs__DOTJ023E-extra" headers="msgs__stentry__4">Check whether the image exists in the
|
||
source location or already exists in the output directory.
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTJ025E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ025E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The input to the "topic merge" transform process could not be found. Correct any earlier transform errors and try the build again, or see the DITA-OT documentation for additional causes.</td><td class="stentry" id="msgs__DOTJ025E-extra" headers="msgs__stentry__4">This message should only appear in
|
||
the following cases:
|
||
<ul class="ul">
|
||
<li class="li">Errors earlier in the transform prevented this step of the transform from running; correct any errors
|
||
and try the build again.</li>
|
||
<li class="li">An Ant build or plug-in is directly calling the toolkit’s topic merge module, and is doing so
|
||
improperly; in this case the Ant build or plug-in needs to be fixed.</li>
|
||
<li class="li">In the past, problems have been encountered when calling this module with an absolute path; this should
|
||
no longer be an issue, but may be fixed in older releases by updating the Ant build or plug-in.</li>
|
||
</ul></td></tr><tr class="strow" id="msgs__DOTJ026E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ026E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The "topic merge" did not generate any output. Correct any earlier transform errors and try the build again, or see the DITA-OT documentation for additional causes.</td><td class="stentry" id="msgs__DOTJ026E-extra" headers="msgs__stentry__4">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
|
||
<a class="xref" href="https://github.com/dita-ot/dita-ot/issues" target="_blank" rel="external noopener">GitHub issues tracker</a>. </td></tr><tr class="strow" id="msgs__DOTJ028E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ028E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">No format attribute was found on a reference to file '<var class="keyword varname">%1</var>', which does not appear to be a DITA file. If this is not a DITA file, set the format attribute to an appropriate value, otherwise set the format attribute to "dita".</td><td class="stentry" id="msgs__DOTJ028E-extra" headers="msgs__stentry__4">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 transform may attempt to parse the referenced document as a DITA topic.</td></tr><tr class="strow" id="msgs__DOTJ029I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ029I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">No 'domains' attribute was found for element '<<var class="keyword varname">%1</var>>'. This generally indicates that your DTD or Schema was not developed properly according to the DITA specification.</td><td class="stentry" id="msgs__DOTJ029I-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTJ030I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ030I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">No 'class' attribute for was found for element '<<var class="keyword varname">%1</var>>'. The element will be processed as an unknown or non-DITA element.</td><td class="stentry" id="msgs__DOTJ030I-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTJ031I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ031I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">No specified rule for '<var class="keyword varname">%1</var>' was found in the ditaval file. This value will use the default action, or a parent prop action if specified. To remove this message, you can specify a rule for '<var class="keyword varname">%1</var>' in the ditaval file.</td><td class="stentry" id="msgs__DOTJ031I-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTJ033E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ033E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">No valid content is found in topicref '<var class="keyword varname">%1</var>' during chunk processing. Please specify an existing and valid topic for the topicref.</td><td class="stentry" id="msgs__DOTJ033E-extra" headers="msgs__stentry__4"></td></tr><tr class="strow" id="msgs__DOTJ034F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ034F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Failed to parse the input file '<var class="keyword varname">%1</var>' (the content of the file is not valid). If the input file '<var class="keyword varname">%1</var>' does not have a DOCTYPE declaration, please make sure that all class attributes are present in the file.</td><td class="stentry" id="msgs__DOTJ034F-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTJ035F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ035F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">The file "<var class="keyword varname">%1</var>" is outside the scope of the input dita/map directory. If you want to lower the severity level, please use the Ant parameter 'outer.control', and set the value to "warn" or "quiet". Otherwise, move the referenced file "<var class="keyword varname">%1</var>" into the input dita/map directory.</td><td class="stentry" id="msgs__DOTJ035F-extra" headers="msgs__stentry__4">This will appear when a topic is
|
||
outside the scope of the map; for example, if the main input map references
|
||
<span class="ph filepath">"../other-directory/some.dita"</span>. The result would cause an output file to be created
|
||
outside of the output directory. See
|
||
<a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">DITA-OT common parameters (outer.control and generate.copy.outer)</a> for
|
||
details.
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTJ036W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ036W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The file "<var class="keyword varname">%1</var>" is outside the scope of the input dita/map directory. </td><td class="stentry" id="msgs__DOTJ036W-extra" headers="msgs__stentry__4">This will appear when a topic is
|
||
outside the scope of the map; for example, if the main input map references
|
||
<span class="ph filepath">"../other-directory/some.dita"</span>. 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, please use the Ant parameter
|
||
'outer.control', and set the value to "quiet". Otherwise, move the referenced file into the input dita/map
|
||
directory. See
|
||
<a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">DITA-OT common parameters (outer.control and generate.copy.outer)</a> for
|
||
details.
|
||
</td></tr><tr class="strow" id="msgs__DOTJ037W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ037W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The XML schema and DTD validation function of the parser is turned off. Please make sure the input is normalized DITA with class attributes included, otherwise it will not be processed correctly.</td><td class="stentry" id="msgs__DOTJ037W-extra" headers="msgs__stentry__4">DITA processing is based on class
|
||
attributes defined for every element. Usually these are defaulted in the DTD or Schema; if validation against
|
||
the DTD or Schema is turned off, the class attributes must be explicitly included in the map or
|
||
topic.</td></tr><tr class="strow" id="msgs__DOTJ038E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ038E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The tag "<var class="keyword varname">%1</var>" is specialized from unrecognized metadata. Please make sure that tag "<var class="keyword varname">%1</var>" is specialized from an existing metadata tag in the core DITA vocabulary.</td><td class="stentry" id="msgs__DOTJ038E-extra" headers="msgs__stentry__4">This appears to indicate an error in
|
||
creating specialized metadata elements. Please verify that the document type you are using is complete and
|
||
complies with DITA Specialization rules.
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTJ039E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ039E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">There is no target specified for conref push action "pushafter". Please add <elementname conref="pushtarget" conaction="mark"> before current element.</td><td class="stentry" id="msgs__DOTJ039E-extra" headers="msgs__stentry__4">Please see the topic on
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute" target="_blank" rel="external noopener">Conref Push</a> in the DITA specification for details on expected syntax
|
||
for this function.</td></tr><tr class="strow" id="msgs__DOTJ040E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ040E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">An element uses the attribute conaction="replace", but a conref attribute is not found in the expected location. </td><td class="stentry" id="msgs__DOTJ040E-extra" headers="msgs__stentry__4">Please see the topic on
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute" target="_blank" rel="external noopener">Conref Push</a> in the DITA specification for details on expected syntax
|
||
for this function.</td></tr><tr class="strow" id="msgs__DOTJ041E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ041E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The attribute conref="<var class="keyword varname">%1</var>" uses invalid syntax. The value should contain '#' followed by a topic or map ID, optionally followed by '/elemID' for a sub-topic element.</td><td class="stentry" id="msgs__DOTJ041E-extra" headers="msgs__stentry__4">The conref attribute must be a URI
|
||
reference to a DITA element. Please see the topic on
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank" rel="external noopener">URI-based addressing</a> in the DITA specification for details on the
|
||
expected syntax.</td></tr><tr class="strow" id="msgs__DOTJ042E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ042E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Two elements both use conref push to replace the target "<var class="keyword varname">%1</var>". Please delete one of the duplicate "replace" actions.</td><td class="stentry" id="msgs__DOTJ042E-extra" headers="msgs__stentry__4">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. See
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute" target="_blank" rel="external noopener">Conref Push</a> in the DITA specification for more information about the
|
||
conref push "replace" function.</td></tr><tr class="strow" id="msgs__DOTJ043W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ043W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The conref push function is trying to replace an element that does not exist (element "<var class="keyword varname">%1</var>" in file "<var class="keyword varname">%2</var>"). </td><td class="stentry" id="msgs__DOTJ043W-extra" headers="msgs__stentry__4">The target for a conref push action
|
||
does not exist; please make sure that the syntax is correct and that the target exists. See the topic on
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank" rel="external noopener">URI-based addressing</a> 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.</td></tr><tr class="strow" id="msgs__DOTJ044W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ044W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">There is a redundant conref action "pushbefore". Please make sure that "mark" and "pushbefore" occur in pairs.</td><td class="stentry" id="msgs__DOTJ044W-extra" headers="msgs__stentry__4">Please see the topic on
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute" target="_blank" rel="external noopener">Conref Push</a> in the DITA specification for details on expected syntax
|
||
for this function.</td></tr><tr class="strow" id="msgs__DOTJ045I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ045I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">The key "<var class="keyword varname">%1</var>" is defined more than once in the same map file. </td><td class="stentry" id="msgs__DOTJ045I-extra" headers="msgs__stentry__4">This informational message is
|
||
intended to help you catch catch duplicate key definitions; if the keys are defined as expected, no action is
|
||
needed.</td></tr><tr class="strow" id="msgs__DOTJ046E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ046E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Conkeyref="<var class="keyword varname">%1</var>" can not be resolved because it does not contain a key or the key is not defined. The build will use the conref attribute for fallback, if one exists.</td><td class="stentry" id="msgs__DOTJ046E-extra" headers="msgs__stentry__4">See
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconkeyrefattribute.html#theconkeyrefattribute" target="_blank" rel="external noopener">the conkeyref definition</a> for details on expected syntax and
|
||
usage.</td></tr><tr class="strow" id="msgs__DOTJ047I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ047I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Unable to find key definition for key reference "<var class="keyword varname">%1</var>" in root scope. The href attribute may be used as fallback if it exists</td><td class="stentry" id="msgs__DOTJ047I-extra" headers="msgs__stentry__4">This message is intended to help you
|
||
locate incorrectly specified keys; if the key was specified correctly, this message may be ignored.</td></tr><tr class="strow" id="msgs__DOTJ048I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ048I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Unable to find key definition for key reference "<var class="keyword varname">%1</var>" in scope "<var class="keyword varname">%2</var>". The href attribute may be used as fallback if it exists</td><td class="stentry" id="msgs__DOTJ048I-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ049W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ049W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The attribute value <var class="keyword varname">%1</var>="<var class="keyword varname">%3</var>" on element "<var class="keyword varname">%2</var>" does not comply with the specified subject scheme. According to the subject scheme map, the following values are valid for the <var class="keyword varname">%1</var> attribute: <var class="keyword varname">%4</var></td><td class="stentry" id="msgs__DOTJ049W-extra" headers="msgs__stentry__4">A DITA Subject Scheme map was used to
|
||
limit values that are available to the specified attribute. Please correct the attribute so that it uses one
|
||
of the allowed values.</td></tr><tr class="strow" id="msgs__DOTJ050W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ050W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Found an <index-see> or <index-see-also> reference to the term '<var class="keyword varname">%1</var>', but that term is not defined in the index. </td><td class="stentry" id="msgs__DOTJ050W-extra" headers="msgs__stentry__4">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 <em class="ph i">always</em> loaded into Eclipse with another plug-in that defines otherEntry
|
||
as an index term.</td></tr><tr class="strow" id="msgs__DOTJ051E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ051E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to load target for coderef "<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTJ051E-extra" headers="msgs__stentry__4">The target for a coderef element,
|
||
which specifies an external text-based file, could not be located or loaded. Please verify that the reference
|
||
is correct.
|
||
<p class="p">Note that 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
|
||
<a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">DITA-OT common parameters (outer.control and generate.copy.outer)</a> for
|
||
details.
|
||
</p></td></tr><tr class="strow" id="msgs__DOTJ052E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ052E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Code reference charset "<var class="keyword varname">%1</var>" not supported. See the DITA-OT documentation for supported charset values on the format attribute.</td><td class="stentry" id="msgs__DOTJ052E-extra" headers="msgs__stentry__4">DITA-OT supports a special syntax on
|
||
coderef elements to specify the character set of the target document. See
|
||
<a class="xref" href="../reference/extended-functionality.html" title="DITA-OT provides additional processing support beyond that which is mandated by the DITA specification. These extensions can be used to define character encodings or line ranges for code references, normalize indendation, add line numbers or display whitespace characters in code blocks.">Extended codeblock processing</a> for details on the expected syntax.</td></tr><tr class="strow" id="msgs__DOTJ053W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ053W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Input file '<var class="keyword varname">%1</var>' is not valid DITA file name. Please check '<var class="keyword varname">%1</var>' to see if it is correct. The extensions ".dita" or ".xml" are supported for DITA topics.</td><td class="stentry" id="msgs__DOTJ053W-extra" headers="msgs__stentry__4">By default, DITA-OT supports the
|
||
extensions "dita" and "xml" for DITA topics, as mandated by the DITA specification. Please verify that your
|
||
topics use one of these extensions, or configure the toolkit to allow additional extensions.</td></tr><tr class="strow" id="msgs__DOTJ054E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ054E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to parse invalid <var class="keyword varname">%1</var> attribute value "<var class="keyword varname">%2</var>" </td><td class="stentry" id="msgs__DOTJ054E-extra" headers="msgs__stentry__4">This message indicates that the
|
||
<code class="keyword markupname xmlatt">@href</code> value specified in <var class="keyword varname">%1</var> does not use proper URI syntax. This may
|
||
occur when <code class="keyword markupname xmlatt">@href</code> includes characters that should be escaped (such as the space character,
|
||
which should be <code class="ph codeph">%20</code> 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 <var class="keyword varname">%2</var>.</td></tr><tr class="strow" id="msgs__DOTJ055E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ055E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Invalid key name "<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTJ055E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ056E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ056E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Invalid xml:lang "<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTJ056E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ057E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ057E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The id attribute value "<var class="keyword varname">%1</var>" is not unique within the topic that contains it. </td><td class="stentry" id="msgs__DOTJ057E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ058E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ058E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Both <var class="keyword varname">%1</var> and <var class="keyword varname">%2</var> attributes defined. A single element may not contain both generalized and specialized values for the same attribute.</td><td class="stentry" id="msgs__DOTJ058E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ059E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ059E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Invalid key scope name "<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTJ059E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ060W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ060W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Key "<var class="keyword varname">%1</var>" was used in conkeyref but is not bound to a DITA topic or map. Cannot resolve conkeyref value "<var class="keyword varname">%2</var>" as a valid conref reference.</td><td class="stentry" id="msgs__DOTJ060W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ061E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ061E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Topic reference target is a DITA map but format attribute has not been set. Set format attribute value to "ditamap".</td><td class="stentry" id="msgs__DOTJ061E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ062E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ062E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Invalid <var class="keyword varname">%1</var> attribute value "<var class="keyword varname">%2</var>". </td><td class="stentry" id="msgs__DOTJ062E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ063E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ063E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The cols attribute is "<var class="keyword varname">%1</var>" but number of colspec elements was <var class="keyword varname">%2</var>. </td><td class="stentry" id="msgs__DOTJ063E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ064W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ064W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Chunk attribute uses both "to-content" and "by-topic" that conflict with each other. Ignoring "by-topic" token.</td><td class="stentry" id="msgs__DOTJ064W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ065I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ065I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Branch filter generated topic <var class="keyword varname">%1</var> used more than once. Renaming <var class="keyword varname">%1</var> to <var class="keyword varname">%2</var>.</td><td class="stentry" id="msgs__DOTJ065I-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ066E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ066E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">No id attribute on topic type element <var class="keyword varname">%1</var>. Using generated id <var class="keyword varname">%2</var>.</td><td class="stentry" id="msgs__DOTJ066E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ067E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ067E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">No id attribute on topic type element <var class="keyword varname">%1</var>. </td><td class="stentry" id="msgs__DOTJ067E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ068E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ068E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Conref action "mark" without conref target. </td><td class="stentry" id="msgs__DOTJ068E-extra" headers="msgs__stentry__4">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 "mark" element and the pushed element is reversed.</td></tr><tr class="strow" id="msgs__DOTJ069E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ069E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Circular key definition <var class="keyword varname">%1</var>. </td><td class="stentry" id="msgs__DOTJ069E-extra" headers="msgs__stentry__4">
|
||
<p class="p">A circular reference was found in key definitions: a series of key references where the last key references
|
||
the first.</p>
|
||
<p class="p">This may occur if a <code class="keyword markupname xmlelement"><topicref></code> element contains both a key name in the
|
||
<code class="keyword markupname xmlatt">@keys</code> attribute and a reference to the same key in the <code class="keyword markupname xmlatt">@keyref</code> attribute,
|
||
or if a <code class="keyword markupname xmlatt">@keyref</code> attribute points to a key that refers back to the referencing element.</p>
|
||
<p class="p">To resolve this issue, change the target of the <code class="keyword markupname xmlatt">@keyref</code> so the key is defined by pointing
|
||
to a resource other than itself.</p>
|
||
</td></tr><tr class="strow" id="msgs__DOTJ070I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ070I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Invalid 'class' attribute '<var class="keyword varname">%1</var>' for was found for element '<<var class="keyword varname">%2</var>>'. The element will be processed as an unknown or non-DITA element.</td><td class="stentry" id="msgs__DOTJ070I-extra" headers="msgs__stentry__4">
|
||
<p class="p">When a <code class="keyword markupname xmlatt">@class</code> attribute does not use the expected syntax, this usually indicates that
|
||
<code class="keyword markupname xmlatt">@class</code> has been explicitly set on a DITA element. The attribute should be removed from the
|
||
document so that the expected default value can be automatically used.</p>
|
||
<p class="p">If this is a non-DITA element, it needs to be placed inside a <code class="keyword markupname xmlelement"><foreign></code> element so
|
||
that is not validated against DITA rules.
|
||
|
||
</p>
|
||
</td></tr><tr class="strow" id="msgs__DOTJ071E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ071E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Cannot find the specified DITAVAL '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTJ071E-extra" headers="msgs__stentry__4">
|
||
<p class="p">Ensure that 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
|
||
‘<code class="ph codeph">;</code>’ on Windows, or colon ‘<code class="ph codeph">:</code>’ on macOS or Linux).</p>
|
||
</td></tr><tr class="strow" id="msgs__DOTJ072E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ072E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Email link without correct 'format' attribute. Using 'format' attribute value 'email'.</td><td class="stentry" id="msgs__DOTJ072E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ073E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ073E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Email link without correct 'scope' attribute. Using 'scope' attribute value 'external'.</td><td class="stentry" id="msgs__DOTJ073E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ074W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ074W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Rev attribute cannot be used with prop filter. </td><td class="stentry" id="msgs__DOTJ074W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ075W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ075W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Absolute link '<var class="keyword varname">%1</var>' without correct 'scope' attribute. Using 'scope' attribute value 'external'.</td><td class="stentry" id="msgs__DOTJ075W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ076W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ076W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Absolute link '<var class="keyword varname">%1</var>' without correct 'scope' attribute. </td><td class="stentry" id="msgs__DOTJ076W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ077F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ077F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Invalid action attribute '<var class="keyword varname">%1</var>' on DITAVAL property. </td><td class="stentry" id="msgs__DOTJ077F-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ078F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ078F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">Input file '<var class="keyword varname">%1</var>' could not be loaded. Ensure that grammar files for this document type are referenced and installed properly.</td><td class="stentry" id="msgs__DOTJ078F-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ079E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ079E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">File '<var class="keyword varname">%1</var>' could not be loaded. Ensure that grammar files for this document type are referenced and installed properly.</td><td class="stentry" id="msgs__DOTJ079E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ080W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ080W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Integrator configuration '<var class="keyword varname">%1</var>' has been deprecated. Use plugin configuration '<var class="keyword varname">%1</var>' instead.</td><td class="stentry" id="msgs__DOTJ080W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ081W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ081W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Ignoring empty conref attribute conref="". </td><td class="stentry" id="msgs__DOTJ081W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ082E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ082E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Processing table cell failed. </td><td class="stentry" id="msgs__DOTJ082E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTJ083E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTJ083E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The resource referenced as <var class="keyword varname">%1</var> is capitalized differently on disk </td><td class="stentry" id="msgs__DOTJ083E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX001W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX001W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">No string named '<var class="keyword varname">%1</var>' was found for language '<var class="keyword varname">%2</var>'. Using the default language '<var class="keyword varname">%3</var>'. Add a mapping between default language and desired language for the string '<var class="keyword varname">%1</var>'.</td><td class="stentry" id="msgs__DOTX001W-extra" headers="msgs__stentry__4">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 <var class="keyword varname">%1</var> for your specified language, so the string 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.</td></tr><tr class="strow" id="msgs__DOTX002W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX002W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The title element or attribute in the ditamap is required for Eclipse output. </td><td class="stentry" id="msgs__DOTX002W-extra" headers="msgs__stentry__4">The Eclipse help system requires a
|
||
title in the project files generated from your map. Please add a title to your input map to get valid Eclipse
|
||
help output.</td></tr><tr class="strow" id="msgs__DOTX003I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX003I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">The anchorref attribute should either reference another dita map or an Eclipse XML TOC file. The value '<var class="keyword varname">%1</var>' does not appear to reference either. </td><td class="stentry" id="msgs__DOTX003I-extra" headers="msgs__stentry__4">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).
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTX004I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX004I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Found a navref element that does not reference anything. The navref element should either reference another dita map or an Eclipse XML file.</td><td class="stentry" id="msgs__DOTX004I-extra" headers="msgs__stentry__4">Eclipse builds use DITA’s
|
||
<code class="keyword markupname xmlelement"><navref></code> element to pull in other Eclipse TOC files. The build found a
|
||
<code class="keyword markupname xmlelement"><navref></code> element that does not reference any other file; the element will be
|
||
ignored.</td></tr><tr class="strow" id="msgs__DOTX005E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX005E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to find navigation title for reference to '<var class="keyword varname">%1</var>'. The build will use '<var class="keyword varname">%1</var>' as the title in the Eclipse Table of Contents.</td><td class="stentry" id="msgs__DOTX005E-extra" headers="msgs__stentry__4">To remove this message, provide a
|
||
navigation title for the referenced object in the map or topic, or ensure that you are referencing a valid
|
||
local DITA target.</td></tr><tr class="strow" id="msgs__DOTX006E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX006E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unknown file extension in href="<var class="keyword varname">%1</var>". References to non-DITA resources should set the format attribute to match the resource (for example, 'txt', 'pdf', or 'html').</td><td class="stentry" id="msgs__DOTX006E-extra" headers="msgs__stentry__4">Set the format attribute to identify
|
||
the format of the file. If the reference is to a DITA document, ensure that the document uses a valid DITA
|
||
extension (default supported extensions are "dita" and "xml").</td></tr><tr class="strow" id="msgs__DOTX007I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX007I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Only DITA topics, HTML files, and images may be included in your compiled CHM file. The reference to "<var class="keyword varname">%1</var>" will be ignored. To remove this message, you can set the toc="no" or processing-role="resource-only" attribute on your topicref.</td><td class="stentry" id="msgs__DOTX007I-extra" headers="msgs__stentry__4">The HTML Help compiler will only
|
||
include some types of information in the compiled CHM file; the current reference will not be
|
||
included.</td></tr><tr class="strow" id="msgs__DOTX008E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX008E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">File '<var class="keyword varname">%1</var>' does not exist or cannot be loaded. </td><td class="stentry" id="msgs__DOTX008E-extra" headers="msgs__stentry__4">Ensure that the file exists and can
|
||
be read. <span class="ph">Note that the name of the file in this message may have be changed
|
||
to use a standard dita topic file 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.</span></td></tr><tr class="strow" id="msgs__DOTX008W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX008W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">File '<var class="keyword varname">%1</var>' cannot be loaded, and no navigation title is specified for the table of contents. </td><td class="stentry" id="msgs__DOTX008W-extra" headers="msgs__stentry__4">To fix the table of contents, specify
|
||
a navigation title in your map or ensure that the referenced file is local and can be accessed. <span class="ph">Note that the name of the file in this message may have be changed
|
||
to use a standard dita topic file 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.</span>
|
||
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTX009W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX009W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Could not retrieve a title from '<var class="keyword varname">%1</var>'. Using '<var class="keyword varname">%2</var>' instead. </td><td class="stentry" id="msgs__DOTX009W-extra" headers="msgs__stentry__4">No title was found in the specified
|
||
topic, so the table of contents will use the indicated fallback value for this topic.
|
||
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTX010E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX010E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to find target for conref="<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTX010E-extra" headers="msgs__stentry__4">The conref attribute must be a URI
|
||
reference to an existing DITA element. Please see the topic on
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank" rel="external noopener">URI-based addressing</a> in the DITA specification for details on the
|
||
expected syntax. <span class="ph" id="msgs__changeExtension">Note that the name of the file in this message may have be changed
|
||
to use a standard dita topic file 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.</span>
|
||
<p class="p">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).</p></td></tr><tr class="strow" id="msgs__DOTX011W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX011W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">There is more than one possible target for the reference conref="<var class="keyword varname">%1</var>". Only the first will be used. Remove the duplicate id in the referenced file.</td><td class="stentry" id="msgs__DOTX011W-extra" headers="msgs__stentry__4">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.
|
||
<span class="ph">Note that the name of the file in this message may have be changed
|
||
to use a standard dita topic file 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.</span></td></tr><tr class="strow" id="msgs__DOTX012W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX012W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">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 your target under an appropriate domain. You can see the messages guide for more help.</td><td class="stentry" id="msgs__DOTX012W-extra" headers="msgs__stentry__4">This message is deprecated and should
|
||
no longer appear in any logs.</td></tr><tr class="strow" id="msgs__DOTX013E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX013E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">A element with attribute conref="<var class="keyword varname">%1</var>" indirectly includes itself, which results in an infinite loop. </td><td class="stentry" id="msgs__DOTX013E-extra" headers="msgs__stentry__4">This may appear if (for example) you
|
||
have a <code class="keyword markupname xmlelement"><ph></code> element that references another phrase, but that phrase itself contains a
|
||
reference to the original. This will result in an infinite loop. The toolkit will stop following the conref
|
||
trail when this is detected; you will need to correct the reference in your source files. <span class="ph">Note that the name of the file in this message may have be changed
|
||
to use a standard dita topic file 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.</span></td></tr><tr class="strow" id="msgs__DOTX014E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX014E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The attribute conref="<var class="keyword varname">%1</var>" uses invalid syntax. Conref references to a map element should contain '#' followed by an ID, such as mymap.ditamap#mytopicrefid.</td><td class="stentry" id="msgs__DOTX014E-extra" headers="msgs__stentry__4">The conref attribute must be a URI
|
||
reference to a DITA element. Please see the topic on
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank" rel="external noopener">URI-based addressing</a> in the DITA specification for details on the
|
||
expected syntax.</td></tr><tr class="strow" id="msgs__DOTX015E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX015E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The attribute conref="<var class="keyword varname">%1</var>" uses invalid syntax. The value should contain '#' followed by a topic or map ID, optionally followed by '/elemID' for a sub-topic element.</td><td class="stentry" id="msgs__DOTX015E-extra" headers="msgs__stentry__4">The conref attribute must be a URI
|
||
reference to a DITA element. Please see the topic on
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank" rel="external noopener">URI-based addressing</a> in the DITA specification for details on the
|
||
expected syntax. <span class="ph">Note that the name of the file in this message may have be changed
|
||
to use a standard dita topic file 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.</span></td></tr><tr class="strow" id="msgs__DOTX016W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX016W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">A reference to "<var class="keyword varname">%2</var>" appears to reference a DITA document, but the format attribute has inherited a value of "<var class="keyword varname">%1</var>". The document will not be processed as DITA. </td><td class="stentry" id="msgs__DOTX016W-extra" headers="msgs__stentry__4">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.
|
||
<span class="ph">Note that the name of the file in this message may have be changed
|
||
to use a standard dita topic file 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.</span></td></tr><tr class="strow" id="msgs__DOTX017E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX017E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Found a link or cross reference with an empty href attribute (href=""). Remove the empty href attribute or provide a value.</td><td class="stentry" id="msgs__DOTX017E-extra" headers="msgs__stentry__4">Found a value such as <xref
|
||
href="">link text</xref>. The empty href attribute 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.</td></tr><tr class="strow" id="msgs__DOTX018I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX018I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">The type attribute on a topicref was set to '<var class="keyword varname">%1</var>', but the topicref references a more specific '<var class="keyword varname">%2</var>' topic. Note that the type attribute cascades in maps, so the value '<var class="keyword varname">%1</var>' may come from an ancestor topicref. </td><td class="stentry" id="msgs__DOTX018I-extra" headers="msgs__stentry__4">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 may result in unexpected sorting for links to this topic.</td></tr><tr class="strow" id="msgs__DOTX019W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX019W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The type attribute on a topicref was set to '<var class="keyword varname">%1</var>', but the topicref references a '<var class="keyword varname">%2</var>' topic. This may cause your links to sort incorrectly in the output. Note that the type attribute cascades in maps, so the value '<var class="keyword varname">%1</var>' may come from an ancestor topicref. </td><td class="stentry" id="msgs__DOTX019W-extra" headers="msgs__stentry__4">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, which may cause
|
||
your links to sort inappropriately.</td></tr><tr class="strow" id="msgs__DOTX020E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX020E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Missing navtitle attribute or element for peer topic "<var class="keyword varname">%1</var>". References must provide a local navigation title when the target is not a local DITA resource.</td><td class="stentry" id="msgs__DOTX020E-extra" headers="msgs__stentry__4">DITA-OT is only able to dynamically
|
||
retrieve titles when the target is a local (not peer or external) DITA resource.
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTX021E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX021E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Missing navtitle attribute or element for non-DITA resource "<var class="keyword varname">%1</var>". References must provide a local navigation title when the target is not a local DITA resource.</td><td class="stentry" id="msgs__DOTX021E-extra" headers="msgs__stentry__4">DITA-OT is only able to dynamically
|
||
retrieve titles when the target is a local DITA resource.</td></tr><tr class="strow" id="msgs__DOTX022W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX022W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Unable to retrieve navtitle from target: '<var class="keyword varname">%1</var>'. Using linktext (specified in topicmeta) as the navigation title. </td><td class="stentry" id="msgs__DOTX022W-extra" headers="msgs__stentry__4">The build was unable to get a title
|
||
from the referenced topic; instead, a navigation title will be created based on the specified
|
||
<code class="keyword markupname xmlelement"><linktext></code> element inside of <code class="keyword markupname xmlelement"><topicmeta></code>.</td></tr><tr class="strow" id="msgs__DOTX023W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX023W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Unable to retrieve navtitle from target: '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTX023W-extra" headers="msgs__stentry__4">If the target is a local DITA topic,
|
||
ensure the reference is correct and the topic is available. Otherwise, provide a navigation title, and ensure
|
||
the scope and format attributes are set appropriately.</td></tr><tr class="strow" id="msgs__DOTX024E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX024E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Missing linktext and navtitle for peer topic "<var class="keyword varname">%1</var>". References must provide a local navigation title when the target is not a local DITA resource.</td><td class="stentry" id="msgs__DOTX024E-extra" headers="msgs__stentry__4">DITA-OT is only able to dynamically
|
||
retrieve titles and link text when the target is a local (not peer or external) DITA resource.</td></tr><tr class="strow" id="msgs__DOTX025E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX025E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Missing linktext and navtitle for non-DITA resource "<var class="keyword varname">%1</var>". References must provide a local navigation title when the target is not a local DITA resource.</td><td class="stentry" id="msgs__DOTX025E-extra" headers="msgs__stentry__4">DITA-OT is only able to dynamically
|
||
retrieve titles when the target is a local DITA resource.</td></tr><tr class="strow" id="msgs__DOTX026W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX026W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Unable to retrieve linktext from target: '<var class="keyword varname">%1</var>'. Using navigation title as fallback. </td><td class="stentry" id="msgs__DOTX026W-extra" headers="msgs__stentry__4">The referenc to this document did not
|
||
specify any link text for generated map-based links; the navigation title will be used as fallback.</td></tr><tr class="strow" id="msgs__DOTX027W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX027W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Unable to retrieve linktext from target: '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTX027W-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTX028E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX028E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Link or cross reference must contain a valid href or keyref attribute; no link target is specified. </td><td class="stentry" id="msgs__DOTX028E-extra" headers="msgs__stentry__4">The link or cross reference has no
|
||
target specified and will not generate a link.</td></tr><tr class="strow" id="msgs__DOTX029I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX029I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">The type attribute on a <var class="keyword varname">%1</var> element was set to <var class="keyword varname">%3</var>, but the reference is to a more specific <var class="keyword varname">%4</var> <var class="keyword varname">%2</var>. This may cause your links to sort incorrectly in the output. </td><td class="stentry" id="msgs__DOTX029I-extra" headers="msgs__stentry__4">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 may result in unexpected sorting for links to this topic.</td></tr><tr class="strow" id="msgs__DOTX030W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX030W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The type attribute on a <var class="keyword varname">%1</var> element was set to <var class="keyword varname">%3</var>, but the reference is to a <var class="keyword varname">%4</var> <var class="keyword varname">%2</var>. This may cause your links to sort incorrectly in the output. </td><td class="stentry" id="msgs__DOTX030W-extra" headers="msgs__stentry__4">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, which may cause
|
||
your links to sort inappropriately.</td></tr><tr class="strow" id="msgs__DOTX031E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX031E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The file <var class="keyword varname">%1</var> is not available to resolve link information. </td><td class="stentry" id="msgs__DOTX031E-extra" headers="msgs__stentry__4">The build attempted to access the
|
||
specified file in order to retrive 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.</td></tr><tr class="strow" id="msgs__DOTX032E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX032E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to retrieve link text from target: '<var class="keyword varname">%1</var>'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.</td><td class="stentry" id="msgs__DOTX032E-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTX033E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX033E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to generate link text for a cross reference to a list item: '<var class="keyword varname">%1</var>' </td><td class="stentry" id="msgs__DOTX033E-extra" headers="msgs__stentry__4">An <code class="keyword markupname xmlelement"><xref></code>
|
||
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. Please specify link text inside the reference, or ensure that you are
|
||
referencing an available list item.</td></tr><tr class="strow" id="msgs__DOTX034E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX034E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to generate link text for a cross reference to an undered list item: '<var class="keyword varname">%1</var>' </td><td class="stentry" id="msgs__DOTX034E-extra" headers="msgs__stentry__4">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. Please provide link text within the cross reference.</td></tr><tr class="strow" id="msgs__DOTX035E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX035E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to generate the correct number for a cross reference to a footnote: '<var class="keyword varname">%1</var>' </td><td class="stentry" id="msgs__DOTX035E-extra" headers="msgs__stentry__4">An <code class="keyword markupname xmlelement"><xref></code>
|
||
element specifies type="fn", which indicates a link to a footnote, but the footnote number could not be
|
||
determined to use as link text. Please specify link text inside the reference, or ensure that you are
|
||
referencing an available footnote.</td></tr><tr class="strow" id="msgs__DOTX036E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX036E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Unable to generate link text for a cross reference to a dlentry (the dlentry or term could not be found): '<var class="keyword varname">%1</var>' </td><td class="stentry" id="msgs__DOTX036E-extra" headers="msgs__stentry__4">An <code class="keyword markupname xmlelement"><xref></code>
|
||
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. Please specify link text inside the reference, or ensure that you are referencing
|
||
an available definition list entry</td></tr><tr class="strow" id="msgs__DOTX037W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX037W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">No title found for this document; using "***" in XHTML title bar. </td><td class="stentry" id="msgs__DOTX037W-extra" headers="msgs__stentry__4">No title was found for the current
|
||
document, so the HTML output file will set the <code class="keyword markupname xmlelement"><title></code> to "***". This value generally
|
||
appears in the title bar at the top of a browser.</td></tr><tr class="strow" id="msgs__DOTX038I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX038I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">The longdescref attribute on tag '<var class="keyword varname">%1</var>' will be ignored. Accessibility for object elements needs to be handled another way. </td><td class="stentry" id="msgs__DOTX038I-extra" headers="msgs__stentry__4">The <code class="keyword markupname xmlelement"><object></code>
|
||
element in HTML does not support using 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
|
||
<code class="keyword markupname xmlelement"><param></code> element inside the object.</td></tr><tr class="strow" id="msgs__DOTX039W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX039W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Required cleanup area found. To remove this message and hide the content, build your content without using the DRAFT parameter.</td><td class="stentry" id="msgs__DOTX039W-extra" headers="msgs__stentry__4">This message is generated when
|
||
creating draft output in order 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.</td></tr><tr class="strow" id="msgs__DOTX040I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX040I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Draft comment area found. To remove this message and hide the comments, build your content without using the DRAFT parameter.</td><td class="stentry" id="msgs__DOTX040I-extra" headers="msgs__stentry__4">This message is generated when
|
||
creating draft output in order 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.</td></tr><tr class="strow" id="msgs__DOTX041W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX041W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Found more than one title element in a <var class="keyword varname">%1</var> element. Using the first one for the <var class="keyword varname">%1</var>'s title. </td><td class="stentry" id="msgs__DOTX041W-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTX042I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX042I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">DITAVAL based flagging is not currently supported for inline phrases in XHTML; ignoring flag value on '<var class="keyword varname">%1</var>' attribute. </td><td class="stentry" id="msgs__DOTX042I-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTX043I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX043I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">The link to '<var class="keyword varname">%1</var>' may appear more than once in '<var class="keyword varname">%2</var>'. </td><td class="stentry" id="msgs__DOTX043I-extra" headers="msgs__stentry__4">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 <code class="keyword markupname xmlelement"><reltable></code> in a DITA map will have the role attribute set to "friend".
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTX044E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX044E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The area element in an image map does not specify a link target. Please add an xref element with a link target to the area element.</td><td class="stentry" id="msgs__DOTX044E-extra" headers="msgs__stentry__4">The <code class="keyword markupname xmlelement"><area></code>
|
||
element in an image map must provide a link target for the specified area. Please add an
|
||
<code class="keyword markupname xmlelement"><xref></code> element as a child of <code class="keyword markupname xmlelement"><area></code> and ensure that it
|
||
specifies a link target.
|
||
</td></tr><tr class="strow" id="msgs__DOTX045W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX045W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The area element in an image map should specify link text for greater accessibility. Link text should be specified directly when the target is not a local DITA resource.</td><td class="stentry" id="msgs__DOTX045W-extra" headers="msgs__stentry__4">Cross reference text inside the
|
||
<code class="keyword markupname xmlelement"><area></code> 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.</td></tr><tr class="strow" id="msgs__DOTX046W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX046W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Area shape should be: default, rect, circle, poly, or blank (no value). The value '<var class="keyword varname">%1</var>' is not recognized. </td><td class="stentry" id="msgs__DOTX046W-extra" headers="msgs__stentry__4">The specified value was passed as-is
|
||
through to the <code class="keyword markupname xmlelement"><area></code> element in the HTML.</td></tr><tr class="strow" id="msgs__DOTX047W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX047W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Area coordinates are blank. Coordinate points for the shape need to be specified. </td><td class="stentry" id="msgs__DOTX047W-extra" headers="msgs__stentry__4">The area element is intended to
|
||
define a region in an image map; coordinates must be specified in order to define that region.</td></tr><tr class="strow" id="msgs__DOTX048I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX048I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">In order to include peer or external topic '<var class="keyword varname">%1</var>' in your help file, you may need to recompile the CHM file after making the file available. </td><td class="stentry" id="msgs__DOTX048I-extra" headers="msgs__stentry__4">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 your topicref element. Otherwise, check to be sure your 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.
|
||
|
||
</td></tr><tr class="strow" id="msgs__DOTX049I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX049I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">References to non-dita files will be ignored by the PDF, ODT, and RTF output transforms. </td><td class="stentry" id="msgs__DOTX049I-extra" headers="msgs__stentry__4">The PDF, ODT, and RTF output
|
||
processes cannot automatically convert non-DITA content into DITA in order to merge it with the rest of your
|
||
content. The referenced items are ignored.</td></tr><tr class="strow" id="msgs__DOTX050W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX050W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Default id "org.sample.help.doc" is used for Eclipse plug-in. If you want to use your own plug-in id, please specify it using the id attribute on your map.</td><td class="stentry" id="msgs__DOTX050W-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTX052W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX052W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">No string named '<var class="keyword varname">%1</var>' was found when creating generated text; using the value '<var class="keyword varname">%1</var>' in your output file. </td><td class="stentry" id="msgs__DOTX052W-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTX053E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX053E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">A element that references another map indirectly includes itself, which results in an infinite loop. The original map reference is to '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__DOTX053E-extra" headers="msgs__stentry__4">This will occur if a map references
|
||
another map, and then that second map (or another further nested map) references the original map. The result
|
||
is an infinite nesting of maps; please correct the chain of map references to remove circular
|
||
reference.</td></tr><tr class="strow" id="msgs__DOTX054W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX054W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Conflict text style is applied on the current element based on DITAVAL flagging rules. Please check ditaval and dita source to make sure there is no style conflict on the element which needs to be flagged.</td><td class="stentry" id="msgs__DOTX054W-extra" headers="msgs__stentry__4">This will occur when a DITAVAL file
|
||
contains multiple styling rules that apply to the same element.</td></tr><tr class="strow" id="msgs__DOTX055W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX055W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Customized stylesheet uses deprecated template "flagit". Conditional processing is no longer supported using this template. Please update your stylesheet to use template "start-flagit" instead of deprecated template "flagit".</td><td class="stentry" id="msgs__DOTX055W-extra" headers="msgs__stentry__4">The "flagit" named template was
|
||
deprecated in DITA-OT version 1.4, when the OASIS standard formalized the DITAVAL syntax. The template is
|
||
removed in DITA-OT 1.6. Stylesheets that used this template need to be updated.</td></tr><tr class="strow" id="msgs__DOTX056W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX056W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The file '<var class="keyword varname">%1</var>' is not available to resolve link information. </td><td class="stentry" id="msgs__DOTX056W-extra" headers="msgs__stentry__4">The build attempted to access the
|
||
specified file in order to retrive 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
|
||
<a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">onlytopic.in.map</a> parameter was specified. Be aware that the path
|
||
information above may not match the link in your topic.</td></tr><tr class="strow" id="msgs__DOTX057W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX057W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The link or cross reference target '<var class="keyword varname">%1</var>' cannot be found, which may cause errors creating links or cross references in your output file. </td><td class="stentry" id="msgs__DOTX057W-extra" headers="msgs__stentry__4">The link appears to use valid syntax
|
||
to reference a DITA element, but that element cannot be found. Please verify that the element exists, and is
|
||
not removed from the build by DITAVAL based filtering.</td></tr><tr class="strow" id="msgs__DOTX058W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX058W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">No glossary entry was found associated with key '<var class="keyword varname">%1</var>' on <var class="keyword varname">%2</var> element. The build will try to determine the best display text and hover text for terms and abbreviations. </td><td class="stentry" id="msgs__DOTX058W-extra" headers="msgs__stentry__4">Processing for terms, acronyms, or
|
||
abbreviated forms will associate the key from the element’s keyref attribute with a glossentry (glossary
|
||
entry) topic. This message will appear if the key was defined, but was not associated with a glossentry topic.
|
||
The process will try to use the best available fallback (usually the title of the referenced topic).</td></tr><tr class="strow" id="msgs__DOTX060W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX060W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Key '<var class="keyword varname">%1</var>' was used in an abbreviated-form element, but the key is not associated with a glossary entry. Abbreviated-form should ONLY be used to reference to a glossary entry.</td><td class="stentry" id="msgs__DOTX060W-extra" headers="msgs__stentry__4">Processing for abbreviated form
|
||
elements will associate the key from the element’s keyref attribute with a glossentry (glossary entry) topic.
|
||
This message will appear if the key was defined, but was not associated with a glossentry topic. This element
|
||
is only supported with keys that are associated with glossary topics; the element will not generate any
|
||
output. Please correct the reference, or use a different element to reference your topic.</td></tr><tr class="strow" id="msgs__DOTX061W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX061W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">ID '<var class="keyword varname">%1</var>' was used in topicref tag but did not reference a topic element. The href attribute on a topicref element should only reference topic level elements. </td><td class="stentry" id="msgs__DOTX061W-extra" headers="msgs__stentry__4">According to the DITA Specification,
|
||
references from maps should either go to DITA Maps, DITA Topics, or any non-DITA resource. References below
|
||
the topic level should only be made from cross references (using <code class="keyword markupname xmlelement"><xref></code> or similar)
|
||
inside of a topic. For details, see the href attribute description in the OASIS standard’s definition of the
|
||
<a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/langref/topicref.html" target="_blank" rel="external noopener">topicref element</a>.</td></tr><tr class="strow" id="msgs__DOTX062I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX062I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">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, please upgrade to an XSLT 2.0 processor.</td><td class="stentry" id="msgs__DOTX062I-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX063W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX063W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The dita document '<var class="keyword varname">%1</var>' is linked to from your content, but is not referenced by a topicref tag in the ditamap file. Include the topic in your map to avoid a broken link.</td><td class="stentry" id="msgs__DOTX063W-extra" headers="msgs__stentry__4">This will appear 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.</td></tr><tr class="strow" id="msgs__DOTX064W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX064W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">The copy-to attribute [copy-to="<var class="keyword varname">%1</var>"] uses the name of a file that already exists, so this attribute is ignored. </td><td class="stentry" id="msgs__DOTX064W-extra" headers="msgs__stentry__4">The copy-to attribute is used to copy
|
||
a topic over a document that already exists. Please make sure that any copy-to attributes use a unique name so
|
||
that the copy will not overwrite existing content.</td></tr><tr class="strow" id="msgs__DOTX065W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX065W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Two unique source files each specify copy-to="<var class="keyword varname">%2</var>", which results in a collision. The value associated with href="<var class="keyword varname">%1</var>" is ignored. </td><td class="stentry" id="msgs__DOTX065W-extra" headers="msgs__stentry__4">Two different topics are copied to
|
||
the same location using copy-to; as a result, one of these files would be over-written. Only the first
|
||
instance of this copy-to value will be recognized. Please correct the use of copy-to attributes.</td></tr><tr class="strow" id="msgs__DOTX066W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX066W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Template "<var class="keyword varname">%1</var>" is deprecated. Remove references to this template from your custom XSLT or plug-ins.</td><td class="stentry" id="msgs__DOTX066W-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__DOTX067E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX067E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">No string named '<var class="keyword varname">%1</var>' was found for language '<var class="keyword varname">%2</var>'. Add a mapping for the string '<var class="keyword varname">%1</var>'.</td><td class="stentry" id="msgs__DOTX067E-extra" headers="msgs__stentry__4">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 <var class="keyword varname">%1</var> for your specified language, so the string 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.</td></tr><tr class="strow" id="msgs__DOTX068W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX068W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">A topicref element that references a map contains child topicref elements. Child topicref elements are ignored.</td><td class="stentry" id="msgs__DOTX068W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX069W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX069W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Template mode "<var class="keyword varname">%1</var>" is deprecated. Remove references to this template mode from your custom XSLT or plug-ins.</td><td class="stentry" id="msgs__DOTX069W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX070W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX070W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Target "<var class="keyword varname">%1</var>" is deprecated. Remove references to this target from your custom Ant files.</td><td class="stentry" id="msgs__DOTX070W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX071E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX071E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Conref range: Unable to find conref range end element with ID "<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTX071E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX071W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX071W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Parameter "<var class="keyword varname">%1</var>" on template "<var class="keyword varname">%2</var>" is deprecated. Use parameter "<var class="keyword varname">%3</var>" instead.</td><td class="stentry" id="msgs__DOTX071W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX072I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX072I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Ignoring navtitle within topicgroup. </td><td class="stentry" id="msgs__DOTX072I-extra" headers="msgs__stentry__4">
|
||
</td></tr><tr class="strow" id="msgs__DOTX073I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX073I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Removing broken link to "<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTX073I-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX074W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX074W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">No formatting defined for unknown class attribute value "<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTX074W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX075W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX075W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">A content reference in a constrained document type is pulling content from an unconstrained document type. The reference will resolve, but may result in content that violates one of the document constraints in "<var class="keyword varname">%1</var>". </td><td class="stentry" id="msgs__DOTX075W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__DOTX076E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">DOTX076E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">A content reference in a constrained document type cannot be resolved because it would violate one of the document constraints "<var class="keyword varname">%1</var>". The current constrained document may only reuse content from documents with equivalent constraints.</td><td class="stentry" id="msgs__DOTX076E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__INDX001I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">INDX001I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Index entry '<var class="keyword varname">%1</var>' will be sorted under the "Special characters" heading. </td><td class="stentry" id="msgs__INDX001I-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__INDX002E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">INDX002E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The PDF indexing process could not find the proper sort location for '<var class="keyword varname">%1</var>', so the term has been dropped from the index. </td><td class="stentry" id="msgs__INDX002E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__INDX003E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">INDX003E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The build failed due to problems encountered when sorting the PDF index. </td><td class="stentry" id="msgs__INDX003E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFJ001E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFJ001E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The PDF indexing process could not find the proper sort location for '<var class="keyword varname">%1</var>', so the term has been dropped from the index. </td><td class="stentry" id="msgs__PDFJ001E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFJ002E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFJ002E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The build failed due to problems encountered when sorting the PDF index. Please address any messages located earlier in the log.</td><td class="stentry" id="msgs__PDFJ002E-extra" headers="msgs__stentry__4">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.</td></tr><tr class="strow" id="msgs__PDFJ003I"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFJ003I</span></td><td class="stentry" headers="msgs__stentry__2">Info</td><td class="stentry" headers="msgs__stentry__3">Index entry '<var class="keyword varname">%1</var>' will be sorted under the "Special characters" heading. </td><td class="stentry" id="msgs__PDFJ003I-extra" headers="msgs__stentry__4">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, please
|
||
open an issue with DITA-OT to correct the sort.</td></tr><tr class="strow" id="msgs__PDFX001W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX001W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">There is an index term specified with start="<var class="keyword varname">%1</var>", but there is no matching end for this term. Add an index term in a valid location with end="<var class="keyword varname">%1</var>".</td><td class="stentry" id="msgs__PDFX001W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX002W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX002W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">There are multiple index terms specified with start="<var class="keyword varname">%1</var>", but there is only one term to end this range, or the ranges for this term overlap. Ensure that each term with this start value has a matching end value, and that the specified ranges for this value do not overlap</td><td class="stentry" id="msgs__PDFX002W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX003W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX003W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">There are multiple index entries found to close the index range for "<var class="keyword varname">%1</var>". Ensure that any index term with start="<var class="keyword varname">%1</var>" has only one matching end term with end="<var class="keyword varname">%1</var>".</td><td class="stentry" id="msgs__PDFX003W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX004F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX004F</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">A topic reference was found with href="". Please specify a target or remove the href attribute.</td><td class="stentry" id="msgs__PDFX004F-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX005F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX005F</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The topic reference href="<var class="keyword varname">%1</var>" could not be found. Please correct the reference, or set the scope or format attribute if the target is not a local DITA topic.</td><td class="stentry" id="msgs__PDFX005F-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX007W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX007W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Found an index term with end="<var class="keyword varname">%1</var>", but no starting term was found for this entry. </td><td class="stentry" id="msgs__PDFX007W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX008W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX008W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3">Font definition not found for the logical name or alias '<var class="keyword varname">%1</var>'. </td><td class="stentry" id="msgs__PDFX008W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX009E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX009E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Attribute set reflection cannot handle XSLT element <var class="keyword varname">%1</var>. </td><td class="stentry" id="msgs__PDFX009E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX011E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX011E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">The index term '<var class="keyword varname">%2</var>' uses both an index-see element and <var class="keyword varname">%1</var> element. Convert the index-see element to index-see-also.</td><td class="stentry" id="msgs__PDFX011E-extra" headers="msgs__stentry__4">Found an
|
||
<code class="keyword markupname xmlelement"><index-see></code> element as a child of a term that also exists as a standalone index
|
||
term, or as a term that also uses <code class="keyword markupname xmlelement"><index-see-also></code>. When using
|
||
<code class="keyword markupname xmlelement"><index-see></code> with an index term, that term should not be used to create page
|
||
references and should not reference additional terms. Treating the <code class="keyword markupname xmlelement"><index-see></code> as
|
||
<code class="keyword markupname xmlelement"><index-see-also></code>.</td></tr><tr class="strow" id="msgs__PDFX012E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX012E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3">Found a table row with more entries than allowed. </td><td class="stentry" id="msgs__PDFX012E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__PDFX013F"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">PDFX013F</span></td><td class="stentry" headers="msgs__stentry__2">Fatal</td><td class="stentry" headers="msgs__stentry__3">The PDF file '<var class="keyword varname">%1</var>' could not be generated. </td><td class="stentry" id="msgs__PDFX013F-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__XEPJ001W"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">XEPJ001W</span></td><td class="stentry" headers="msgs__stentry__2">Warning</td><td class="stentry" headers="msgs__stentry__3"><var class="keyword varname">%1</var> </td><td class="stentry" id="msgs__XEPJ001W-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__XEPJ002E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">XEPJ002E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3"><var class="keyword varname">%1</var> </td><td class="stentry" id="msgs__XEPJ002E-extra" headers="msgs__stentry__4"> </td></tr><tr class="strow" id="msgs__XEPJ003E"><td class="stentry" headers="msgs__stentry__1"><span class="keyword msgnum">XEPJ003E</span></td><td class="stentry" headers="msgs__stentry__2">Error</td><td class="stentry" headers="msgs__stentry__3"><var class="keyword varname">%1</var> </td><td class="stentry" id="msgs__XEPJ003E-extra" headers="msgs__stentry__4"> </td></tr></tbody></table></div><nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../topics/troubleshooting-overview.html" title="This section contains information about problems that you might encounter and how to resolve them.">Error messages and troubleshooting</a></div></div><div class="linklist reltasks"><strong>Related tasks</strong><br><ul class="linklist"><li class="linklist"><a class="link" href="../topics/rebuilding-docs.html" title="When you add or remove plug-ins, you can rebuild the documentation to update the information on the extension points, messages, and parameters that are available in your environment.">Rebuilding the DITA-OT documentation</a></li></ul></div></nav></article></main></body></html> |