DITA-messages.html@ 99507

最後變更在這個檔案從99507是 98584,由 vboxsync 提交於 2 年前
Docs: bugref:10302. Setting svn properties of DITA-OT library.
屬性 svn:eol-style 設為 `native` 屬性 svn:keywords 設為 `Author Date Id Revision`
檔案大小: 111.8 KB

行
1	<?xml version="1.0" encoding="UTF-8"?>
2	<!DOCTYPE html
3	PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
4	<html xml:lang="en-us" lang="en-us">
5	<head>
6	<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
7	<meta name="copyright" content="(C) Copyright 2005"/>
8	<meta name="DC.rights.owner" content="(C) Copyright 2005"/>
9	<meta name="DC.Type" content="reference"/>
10	<meta name="DC.Title" content="DITA-OT error messages"/>
11	<meta name="abstract" content="The error messages generated by the DITA Open Toolkit contain a message ID, severity information, and message text. 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."/>
12	<meta name="description" content="The error messages generated by the DITA Open Toolkit contain a message ID, severity information, and message text. 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."/>
13	<meta name="DC.Relation" scheme="URI" content="../readme/troubleshooting-overview.html"/>
14	<meta name="DC.Format" content="XHTML"/>
15	<meta name="DC.Identifier" content="msgs"/>
16	<link rel="stylesheet" type="text/css" href="../commonltr.css"/>
17	<link rel="stylesheet" type="text/css" href="../dita-ot-doc.css"/>
18	<title>DITA-OT error messages</title>
19	</head>
20	<body id="msgs">
21
22	<h1 class="title topictitle1">DITA-OT error messages</h1>
23	<div class="body refbody"><p class="shortdesc">The error messages
24	generated by the DITA Open Toolkit contain a message ID, severity information, and message text.
25	This topic lists each error message generated by the toolkit and provides additional information
26	that might be helpful in understanding and resolving the error condition.</p>
27	<div class="section" id="msgs__overview">
28	<div class="p">Each message ID is composed of a message prefix, a message number, and a letter that indicates
29	the severity (I, W, E, or F). The toolkit uses the following severity scale:<dl class="dl">
30
31	<dt class="dt dlterm">Informational (I)</dt>
32
33	<dd class="dd">The toolkit encountered a condition of which you should be aware. For example, draft
34	comments are enabled and will be rendered in the output.</dd>
35
36
37
38	<dt class="dt dlterm">Warning (W)</dt>
39
40	<dd class="dd">The toolkit encountered a problem that should be corrected. Processing will continue,
41	but the output might not be as expected.</dd>
42
43
44
45	<dt class="dt dlterm">Error (E)</dt>
46
47	<dd class="dd">The toolkit encountered a more severe problem, and the output is affected. For example,
48	some content is missing or invalid, or the content is not rendered in the output</dd>
49
50
51
52	<dt class="dt dlterm">Fatal (F)</dt>
53
54	<dd class="dd">The toolkit encountered a severe condition, processing stopped, and no output is
55	generated.</dd>
56
57
58	</dl>
59	</div>
60
61
62
63	</div>
64	<table cellpadding="4" cellspacing="0" summary="" border="1" class="simpletable"><tr class="sthead"><th valign="bottom" align="left" id="d17474e56" class="stentry" width="13.27433628318584%">Message ID</th>
65	<th valign="bottom" align="left" id="d17474e58" class="stentry" width="15.929203539823009%">Severity</th>
66	<th valign="bottom" align="left" id="d17474e60" class="stentry" width="35.39823008849557%">Message text</th>
67	<th valign="bottom" align="left" id="d17474e62" class="stentry" width="35.39823008849557%">Additional details</th>
68	</tr>
69	<tr id="msgs__DOTA001F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA001F</span></td>
70	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
71	<td valign="top" headers="d17474e60" class="stentry">"<var class="keyword varname">%1</var>" is not a recognized transformation type. Supported transformation types are docbook, eclipsecontent, eclipsehelp, htmlhelp, javahelp, net.sourceforge.dita-ot.html, odt, pdf, pdf2, tocjs, troff, wordrtf, xhtml.</td>
72	<td valign="top" id="DOTA001F-extra" headers="d17474e62" class="stentry">Default transformation types
73	that ship with the toolkit include xhtml, eclipsehelp, pdf (or pdf2), tocjs, htmlhelp, javahelp, odt, eclipsecontent, troff, docbook, and wordrtf.
74	Additional transformation types may be available if toolkit plug-ins are installed.</td>
75	</tr>
76	<tr id="msgs__DOTA002F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA002F</span></td>
77	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
78	<td valign="top" headers="d17474e60" class="stentry">Input file is not specified, or is specified using the wrong parameter. </td>
79	<td valign="top" id="DOTA002F-extra" headers="d17474e62" class="stentry">The input parameter
80	was not specified, so there is no DITA or DITAMAP file to transform. Ensure the parameter
81	is set properly; see <a class="xref" href="dita-ot_ant_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Ant arguments</a> or
82	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Command line tool arguments</a>
83	if you are unsure how to specify the input file.</td>
84	</tr>
85	<tr id="msgs__DOTA003F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA003F</span></td>
86	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
87	<td valign="top" headers="d17474e60" class="stentry">Cannot find the user specified XSLT stylesheet '<var class="keyword varname">%1</var>'. </td>
88	<td valign="top" id="DOTA003F-extra" headers="d17474e62" class="stentry">An alternate
89	stylesheet was specified to run in place of the default XSLT output process, but that
90	stylesheet could not be loaded. Please correct the parameter to specify a valid stylesheet.</td>
91	</tr>
92	<tr id="msgs__DOTA004F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA004F</span></td>
93	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
94	<td valign="top" headers="d17474e60" class="stentry">Invalid DITA topic extension '<var class="keyword varname">%1</var>'. Supported values are '.dita' and '.xml'.</td>
95	<td valign="top" id="DOTA004F-extra" headers="d17474e62" class="stentry">This optional parameter is used
96	to set an extension for DITA topic documents in the temporary processing directory. Only
97	"dita", ".dita", "xml", or ".xml" are allowed.</td>
98	</tr>
99	<tr id="msgs__DOTA006W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA006W</span></td>
100	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
101	<td valign="top" headers="d17474e60" class="stentry">Absolute paths on the local file system are not supported for the CSSPATH parameter. Please use a relative path or full URI instead.</td>
102	<td valign="top" id="DOTA006W-extra" headers="d17474e62" class="stentry">If the CSSPATH uses an
103	absolute path, it should be one that can still be accessed after the files are moved to
104	another system (such as <samp class="ph codeph">http://www.example.org/</samp>). Absolute paths on the
105	local file system will be broken if the content is moved to a new system.</td>
106	</tr>
107	<tr id="msgs__DOTA007E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA007E</span></td>
108	<td valign="top" headers="d17474e58" class="stentry">Error</td>
109	<td valign="top" headers="d17474e60" class="stentry">Cannot find the running-footer file "<var class="keyword varname">%1</var>". Please double check the value to ensure it is specified correctly.</td>
110	<td valign="top" id="DOTA007E-extra" headers="d17474e62" class="stentry">The running footer file,
111	which contains content to be added to the bottom of each XHTML output topic, cannot be located or read. This is
112	usually caused by a typo in the parameter value. You should also ensure that the value is not specified
113	with "file:" as a prefix.</td>
114	</tr>
115	<tr id="msgs__DOTA008E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA008E</span></td>
116	<td valign="top" headers="d17474e58" class="stentry">Error</td>
117	<td valign="top" headers="d17474e60" class="stentry">Cannot find the running-header file "<var class="keyword varname">%1</var>". Please double check the value to ensure it is specified correctly.</td>
118	<td valign="top" id="DOTA008E-extra" headers="d17474e62" class="stentry">The running header file,
119	which contains content to be added to the top of each XHTML output topic, cannot be located or read. This is
120	usually caused by a typo in the parameter value. You should also ensure that the value is not specified
121	with "file:" as a prefix.</td>
122	</tr>
123	<tr id="msgs__DOTA009E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA009E</span></td>
124	<td valign="top" headers="d17474e58" class="stentry">Error</td>
125	<td valign="top" headers="d17474e60" class="stentry">Cannot find the specified heading file "<var class="keyword varname">%1</var>". Please double check the value to ensure it is specified correctly.</td>
126	<td valign="top" id="DOTA009E-extra" headers="d17474e62" class="stentry">The running heading file,
127	which contains content to be added to the <head> section of each XHTML output topic, cannot be located or read. This is
128	usually caused by a typo in the parameter value. You should also ensure that the value is not specified
129	with "file:" as a prefix.</td>
130	</tr>
131	<tr id="msgs__DOTA010E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA010E</span></td>
132	<td valign="top" headers="d17474e58" class="stentry">Error</td>
133	<td valign="top" headers="d17474e60" class="stentry">The Apache FOP program cannot be found in the default location. Please place FOP into the default directory demo/fo/fop/ or update the build file to support your local configuration.</td>
134	<td valign="top" id="DOTA010E-extra" headers="d17474e62" class="stentry">By default, the
135	DITA-OT expects to find Apache FOP in the <span class="ph filepath">fop/</span> directory inside of the PDF plug-in. If you
136	are using an alternate renderer, or if you have placed FOP in a different directory, you will
137	need to update your configuration accordingly.</td>
138	</tr>
139	<tr id="msgs__DOTA011W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA011W</span></td>
140	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
141	<td valign="top" headers="d17474e60" class="stentry">Argument "<var class="keyword varname">%1</var>" is deprecated. This argument is no longer supported in the toolkit.</td>
142	<td valign="top" id="DOTA011W-extra" headers="d17474e62" class="stentry"> </td>
143	</tr>
144	<tr id="msgs__DOTA012W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA012W</span></td>
145	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
146	<td valign="top" headers="d17474e60" class="stentry">Argument "<var class="keyword varname">%1</var>" is deprecated. Please use the argument "<var class="keyword varname">%2</var>" instead.</td>
147	<td valign="top" id="DOTA012W-extra" headers="d17474e62" class="stentry"> </td>
148	</tr>
149	<tr id="msgs__DOTA066F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA066F</span></td>
150	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
151	<td valign="top" headers="d17474e60" class="stentry">Cannot find the user specified XSLT stylesheet '<var class="keyword varname">%1</var>'. </td>
152	<td valign="top" id="DOTA066F-extra" headers="d17474e62" class="stentry">An alternate
153	stylesheet was specified to run in place of the default XSL-FO output process, but that
154	stylesheet could not be loaded. Please correct the parameter to specify a valid stylesheet.</td>
155	</tr>
156	<tr id="msgs__DOTA067W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA067W</span></td>
157	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
158	<td valign="top" headers="d17474e60" class="stentry">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. According to the DITA Specification, the index-see element should be ignored if the parent indexterm contains other indexterm children.</td>
159	<td valign="top" id="DOTA067W-extra" headers="d17474e62" class="stentry">This
160	condition is ignored, as instructed in the OASIS DITA Standard.</td>
161	</tr>
162	<tr id="msgs__DOTA068W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA068W</span></td>
163	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
164	<td valign="top" headers="d17474e60" class="stentry">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. According to the DITA Specification, the index-see-also element should be ignored if the parent indexterm contains other indexterm children.</td>
165	<td valign="top" id="DOTA068W-extra" headers="d17474e62" class="stentry">This
166	condition is ignored, as instructed in the OASIS DITA Standard.</td>
167	</tr>
168	<tr id="msgs__DOTA069F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA069F</span></td>
169	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
170	<td valign="top" headers="d17474e60" class="stentry">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>
171	<td valign="top" id="DOTA069F-extra" headers="d17474e62" class="stentry">Please ensure
172	that the input file path and file name were entered correctly.</td>
173	</tr>
174	<tr id="msgs__DOTA069W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTA069W</span></td>
175	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
176	<td valign="top" headers="d17474e60" class="stentry">Target "<var class="keyword varname">%1</var>" is deprecated. Remove references to this target from your custom XSLT or plug-ins.</td>
177	<td valign="top" id="DOTA069W-extra" headers="d17474e62" class="stentry"> </td>
178	</tr>
179	<tr id="msgs__DOTJ001F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ001F</span></td>
180	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
181	<td valign="top" headers="d17474e60" class="stentry">Invalid command line syntax for the parameter '<var class="keyword varname">%1</var>'. Parameters to the command line tool should use the syntax /parameter:value.</td>
182	<td valign="top" id="DOTJ001F-extra" headers="d17474e62" class="stentry">See
183	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">Command-line tool parameters</a> for a list of available
184	parameters and values.</td>
185	</tr>
186	<tr id="msgs__DOTJ002F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ002F</span></td>
187	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
188	<td valign="top" headers="d17474e60" class="stentry">Unsupported parameter '<var class="keyword varname">%1</var>'. Please refer to the DITA-OT User Guide for supported parameters.</td>
189	<td valign="top" id="DOTJ002F-extra" headers="d17474e62" class="stentry">See
190	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">Command-line tool parameters</a> for a list of available
191	parameters and values.</td>
192	</tr>
193	<tr id="msgs__DOTJ003F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ003F</span></td>
194	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
195	<td valign="top" headers="d17474e60" class="stentry">Parameter '<var class="keyword varname">%1</var>' was specified without a value. Parameters to the command line tool should use the syntax /parameter:value.</td>
196	<td valign="top" id="DOTJ003F-extra" headers="d17474e62" class="stentry">See
197	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">Command-line tool parameters</a> for a list of available
198	parameters and values.</td>
199	</tr>
200	<tr id="msgs__DOTJ004F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ004F</span></td>
201	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
202	<td valign="top" headers="d17474e60" class="stentry">Cannot create temporary processing directory '<var class="keyword varname">%1</var>'. Please ensure that you have permission to create the directory '<var class="keyword varname">%1</var>'.</td>
203	<td valign="top" id="DOTJ004F-extra" headers="d17474e62" class="stentry">The
204	transform was unable to create a temporary processing directory; this is usually caused by
205	account control settings that prevent creating a temporary directory in the specified
206	location. Please verify that you have permission to write to the default location, or
207	specify an alternate temporary directory location. See <a class="xref" href="dita-ot_ant_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Ant arguments</a> or
208	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Command line tool arguments</a>
209	for details on how to specify the temporary directory.</td>
210	</tr>
211	<tr id="msgs__DOTJ005F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ005F</span></td>
212	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
213	<td valign="top" headers="d17474e60" class="stentry">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>
214	<td valign="top" id="DOTJ005F-extra" headers="d17474e62" class="stentry"> </td>
215	</tr>
216	<tr id="msgs__DOTJ006F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ006F</span></td>
217	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
218	<td valign="top" headers="d17474e60" class="stentry">An Ant build file used the following illegal syntax when calling AntInvoker: extparam='<var class="keyword varname">%1</var>'. Please correct the call to AntInvoker when directly calling DITA-OT Java code from Ant; for example, extparam="maplinks=XXXX;other=YYYY".</td>
219	<td valign="top" id="DOTJ006F-extra" headers="d17474e62" class="stentry">This message
220	occurs when an Ant build calls a DITA-OT pipeline module directly instead
221	of using the default call to that module. Please check that all parameters are set correctly
222	in your Ant build. The syntax for extparam is "name1=value1;name2=value2".</td>
223	</tr>
224	<tr id="msgs__DOTJ007E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ007E</span></td>
225	<td valign="top" headers="d17474e58" class="stentry">Error</td>
226	<td valign="top" headers="d17474e60" class="stentry">Duplicate condition in filter file for rule '<var class="keyword varname">%1</var>'. The first encountered condition will be used.</td>
227	<td valign="top" id="DOTJ007E-extra" headers="d17474e62" class="stentry">If a condition
228	is defined more than once (such as setting audience="all" to include, then resetting it to exclude),
229	only the first definition will be used.</td>
230	</tr>
231	<tr id="msgs__DOTJ009E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ009E</span></td>
232	<td valign="top" headers="d17474e58" class="stentry">Error</td>
233	<td valign="top" headers="d17474e60" class="stentry">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>
234	<td valign="top" id="DOTJ009E-extra" headers="d17474e62" class="stentry">The transform
235	was unable to create files properly during the transform; results may not be as expected.</td>
236	</tr>
237	<tr id="msgs__DOTJ012F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ012F</span></td>
238	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
239	<td valign="top" headers="d17474e60" class="stentry">Failed to parse the input file '<var class="keyword varname">%1</var>'. The XML parser reported the following error: </td>
240	<td valign="top" id="DOTJ012F-extra" headers="d17474e62" class="stentry">This message may
241	indicate an invalid input file (such as accidentally specifying a PDF file as input rather
242	than a DITA map file), an input file that uses elements which are not allowed, are not part
243	or a DITA file that has errors and cannot be parsed as XML.
244	You could also be using a specialized DITA document type that needs external plug-ins in order
245	to be parsed correctly. The message issued by the XML parser should provide
246	additional information to help diagnose the cause.</td>
247	</tr>
248	<tr id="msgs__DOTJ013E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ013E</span></td>
249	<td valign="top" headers="d17474e58" class="stentry">Error</td>
250	<td valign="top" headers="d17474e60" class="stentry">Failed to parse the referenced file '<var class="keyword varname">%1</var>'. The XML parser reported the following error: </td>
251	<td valign="top" id="DOTJ013E-extra" headers="d17474e62" class="stentry">This message may
252	indicate a reference to an invalid file (such as accidentally referencing a PDF or unknown
253	XML file as if it was DITA), a referenced file that uses elements which are not allowed,
254	or a referenced DITA file that has errors and cannot be parsed as XML.
255	You could also be using a specialized DITA document type that needs external plug-ins in order
256	to be parsed correctly. The message issued by the XML parser should provide
257	additional information to help diagnose the cause.</td>
258	</tr>
259	<tr id="msgs__DOTJ014W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ014W</span></td>
260	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
261	<td valign="top" headers="d17474e60" class="stentry">Found an indexterm element with no content. Setting the term to ***. </td>
262	<td valign="top" id="DOTJ014W-extra" headers="d17474e62" class="stentry">An empty
263	<indexterm> element was found, and will appear in the index as ***. This
264	index term should be removed from the source.</td>
265	</tr>
266	<tr id="msgs__DOTJ015F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ015F</span></td>
267	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
268	<td valign="top" headers="d17474e60" class="stentry">Log directory cannot be null. Please specify a valid directory for the build log.</td>
269	<td valign="top" id="DOTJ015F-extra" headers="d17474e62" class="stentry"> </td>
270	</tr>
271	<tr id="msgs__DOTJ016F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ016F</span></td>
272	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
273	<td valign="top" headers="d17474e60" class="stentry">Failed to create log directory '<var class="keyword varname">%1</var>'. Please specify a valid directory for the build log.</td>
274	<td valign="top" id="DOTJ016F-extra" headers="d17474e62" class="stentry"> </td>
275	</tr>
276	<tr id="msgs__DOTJ017F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ017F</span></td>
277	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
278	<td valign="top" headers="d17474e60" class="stentry">No input file was specified; failed to initialize log name based on input file. </td>
279	<td valign="top" id="DOTJ017F-extra" headers="d17474e62" class="stentry">The transform
280	failed because the input file was not specified; log file names are based on the name
281	of the input file, so no log could be generated.</td>
282	</tr>
283	<tr id="msgs__DOTJ018I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ018I</span></td>
284	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
285	<td valign="top" headers="d17474e60" class="stentry">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 user guide.</td>
286	<td valign="top" id="DOTJ018I-extra" headers="d17474e62" class="stentry"> </td>
287	</tr>
288	<tr id="msgs__DOTJ020W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ020W</span></td>
289	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
290	<td valign="top" headers="d17474e60" class="stentry">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>
291	<td valign="top" id="DOTJ020W-extra" headers="d17474e62" class="stentry">This will
292	appear when one installed plug-in requires another in order to function correctly, but the
293	required plug-in is not found. The installed plug-in will be ignored.</td>
294	</tr>
295	<tr id="msgs__DOTJ021W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ021W</span></td>
296	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
297	<td valign="top" headers="d17474e60" class="stentry">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>
298	<td valign="top" id="DOTJ021W-extra" headers="d17474e62" class="stentry">This may
299	appear if filter conditions on the root element of a topic cause the entire topic to be filtered
300	out. To remove this message, you could place any filter conditions on the reference to this file,
301	which will prevent the build from accessing this file.</td>
302	</tr>
303	<tr id="msgs__DOTJ022F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ022F</span></td>
304	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
305	<td valign="top" headers="d17474e60" class="stentry">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>
306	<td valign="top" id="DOTJ022F-extra" headers="d17474e62" class="stentry">Either the
307	input file or the ditaval file should change, otherwise your build is explicitly excluding all
308	content.</td>
309	</tr>
310	<tr id="msgs__DOTJ023E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ023E</span></td>
311	<td valign="top" headers="d17474e58" class="stentry">Error</td>
312	<td valign="top" headers="d17474e60" class="stentry">Failed to get the specified image file '<var class="keyword varname">%1</var>', so it will not be included with your output. </td>
313	<td valign="top" id="DOTJ023E-extra" headers="d17474e62" class="stentry">Check
314	whether the image exists in the source location or already exists in the output directory.</td>
315	</tr>
316	<tr id="msgs__DOTJ025E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ025E</span></td>
317	<td valign="top" headers="d17474e58" class="stentry">Error</td>
318	<td valign="top" headers="d17474e60" class="stentry">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 User Guide for additional causes.</td>
319	<td valign="top" id="DOTJ025E-extra" headers="d17474e62" class="stentry">This message
320	should only appear in the following cases: <ul class="ul">
321	<li class="li">Errors earlier in the transform prevented this step of the transform from running; correct any
322	errors and try the build again.</li>
323
324	<li class="li">An Ant build or plug-in is directly calling the toolkit's topic merge
325	module, and is doing so improperly; in this case the Ant build or plug-in needs to be fixed.</li>
326
327	<li class="li">In the past, problems have been encountered when calling this module with an absolute path;
328	this should no longer be an issue, but may be fixed in older releases by updating the Ant build or plug-in.</li>
329	</ul>
330	</td>
331	</tr>
332	<tr id="msgs__DOTJ026E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ026E</span></td>
333	<td valign="top" headers="d17474e58" class="stentry">Error</td>
334	<td valign="top" headers="d17474e60" class="stentry">The "topic merge" did not generate any output. Correct any earlier transform errors and try the build again, or see the DITA-OT User Guide for additional causes.</td>
335	<td valign="top" id="DOTJ026E-extra" headers="d17474e62" class="stentry">This message
336	should only appear if an Ant build or plug-in is directly calling the toolkit's topic merge
337	module, or if earlier errors resulted in problems with some of the content.
338	If the topic merge module is called correctly, then this indicates a program error
339	that should be reported to the DITA-OT development team, at <a class="xref" href="https://github.com/dita-ot/dita-ot/issues" target="_blank">DITA-OT bug and feature tracker</a>.</td>
340	</tr>
341	<tr id="msgs__DOTJ028E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ028E</span></td>
342	<td valign="top" headers="d17474e58" class="stentry">Error</td>
343	<td valign="top" headers="d17474e60" class="stentry">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>
344	<td valign="top" id="DOTJ028E-extra" headers="d17474e62" class="stentry">When
345	referencing a non-DITA file, the format attribute should indicate the type of file referenced
346	(such as "html" for HTML topics or "pdf" for PDF files). Otherwise, the transform may attempt
347	to parse the referenced document as a DITA topic.</td>
348	</tr>
349	<tr id="msgs__DOTJ029I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ029I</span></td>
350	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
351	<td valign="top" headers="d17474e60" class="stentry">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>
352	<td valign="top" id="DOTJ029I-extra" headers="d17474e62" class="stentry">The domains
353	attribute is used in specialized DITA documents to help determine which domain elements are legal.
354	This message will only appear if DITA specialization was not defined properly.</td>
355	</tr>
356	<tr id="msgs__DOTJ030I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ030I</span></td>
357	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
358	<td valign="top" headers="d17474e60" class="stentry">No 'class' attribute for 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>
359	<td valign="top" id="DOTJ030I-extra" headers="d17474e62" class="stentry">All
360	specialized DITA elements must define a class attribute to provide ancestry information.
361	This message will only appear a specialized DITA element did not define a class attribute.</td>
362	</tr>
363	<tr id="msgs__DOTJ031I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ031I</span></td>
364	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
365	<td valign="top" headers="d17474e60" class="stentry">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>
366	<td valign="top" id="DOTJ031I-extra" headers="d17474e62" class="stentry">This informational
367	message is intended to help you catch filter conditions that may have been specified improperly;
368	if the value is correct, no action is needed.</td>
369	</tr>
370	<tr id="msgs__DOTJ033E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ033E</span></td>
371	<td valign="top" headers="d17474e58" class="stentry">Error</td>
372	<td valign="top" headers="d17474e60" class="stentry">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>
373	<td valign="top" id="DOTJ033E-extra" headers="d17474e62" class="stentry"> </td>
374	</tr>
375	<tr id="msgs__DOTJ034F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ034F</span></td>
376	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
377	<td valign="top" headers="d17474e60" class="stentry">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>
378	<td valign="top" id="DOTJ034F-extra" headers="d17474e62" class="stentry">DITA processing
379	is based on class attributes defined for every element. Usually these are defaulted in the DTD or
380	Schema; if no DTD or Schema is used, the class attributes must be explicitly included in the
381	map or topic.</td>
382	</tr>
383	<tr id="msgs__DOTJ035F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ035F</span></td>
384	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
385	<td valign="top" headers="d17474e60" class="stentry">The file "<var class="keyword varname">%1</var>" referenced by "<var class="keyword varname">%2</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>
386	<td valign="top" id="DOTJ035F-extra" headers="d17474e62" class="stentry">This
387	will appear when a topic is outside the scope of the map; for example, if the main input map references
388	<span class="ph filepath">"../other-directory/some.dita"</span>. The result would cause an output file to be
389	created outside of the output directory. Please see <a class="xref" href="dita-ot_ant_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Ant arguments (outer.control and generate.copy.outer)</a> or
390	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Command line tool arguments (/outercontrol and /generateouter)</a> for more details.</td>
391	</tr>
392	<tr id="msgs__DOTJ036W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ036W</span></td>
393	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
394	<td valign="top" headers="d17474e60" class="stentry">The file "<var class="keyword varname">%1</var>" referenced by "<var class="keyword varname">%2</var>" is outside the scope of the input dita/map 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 "<var class="keyword varname">%1</var>" into the input dita/map directory.</td>
395	<td valign="top" id="DOTJ036W-extra" headers="d17474e62" class="stentry">This
396	will appear when a topic is outside the scope of the map; for example, if the main input map references
397	<span class="ph filepath">"../other-directory/some.dita"</span>. The result would cause an output file to be
398	created outside of the output directory. Please see <a class="xref" href="dita-ot_ant_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Ant arguments (outer.control and generate.copy.outer)</a> or
399	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Command line tool arguments (/outercontrol and /generateouter)</a> for more details.</td>
400	</tr>
401	<tr id="msgs__DOTJ037W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ037W</span></td>
402	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
403	<td valign="top" headers="d17474e60" class="stentry">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>
404	<td valign="top" id="DOTJ037W-extra" headers="d17474e62" class="stentry">DITA processing
405	is based on class attributes defined for every element. Usually these are defaulted in the DTD or
406	Schema; if validation against the DTD or Schema is turned off, the class attributes must be explicitly included in the
407	map or topic.</td>
408	</tr>
409	<tr id="msgs__DOTJ038E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ038E</span></td>
410	<td valign="top" headers="d17474e58" class="stentry">Error</td>
411	<td valign="top" headers="d17474e60" class="stentry">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>
412	<td valign="top" id="DOTJ038E-extra" headers="d17474e62" class="stentry">This appears
413	to indicate an error in creating specialized metadata elements. Please verify that the document
414	type you are using is complete and complies with DITA Specialization rules.</td>
415	</tr>
416	<tr id="msgs__DOTJ039E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ039E</span></td>
417	<td valign="top" headers="d17474e58" class="stentry">Error</td>
418	<td valign="top" headers="d17474e60" class="stentry">There is no target specified for conref push action "pushafter". Found in file="<var class="keyword varname">%1</var>", element="<var class="keyword varname">%2</var>". Please add <elementname conref="pushtarget" conaction="mark"> before current element.</td>
419	<td valign="top" id="DOTJ039E-extra" headers="d17474e62" class="stentry">Please see
420	the topic on <a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/common/theconactionattribute.html" target="_blank">Conref Push</a> in the DITA specification for details on
421	expected syntax for this function.</td>
422	</tr>
423	<tr id="msgs__DOTJ040E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ040E</span></td>
424	<td valign="top" headers="d17474e58" class="stentry">Error</td>
425	<td valign="top" headers="d17474e60" class="stentry">An element uses the attribute conaction="replace", but a conref attribute is not found in the expected location. Found in file="<var class="keyword varname">%1</var>", element="<var class="keyword varname">%2</var>". </td>
426	<td valign="top" id="DOTJ040E-extra" headers="d17474e62" class="stentry">Please see
427	the topic on <a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/common/theconactionattribute.html" target="_blank">Conref Push</a> in the DITA specification for details on
428	expected syntax for this function.</td>
429	</tr>
430	<tr id="msgs__DOTJ041E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ041E</span></td>
431	<td valign="top" headers="d17474e58" class="stentry">Error</td>
432	<td valign="top" headers="d17474e60" class="stentry">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>
433	<td valign="top" id="DOTJ041E-extra" headers="d17474e62" class="stentry">The conref
434	attribute must be a URI reference to a DITA element. Please see the topic on
435	<a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/uri-based-addressing.html" target="_blank">URI-based
436	addressing</a> in the DITA specification for details on the expected syntax.</td>
437	</tr>
438	<tr id="msgs__DOTJ042E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ042E</span></td>
439	<td valign="top" headers="d17474e58" class="stentry">Error</td>
440	<td valign="top" headers="d17474e60" class="stentry">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>
441	<td valign="top" id="DOTJ042E-extra" headers="d17474e62" class="stentry">The conref
442	push function was used to replace a single element with two or more alternatives. Only one element may directly
443	replace another using conref push. See <a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/common/theconactionattribute.html" target="_blank">Conref Push</a> in the DITA specification for more information about
444	the conref push "replace" function.</td>
445	</tr>
446	<tr id="msgs__DOTJ043W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ043W</span></td>
447	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
448	<td valign="top" headers="d17474e60" class="stentry">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>
449	<td valign="top" id="DOTJ043W-extra" headers="d17474e62" class="stentry">The target
450	for a conref push action does not exist; please make sure that the syntax is correct and that
451	the target exists. See the topic on <a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/uri-based-addressing.html" target="_blank">URI-based
452	addressing</a> in the DITA specification for details on the expected syntax. If the syntax
453	is correct, it is possible that the target was filtered out of your build using a DITAVAL file.</td>
454	</tr>
455	<tr id="msgs__DOTJ044W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ044W</span></td>
456	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
457	<td valign="top" headers="d17474e60" class="stentry">There is a redundant conref action "pushbefore". Found in file="<var class="keyword varname">%1</var>", element="<var class="keyword varname">%2</var>". Please make sure that "mark" and "pushbefore" occur in pairs.</td>
458	<td valign="top" id="DOTJ044W-extra" headers="d17474e62" class="stentry">Please see
459	the topic on <a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/common/theconactionattribute.html" target="_blank">Conref Push</a> in the DITA specification for details on
460	expected syntax for this function.</td>
461	</tr>
462	<tr id="msgs__DOTJ045I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ045I</span></td>
463	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
464	<td valign="top" headers="d17474e60" class="stentry">The key "<var class="keyword varname">%1</var>" is defined more than once in the same map file. The reference href="<var class="keyword varname">%2</var>" is ignored. </td>
465	<td valign="top" id="DOTJ045I-extra" headers="d17474e62" class="stentry">No response
466	is needed if the keys are defined as expected; this is informational only, to help catch
467	incorrectly defined keys.</td>
468	</tr>
469	<tr id="msgs__DOTJ046E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ046E</span></td>
470	<td valign="top" headers="d17474e58" class="stentry">Error</td>
471	<td valign="top" headers="d17474e60" class="stentry">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>
472	<td valign="top" id="DOTJ046E-extra" headers="d17474e62" class="stentry">See
473	<a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/common/theconkeyrefattribute.html" target="_blank">the conkeyref definition</a>
474	for details on expected syntax and usage.</td>
475	</tr>
476	<tr id="msgs__DOTJ047I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ047I</span></td>
477	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
478	<td valign="top" headers="d17474e60" class="stentry">Unable to find key definition for keyref="<var class="keyword varname">%1</var>", href may be used as fallback if it exists. </td>
479	<td valign="top" id="DOTJ047I-extra" headers="d17474e62" class="stentry">This message
480	is intended to help you locate incorrectly specified keys; if the key was specified correctly,
481	this message may be ignored.</td>
482	</tr>
483	<tr id="msgs__DOTJ049W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ049W</span></td>
484	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
485	<td valign="top" headers="d17474e60" class="stentry">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>
486	<td valign="top" id="DOTJ049W-extra" headers="d17474e62" class="stentry">A DITA
487	Subject Scheme map was used to limit values that are available to the specified attribute.
488	Please correct the attribute so that it uses one of the allowed values.</td>
489	</tr>
490	<tr id="msgs__DOTJ050W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ050W</span></td>
491	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
492	<td valign="top" headers="d17474e60" class="stentry">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>
493	<td valign="top" id="DOTJ050W-extra" headers="d17474e62" class="stentry">The
494	Eclipse index will contain a value such as "See also otherEntry", but otherEntry does not exist in this index.
495	The index reference will be broken unless this plug-in is <em class="ph i">always</em> loaded into Eclipse with
496	another plug-in that defines otherEntry as an index term.</td>
497	</tr>
498	<tr id="msgs__DOTJ051E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ051E</span></td>
499	<td valign="top" headers="d17474e58" class="stentry">Error</td>
500	<td valign="top" headers="d17474e60" class="stentry">Unable to load target for coderef "<var class="keyword varname">%1</var>". </td>
501	<td valign="top" id="DOTJ051E-extra" headers="d17474e62" class="stentry">The target for
502	a coderef element, which specifies an external text-based file, could not be located or loaded. Please
503	verify that the reference is correct.<p class="p">Note that for security reasons, references to code samples outside of the scope
504	of the map directory are not supported by default, as this could allow a reference to access and
505	display any restricted or hidden file on the system. If you are certain that the path is valid and
506	the file should be loaded, the current workaround is to set a parameter to allow
507	these references. See <a class="xref" href="dita-ot_ant_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Ant arguments (outer.control and generate.copy.outer)</a> or
508	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">DITA-OT Command line tool arguments (/outercontrol and /generateouter)</a> for details.</p>
509	</td>
510	</tr>
511	<tr id="msgs__DOTJ052E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ052E</span></td>
512	<td valign="top" headers="d17474e58" class="stentry">Error</td>
513	<td valign="top" headers="d17474e60" class="stentry">Code reference charset "<var class="keyword varname">%1</var>" not supported. See the DITA-OT User guide for supported charset values on the format attribute.</td>
514	<td valign="top" id="DOTJ052E-extra" headers="d17474e62" class="stentry">The DITA-OT
515	supports a special syntax on coderef elements to specify the character set of the target
516	document. See <a class="xref" href="../dev_ref/extended-functionality.html">Extended functionality</a> for details
517	on the expected syntax.</td>
518	</tr>
519	<tr id="msgs__DOTJ053W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ053W</span></td>
520	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
521	<td valign="top" headers="d17474e60" class="stentry">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>
522	<td valign="top" id="DOTJ053W-extra" headers="d17474e62" class="stentry">By default,
523	the DITA-OT supports the extensions "dita" and "xml" for DITA topics, as mandated by the
524	DITA Specification. Please verify that your topics use one of these extensions, or configure
525	the toolkit to allow additional extensions.</td>
526	</tr>
527	<tr id="msgs__DOTJ054E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ054E</span></td>
528	<td valign="top" headers="d17474e58" class="stentry">Error</td>
529	<td valign="top" headers="d17474e60" class="stentry">Unable to parse invalid <var class="keyword varname">%1</var> attribute value "<var class="keyword varname">%2</var>" </td>
530	<td valign="top" id="DOTJ054E-extra" headers="d17474e62" class="stentry"> </td>
531	</tr>
532	<tr id="msgs__DOTJ055E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ055E</span></td>
533	<td valign="top" headers="d17474e58" class="stentry">Error</td>
534	<td valign="top" headers="d17474e60" class="stentry">Invalid key name "<var class="keyword varname">%1</var>". </td>
535	<td valign="top" id="DOTJ055E-extra" headers="d17474e62" class="stentry"> </td>
536	</tr>
537	<tr id="msgs__DOTJ056E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ056E</span></td>
538	<td valign="top" headers="d17474e58" class="stentry">Error</td>
539	<td valign="top" headers="d17474e60" class="stentry">Invalid xml:lang "<var class="keyword varname">%1</var>". </td>
540	<td valign="top" id="DOTJ056E-extra" headers="d17474e62" class="stentry"> </td>
541	</tr>
542	<tr id="msgs__DOTJ057E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTJ057E</span></td>
543	<td valign="top" headers="d17474e58" class="stentry">Error</td>
544	<td valign="top" headers="d17474e60" class="stentry">The id attribute value "<var class="keyword varname">%1</var>" is not unique within the topic that contains it. </td>
545	<td valign="top" id="DOTJ057E-extra" headers="d17474e62" class="stentry"> </td>
546	</tr>
547	<tr id="msgs__DOTX001W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX001W</span></td>
548	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
549	<td valign="top" headers="d17474e60" class="stentry">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>
550	<td valign="top" id="DOTX001W-extra" headers="d17474e62" class="stentry">This build
551	uses generated text, such as the phrase "Related information" (which is generated above many
552	link groups). The toolkit was unable to locate the string <var class="keyword varname">%1</var> for your
553	specified language, so the string will appear in the default language. This generally indicates
554	that the toolkit's strings needs to be updated to support your language, or that your language
555	setting is incorrect.</td>
556	</tr>
557	<tr id="msgs__DOTX002W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX002W</span></td>
558	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
559	<td valign="top" headers="d17474e60" class="stentry">The title element or attribute in the ditamap is required for Eclipse output. </td>
560	<td valign="top" id="DOTX002W-extra" headers="d17474e62" class="stentry">The Eclipse
561	help system requires a title in the project files generated from your map. Please add
562	a title to your input map to get valid Eclipse help output.</td>
563	</tr>
564	<tr id="msgs__DOTX003I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX003I</span></td>
565	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
566	<td valign="top" headers="d17474e60" class="stentry">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>
567	<td valign="top" id="DOTX003I-extra" headers="d17474e62" class="stentry">Eclipse uses
568	anchor references to connect with other TOC files. For this to work in content generated
569	from a DITA map, the anchorref element must reference either an existing Eclipse TOC XML file,
570	or another DITA map (which will presumably also be converted to an Eclipse TOC).</td>
571	</tr>
572	<tr id="msgs__DOTX004I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX004I</span></td>
573	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
574	<td valign="top" headers="d17474e60" class="stentry">Found a navref element that does not reference anything. The navref element should either reference another dita map or an Eclipse XML file.</td>
575	<td valign="top" id="DOTX004I-extra" headers="d17474e62" class="stentry">Eclipse builds use
576	DITA's <navref> element to pull in other Eclipse TOC files. The build found a <navref>
577	element that does not reference any other file; the element will be ignored.</td>
578	</tr>
579	<tr id="msgs__DOTX005E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX005E</span></td>
580	<td valign="top" headers="d17474e58" class="stentry">Error</td>
581	<td valign="top" headers="d17474e60" class="stentry">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>
582	<td valign="top" id="DOTX005E-extra" headers="d17474e62" class="stentry">To remove
583	this message, provide a navigation title for the referenced object in the map or topic,
584	or ensure that you are referencing a valid local DITA target.</td>
585	</tr>
586	<tr id="msgs__DOTX006E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX006E</span></td>
587	<td valign="top" headers="d17474e58" class="stentry">Error</td>
588	<td valign="top" headers="d17474e60" class="stentry">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>
589	<td valign="top" id="DOTX006E-extra" headers="d17474e62" class="stentry">Set the
590	format attribute to identify the format of the file. If the reference is to a DITA document,
591	ensure that the document uses a valid DITA extension (default supported extensions are "dita" and "xml").</td>
592	</tr>
593	<tr id="msgs__DOTX007I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX007I</span></td>
594	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
595	<td valign="top" headers="d17474e60" class="stentry">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>
596	<td valign="top" id="DOTX007I-extra" headers="d17474e62" class="stentry">The HTML Help compiler
597	will only include some types of information in the compiled CHM file; the current reference will not be included.</td>
598	</tr>
599	<tr id="msgs__DOTX008E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX008E</span></td>
600	<td valign="top" headers="d17474e58" class="stentry">Error</td>
601	<td valign="top" headers="d17474e60" class="stentry">File '<var class="keyword varname">%1</var>' does not exist or cannot be loaded. </td>
602	<td valign="top" id="DOTX008E-extra" headers="d17474e62" class="stentry">Ensure that the
603	file exists and can be read. <span class="ph">Note that the name
604	of the file in this message may have be changed to use a standard dita topic file extension ('.dita' or '.xml'),
605	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>
606	</tr>
607	<tr id="msgs__DOTX008W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX008W</span></td>
608	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
609	<td valign="top" headers="d17474e60" class="stentry">File '<var class="keyword varname">%1</var>' cannot be loaded, and no navigation title is specified for the table of contents. </td>
610	<td valign="top" id="DOTX008W-extra" headers="d17474e62" class="stentry">To fix the table
611	of contents, specify a navigation title in your map or ensure that the referenced file is local and
612	can be accessed. <span class="ph">Note that the name
613	of the file in this message may have be changed to use a standard dita topic file extension ('.dita' or '.xml'),
614	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>
615	</tr>
616	<tr id="msgs__DOTX009W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX009W</span></td>
617	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
618	<td valign="top" headers="d17474e60" class="stentry">Could not retrieve a title from '<var class="keyword varname">%1</var>'. Using '<var class="keyword varname">%2</var>' instead. </td>
619	<td valign="top" id="DOTX009W-extra" headers="d17474e62" class="stentry">No title was
620	found in the specified topic, so the table of contents will use the indicated fallback value for this topic.</td>
621	</tr>
622	<tr id="msgs__DOTX010E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX010E</span></td>
623	<td valign="top" headers="d17474e58" class="stentry">Error</td>
624	<td valign="top" headers="d17474e60" class="stentry">Unable to find target for conref="<var class="keyword varname">%1</var>". </td>
625	<td valign="top" id="DOTX010E-extra" headers="d17474e62" class="stentry">The conref
626	attribute must be a URI reference to an existing DITA element. Please see the topic on
627	<a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/uri-based-addressing.html" target="_blank">URI-based
628	addressing</a> in the DITA specification for details on the expected syntax. <span class="ph" id="msgs__changeExtension">Note that the name
629	of the file in this message may have be changed to use a standard dita topic file extension ('.dita' or '.xml'),
630	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
631	exists in your source file, check to make sure it is not filtered out of the build with a DITAVAL file (which
632	will remove the target before conref processing runs).</p>
633	</td>
634	</tr>
635	<tr id="msgs__DOTX011W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX011W</span></td>
636	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
637	<td valign="top" headers="d17474e60" class="stentry">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>
638	<td valign="top" id="DOTX011W-extra" headers="d17474e62" class="stentry">When pulling content
639	with a conref attribute, you may only pull from a single element, but the target ID appears twice
640	in the referenced topic. <span class="ph">Note that the name
641	of the file in this message may have be changed to use a standard dita topic file extension ('.dita' or '.xml'),
642	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>
643	</tr>
644	<tr id="msgs__DOTX012W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX012W</span></td>
645	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
646	<td valign="top" headers="d17474e60" class="stentry">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>
647	<td valign="top" id="DOTX012W-extra" headers="d17474e62" class="stentry">This message
648	is deprecated and should no longer appear in any logs.</td>
649	</tr>
650	<tr id="msgs__DOTX013E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX013E</span></td>
651	<td valign="top" headers="d17474e58" class="stentry">Error</td>
652	<td valign="top" headers="d17474e60" class="stentry">A element with attribute conref="<var class="keyword varname">%1</var>" indirectly includes itself, which results in an infinite loop. </td>
653	<td valign="top" id="DOTX013E-extra" headers="d17474e62" class="stentry">This may
654	appear if (for example) you have a <samp class="ph codeph"><ph></samp> element that references another phrase,
655	but that phrase itself contains a reference to the original. This will result in an infinite loop.
656	The toolkit will stop following the conref trail when this is detected; you will need to correct
657	the reference in your source files. <span class="ph">Note that the name
658	of the file in this message may have be changed to use a standard dita topic file extension ('.dita' or '.xml'),
659	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>
660	</tr>
661	<tr id="msgs__DOTX014E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX014E</span></td>
662	<td valign="top" headers="d17474e58" class="stentry">Error</td>
663	<td valign="top" headers="d17474e60" class="stentry">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>
664	<td valign="top" id="DOTX014E-extra" headers="d17474e62" class="stentry">The conref
665	attribute must be a URI reference to a DITA element. Please see the topic on
666	<a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/uri-based-addressing.html" target="_blank">URI-based
667	addressing</a> in the DITA specification for details on the expected syntax.</td>
668	</tr>
669	<tr id="msgs__DOTX015E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX015E</span></td>
670	<td valign="top" headers="d17474e58" class="stentry">Error</td>
671	<td valign="top" headers="d17474e60" class="stentry">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>
672	<td valign="top" id="DOTX015E-extra" headers="d17474e62" class="stentry">The conref
673	attribute must be a URI reference to a DITA element. Please see the topic on
674	<a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/uri-based-addressing.html" target="_blank">URI-based
675	addressing</a> in the DITA specification for details on the expected syntax. <span class="ph">Note that the name
676	of the file in this message may have be changed to use a standard dita topic file extension ('.dita' or '.xml'),
677	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>
678	</tr>
679	<tr id="msgs__DOTX016W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX016W</span></td>
680	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
681	<td valign="top" headers="d17474e60" class="stentry">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>
682	<td valign="top" id="DOTX016W-extra" headers="d17474e62" class="stentry">This warning
683	is intended to catch instances where a non-DITA format setting unexpectedly cascades to a
684	DITA topic, which will prevent the topic from being processed. To remove this message, set
685	the format attribute directly on the indicated reference. <span class="ph">Note that the name
686	of the file in this message may have be changed to use a standard dita topic file extension ('.dita' or '.xml'),
687	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>
688	</tr>
689	<tr id="msgs__DOTX017E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX017E</span></td>
690	<td valign="top" headers="d17474e58" class="stentry">Error</td>
691	<td valign="top" headers="d17474e60" class="stentry">Found a link or cross reference with an empty href attribute (href=""). Remove the empty href attribute or provide a value.</td>
692	<td valign="top" id="DOTX017E-extra" headers="d17474e62" class="stentry">Found a value such as
693	<xref href="">link text</xref>. The empty href attribute is not serving a purpose and has caused
694	problems with some tools in the past; you should remove the attribute entirely or specify a value.</td>
695	</tr>
696	<tr id="msgs__DOTX018I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX018I</span></td>
697	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
698	<td valign="top" headers="d17474e60" class="stentry">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>
699	<td valign="top" id="DOTX018I-extra" headers="d17474e62" class="stentry">The type
700	attribute in DITA is intended to describe the type of the target; for example, a reference to a
701	concept topic may use type="concept". Generally, this attribute
702	is optional, and the DITA-OT build will automatically determine the value during processing. In this
703	case, the type attribute lists a more general type than what is actually found. This is not an error
704	but may result in unexpected sorting for links to this topic.</td>
705	</tr>
706	<tr id="msgs__DOTX019W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX019W</span></td>
707	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
708	<td valign="top" headers="d17474e60" class="stentry">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>
709	<td valign="top" id="DOTX019W-extra" headers="d17474e62" class="stentry">The type
710	attribute in DITA is intended to describe the type of the target; for example, a reference to a
711	concept topic may use type="concept". Generally, this attribute
712	is optional, and the DITA-OT build will automatically determine the value during processing. In
713	this case, the specified type value does not match the target, which may cause your links to
714	sort inappropriately.</td>
715	</tr>
716	<tr id="msgs__DOTX020E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX020E</span></td>
717	<td valign="top" headers="d17474e58" class="stentry">Error</td>
718	<td valign="top" headers="d17474e60" class="stentry">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>
719	<td valign="top" id="DOTX020E-extra" headers="d17474e62" class="stentry">The DITA-OT is only able
720	to dynamically retrieve titles when the target is a local (not peer or external) DITA resource.</td>
721	</tr>
722	<tr id="msgs__DOTX021E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX021E</span></td>
723	<td valign="top" headers="d17474e58" class="stentry">Error</td>
724	<td valign="top" headers="d17474e60" class="stentry">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>
725	<td valign="top" id="DOTX021E-extra" headers="d17474e62" class="stentry">The DITA-OT is only able
726	to dynamically retrieve titles when the target is a local DITA resource.</td>
727	</tr>
728	<tr id="msgs__DOTX022W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX022W</span></td>
729	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
730	<td valign="top" headers="d17474e60" class="stentry">Unable to retrieve navtitle from target: '<var class="keyword varname">%1</var>'. Using linktext (specified in topicmeta) as the navigation title. </td>
731	<td valign="top" id="DOTX022W-extra" headers="d17474e62" class="stentry">The build
732	was unable to get a title from the referenced topic; instead, a navigation title will be
733	created based on the specified <linktext> element inside of <topicmeta>.</td>
734	</tr>
735	<tr id="msgs__DOTX023W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX023W</span></td>
736	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
737	<td valign="top" headers="d17474e60" class="stentry">Unable to retrieve navtitle from target: '<var class="keyword varname">%1</var>'. </td>
738	<td valign="top" id="DOTX023W-extra" headers="d17474e62" class="stentry">If the target is
739	a local DITA topic, ensure the reference is correct and the topic is available. Otherwise, provide a
740	navigation title, and ensure the scope and format attributes are set appropriately.</td>
741	</tr>
742	<tr id="msgs__DOTX024E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX024E</span></td>
743	<td valign="top" headers="d17474e58" class="stentry">Error</td>
744	<td valign="top" headers="d17474e60" class="stentry">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>
745	<td valign="top" id="DOTX024E-extra" headers="d17474e62" class="stentry">The DITA-OT is only able
746	to dynamically retrieve titles and link text when the target is a local (not peer or external) DITA resource.</td>
747	</tr>
748	<tr id="msgs__DOTX025E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX025E</span></td>
749	<td valign="top" headers="d17474e58" class="stentry">Error</td>
750	<td valign="top" headers="d17474e60" class="stentry">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>
751	<td valign="top" id="DOTX025E-extra" headers="d17474e62" class="stentry">The DITA-OT is only able
752	to dynamically retrieve titles when the target is a local DITA resource.</td>
753	</tr>
754	<tr id="msgs__DOTX026W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX026W</span></td>
755	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
756	<td valign="top" headers="d17474e60" class="stentry">Unable to retrieve linktext from target: '<var class="keyword varname">%1</var>'. Using navigation title as fallback. </td>
757	<td valign="top" id="DOTX026W-extra" headers="d17474e62" class="stentry">The referenc to this document
758	did not specify any link text for generated map-based links; the navigation title will be used as fallback.</td>
759	</tr>
760	<tr id="msgs__DOTX027W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX027W</span></td>
761	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
762	<td valign="top" headers="d17474e60" class="stentry">Unable to retrieve linktext from target: '<var class="keyword varname">%1</var>'. </td>
763	<td valign="top" id="DOTX027W-extra" headers="d17474e62" class="stentry">The referenced file
764	did not specify any link text for generated map-based links, and no fallback text could be located. Any links
765	generated from this reference will have incorrect link text.</td>
766	</tr>
767	<tr id="msgs__DOTX028E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX028E</span></td>
768	<td valign="top" headers="d17474e58" class="stentry">Error</td>
769	<td valign="top" headers="d17474e60" class="stentry">Link or cross reference must contain a valid href or keyref attribute; no link target is specified. </td>
770	<td valign="top" id="DOTX028E-extra" headers="d17474e62" class="stentry">The link
771	or cross reference has no target specified and will not generate a link.</td>
772	</tr>
773	<tr id="msgs__DOTX029I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX029I</span></td>
774	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
775	<td valign="top" headers="d17474e60" class="stentry">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>
776	<td valign="top" id="DOTX029I-extra" headers="d17474e62" class="stentry">The type
777	attribute in DITA is intended to describe the type of the target; for example, a reference to a
778	concept topic may use type="concept". Generally, this attribute
779	is optional, and the DITA-OT build will automatically determine the value during processing. In this
780	case, the type attribute lists a more general type than what is actually found. This is not an error
781	but may result in unexpected sorting for links to this topic.</td>
782	</tr>
783	<tr id="msgs__DOTX030W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX030W</span></td>
784	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
785	<td valign="top" headers="d17474e60" class="stentry">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>
786	<td valign="top" id="DOTX030W-extra" headers="d17474e62" class="stentry">The type
787	attribute in DITA is intended to describe the type of the target; for example, a reference to a
788	concept topic may use type="concept". Generally, this attribute
789	is optional, and the DITA-OT build will automatically determine the value during processing. In
790	this case, the specified type value does not match the target, which may cause your links to
791	sort inappropriately.</td>
792	</tr>
793	<tr id="msgs__DOTX031E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX031E</span></td>
794	<td valign="top" headers="d17474e58" class="stentry">Error</td>
795	<td valign="top" headers="d17474e60" class="stentry">The file <var class="keyword varname">%1</var> is not available to resolve link information. </td>
796	<td valign="top" id="DOTX031E-extra" headers="d17474e62" class="stentry">The build
797	attempted to access the specified file in order to retrive a title or short description, but the
798	file could not be found. If the file exists, it is possible that a DITAVAL file was used to remove
799	the file's contents from the build. Be aware that the path information above may not match the link in your topic.</td>
800	</tr>
801	<tr id="msgs__DOTX032E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX032E</span></td>
802	<td valign="top" headers="d17474e58" class="stentry">Error</td>
803	<td valign="top" headers="d17474e60" class="stentry">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>
804	<td valign="top" id="DOTX032E-extra" headers="d17474e62" class="stentry">When a link
805	or cross reference does not have content, the build will attempt to pull the target's title for use
806	as link text. If the target is unavailable, be sure to set the scope attribute to an appropriate value.
807	If the target does not have a title (such as when linking to a paragraph), be sure to provide
808	link text inside the cross reference.</td>
809	</tr>
810	<tr id="msgs__DOTX033E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX033E</span></td>
811	<td valign="top" headers="d17474e58" class="stentry">Error</td>
812	<td valign="top" headers="d17474e60" class="stentry">Unable to generate link text for a cross reference to a list item: '<var class="keyword varname">%1</var>' </td>
813	<td valign="top" id="DOTX033E-extra" headers="d17474e62" class="stentry">An <xref>
814	element specifies type="li", which indicates a link to a list item, but the item number could
815	not be determined to use as link text. Please specify link text inside the reference, or ensure
816	that you are referencing an available list item.</td>
817	</tr>
818	<tr id="msgs__DOTX034E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX034E</span></td>
819	<td valign="top" headers="d17474e58" class="stentry">Error</td>
820	<td valign="top" headers="d17474e60" class="stentry">Unable to generate link text for a cross reference to an undered list item: '<var class="keyword varname">%1</var>' </td>
821	<td valign="top" id="DOTX034E-extra" headers="d17474e62" class="stentry">The cross reference
822	goes to a list item in an unordered list. The process could not automatically generate link text because
823	the list item is not numbered. Please provide link text within the cross reference.</td>
824	</tr>
825	<tr id="msgs__DOTX035E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX035E</span></td>
826	<td valign="top" headers="d17474e58" class="stentry">Error</td>
827	<td valign="top" headers="d17474e60" class="stentry">Unable to generate the correct number for a cross reference to a footnote: '<var class="keyword varname">%1</var>' </td>
828	<td valign="top" id="DOTX035E-extra" headers="d17474e62" class="stentry">An <xref>
829	element specifies type="fn", which indicates a link to a footnote, but the footnote number could
830	not be determined to use as link text. Please specify link text inside the reference, or ensure
831	that you are referencing an available footnote.</td>
832	</tr>
833	<tr id="msgs__DOTX036E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX036E</span></td>
834	<td valign="top" headers="d17474e58" class="stentry">Error</td>
835	<td valign="top" headers="d17474e60" class="stentry">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>
836	<td valign="top" id="DOTX036E-extra" headers="d17474e62" class="stentry">An <xref>
837	element specifies type="dlentry", which indicates a link to a definition list entry, but the term could
838	not be located to use as link text. Please specify link text inside the reference, or ensure
839	that you are referencing an available definition list entry</td>
840	</tr>
841	<tr id="msgs__DOTX037W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX037W</span></td>
842	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
843	<td valign="top" headers="d17474e60" class="stentry">No title found for this document; using "***" in XHTML title bar. </td>
844	<td valign="top" id="DOTX037W-extra" headers="d17474e62" class="stentry">No title
845	was found for the current document, so the XHTML output file will set the <title>
846	to "***". This value generally appears in the title bar at the top of a browser.</td>
847	</tr>
848	<tr id="msgs__DOTX038I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX038I</span></td>
849	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
850	<td valign="top" headers="d17474e60" class="stentry">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>
851	<td valign="top" id="DOTX038I-extra" headers="d17474e62" class="stentry">The
852	<object> element in XHTML does not support using longdescref for accessibility.
853	To make the object accessible, you may need to add text before or after the element.
854	You may also be able to handle it with a <param> element inside the object.</td>
855	</tr>
856	<tr id="msgs__DOTX039W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX039W</span></td>
857	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
858	<td valign="top" headers="d17474e60" class="stentry">Required cleanup area found. To remove this message and hide the content, build your content without using the DRAFT parameter.</td>
859	<td valign="top" id="DOTX039W-extra" headers="d17474e62" class="stentry">This message is
860	generated when creating draft output in order to help you locate all topics that need to be cleaned
861	up; the cleanup items will appear in your output with styling that makes it stand out.
862	The content will be hidden when the draft parameter is not active.</td>
863	</tr>
864	<tr id="msgs__DOTX040I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX040I</span></td>
865	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
866	<td valign="top" headers="d17474e60" class="stentry">Draft comment area found. To remove this message and hide the comments, build your content without using the DRAFT parameter.</td>
867	<td valign="top" id="DOTX040I-extra" headers="d17474e62" class="stentry">This message is
868	generated when creating draft output in order to help you locate all topics that have draft comments.
869	Each comment will appear in your XHTML output; the comments will be hidden when the draft parameter is not active.</td>
870	</tr>
871	<tr id="msgs__DOTX041W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX041W</span></td>
872	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
873	<td valign="top" headers="d17474e60" class="stentry">Found more than one title element in a section. Using the first one for the section's title. </td>
874	<td valign="top" id="DOTX041W-extra" headers="d17474e62" class="stentry">Because
875	of the way XML and DITA are defined, it is generally not possible to prohibit adding a second title
876	to a section during editing (or to force that title to come first). However, the DITA specification states that only one title should
877	be used in a section. When multiple titles are found, only the first one will appear in the output.</td>
878	</tr>
879	<tr id="msgs__DOTX042I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX042I</span></td>
880	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
881	<td valign="top" headers="d17474e60" class="stentry">DITAVAL based flagging is not currently supported for inline phrases in XHTML; ignoring flag value on '<var class="keyword varname">%1</var>' attribute. </td>
882	<td valign="top" id="DOTX042I-extra" headers="d17474e62" class="stentry">If it is important
883	to flag this piece of information, try placing a flag on the block element that contains your phrase.
884	If you just want to have an image next to the phrase, you may place an image directly into the document.</td>
885	</tr>
886	<tr id="msgs__DOTX043I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX043I</span></td>
887	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
888	<td valign="top" headers="d17474e60" class="stentry">The link to '<var class="keyword varname">%1</var>' may appear more than once in '<var class="keyword varname">%2</var>'. </td>
889	<td valign="top" id="DOTX043I-extra" headers="d17474e62" class="stentry">The DITA-OT is able
890	to remove duplicate links in most cases. However, if two links to the same resource use different
891	attributes or link text, it is possible for them to appear together. For example, if the same
892	link shows up with role="next" and again with no specified role, it may show up as both the "Next topic"
893	link and as a related link. Note that links generated from a <reltable> in a DITA Map will
894	have the role attribute set to "friend".</td>
895	</tr>
896	<tr id="msgs__DOTX044E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX044E</span></td>
897	<td valign="top" headers="d17474e58" class="stentry">Error</td>
898	<td valign="top" headers="d17474e60" class="stentry">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>
899	<td valign="top" id="DOTX044E-extra" headers="d17474e62" class="stentry">The
900	<area> element in an image map must provide a link target for the specified area.
901	Please add an <xref> element as a child of <area> and ensure that it
902	specifies a link target.</td>
903	</tr>
904	<tr id="msgs__DOTX045W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX045W</span></td>
905	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
906	<td valign="top" headers="d17474e60" class="stentry">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>
907	<td valign="top" id="DOTX045W-extra" headers="d17474e62" class="stentry">Cross
908	reference text inside the <area> element is used to provide accessibility for
909	screen readers that can identify different areas of an image map. If text cannot be
910	retrieved automatically by referencing a DITA element, it should be specified directly
911	in the cross reference.</td>
912	</tr>
913	<tr id="msgs__DOTX046W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX046W</span></td>
914	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
915	<td valign="top" headers="d17474e60" class="stentry">Area shape should be: default, rect, circle, poly, or blank (no value). The value '<var class="keyword varname">%1</var>' is not recognized. </td>
916	<td valign="top" id="DOTX046W-extra" headers="d17474e62" class="stentry">The specified
917	value was passed as-is through to the area element in the XHTML.</td>
918	</tr>
919	<tr id="msgs__DOTX047W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX047W</span></td>
920	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
921	<td valign="top" headers="d17474e60" class="stentry">Area coordinates are blank. Coordinate points for the shape need to be specified. </td>
922	<td valign="top" id="DOTX047W-extra" headers="d17474e62" class="stentry">The area
923	element is intended to define a region in an image map; coordinates must be specified
924	in order to define that region.</td>
925	</tr>
926	<tr id="msgs__DOTX048I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX048I</span></td>
927	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
928	<td valign="top" headers="d17474e60" class="stentry">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>
929	<td valign="top" id="DOTX048I-extra" headers="d17474e62" class="stentry">The build will
930	not look for peer or external topics before compiling your CHM file, so they may not be included.
931	If you are referencing an actual HTML file that will not be available, it cannot be included in the project,
932	and you should set the toc attribute to "no" on your topicref element. Otherwise, check to be sure
933	your HTML file was included in the CHM; if it was not, you will need to place it in the correct
934	location with your other output files and recompile.</td>
935	</tr>
936	<tr id="msgs__DOTX049I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX049I</span></td>
937	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
938	<td valign="top" headers="d17474e60" class="stentry">References to non-dita files will be ignored by the PDF, ODT, and RTF output transforms. </td>
939	<td valign="top" id="DOTX049I-extra" headers="d17474e62" class="stentry">The PDF, ODT, and RTF output
940	processes cannot automatically convert non-DITA content into DITA in order to merge it with
941	the rest of your content. The referenced items are ignored.</td>
942	</tr>
943	<tr id="msgs__DOTX050W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX050W</span></td>
944	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
945	<td valign="top" headers="d17474e60" class="stentry">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>
946	<td valign="top" id="DOTX050W-extra" headers="d17474e62" class="stentry">Eclipse requires
947	that an ID be specified when creating an Eclipse Help project; the toolkit expects to locate
948	that ID on the root element of your input map.</td>
949	</tr>
950	<tr id="msgs__DOTX052W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX052W</span></td>
951	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
952	<td valign="top" headers="d17474e60" class="stentry">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>
953	<td valign="top" id="DOTX052W-extra" headers="d17474e62" class="stentry">The toolkit
954	is attempting to add generated text, such as the string "Related information" that appears
955	above links. The requested string could not be found in any language. Your output may contain a meaningful string,
956	or it may contain a code that was intended to map to a string. This likely indicates an error in a
957	plug-in or XSL override; either the string was requested incorrectly, or you will need to provide
958	a mapping for the string in all of the languages you require.</td>
959	</tr>
960	<tr id="msgs__DOTX053E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX053E</span></td>
961	<td valign="top" headers="d17474e58" class="stentry">Error</td>
962	<td valign="top" headers="d17474e60" class="stentry">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>
963	<td valign="top" id="DOTX053E-extra" headers="d17474e62" class="stentry">This will
964	occur if a map references another map, and then that second map (or another further nested map)
965	references the original map. The result is an infinite nesting of maps; please correct
966	the chain of map references to remove circular reference.</td>
967	</tr>
968	<tr id="msgs__DOTX054W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX054W</span></td>
969	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
970	<td valign="top" headers="d17474e60" class="stentry">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>
971	<td valign="top" id="DOTX054W-extra" headers="d17474e62" class="stentry">This will
972	occur when a DITAVAL file contains multiple styling rules that apply to the same element.</td>
973	</tr>
974	<tr id="msgs__DOTX055W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX055W</span></td>
975	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
976	<td valign="top" headers="d17474e60" class="stentry">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>
977	<td valign="top" id="DOTX055W-extra" headers="d17474e62" class="stentry">The "flagit"
978	named template was deprecated in DITA-OT version 1.4, when the OASIS standard formalized the
979	DITAVAL syntax. The template is removed in DITA-OT 1.6. Stylesheets
980	that used this template need to be updated.</td>
981	</tr>
982	<tr id="msgs__DOTX056W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX056W</span></td>
983	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
984	<td valign="top" headers="d17474e60" class="stentry">The file '<var class="keyword varname">%1</var>' is not available to resolve link information. </td>
985	<td valign="top" id="DOTX056W-extra" headers="d17474e62" class="stentry">The build
986	attempted to access the specified file in order to retrive a title or short description, but the
987	file could not be found. If the file exists, it is possible that a DITAVAL file was used to remove
988	the file's contents from the build. Another possibility is that the file is located outside of the scope of the main
989	input directory, and was not available because the <a class="xref" href="dita-ot_ant_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">onlytopic.in.map</a> or
990	<a class="xref" href="dita-ot_java_properties.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Finally, some parameters apply only to the specific transformation types.">/onlytopicinmap</a> parameter was specified.
991	Be aware that the path information above may not match the link in your topic.</td>
992	</tr>
993	<tr id="msgs__DOTX057W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX057W</span></td>
994	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
995	<td valign="top" headers="d17474e60" class="stentry">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>
996	<td valign="top" id="DOTX057W-extra" headers="d17474e62" class="stentry">The link appears
997	to use valid syntax to reference a DITA element, but that element cannot be found. Please verify that
998	the element exists, and is not removed from the build by DITAVAL based filtering.</td>
999	</tr>
1000	<tr id="msgs__DOTX058W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX058W</span></td>
1001	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1002	<td valign="top" headers="d17474e60" class="stentry">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>
1003	<td valign="top" id="DOTX058W-extra" headers="d17474e62" class="stentry">Processing
1004	for terms, acronyms, or abbreviated forms will associate the key from the element's keyref attribute
1005	with a glossentry (glossary entry) topic. This message will appear if the key was defined, but was not associated
1006	with a glossentry topic. The process will try to use the best available fallback (usually the title of the
1007	referenced topic).</td>
1008	</tr>
1009	<tr id="msgs__DOTX060W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX060W</span></td>
1010	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1011	<td valign="top" headers="d17474e60" class="stentry">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>
1012	<td valign="top" id="DOTX060W-extra" headers="d17474e62" class="stentry">Processing
1013	for abbreviated form elements will associate the key from the element's keyref attribute
1014	with a glossentry (glossary entry) topic. This message will appear if the key was defined, but was not associated
1015	with a glossentry topic. This element is only supported with keys that are associated with glossary topics; the
1016	element will not generate any output. Please correct the reference, or use a different element to reference
1017	your topic.</td>
1018	</tr>
1019	<tr id="msgs__DOTX061W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX061W</span></td>
1020	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1021	<td valign="top" headers="d17474e60" class="stentry">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>
1022	<td valign="top" id="DOTX061W-extra" headers="d17474e62" class="stentry">According
1023	to the DITA Specification, references from maps should either go to DITA Maps, DITA Topics,
1024	or any non-DITA resource. References below the topic level should only be made from
1025	cross references (using <xref> or similar) inside of a topic. For details, see the href attribute description in
1026	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">topicref element</a>.</td>
1027	</tr>
1028	<tr id="msgs__DOTX062I" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX062I</span></td>
1029	<td valign="top" headers="d17474e58" class="stentry">Informational</td>
1030	<td valign="top" headers="d17474e60" class="stentry">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>
1031	<td valign="top" id="DOTX062I-extra" headers="d17474e62" class="stentry"> </td>
1032	</tr>
1033	<tr id="msgs__DOTX063W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX063W</span></td>
1034	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1035	<td valign="top" headers="d17474e60" class="stentry">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>
1036	<td valign="top" id="DOTX063W-extra" headers="d17474e62" class="stentry">This will
1037	appear when generating PDF or ODT output that includes a link to a local topic, but the referenced topic is
1038	not part of the map itself. This will result in a broken link. You should include the topic in your map
1039	or remove the link from the build.</td>
1040	</tr>
1041	<tr id="msgs__DOTX064W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX064W</span></td>
1042	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1043	<td valign="top" headers="d17474e60" class="stentry">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>
1044	<td valign="top" id="DOTX064W-extra" headers="d17474e62" class="stentry">The copy-to
1045	attribute is used to copy a topic over a document that already exists. Please make sure that any
1046	copy-to attributes use a unique name so that the copy will not overwrite existing content.</td>
1047	</tr>
1048	<tr id="msgs__DOTX065W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX065W</span></td>
1049	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1050	<td valign="top" headers="d17474e60" class="stentry">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>
1051	<td valign="top" id="DOTX065W-extra" headers="d17474e62" class="stentry">Two different
1052	topics are copied to the same location using copy-to; as a result, one of these files would be over-written.
1053	Only the first instance of this copy-to value will be recognized.
1054	Please correct the use of copy-to attributes.</td>
1055	</tr>
1056	<tr id="msgs__DOTX066W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX066W</span></td>
1057	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1058	<td valign="top" headers="d17474e60" class="stentry">Template "<var class="keyword varname">%1</var>" is deprecated. Remove references to this template from your custom XSLT or plug-ins.</td>
1059	<td valign="top" id="DOTX066W-extra" headers="d17474e62" class="stentry">This message
1060	indicates that your custom XSLT or plug-ins rely on templates that will be removed in an
1061	upcoming release. Typically this occurs when a named template has been converted to a mode template;
1062	any code that uses the deprecated template should be updated.</td>
1063	</tr>
1064	<tr id="msgs__DOTX067E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX067E</span></td>
1065	<td valign="top" headers="d17474e58" class="stentry">Error</td>
1066	<td valign="top" headers="d17474e60" class="stentry">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>
1067	<td valign="top" id="DOTX067E-extra" headers="d17474e62" class="stentry">This PDF build
1068	uses generated text, such as the phrase "Related information" (which is generated above many
1069	link groups). The toolkit was unable to locate the string <var class="keyword varname">%1</var> for your
1070	specified language, so the string will appear in the default language. This generally indicates
1071	that the toolkit's strings needs to be updated to support your language, or that your language
1072	setting is incorrect.</td>
1073	</tr>
1074	<tr id="msgs__DOTX068W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">DOTX068W</span></td>
1075	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1076	<td valign="top" headers="d17474e60" class="stentry">A topicref element that references a map contains child topicref elements. Child topicref elements are ignored.</td>
1077	<td valign="top" id="DOTX068W-extra" headers="d17474e62" class="stentry"> </td>
1078	</tr>
1079	<tr id="msgs__PDFJ001E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFJ001E</span></td>
1080	<td valign="top" headers="d17474e58" class="stentry">Error</td>
1081	<td valign="top" headers="d17474e60" class="stentry">Index entry '<var class="keyword varname">%1</var>' is dropped, because corresponding group is not found. </td>
1082	<td valign="top" id="PDFJ001E-extra" headers="d17474e62" class="stentry"> </td>
1083	</tr>
1084	<tr id="msgs__PDFJ002E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFJ002E</span></td>
1085	<td valign="top" headers="d17474e58" class="stentry">Error</td>
1086	<td valign="top" headers="d17474e60" class="stentry">Build stopped. Problems occured during Index preprocess task. Please check the messages above. </td>
1087	<td valign="top" id="PDFJ002E-extra" headers="d17474e62" class="stentry"> </td>
1088	</tr>
1089	<tr id="msgs__PDFX001W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX001W</span></td>
1090	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1091	<td valign="top" headers="d17474e60" class="stentry">There is no index entry found which closing range for ID="<var class="keyword varname">%1</var>". </td>
1092	<td valign="top" id="PDFX001W-extra" headers="d17474e62" class="stentry"> </td>
1093	</tr>
1094	<tr id="msgs__PDFX002W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX002W</span></td>
1095	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1096	<td valign="top" headers="d17474e60" class="stentry">There are multiple index entry found which is opening range for ID="<var class="keyword varname">%1</var>" but there is only one which close it or ranges are overlapping. </td>
1097	<td valign="top" id="PDFX002W-extra" headers="d17474e62" class="stentry"> </td>
1098	</tr>
1099	<tr id="msgs__PDFX003W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX003W</span></td>
1100	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1101	<td valign="top" headers="d17474e60" class="stentry">There are multiple index entry found which closing range for ID="<var class="keyword varname">%1</var>". </td>
1102	<td valign="top" id="PDFX003W-extra" headers="d17474e62" class="stentry"> </td>
1103	</tr>
1104	<tr id="msgs__PDFX004F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX004F</span></td>
1105	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
1106	<td valign="top" headers="d17474e60" class="stentry">Empty href was specified for some topic reference. Please correct your ditamap or bookmap file.</td>
1107	<td valign="top" id="PDFX004F-extra" headers="d17474e62" class="stentry"> </td>
1108	</tr>
1109	<tr id="msgs__PDFX005F" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX005F</span></td>
1110	<td valign="top" headers="d17474e58" class="stentry">Fatal</td>
1111	<td valign="top" headers="d17474e60" class="stentry">Topic reference (href : <var class="keyword varname">%1</var>) not found. Reference may be incorrect. Please correct your ditamap or bookmap file.</td>
1112	<td valign="top" id="PDFX005F-extra" headers="d17474e62" class="stentry"> </td>
1113	</tr>
1114	<tr id="msgs__PDFX006E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX006E</span></td>
1115	<td valign="top" headers="d17474e58" class="stentry">Error</td>
1116	<td valign="top" headers="d17474e60" class="stentry">Number of columns must be specified. </td>
1117	<td valign="top" id="PDFX006E-extra" headers="d17474e62" class="stentry"> </td>
1118	</tr>
1119	<tr id="msgs__PDFX007W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX007W</span></td>
1120	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1121	<td valign="top" headers="d17474e60" class="stentry">There is no index entry found which opening range for ID="<var class="keyword varname">%1</var>". </td>
1122	<td valign="top" id="PDFX007W-extra" headers="d17474e62" class="stentry"> </td>
1123	</tr>
1124	<tr id="msgs__PDFX008W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX008W</span></td>
1125	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1126	<td valign="top" headers="d17474e60" class="stentry">Font definition not found for the logical name or alias '<var class="keyword varname">%1</var>'. </td>
1127	<td valign="top" id="PDFX008W-extra" headers="d17474e62" class="stentry"> </td>
1128	</tr>
1129	<tr id="msgs__PDFX009E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX009E</span></td>
1130	<td valign="top" headers="d17474e58" class="stentry">Error</td>
1131	<td valign="top" headers="d17474e60" class="stentry">Attribute set reflection can't handle XSLT element <var class="keyword varname">%1</var>. </td>
1132	<td valign="top" id="PDFX009E-extra" headers="d17474e62" class="stentry"> </td>
1133	</tr>
1134	<tr id="msgs__PDFX010W" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX010W</span></td>
1135	<td valign="top" headers="d17474e58" class="stentry">Warning</td>
1136	<td valign="top" headers="d17474e60" class="stentry">Index generation is not supported in FOP. </td>
1137	<td valign="top" id="PDFX010W-extra" headers="d17474e62" class="stentry"> </td>
1138	</tr>
1139	<tr id="msgs__PDFX011E" class="strow"><td valign="top" headers="d17474e56" class="stentry"><span class="keyword msgnum">PDFX011E</span></td>
1140	<td valign="top" headers="d17474e58" class="stentry">Error</td>
1141	<td valign="top" headers="d17474e60" class="stentry">Both index-see and <var class="keyword varname">%1</var> defined for index entry '<var class="keyword varname">%2</var>'. Recovering by treating the index-see as an index-see-also.</td>
1142	<td valign="top" id="PDFX011E-extra" headers="d17474e62" class="stentry"> </td>
1143	</tr>
1144	</table>
1145	</div>
1146	<div class="related-links">
1147	<div class="familylinks">
1148	<div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../readme/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>
1149	</div>
1150	</div>
1151
1152	</body>
1153	</html>

注意: 瀏覽 TracBrowser 來幫助您使用儲存庫瀏覽器

source: vbox/trunk/src/libs/dita-ot-1.8.5/doc/readme/DITA-messages.html@ 99507

以其他格式下載: