| 27 | for more information, see the Developer reference section of the User Guide.</p></section><simpletable relcolwidth="1.5* 1.8* 4* 4*"><sthead><stentry>Message ID</stentry><stentry>Severity</stentry><stentry>Message text</stentry><stentry>Additional details</stentry></sthead><strow id="DOTA001F"><stentry><msgnum>DOTA001F</msgnum></stentry><stentry>Fatal</stentry><stentry>"<varname>%1</varname>" 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.</stentry><stentry id="DOTA001F-extra"> </stentry></strow><strow id="DOTA002F"><stentry><msgnum>DOTA002F</msgnum></stentry><stentry>Fatal</stentry><stentry>Input file is not specified, or is specified using the wrong parameter. </stentry><stentry id="DOTA002F-extra"> </stentry></strow><strow id="DOTA003F"><stentry><msgnum>DOTA003F</msgnum></stentry><stentry>Fatal</stentry><stentry>Cannot find the user specified XSLT stylesheet '<varname>%1</varname>'. </stentry><stentry id="DOTA003F-extra"> </stentry></strow><strow id="DOTA004F"><stentry><msgnum>DOTA004F</msgnum></stentry><stentry>Fatal</stentry><stentry>Invalid DITA topic extension '<varname>%1</varname>'. Supported values are '.dita' and '.xml'.</stentry><stentry id="DOTA004F-extra"> </stentry></strow><strow id="DOTA006W"><stentry><msgnum>DOTA006W</msgnum></stentry><stentry>Warning</stentry><stentry>Absolute paths on the local file system are not supported for the CSSPATH parameter. Please use a relative path or full URI instead.</stentry><stentry id="DOTA006W-extra"> </stentry></strow><strow id="DOTA007E"><stentry><msgnum>DOTA007E</msgnum></stentry><stentry>Error</stentry><stentry>Cannot find the running-footer file "<varname>%1</varname>". Please double check the value to ensure it is specified correctly.</stentry><stentry id="DOTA007E-extra"> </stentry></strow><strow id="DOTA008E"><stentry><msgnum>DOTA008E</msgnum></stentry><stentry>Error</stentry><stentry>Cannot find the running-header file "<varname>%1</varname>". Please double check the value to ensure it is specified correctly.</stentry><stentry id="DOTA008E-extra"> </stentry></strow><strow id="DOTA009E"><stentry><msgnum>DOTA009E</msgnum></stentry><stentry>Error</stentry><stentry>Cannot find the specified heading file "<varname>%1</varname>". Please double check the value to ensure it is specified correctly.</stentry><stentry id="DOTA009E-extra"> </stentry></strow><strow id="DOTA010E"><stentry><msgnum>DOTA010E</msgnum></stentry><stentry>Error</stentry><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.</stentry><stentry id="DOTA010E-extra"> </stentry></strow><strow id="DOTA011W"><stentry><msgnum>DOTA011W</msgnum></stentry><stentry>Warning</stentry><stentry>Argument "<varname>%1</varname>" is deprecated. This argument is no longer supported in the toolkit.</stentry><stentry id="DOTA011W-extra"> </stentry></strow><strow id="DOTA012W"><stentry><msgnum>DOTA012W</msgnum></stentry><stentry>Warning</stentry><stentry>Argument "<varname>%1</varname>" is deprecated. Please use the argument "<varname>%2</varname>" instead.</stentry><stentry id="DOTA012W-extra"> </stentry></strow><strow id="DOTA066F"><stentry><msgnum>DOTA066F</msgnum></stentry><stentry>Fatal</stentry><stentry>Cannot find the user specified XSLT stylesheet '<varname>%1</varname>'. </stentry><stentry id="DOTA066F-extra"> </stentry></strow><strow id="DOTA067W"><stentry><msgnum>DOTA067W</msgnum></stentry><stentry>Warning</stentry><stentry>Ignoring index-see '<varname>%1</varname>' inside parent index entry '<varname>%2</varname>' 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.</stentry><stentry id="DOTA067W-extra"> </stentry></strow><strow id="DOTA068W"><stentry><msgnum>DOTA068W</msgnum></stentry><stentry>Warning</stentry><stentry>Ignoring index-see-also '<varname>%1</varname>' inside parent index entry '<varname>%2</varname>' 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.</stentry><stentry id="DOTA068W-extra"> </stentry></strow><strow id="DOTA069F"><stentry><msgnum>DOTA069F</msgnum></stentry><stentry>Fatal</stentry><stentry>Input file '<varname>%1</varname>' cannot be located or read. Ensure that file was specified properly and that you have permission to access it.</stentry><stentry id="DOTA069F-extra"> </stentry></strow><strow id="DOTA069W"><stentry><msgnum>DOTA069W</msgnum></stentry><stentry>Warning</stentry><stentry>Target "<varname>%1</varname>" is deprecated. Remove references to this target from your custom XSLT or plug-ins.</stentry><stentry id="DOTA069W-extra"> </stentry></strow><strow id="DOTJ001F"><stentry><msgnum>DOTJ001F</msgnum></stentry><stentry>Fatal</stentry><stentry>Invalid command line syntax for the parameter '<varname>%1</varname>'. Parameters to the command line tool should use the syntax /parameter:value.</stentry><stentry id="DOTJ001F-extra"> </stentry></strow><strow id="DOTJ002F"><stentry><msgnum>DOTJ002F</msgnum></stentry><stentry>Fatal</stentry><stentry>Unsupported parameter '<varname>%1</varname>'. Please refer to the DITA-OT User Guide for supported parameters.</stentry><stentry id="DOTJ002F-extra"> </stentry></strow><strow id="DOTJ003F"><stentry><msgnum>DOTJ003F</msgnum></stentry><stentry>Fatal</stentry><stentry>Parameter '<varname>%1</varname>' was specified without a value. Parameters to the command line tool should use the syntax /parameter:value.</stentry><stentry id="DOTJ003F-extra"> </stentry></strow><strow id="DOTJ004F"><stentry><msgnum>DOTJ004F</msgnum></stentry><stentry>Fatal</stentry><stentry>Cannot create temporary processing directory '<varname>%1</varname>'. Please ensure that you have permission to create the directory '<varname>%1</varname>'.</stentry><stentry id="DOTJ004F-extra"> </stentry></strow><strow id="DOTJ005F"><stentry><msgnum>DOTJ005F</msgnum></stentry><stentry>Fatal</stentry><stentry>Failed to create new instance for '<varname>%1</varname>'. Please ensure that '<varname>%1</varname>' exists and that you have permission to access it.</stentry><stentry id="DOTJ005F-extra"> </stentry></strow><strow id="DOTJ006F"><stentry><msgnum>DOTJ006F</msgnum></stentry><stentry>Fatal</stentry><stentry>An Ant build file used the following illegal syntax when calling AntInvoker: extparam='<varname>%1</varname>'. Please correct the call to AntInvoker when directly calling DITA-OT Java code from Ant; for example, extparam="maplinks=XXXX;other=YYYY".</stentry><stentry id="DOTJ006F-extra"> </stentry></strow><strow id="DOTJ007E"><stentry><msgnum>DOTJ007E</msgnum></stentry><stentry>Error</stentry><stentry>Duplicate condition in filter file for rule '<varname>%1</varname>'. The first encountered condition will be used.</stentry><stentry id="DOTJ007E-extra"> </stentry></strow><strow id="DOTJ009E"><stentry><msgnum>DOTJ009E</msgnum></stentry><stentry>Error</stentry><stentry>Cannot overwrite file '<varname>%1</varname>' with file '<varname>%2</varname>'. 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.</stentry><stentry id="DOTJ009E-extra"> </stentry></strow><strow id="DOTJ012F"><stentry><msgnum>DOTJ012F</msgnum></stentry><stentry>Fatal</stentry><stentry>Failed to parse the input file '<varname>%1</varname>'. The XML parser reported the following error: </stentry><stentry id="DOTJ012F-extra"> </stentry></strow><strow id="DOTJ013E"><stentry><msgnum>DOTJ013E</msgnum></stentry><stentry>Error</stentry><stentry>Failed to parse the referenced file '<varname>%1</varname>'. The XML parser reported the following error: </stentry><stentry id="DOTJ013E-extra"> </stentry></strow><strow id="DOTJ014W"><stentry><msgnum>DOTJ014W</msgnum></stentry><stentry>Warning</stentry><stentry>Found an indexterm element with no content. Setting the term to ***. </stentry><stentry id="DOTJ014W-extra"> </stentry></strow><strow id="DOTJ015F"><stentry><msgnum>DOTJ015F</msgnum></stentry><stentry>Fatal</stentry><stentry>Log directory cannot be null. Please specify a valid directory for the build log.</stentry><stentry id="DOTJ015F-extra"> </stentry></strow><strow id="DOTJ016F"><stentry><msgnum>DOTJ016F</msgnum></stentry><stentry>Fatal</stentry><stentry>Failed to create log directory '<varname>%1</varname>'. Please specify a valid directory for the build log.</stentry><stentry id="DOTJ016F-extra"> </stentry></strow><strow id="DOTJ017F"><stentry><msgnum>DOTJ017F</msgnum></stentry><stentry>Fatal</stentry><stentry>No input file was specified; failed to initialize log name based on input file. </stentry><stentry id="DOTJ017F-extra"> </stentry></strow><strow id="DOTJ018I"><stentry><msgnum>DOTJ018I</msgnum></stentry><stentry>Informational</stentry><stentry>Log file '<varname>%1</varname>' was generated successfully in directory '<varname>%2</varname>'. 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.</stentry><stentry id="DOTJ018I-extra"> </stentry></strow><strow id="DOTJ020W"><stentry><msgnum>DOTJ020W</msgnum></stentry><stentry>Warning</stentry><stentry>At least one plug-in in '<varname>%1</varname>' is required by plug-in '<varname>%2</varname>'. Plug-in '<varname>%2</varname>' cannot be loaded. Check and see whether all prerequisite plug-ins are installed in toolkit.</stentry><stentry id="DOTJ020W-extra"> </stentry></strow><strow id="DOTJ021W"><stentry><msgnum>DOTJ021W</msgnum></stentry><stentry>Warning</stentry><stentry>File '<varname>%1</varname>' 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 '<varname>%1</varname>' and the ditaval file to see if this is the intended result.</stentry><stentry id="DOTJ021W-extra"> </stentry></strow><strow id="DOTJ022F"><stentry><msgnum>DOTJ022F</msgnum></stentry><stentry>Fatal</stentry><stentry>Failed to parse the input file '<varname>%1</varname>' 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.</stentry><stentry id="DOTJ022F-extra"> </stentry></strow><strow id="DOTJ023E"><stentry><msgnum>DOTJ023E</msgnum></stentry><stentry>Error</stentry><stentry>Failed to get the specified image file '<varname>%1</varname>', so it will not be included with your output. </stentry><stentry id="DOTJ023E-extra"> </stentry></strow><strow id="DOTJ025E"><stentry><msgnum>DOTJ025E</msgnum></stentry><stentry>Error</stentry><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.</stentry><stentry id="DOTJ025E-extra"> </stentry></strow><strow id="DOTJ026E"><stentry><msgnum>DOTJ026E</msgnum></stentry><stentry>Error</stentry><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.</stentry><stentry id="DOTJ026E-extra"> </stentry></strow><strow id="DOTJ028E"><stentry><msgnum>DOTJ028E</msgnum></stentry><stentry>Error</stentry><stentry>No format attribute was found on a reference to file '<varname>%1</varname>', 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".</stentry><stentry id="DOTJ028E-extra"> </stentry></strow><strow id="DOTJ029I"><stentry><msgnum>DOTJ029I</msgnum></stentry><stentry>Informational</stentry><stentry>No 'domains' attribute was found for element '<<varname>%1</varname>>'. This generally indicates that your DTD or Schema was not developed properly according to the DITA specification.</stentry><stentry id="DOTJ029I-extra"> </stentry></strow><strow id="DOTJ030I"><stentry><msgnum>DOTJ030I</msgnum></stentry><stentry>Informational</stentry><stentry>No 'class' attribute for was found for element '<<varname>%1</varname>>'. This generally indicates that your DTD or Schema was not developed properly according to the DITA specification.</stentry><stentry id="DOTJ030I-extra"> </stentry></strow><strow id="DOTJ031I"><stentry><msgnum>DOTJ031I</msgnum></stentry><stentry>Informational</stentry><stentry>No specified rule for '<varname>%1</varname>' 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 '<varname>%1</varname>' in the ditaval file.</stentry><stentry id="DOTJ031I-extra"> </stentry></strow><strow id="DOTJ033E"><stentry><msgnum>DOTJ033E</msgnum></stentry><stentry>Error</stentry><stentry>No valid content is found in topicref '<varname>%1</varname>' during chunk processing. Please specify an existing and valid topic for the topicref.</stentry><stentry id="DOTJ033E-extra"> </stentry></strow><strow id="DOTJ034F"><stentry><msgnum>DOTJ034F</msgnum></stentry><stentry>Fatal</stentry><stentry>Failed to parse the input file '<varname>%1</varname>' (the content of the file is not valid). If the input file '<varname>%1</varname>' does not have a DOCTYPE declaration, please make sure that all class attributes are present in the file.</stentry><stentry id="DOTJ034F-extra"> </stentry></strow><strow id="DOTJ035F"><stentry><msgnum>DOTJ035F</msgnum></stentry><stentry>Fatal</stentry><stentry>The file "<varname>%1</varname>" referenced by "<varname>%2</varname>" 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 "<varname>%1</varname>" into the input dita/map directory.</stentry><stentry id="DOTJ035F-extra"> </stentry></strow><strow id="DOTJ036W"><stentry><msgnum>DOTJ036W</msgnum></stentry><stentry>Warning</stentry><stentry>The file "<varname>%1</varname>" referenced by "<varname>%2</varname>" 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 "<varname>%1</varname>" into the input dita/map directory.</stentry><stentry id="DOTJ036W-extra"> </stentry></strow><strow id="DOTJ037W"><stentry><msgnum>DOTJ037W</msgnum></stentry><stentry>Warning</stentry><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.</stentry><stentry id="DOTJ037W-extra"> </stentry></strow><strow id="DOTJ038E"><stentry><msgnum>DOTJ038E</msgnum></stentry><stentry>Error</stentry><stentry>The tag "<varname>%1</varname>" is specialized from unrecognized metadata. Please make sure that tag "<varname>%1</varname>" is specialized from an existing metadata tag in the core DITA vocabulary.</stentry><stentry id="DOTJ038E-extra"> </stentry></strow><strow id="DOTJ039E"><stentry><msgnum>DOTJ039E</msgnum></stentry><stentry>Error</stentry><stentry>There is no target specified for conref push action "pushafter". Found in file="<varname>%1</varname>", element="<varname>%2</varname>". Please add <elementname conref="pushtarget" conaction="mark"> before current element.</stentry><stentry id="DOTJ039E-extra"> </stentry></strow><strow id="DOTJ040E"><stentry><msgnum>DOTJ040E</msgnum></stentry><stentry>Error</stentry><stentry>An element uses the attribute conaction="replace", but a conref attribute is not found in the expected location. Found in file="<varname>%1</varname>", element="<varname>%2</varname>". </stentry><stentry id="DOTJ040E-extra"> </stentry></strow><strow id="DOTJ041E"><stentry><msgnum>DOTJ041E</msgnum></stentry><stentry>Error</stentry><stentry>The attribute conref="<varname>%1</varname>" uses invalid syntax. The value should contain '#' followed by a topic or map ID, optionally followed by '/elemID' for a sub-topic element.</stentry><stentry id="DOTJ041E-extra"> </stentry></strow><strow id="DOTJ042E"><stentry><msgnum>DOTJ042E</msgnum></stentry><stentry>Error</stentry><stentry>Two elements both use conref push to replace the target "<varname>%1</varname>". Please delete one of the duplicate "replace" actions.</stentry><stentry id="DOTJ042E-extra"> </stentry></strow><strow id="DOTJ043W"><stentry><msgnum>DOTJ043W</msgnum></stentry><stentry>Warning</stentry><stentry>The conref push function is trying to replace an element that does not exist (element "<varname>%1</varname>" in file "<varname>%2</varname>"). </stentry><stentry id="DOTJ043W-extra"> </stentry></strow><strow id="DOTJ044W"><stentry><msgnum>DOTJ044W</msgnum></stentry><stentry>Warning</stentry><stentry>There is a redundant conref action "pushbefore". Found in file="<varname>%1</varname>", element="<varname>%2</varname>". Please make sure that "mark" and "pushbefore" occur in pairs.</stentry><stentry id="DOTJ044W-extra"> </stentry></strow><strow id="DOTJ045I"><stentry><msgnum>DOTJ045I</msgnum></stentry><stentry>Informational</stentry><stentry>The key "<varname>%1</varname>" is defined more than once in the same map file. The reference href="<varname>%2</varname>" is ignored. </stentry><stentry id="DOTJ045I-extra"> </stentry></strow><strow id="DOTJ046E"><stentry><msgnum>DOTJ046E</msgnum></stentry><stentry>Error</stentry><stentry>Conkeyref="<varname>%1</varname>" 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.</stentry><stentry id="DOTJ046E-extra"> </stentry></strow><strow id="DOTJ047I"><stentry><msgnum>DOTJ047I</msgnum></stentry><stentry>Informational</stentry><stentry>Unable to find key definition for keyref="<varname>%1</varname>", href may be used as fallback if it exists. </stentry><stentry id="DOTJ047I-extra"> </stentry></strow><strow id="DOTJ049W"><stentry><msgnum>DOTJ049W</msgnum></stentry><stentry>Warning</stentry><stentry>The attribute value <varname>%1</varname>="<varname>%3</varname>" on element "<varname>%2</varname>" does not comply with the specified subject scheme. According to the subject scheme map, the following values are valid for the <varname>%1</varname> attribute: <varname>%4</varname></stentry><stentry id="DOTJ049W-extra"> </stentry></strow><strow id="DOTJ050W"><stentry><msgnum>DOTJ050W</msgnum></stentry><stentry>Warning</stentry><stentry>Found an <index-see> or <index-see-also> reference to the term '<varname>%1</varname>', but that term is not defined in the index. </stentry><stentry id="DOTJ050W-extra"> </stentry></strow><strow id="DOTJ051E"><stentry><msgnum>DOTJ051E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to load target for coderef "<varname>%1</varname>". </stentry><stentry id="DOTJ051E-extra"> </stentry></strow><strow id="DOTJ052E"><stentry><msgnum>DOTJ052E</msgnum></stentry><stentry>Error</stentry><stentry>Code reference charset "<varname>%1</varname>" not supported. See the DITA-OT User guide for supported charset values on the format attribute.</stentry><stentry id="DOTJ052E-extra"> </stentry></strow><strow id="DOTJ053W"><stentry><msgnum>DOTJ053W</msgnum></stentry><stentry>Warning</stentry><stentry>Input file '<varname>%1</varname>' is not valid DITA file name. Please check '<varname>%1</varname>' to see if it is correct. The extensions ".dita" or ".xml" are supported for DITA topics.</stentry><stentry id="DOTJ053W-extra"> </stentry></strow><strow id="DOTJ054E"><stentry><msgnum>DOTJ054E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to parse invalid <varname>%1</varname> attribute value "<varname>%2</varname>" </stentry><stentry id="DOTJ054E-extra"> </stentry></strow><strow id="DOTJ055E"><stentry><msgnum>DOTJ055E</msgnum></stentry><stentry>Error</stentry><stentry>Invalid key name "<varname>%1</varname>". </stentry><stentry id="DOTJ055E-extra"> </stentry></strow><strow id="DOTJ056E"><stentry><msgnum>DOTJ056E</msgnum></stentry><stentry>Error</stentry><stentry>Invalid xml:lang "<varname>%1</varname>". </stentry><stentry id="DOTJ056E-extra"> </stentry></strow><strow id="DOTJ057E"><stentry><msgnum>DOTJ057E</msgnum></stentry><stentry>Error</stentry><stentry>The id attribute value "<varname>%1</varname>" is not unique within the topic that contains it. </stentry><stentry id="DOTJ057E-extra"> </stentry></strow><strow id="DOTX001W"><stentry><msgnum>DOTX001W</msgnum></stentry><stentry>Warning</stentry><stentry>No string named '<varname>%1</varname>' was found for language '<varname>%2</varname>'. Using the default language '<varname>%3</varname>'. Add a mapping between default language and desired language for the string '<varname>%1</varname>'.</stentry><stentry id="DOTX001W-extra"> </stentry></strow><strow id="DOTX002W"><stentry><msgnum>DOTX002W</msgnum></stentry><stentry>Warning</stentry><stentry>The title element or attribute in the ditamap is required for Eclipse output. </stentry><stentry id="DOTX002W-extra"> </stentry></strow><strow id="DOTX003I"><stentry><msgnum>DOTX003I</msgnum></stentry><stentry>Informational</stentry><stentry>The anchorref attribute should either reference another dita map or an Eclipse XML TOC file. The value '<varname>%1</varname>' does not appear to reference either. </stentry><stentry id="DOTX003I-extra"> </stentry></strow><strow id="DOTX004I"><stentry><msgnum>DOTX004I</msgnum></stentry><stentry>Informational</stentry><stentry>Found a navref element that does not reference anything. The navref element should either reference another dita map or an Eclipse XML file.</stentry><stentry id="DOTX004I-extra"> </stentry></strow><strow id="DOTX005E"><stentry><msgnum>DOTX005E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to find navigation title for reference to '<varname>%1</varname>'. The build will use '<varname>%1</varname>' as the title in the Eclipse Table of Contents.</stentry><stentry id="DOTX005E-extra"> </stentry></strow><strow id="DOTX006E"><stentry><msgnum>DOTX006E</msgnum></stentry><stentry>Error</stentry><stentry>Unknown file extension in href="<varname>%1</varname>". References to non-DITA resources should set the format attribute to match the resource (for example, 'txt', 'pdf', or 'html').</stentry><stentry id="DOTX006E-extra"> </stentry></strow><strow id="DOTX007I"><stentry><msgnum>DOTX007I</msgnum></stentry><stentry>Informational</stentry><stentry>Only DITA topics, HTML files, and images may be included in your compiled CHM file. The reference to "<varname>%1</varname>" will be ignored. To remove this message, you can set the toc="no" or processing-role="resource-only" attribute on your topicref.</stentry><stentry id="DOTX007I-extra"> </stentry></strow><strow id="DOTX008E"><stentry><msgnum>DOTX008E</msgnum></stentry><stentry>Error</stentry><stentry>File '<varname>%1</varname>' does not exist or cannot be loaded. </stentry><stentry id="DOTX008E-extra"> </stentry></strow><strow id="DOTX008W"><stentry><msgnum>DOTX008W</msgnum></stentry><stentry>Warning</stentry><stentry>File '<varname>%1</varname>' cannot be loaded, and no navigation title is specified for the table of contents. </stentry><stentry id="DOTX008W-extra"> </stentry></strow><strow id="DOTX009W"><stentry><msgnum>DOTX009W</msgnum></stentry><stentry>Warning</stentry><stentry>Could not retrieve a title from '<varname>%1</varname>'. Using '<varname>%2</varname>' instead. </stentry><stentry id="DOTX009W-extra"> </stentry></strow><strow id="DOTX010E"><stentry><msgnum>DOTX010E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to find target for conref="<varname>%1</varname>". </stentry><stentry id="DOTX010E-extra"> </stentry></strow><strow id="DOTX011W"><stentry><msgnum>DOTX011W</msgnum></stentry><stentry>Warning</stentry><stentry>There is more than one possible target for the reference conref="<varname>%1</varname>". Only the first will be used. Remove the duplicate id in the referenced file.</stentry><stentry id="DOTX011W-extra"> </stentry></strow><strow id="DOTX012W"><stentry><msgnum>DOTX012W</msgnum></stentry><stentry>Warning</stentry><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.</stentry><stentry id="DOTX012W-extra"> </stentry></strow><strow id="DOTX013E"><stentry><msgnum>DOTX013E</msgnum></stentry><stentry>Error</stentry><stentry>A element with attribute conref="<varname>%1</varname>" indirectly includes itself, which results in an infinite loop. </stentry><stentry id="DOTX013E-extra"> </stentry></strow><strow id="DOTX014E"><stentry><msgnum>DOTX014E</msgnum></stentry><stentry>Error</stentry><stentry>The attribute conref="<varname>%1</varname>" uses invalid syntax. Conref references to a map element should contain '#' followed by an ID, such as mymap.ditamap#mytopicrefid.</stentry><stentry id="DOTX014E-extra"> </stentry></strow><strow id="DOTX015E"><stentry><msgnum>DOTX015E</msgnum></stentry><stentry>Error</stentry><stentry>The attribute conref="<varname>%1</varname>" uses invalid syntax. The value should contain '#' followed by a topic or map ID, optionally followed by '/elemID' for a sub-topic element.</stentry><stentry id="DOTX015E-extra"> </stentry></strow><strow id="DOTX016W"><stentry><msgnum>DOTX016W</msgnum></stentry><stentry>Warning</stentry><stentry>A reference to "<varname>%2</varname>" appears to reference a DITA document, but the format attribute has inherited a value of "<varname>%1</varname>". The document will not be processed as DITA. </stentry><stentry id="DOTX016W-extra"> </stentry></strow><strow id="DOTX017E"><stentry><msgnum>DOTX017E</msgnum></stentry><stentry>Error</stentry><stentry>Found a link or cross reference with an empty href attribute (href=""). Remove the empty href attribute or provide a value.</stentry><stentry id="DOTX017E-extra"> </stentry></strow><strow id="DOTX018I"><stentry><msgnum>DOTX018I</msgnum></stentry><stentry>Informational</stentry><stentry>The type attribute on a topicref was set to '<varname>%1</varname>', but the topicref references a more specific '<varname>%2</varname>' topic. Note that the type attribute cascades in maps, so the value '<varname>%1</varname>' may come from an ancestor topicref. </stentry><stentry id="DOTX018I-extra"> </stentry></strow><strow id="DOTX019W"><stentry><msgnum>DOTX019W</msgnum></stentry><stentry>Warning</stentry><stentry>The type attribute on a topicref was set to '<varname>%1</varname>', but the topicref references a '<varname>%2</varname>' topic. This may cause your links to sort incorrectly in the output. Note that the type attribute cascades in maps, so the value '<varname>%1</varname>' may come from an ancestor topicref. </stentry><stentry id="DOTX019W-extra"> </stentry></strow><strow id="DOTX020E"><stentry><msgnum>DOTX020E</msgnum></stentry><stentry>Error</stentry><stentry>Missing navtitle attribute or element for peer topic "<varname>%1</varname>". References must provide a local navigation title when the target is not a local DITA resource.</stentry><stentry id="DOTX020E-extra"> </stentry></strow><strow id="DOTX021E"><stentry><msgnum>DOTX021E</msgnum></stentry><stentry>Error</stentry><stentry>Missing navtitle attribute or element for non-DITA resource "<varname>%1</varname>". References must provide a local navigation title when the target is not a local DITA resource.</stentry><stentry id="DOTX021E-extra"> </stentry></strow><strow id="DOTX022W"><stentry><msgnum>DOTX022W</msgnum></stentry><stentry>Warning</stentry><stentry>Unable to retrieve navtitle from target: '<varname>%1</varname>'. Using linktext (specified in topicmeta) as the navigation title. </stentry><stentry id="DOTX022W-extra"> </stentry></strow><strow id="DOTX023W"><stentry><msgnum>DOTX023W</msgnum></stentry><stentry>Warning</stentry><stentry>Unable to retrieve navtitle from target: '<varname>%1</varname>'. </stentry><stentry id="DOTX023W-extra"> </stentry></strow><strow id="DOTX024E"><stentry><msgnum>DOTX024E</msgnum></stentry><stentry>Error</stentry><stentry>Missing linktext and navtitle for peer topic "<varname>%1</varname>". References must provide a local navigation title when the target is not a local DITA resource.</stentry><stentry id="DOTX024E-extra"> </stentry></strow><strow id="DOTX025E"><stentry><msgnum>DOTX025E</msgnum></stentry><stentry>Error</stentry><stentry>Missing linktext and navtitle for non-DITA resource "<varname>%1</varname>". References must provide a local navigation title when the target is not a local DITA resource.</stentry><stentry id="DOTX025E-extra"> </stentry></strow><strow id="DOTX026W"><stentry><msgnum>DOTX026W</msgnum></stentry><stentry>Warning</stentry><stentry>Unable to retrieve linktext from target: '<varname>%1</varname>'. Using navigation title as fallback. </stentry><stentry id="DOTX026W-extra"> </stentry></strow><strow id="DOTX027W"><stentry><msgnum>DOTX027W</msgnum></stentry><stentry>Warning</stentry><stentry>Unable to retrieve linktext from target: '<varname>%1</varname>'. </stentry><stentry id="DOTX027W-extra"> </stentry></strow><strow id="DOTX028E"><stentry><msgnum>DOTX028E</msgnum></stentry><stentry>Error</stentry><stentry>Link or cross reference must contain a valid href or keyref attribute; no link target is specified. </stentry><stentry id="DOTX028E-extra"> </stentry></strow><strow id="DOTX029I"><stentry><msgnum>DOTX029I</msgnum></stentry><stentry>Informational</stentry><stentry>The type attribute on a <varname>%1</varname> element was set to <varname>%3</varname>, but the reference is to a more specific <varname>%4</varname> <varname>%2</varname>. This may cause your links to sort incorrectly in the output. </stentry><stentry id="DOTX029I-extra"> </stentry></strow><strow id="DOTX030W"><stentry><msgnum>DOTX030W</msgnum></stentry><stentry>Warning</stentry><stentry>The type attribute on a <varname>%1</varname> element was set to <varname>%3</varname>, but the reference is to a <varname>%4</varname> <varname>%2</varname>. This may cause your links to sort incorrectly in the output. </stentry><stentry id="DOTX030W-extra"> </stentry></strow><strow id="DOTX031E"><stentry><msgnum>DOTX031E</msgnum></stentry><stentry>Error</stentry><stentry>The file <varname>%1</varname> is not available to resolve link information. </stentry><stentry id="DOTX031E-extra"> </stentry></strow><strow id="DOTX032E"><stentry><msgnum>DOTX032E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to retrieve link text from target: '<varname>%1</varname>'. If the target is not accessible at build time, or does not have a title, provide the link text inside the reference.</stentry><stentry id="DOTX032E-extra"> </stentry></strow><strow id="DOTX033E"><stentry><msgnum>DOTX033E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to generate link text for a cross reference to a list item: '<varname>%1</varname>' </stentry><stentry id="DOTX033E-extra"> </stentry></strow><strow id="DOTX034E"><stentry><msgnum>DOTX034E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to generate link text for a cross reference to an undered list item: '<varname>%1</varname>' </stentry><stentry id="DOTX034E-extra"> </stentry></strow><strow id="DOTX035E"><stentry><msgnum>DOTX035E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to generate the correct number for a cross reference to a footnote: '<varname>%1</varname>' </stentry><stentry id="DOTX035E-extra"> </stentry></strow><strow id="DOTX036E"><stentry><msgnum>DOTX036E</msgnum></stentry><stentry>Error</stentry><stentry>Unable to generate link text for a cross reference to a dlentry (the dlentry or term could not be found): '<varname>%1</varname>' </stentry><stentry id="DOTX036E-extra"> </stentry></strow><strow id="DOTX037W"><stentry><msgnum>DOTX037W</msgnum></stentry><stentry>Warning</stentry><stentry>No title found for this document; using "***" in XHTML title bar. </stentry><stentry id="DOTX037W-extra"> </stentry></strow><strow id="DOTX038I"><stentry><msgnum>DOTX038I</msgnum></stentry><stentry>Informational</stentry><stentry>The longdescref attribute on tag '<varname>%1</varname>' will be ignored. Accessibility for object elements needs to be handled another way. </stentry><stentry id="DOTX038I-extra"> </stentry></strow><strow id="DOTX039W"><stentry><msgnum>DOTX039W</msgnum></stentry><stentry>Warning</stentry><stentry>Required cleanup area found. To remove this message and hide the content, build your content without using the DRAFT parameter.</stentry><stentry id="DOTX039W-extra"> </stentry></strow><strow id="DOTX040I"><stentry><msgnum>DOTX040I</msgnum></stentry><stentry>Informational</stentry><stentry>Draft comment area found. To remove this message and hide the comments, build your content without using the DRAFT parameter.</stentry><stentry id="DOTX040I-extra"> </stentry></strow><strow id="DOTX041W"><stentry><msgnum>DOTX041W</msgnum></stentry><stentry>Warning</stentry><stentry>Found more than one title element in a section. Using the first one for the section's title. </stentry><stentry id="DOTX041W-extra"> </stentry></strow><strow id="DOTX042I"><stentry><msgnum>DOTX042I</msgnum></stentry><stentry>Informational</stentry><stentry>DITAVAL based flagging is not currently supported for inline phrases in XHTML; ignoring flag value on '<varname>%1</varname>' attribute. </stentry><stentry id="DOTX042I-extra"> </stentry></strow><strow id="DOTX043I"><stentry><msgnum>DOTX043I</msgnum></stentry><stentry>Informational</stentry><stentry>The link to '<varname>%1</varname>' may appear more than once in '<varname>%2</varname>'. </stentry><stentry id="DOTX043I-extra"> </stentry></strow><strow id="DOTX044E"><stentry><msgnum>DOTX044E</msgnum></stentry><stentry>Error</stentry><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.</stentry><stentry id="DOTX044E-extra"> </stentry></strow><strow id="DOTX045W"><stentry><msgnum>DOTX045W</msgnum></stentry><stentry>Warning</stentry><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.</stentry><stentry id="DOTX045W-extra"> </stentry></strow><strow id="DOTX046W"><stentry><msgnum>DOTX046W</msgnum></stentry><stentry>Warning</stentry><stentry>Area shape should be: default, rect, circle, poly, or blank (no value). The value '<varname>%1</varname>' is not recognized. </stentry><stentry id="DOTX046W-extra"> </stentry></strow><strow id="DOTX047W"><stentry><msgnum>DOTX047W</msgnum></stentry><stentry>Warning</stentry><stentry>Area coordinates are blank. Coordinate points for the shape need to be specified. </stentry><stentry id="DOTX047W-extra"> </stentry></strow><strow id="DOTX048I"><stentry><msgnum>DOTX048I</msgnum></stentry><stentry>Informational</stentry><stentry>In order to include peer or external topic '<varname>%1</varname>' in your help file, you may need to recompile the CHM file after making the file available. </stentry><stentry id="DOTX048I-extra"> </stentry></strow><strow id="DOTX049I"><stentry><msgnum>DOTX049I</msgnum></stentry><stentry>Informational</stentry><stentry>References to non-dita files will be ignored by the PDF, ODT, and RTF output transforms. </stentry><stentry id="DOTX049I-extra"> </stentry></strow><strow id="DOTX050W"><stentry><msgnum>DOTX050W</msgnum></stentry><stentry>Warning</stentry><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.</stentry><stentry id="DOTX050W-extra"> </stentry></strow><strow id="DOTX052W"><stentry><msgnum>DOTX052W</msgnum></stentry><stentry>Warning</stentry><stentry>No string named '<varname>%1</varname>' was found when creating generated text; using the value '<varname>%1</varname>' in your output file. </stentry><stentry id="DOTX052W-extra"> </stentry></strow><strow id="DOTX053E"><stentry><msgnum>DOTX053E</msgnum></stentry><stentry>Error</stentry><stentry>A element that references another map indirectly includes itself, which results in an infinite loop. The original map reference is to '<varname>%1</varname>'. </stentry><stentry id="DOTX053E-extra"> </stentry></strow><strow id="DOTX054W"><stentry><msgnum>DOTX054W</msgnum></stentry><stentry>Warning</stentry><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.</stentry><stentry id="DOTX054W-extra"> </stentry></strow><strow id="DOTX055W"><stentry><msgnum>DOTX055W</msgnum></stentry><stentry>Warning</stentry><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".</stentry><stentry id="DOTX055W-extra"> </stentry></strow><strow id="DOTX056W"><stentry><msgnum>DOTX056W</msgnum></stentry><stentry>Warning</stentry><stentry>The file '<varname>%1</varname>' is not available to resolve link information. </stentry><stentry id="DOTX056W-extra"> </stentry></strow><strow id="DOTX057W"><stentry><msgnum>DOTX057W</msgnum></stentry><stentry>Warning</stentry><stentry>The link or cross reference target '<varname>%1</varname>' cannot be found, which may cause errors creating links or cross references in your output file. </stentry><stentry id="DOTX057W-extra"> </stentry></strow><strow id="DOTX058W"><stentry><msgnum>DOTX058W</msgnum></stentry><stentry>Warning</stentry><stentry>No glossary entry was found associated with key '<varname>%1</varname>' on <varname>%2</varname> element. The build will try to determine the best display text and hover text for terms and abbreviations. </stentry><stentry id="DOTX058W-extra"> </stentry></strow><strow id="DOTX060W"><stentry><msgnum>DOTX060W</msgnum></stentry><stentry>Warning</stentry><stentry>Key '<varname>%1</varname>' 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.</stentry><stentry id="DOTX060W-extra"> </stentry></strow><strow id="DOTX061W"><stentry><msgnum>DOTX061W</msgnum></stentry><stentry>Warning</stentry><stentry>ID '<varname>%1</varname>' 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. </stentry><stentry id="DOTX061W-extra"> </stentry></strow><strow id="DOTX062I"><stentry><msgnum>DOTX062I</msgnum></stentry><stentry>Informational</stentry><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.</stentry><stentry id="DOTX062I-extra"> </stentry></strow><strow id="DOTX063W"><stentry><msgnum>DOTX063W</msgnum></stentry><stentry>Warning</stentry><stentry>The dita document '<varname>%1</varname>' 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.</stentry><stentry id="DOTX063W-extra"> </stentry></strow><strow id="DOTX064W"><stentry><msgnum>DOTX064W</msgnum></stentry><stentry>Warning</stentry><stentry>The copy-to attribute [copy-to="<varname>%1</varname>"] uses the name of a file that already exists, so this attribute is ignored. </stentry><stentry id="DOTX064W-extra"> </stentry></strow><strow id="DOTX065W"><stentry><msgnum>DOTX065W</msgnum></stentry><stentry>Warning</stentry><stentry>Two unique source files each specify copy-to="<varname>%2</varname>", which results in a collision. The value associated with href="<varname>%1</varname>" is ignored. </stentry><stentry id="DOTX065W-extra"> </stentry></strow><strow id="DOTX066W"><stentry><msgnum>DOTX066W</msgnum></stentry><stentry>Warning</stentry><stentry>Template "<varname>%1</varname>" is deprecated. Remove references to this template from your custom XSLT or plug-ins.</stentry><stentry id="DOTX066W-extra"> </stentry></strow><strow id="DOTX067E"><stentry><msgnum>DOTX067E</msgnum></stentry><stentry>Error</stentry><stentry>No string named '<varname>%1</varname>' was found for language '<varname>%2</varname>'. Add a mapping for the string '<varname>%1</varname>'.</stentry><stentry id="DOTX067E-extra"> </stentry></strow><strow id="DOTX068W"><stentry><msgnum>DOTX068W</msgnum></stentry><stentry>Warning</stentry><stentry>A topicref element that references a map contains child topicref elements. Child topicref elements are ignored.</stentry><stentry id="DOTX068W-extra"> </stentry></strow><strow id="PDFJ001E"><stentry><msgnum>PDFJ001E</msgnum></stentry><stentry>Error</stentry><stentry>Index entry '<varname>%1</varname>' is dropped, because corresponding group is not found. </stentry><stentry id="PDFJ001E-extra"> </stentry></strow><strow id="PDFJ002E"><stentry><msgnum>PDFJ002E</msgnum></stentry><stentry>Error</stentry><stentry>Build stopped. Problems occured during Index preprocess task. Please check the messages above. </stentry><stentry id="PDFJ002E-extra"> </stentry></strow><strow id="PDFX001W"><stentry><msgnum>PDFX001W</msgnum></stentry><stentry>Warning</stentry><stentry>There is no index entry found which closing range for ID="<varname>%1</varname>". </stentry><stentry id="PDFX001W-extra"> </stentry></strow><strow id="PDFX002W"><stentry><msgnum>PDFX002W</msgnum></stentry><stentry>Warning</stentry><stentry>There are multiple index entry found which is opening range for ID="<varname>%1</varname>" but there is only one which close it or ranges are overlapping. </stentry><stentry id="PDFX002W-extra"> </stentry></strow><strow id="PDFX003W"><stentry><msgnum>PDFX003W</msgnum></stentry><stentry>Warning</stentry><stentry>There are multiple index entry found which closing range for ID="<varname>%1</varname>". </stentry><stentry id="PDFX003W-extra"> </stentry></strow><strow id="PDFX004F"><stentry><msgnum>PDFX004F</msgnum></stentry><stentry>Fatal</stentry><stentry>Empty href was specified for some topic reference. Please correct your ditamap or bookmap file.</stentry><stentry id="PDFX004F-extra"> </stentry></strow><strow id="PDFX005F"><stentry><msgnum>PDFX005F</msgnum></stentry><stentry>Fatal</stentry><stentry>Topic reference (href : <varname>%1</varname>) not found. Reference may be incorrect. Please correct your ditamap or bookmap file.</stentry><stentry id="PDFX005F-extra"> </stentry></strow><strow id="PDFX006E"><stentry><msgnum>PDFX006E</msgnum></stentry><stentry>Error</stentry><stentry>Number of columns must be specified. </stentry><stentry id="PDFX006E-extra"> </stentry></strow><strow id="PDFX007W"><stentry><msgnum>PDFX007W</msgnum></stentry><stentry>Warning</stentry><stentry>There is no index entry found which opening range for ID="<varname>%1</varname>". </stentry><stentry id="PDFX007W-extra"> </stentry></strow><strow id="PDFX008W"><stentry><msgnum>PDFX008W</msgnum></stentry><stentry>Warning</stentry><stentry>Font definition not found for the logical name or alias '<varname>%1</varname>'. </stentry><stentry id="PDFX008W-extra"> </stentry></strow><strow id="PDFX009E"><stentry><msgnum>PDFX009E</msgnum></stentry><stentry>Error</stentry><stentry>Attribute set reflection can't handle XSLT element <varname>%1</varname>. </stentry><stentry id="PDFX009E-extra"> </stentry></strow><strow id="PDFX010W"><stentry><msgnum>PDFX010W</msgnum></stentry><stentry>Warning</stentry><stentry>Index generation is not supported in FOP. </stentry><stentry id="PDFX010W-extra"> </stentry></strow><strow id="PDFX011E"><stentry><msgnum>PDFX011E</msgnum></stentry><stentry>Error</stentry><stentry>Both index-see and <varname>%1</varname> defined for index entry '<varname>%2</varname>'. Recovering by treating the index-see as an index-see-also.</stentry><stentry id="PDFX011E-extra"> </stentry></strow></simpletable></refbody></reference>
|
|---|
