Почетна Преглед Помоћ
Пријавите се
bn
/
se
2
0
Креирај огранак 0
Датотеке Дискусије 0 Захтеви за спајање 0 Вики
Дрво: 1dd225b210
Гране Ознаке
se
/
SE
/
schema
/
WPS_Functions
/
dita-ot
/
dita-ot-3.3.3
/
doc
/
topics
/
DITA-messages-details.html

DITA-messages-details.html 52 KB
Историја Датотека

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666 
  1. <!DOCTYPE html
    2. 

  2.   SYSTEM "about:legacy-compat">
    3. 

  3. <html lang="en-us"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2019"><meta name="DC.rights.owner" content="(C) Copyright 2019"><meta name="DC.type" content="reference"><meta name="description" content="This topic lists each error message generated by the toolkit and provides additional information that might be helpful in understanding and resolving the error condition. If your toolkit installation includes custom plug-ins that define additional messages, you can add to this list by rebuilding the DITA-OT documentation."><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="errormessages"><meta name="DC.language" content="en-US"><link rel="stylesheet" type="text/css" href="../css/commonltr.css"><link rel="stylesheet" type="text/css" href="../css/dita-ot-doc.css"><title>DITA-OT error messages</title></head><body id="errormessages"><header role="banner"><div class="header">
    4. 

  4.   <p>DITA Open Toolkit</p>
    5. 

  5.   <hr>
    6. 

  6. </div></header><nav role="toc"><ul></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1">
    7. 

  7.   <h1 class="title topictitle1" id="ariaid-title1">DITA-OT error messages</h1>
    8. 

  8.   
    9. 

  9.   <div class="body refbody"><p class="shortdesc">This topic lists each error message
    10. 

  10.     generated by the toolkit and provides additional information that might be helpful in understanding and resolving
    11. 

  11.     the error condition. If your toolkit installation includes custom plug-ins that define additional messages, you can
    12. 

  12.     add to this list by rebuilding the DITA-OT documentation.</p>
    13. 

  13.     <section class="section" id="errormessages__overview">
    14. 

  14.       <p class="p">Each message ID is composed of a message prefix, a message number, and a letter that indicates the severity
    15. 

  15.         level (I, W, E, or F). </p>
    16. 

  16.       <p class="p">The toolkit uses the following severity scale:</p>
    17. 

  17.       <dl class="dl" id="errormessages__severity-levels">
    18. 

  18.         
    19. 

  19.           <dt class="dt dlterm">Info (I)</dt>
    20. 

  20.           <dd class="dd">Informational messages highlight the progress of transformation and call attention to conditions of which
    21. 

  21.             you should be aware. For example, draft comments are enabled and will be rendered in the output.</dd>
    22. 

  22.         
    23. 

  23.         
    24. 

  24.           <dt class="dt dlterm">Warning (W)</dt>
    25. 

  25.           <dd class="dd">The toolkit encountered a problem that should be corrected. Processing will continue, but the output might
    26. 

  26.             not be as expected.</dd>
    27. 

  27.         
    28. 

  28.         
    29. 

  29.           <dt class="dt dlterm">Error (E)</dt>
    30. 

  30.           <dd class="dd">The toolkit encountered a more severe problem, and the output is affected. For example, some content is
    31. 

  31.             missing or invalid, or the content is not rendered in the output</dd>
    32. 

  32.         
    33. 

  33.         
    34. 

  34.           <dt class="dt dlterm">Fatal (F)</dt>
    35. 

  35.           <dd class="dd">The toolkit encountered a severe condition, processing stopped, and no output is generated.</dd>
    36. 

  36.         
    37. 

  37.       </dl>
    38. 

  38.       <p class="p">Plug-ins may be used to add additional messages to the toolkit; for more information, see <a class="xref" href="rebuilding-docs.html" title="DITA-OT ships with a Gradle build script that enables you to rebuild the toolkit documentation. This is especially helpful if your environment contains plug-ins that add new extension points, messages, or parameters to the toolkit.">Rebuilding the DITA-OT documentation</a>.</p>
    39. 

  39.     </section>
    40. 

  40.     <table class="simpletable"><colgroup><col style="width:100%"></colgroup><thead><tr class="sthead">
    41. 

  41.         <th class="stentry" scope="col">Individual cells in this table may be used to push additional explanations for any existing error
    42. 

  42.           message into the generated message topic.</th>
    43. 

  43.       </tr></thead><tbody><tr class="strow">
    44. 

  44.         <td class="stentry">To add additional explanation to any message, add the explanation to this table in a single cell, and
    45. 

  45.           set the following attributes on the <code class="keyword markupname xmlelement">&lt;stentry&gt;</code> tag:
    46. 

  46.           <ul class="ul">
    47. 

  47.             <li class="li"><code class="ph codeph">conref="DITA-messages.xml#msgs/MESSAGEID-extra"</code> -- for example, use the following to
    48. 

  48.               add additional info to message DOTX001F:
    49. 

  49.               <code class="ph codeph">conref="DITA-messages.xml#msgs/DOTX001F-extra"</code></li>
    50. 

  50.             <li class="li"><code class="ph codeph">conaction="pushreplace"</code></li>
    51. 

  51.           </ul></td>
    52. 

  52.       </tr><tr class="strow">
    53. 

  53.         <td class="stentry">Default transformation types
    54. 

  54.           that ship with the toolkit include dita, eclipsehelp, html5, htmlhelp, markdown variants, pdf (or pdf2),
    55. 

  55.           tocjs, troff, xhtml, and xhtml. Additional transformation types may be available if toolkit plug-ins are
    56. 

  56.           installed.</td>
    57. 

  57.       </tr><tr class="strow">
    58. 

  58.         <td class="stentry">The input parameter was not
    59. 

  59.           specified, so there is no DITA or DITAMAP file to transform. Ensure the parameter is set properly; see <a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">DITA-OT common parameters (args.input)</a> if you are unsure how to specify the
    60. 

  60.           input file.
    61. 

  61.         
    62. 

  62.         </td>
    63. 

  63.       </tr><tr class="strow">
    64. 

  64.         <td class="stentry">An alternate stylesheet was
    65. 

  65.           specified to run in place of the default XSLT output process, but that stylesheet could not be loaded. Please
    66. 

  66.           correct the parameter to specify a valid stylesheet.</td>
    67. 

  67.       </tr><tr class="strow">
    68. 

  68.         <td class="stentry">This optional parameter is used
    69. 

  69.           to set an extension for DITA topic documents in the temporary processing directory. Only "dita", ".dita",
    70. 

  70.           "xml", or ".xml" are allowed.</td>
    71. 

  71.       </tr><tr class="strow">
    72. 

  72.         <td class="stentry">If the CSSPATH uses an absolute
    73. 

  73.           path, it should be one that can still be accessed after the files are moved to another system (such as
    74. 

  74.             <code class="ph codeph">http://www.example.org/</code>). Absolute paths on the local file system will be broken if the
    75. 

  75.           content is moved to a new system.</td>
    76. 

  76.       </tr><tr class="strow">
    77. 

  77.         <td class="stentry">The running footer file, which
    78. 

  78.           contains content to be added to the bottom of each XHTML output topic, cannot be located or read. This is
    79. 

  79.           usually caused by a typo in the parameter value. You should also ensure that the value is not specified with
    80. 

  80.           "file:" as a prefix.</td>
    81. 

  81.       </tr><tr class="strow">
    82. 

  82.         <td class="stentry">The running header file, which
    83. 

  83.           contains content to be added to the top of each XHTML output topic, cannot be located or read. This is usually
    84. 

  84.           caused by a typo in the parameter value. You should also ensure that the value is not specified with "file:"
    85. 

  85.           as a prefix.</td>
    86. 

  86.       </tr><tr class="strow">
    87. 

  87.         <td class="stentry">The running heading file, which
    88. 

  88.           contains content to be added to the <code class="keyword markupname xmlelement">&lt;head&gt;</code> section of each HTML output topic, cannot be
    89. 

  89.           located or read. This is usually caused by a typo in the parameter value. You should also ensure that the
    90. 

  90.           value is not specified with "file:" as a prefix.</td>
    91. 

  91.       </tr><tr class="strow">
    92. 

  92.         <td class="stentry">An alternate stylesheet was
    93. 

  93.           specified to run in place of the default XSL-FO output process, but that stylesheet could not be loaded.
    94. 

  94.           Please correct the parameter to specify a valid stylesheet.</td>
    95. 

  95.       </tr><tr class="strow">
    96. 

  96.         
    97. 

  97.         <td class="stentry">According to the OASIS DITA
    98. 

  98.           Specification, the <code class="keyword markupname xmlelement">&lt;index-see&gt;</code> element should be ignored if the parent
    99. 

  99.             <code class="keyword markupname xmlelement">&lt;indexterm&gt;</code> contains other <code class="keyword markupname xmlelement">&lt;indexterm&gt;</code> children.</td>
    100. 

  100.       </tr><tr class="strow">
    101. 

  101.         <td class="stentry">According to the OASIS DITA
    102. 

  102.           Specification, the <code class="keyword markupname xmlelement">&lt;index-see-also&gt;</code> element should be ignored if the parent
    103. 

  103.             <code class="keyword markupname xmlelement">&lt;indexterm&gt;</code> contains other <code class="keyword markupname xmlelement">&lt;indexterm&gt;</code> children.</td>
    104. 

  104.       </tr><tr class="strow">
    105. 

  105.         <td class="stentry">Please ensure that the input
    106. 

  106.           file path and file name were entered correctly.</td>
    107. 

  107.       </tr><tr class="strow">
    108. 

  108.         <td class="stentry"></td>
    109. 

  109.       </tr><tr class="strow">
    110. 

  110.         <td class="stentry">The transform was unable to
    111. 

  111.           create files properly during the transform; results may not be as expected.</td>
    112. 

  112.       </tr><tr class="strow">
    113. 

  113.         <td class="stentry">This message may indicate an
    114. 

  114.           invalid input file (such as accidentally specifying a PDF file as input rather than a DITA map file), an input
    115. 

  115.           file that uses elements which are not allowed, are not part or a DITA file that has errors and cannot be
    116. 

  116.           parsed as XML. You could also be using a specialized DITA document type that needs external plug-ins in order
    117. 

  117.           to be parsed correctly. The message issued by the XML parser should provide additional information to help
    118. 

  118.           diagnose the cause.</td>
    119. 

  119.       </tr><tr class="strow">
    120. 

  120.         <td class="stentry">This message may indicate a
    121. 

  121.           reference to an invalid file (such as accidentally referencing a PDF or unknown XML file as if it was DITA), a
    122. 

  122.           referenced file that uses elements which are not allowed, or a referenced DITA file that has errors and cannot
    123. 

  123.           be parsed as XML. You could also be using a specialized DITA document type that needs external plug-ins in
    124. 

  124.           order to be parsed correctly. The message issued by the XML parser should provide additional information to
    125. 

  125.           help diagnose the cause.</td>
    126. 

  126.       </tr><tr class="strow">
    127. 

  127.         <td class="stentry">An empty
    128. 

  128.             <code class="keyword markupname xmlelement">&lt;indexterm&gt;</code> element was found, and will appear in the index as ***. This index term
    129. 

  129.           should be removed from the source.</td>
    130. 

  130.       </tr><tr class="strow">
    131. 

  131.         <td class="stentry">This will appear when one
    132. 

  132.           installed plug-in requires another in order to function correctly, but the required plug-in is not found. The
    133. 

  133.           installed plug-in will be ignored.</td>
    134. 

  134.       </tr><tr class="strow">
    135. 

  135.         <td class="stentry">This may appear if filter
    136. 

  136.           conditions on the root element of a topic cause the entire topic to be filtered out. To remove this message,
    137. 

  137.           you could place any filter conditions on the reference to this file, which will prevent the build from
    138. 

  138.           accessing this file.</td>
    139. 

  139.       </tr><tr class="strow">
    140. 

  140.         <td class="stentry">Either the input file or the
    141. 

  141.           ditaval file should change, otherwise your build is explicitly excluding all content.</td>
    142. 

  142.       </tr><tr class="strow">
    143. 

  143.         <td class="stentry">Check whether the image exists
    144. 

  144.           in the source location or already exists in the output directory.
    145. 

  145.           
    146. 

  146.         </td>
    147. 

  147.       </tr><tr class="strow">
    148. 

  148.         <td class="stentry">This message should only appear
    149. 

  149.           in the following cases:
    150. 

  150.           <ul class="ul">
    151. 

  151.             <li class="li">Errors earlier in the transform prevented this step of the transform from running; correct any errors
    152. 

  152.               and try the build again.</li>
    153. 

  153.             <li class="li">An Ant build or plug-in is directly calling the toolkit’s topic merge module, and is doing so
    154. 

  154.               improperly; in this case the Ant build or plug-in needs to be fixed.</li>
    155. 

  155.             <li class="li">In the past, problems have been encountered when calling this module with an absolute path; this should
    156. 

  156.               no longer be an issue, but may be fixed in older releases by updating the Ant build or plug-in.</li>
    157. 

  157.           </ul></td>
    158. 

  158.       </tr><tr class="strow">
    159. 

  159.         <td class="stentry">This message should only appear
    160. 

  160.           if an Ant build or plug-in is directly calling the toolkit’s topic merge module, or if earlier errors resulted
    161. 

  161.           in problems with some of the content. If the topic merge module is called correctly, then this indicates a
    162. 

  162.           program error that should be reported to the DITA-OT development team via the <a class="xref" href="https://github.com/dita-ot/dita-ot/issues" target="_blank">GitHub issues tracker</a>.
    163. 

  163.         </td>
    164. 

  164.       </tr><tr class="strow">
    165. 

  165.         <td class="stentry">When referencing a non-DITA
    166. 

  166.           file, the format attribute should indicate the type of file referenced (such as "html" for HTML topics or
    167. 

  167.           "pdf" for PDF files). Otherwise, the transform may attempt to parse the referenced document as a DITA
    168. 

  168.           topic.</td>
    169. 

  169.       </tr><tr class="strow">
    170. 

  170.         <td class="stentry">The domains attribute is used in
    171. 

  171.           specialized DITA documents to help determine which domain elements are legal. This message will only appear if
    172. 

  172.           a DITA specialization was not defined properly.</td>
    173. 

  173.       </tr><tr class="strow">
    174. 

  174.         <td class="stentry">All specialized DITA elements
    175. 

  175.           must define a class attribute to provide ancestry information. This message will only appear if a specialized
    176. 

  176.           DITA element did not define a class attribute, or if non-DITA elements are included in a DITA
    177. 

  177.           context.</td>
    178. 

  178.       </tr><tr class="strow">
    179. 

  179.         <td class="stentry">This informational message is
    180. 

  180.           intended to help you catch filter conditions that may have been specified improperly; if the value is correct,
    181. 

  181.           no action is needed.</td>
    182. 

  182.       </tr><tr class="strow">
    183. 

  183.         <td class="stentry"></td>
    184. 

  184.       </tr><tr class="strow">
    185. 

  185.         <td class="stentry">DITA processing is based on
    186. 

  186.           class attributes defined for every element. Usually these are defaulted in the DTD or Schema; if no DTD or
    187. 

  187.           Schema is used, the class attributes must be explicitly included in the map or topic.</td>
    188. 

  188.       </tr><tr class="strow">
    189. 

  189.         <td class="stentry">This will appear when a topic is
    190. 

  190.           outside the scope of the map; for example, if the main input map references
    191. 

  191.             <span class="ph filepath">"../other-directory/some.dita"</span>. The result would cause an output file to be created
    192. 

  192.           outside of the output directory. See <a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">DITA-OT common parameters (outer.control
    193. 

  193.             and generate.copy.outer)</a> for details.
    194. 

  194.           
    195. 

  195.         </td>
    196. 

  196.       </tr><tr class="strow">
    197. 

  197.         <td class="stentry">This will appear when a topic is
    198. 

  198.           outside the scope of the map; for example, if the main input map references
    199. 

  199.             <span class="ph filepath">"../other-directory/some.dita"</span>. The result would cause an output file to be created
    200. 

  200.           outside of the output directory. If you do not want to see the warning message, please use the Ant parameter
    201. 

  201.           'outer.control', and set the value to "quiet". Otherwise, move the referenced file into the input dita/map
    202. 

  202.           directory. See <a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">DITA-OT common parameters (outer.control and
    203. 

  203.             generate.copy.outer)</a> for details.
    204. 

  204.           </td>
    205. 

  205.       </tr><tr class="strow">
    206. 

  206.         <td class="stentry">DITA processing is based on
    207. 

  207.           class attributes defined for every element. Usually these are defaulted in the DTD or Schema; if validation
    208. 

  208.           against the DTD or Schema is turned off, the class attributes must be explicitly included in the map or
    209. 

  209.           topic.</td>
    210. 

  210.       </tr><tr class="strow">
    211. 

  211.         <td class="stentry">This appears to indicate an
    212. 

  212.           error in creating specialized metadata elements. Please verify that the document type you are using is
    213. 

  213.           complete and complies with DITA Specialization rules.
    214. 

  214.           
    215. 

  215.         </td>
    216. 

  216.       </tr><tr class="strow">
    217. 

  217.         <td class="stentry">Please see the topic on <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute" target="_blank">Conref Push</a> in the DITA specification for details on expected syntax
    218. 

  218.           for this function.</td>
    219. 

  219.       </tr><tr class="strow">
    220. 

  220.         <td class="stentry">Please see the topic on <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute" target="_blank">Conref Push</a> in the DITA specification for details on expected syntax
    221. 

  221.           for this function.</td>
    222. 

  222.       </tr><tr class="strow">
    223. 

  223.         <td class="stentry">The conref attribute must be a
    224. 

  224.           URI reference to a DITA element. Please see the topic on <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank">URI-based addressing</a> in the DITA specification for details on the
    225. 

  225.           expected syntax.</td>
    226. 

  226.       </tr><tr class="strow">
    227. 

  227.         <td class="stentry">The conref push function was
    228. 

  228.           used to replace a single element with two or more alternatives. Only one element may directly replace another
    229. 

  229.           using conref push. See <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute" target="_blank">Conref Push</a> in the DITA specification for more information about the
    230. 

  230.           conref push "replace" function.</td>
    231. 

  231.       </tr><tr class="strow">
    232. 

  232.         <td class="stentry">The target for a conref push
    233. 

  233.           action does not exist; please make sure that the syntax is correct and that the target exists. See the topic
    234. 

  234.           on <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank">URI-based addressing</a> in the DITA specification for details on the
    235. 

  235.           expected syntax. If the syntax is correct, it is possible that the target was filtered out of your build using
    236. 

  236.           a DITAVAL file.</td>
    237. 

  237.       </tr><tr class="strow">
    238. 

  238.         <td class="stentry">Please see the topic on <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconactionattribute.html#theconactionattribute" target="_blank">Conref Push</a> in the DITA specification for details on expected syntax
    239. 

  239.           for this function.</td>
    240. 

  240.       </tr><tr class="strow">
    241. 

  241.         <td class="stentry">This informational message is
    242. 

  242.           intended to help you catch catch duplicate key definitions; if the keys are defined as expected, no action is
    243. 

  243.           needed.</td>
    244. 

  244.       </tr><tr class="strow">
    245. 

  245.         <td class="stentry">See <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/langRef/attributes/theconkeyrefattribute.html#theconkeyrefattribute" target="_blank">the conkeyref definition</a> for details on expected syntax and
    246. 

  246.           usage.</td>
    247. 

  247.       </tr><tr class="strow">
    248. 

  248.         <td class="stentry">This message is intended to help
    249. 

  249.           you locate incorrectly specified keys; if the key was specified correctly, this message may be
    250. 

  250.           ignored.</td>
    251. 

  251.       </tr><tr class="strow">
    252. 

  252.         <td class="stentry">A DITA Subject Scheme map was
    253. 

  253.           used to limit values that are available to the specified attribute. Please correct the attribute so that it
    254. 

  254.           uses one of the allowed values.</td>
    255. 

  255.       </tr><tr class="strow">
    256. 

  256.         <td class="stentry">The Eclipse index will contain a
    257. 

  257.           value such as "See also otherEntry", but otherEntry does not exist in this index. The index reference will be
    258. 

  258.           broken unless this plug-in is <em class="ph i">always</em> loaded into Eclipse with another plug-in that defines otherEntry
    259. 

  259.           as an index term.</td>
    260. 

  260.       </tr><tr class="strow">
    261. 

  261.         <td class="stentry">The target for a coderef
    262. 

  262.           element, which specifies an external text-based file, could not be located or loaded. Please verify that the
    263. 

  263.           reference is correct.
    264. 

  264.           <p class="p">Note that for security reasons, references to code samples outside of the scope of the map directory are
    265. 

  265.             not supported by default, as this could allow a reference to access and display any restricted or hidden
    266. 

  266.             file on the system. If you are certain that the path is valid and the file should be loaded, the current
    267. 

  267.             workaround is to set a parameter to allow these references. See <a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">DITA-OT
    268. 

  268.               common parameters (outer.control and generate.copy.outer)</a> for details.</p></td>
    269. 

  269.       </tr><tr class="strow">
    270. 

  270.         <td class="stentry">DITA-OT supports a special
    271. 

  271.           syntax on coderef elements to specify the character set of the target document. See <a class="xref" href="../reference/extended-functionality.html" title="DITA-OT provides additional processing support beyond that which is mandated by the DITA specification. These extensions can be used to define character encodings or line ranges for code references, normalize indendation, add line numbers or display whitespace characters in code blocks.">Extended codeblock processing</a> for details on the expected syntax.</td>
    272. 

  272.       </tr><tr class="strow">
    273. 

  273.         <td class="stentry">By default, DITA-OT supports the
    274. 

  274.           extensions "dita" and "xml" for DITA topics, as mandated by the DITA specification. Please verify that your
    275. 

  275.           topics use one of these extensions, or configure the toolkit to allow additional extensions.</td>
    276. 

  276.       </tr><tr class="strow">
    277. 

  277.         <td class="stentry">This message indicates that the
    278. 

  278.           <code class="keyword markupname xmlatt">@href</code> value specified in <var class="keyword varname">%1</var> does not use proper URI syntax. This may occur when
    279. 

  279.           <code class="keyword markupname xmlatt">@href</code> includes characters that should be escaped (such as the space character, which should be
    280. 

  280.           <code class="ph codeph">%20</code> when in a URI). In strict processing mode this will cause a build failure;
    281. 

  281.           in other processing modes the build will continue using the value in <var class="keyword varname">%2</var>.</td>
    282. 

  282.       </tr><tr class="strow">
    283. 

  283.         <td class="stentry">A conref "mark" action has been
    284. 

  284.           used to mark a target element without a corresponding content reference target. This may occur when the order
    285. 

  285.           of the "mark" element and the pushed element is reversed.</td>
    286. 

  286.       </tr><tr class="strow">
    287. 

  287.         <td class="stentry">
    288. 

  288.           <p class="p">A circular reference was found in key definitions: a series of key references where the last key references
    289. 

  289.             the first.</p>
    290. 

  290.           <p class="p">This may occur if a <code class="keyword markupname xmlelement">&lt;topicref&gt;</code> element contains both a key name in the
    291. 

  291.               <code class="keyword markupname xmlatt">@keys</code> attribute and a reference to the same key in the <code class="keyword markupname xmlatt">@keyref</code> attribute,
    292. 

  292.             or if a <code class="keyword markupname xmlatt">@keyref</code> attribute points to a key that refers back to the referencing element.</p>
    293. 

  293.           <p class="p">To resolve this issue, change the target of the <code class="keyword markupname xmlatt">@keyref</code> so the key is defined by pointing
    294. 

  294.             to a resource other than itself.</p>
    295. 

  295.         </td>
    296. 

  296.       </tr><tr class="strow">
    297. 

  297.         <td class="stentry">
    298. 

  298.           <p class="p">When a <code class="keyword markupname xmlatt">@class</code> attribute does not use the expected syntax, this usually indicates that
    299. 

  299.               <code class="keyword markupname xmlatt">@class</code> has been explicitly set on a DITA element. The attribute should be removed from the
    300. 

  300.             document so that the expected default value can be automatically used.</p>
    301. 

  301.           <p class="p">If this is a non-DITA element, it needs to be placed inside a <code class="keyword markupname xmlelement">&lt;foreign&gt;</code> element so
    302. 

  302.             that is not validated against DITA rules.
    303. 

  303.           
    304. 

  304.           </p>
    305. 

  305.         </td>
    306. 

  306.       </tr><tr class="strow">
    307. 

  307.         <td class="stentry">
    308. 

  308.           <p class="p">Ensure that the DITAVAL file exists. If more than one DITAVAL file is specified, ensure that the paths are
    309. 

  309.             delimited using the file path separator character appropriate for your operating system (semicolon
    310. 

  310.               ‘<code class="ph codeph">;</code>’ on Windows, or colon ‘<code class="ph codeph">:</code>’ on macOS or Linux).</p>
    311. 

  311.         </td>
    312. 

  312.       </tr><tr class="strow">
    313. 

  313.         <td class="stentry">This build uses generated text,
    314. 

  314.           such as the phrase "Related information" (which is generated above many link groups). The toolkit was unable
    315. 

  315.           to locate the string <var class="keyword varname">%1</var> for your specified language, so the string will appear in the
    316. 

  316.           default language. This generally indicates that the toolkit’s strings need to be updated to support your
    317. 

  317.           language, or that your language setting is incorrect.</td>
    318. 

  318.       </tr><tr class="strow">
    319. 

  319.         <td class="stentry">The Eclipse help system requires
    320. 

  320.           a title in the project files generated from your map. Please add a title to your input map to get valid
    321. 

  321.           Eclipse help output.</td>
    322. 

  322.       </tr><tr class="strow">
    323. 

  323.         <td class="stentry">Eclipse uses anchor references
    324. 

  324.           to connect with other TOC files. For this to work in content generated from a DITA map, the anchorref element
    325. 

  325.           must reference either an existing Eclipse TOC XML file, or another DITA map (which will presumably also be
    326. 

  326.           converted to an Eclipse TOC).
    327. 

  327.           
    328. 

  328.         </td>
    329. 

  329.       </tr><tr class="strow">
    330. 

  330.         <td class="stentry">Eclipse builds use DITA’s
    331. 

  331.             <code class="keyword markupname xmlelement">&lt;navref&gt;</code> element to pull in other Eclipse TOC files. The build found a
    332. 

  332.             <code class="keyword markupname xmlelement">&lt;navref&gt;</code> element that does not reference any other file; the element will be
    333. 

  333.           ignored.</td>
    334. 

  334.       </tr><tr class="strow">
    335. 

  335.         <td class="stentry">To remove this message, provide
    336. 

  336.           a navigation title for the referenced object in the map or topic, or ensure that you are referencing a valid
    337. 

  337.           local DITA target.</td>
    338. 

  338.       </tr><tr class="strow">
    339. 

  339.         <td class="stentry">Set the format attribute to
    340. 

  340.           identify the format of the file. If the reference is to a DITA document, ensure that the document uses a valid
    341. 

  341.           DITA extension (default supported extensions are "dita" and "xml").</td>
    342. 

  342.       </tr><tr class="strow">
    343. 

  343.         <td class="stentry">The HTML Help compiler will only
    344. 

  344.           include some types of information in the compiled CHM file; the current reference will not be
    345. 

  345.           included.</td>
    346. 

  346.       </tr><tr class="strow">
    347. 

  347.         <td class="stentry">Ensure that the file exists and
    348. 

  348.           can be read. <span class="ph">Note that the name of the file in this message may have be changed
    349. 

  349.             to use a standard dita topic file extension ('.dita' or '.xml'), instead of the original extension used by
    350. 

  350.             the file; it may also include a path to the temporary directory rather than to the original.</span></td>
    351. 

  351.       </tr><tr class="strow">
    352. 

  352.         <td class="stentry">To fix the table of contents,
    353. 

  353.           specify a navigation title in your map or ensure that the referenced file is local and can be accessed. <span class="ph">Note that the name of the file in this message may have be changed
    354. 

  354.             to use a standard dita topic file extension ('.dita' or '.xml'), instead of the original extension used by
    355. 

  355.             the file; it may also include a path to the temporary directory rather than to the original.</span>
    356. 

  356.           
    357. 

  357.           
    358. 

  358.         </td>
    359. 

  359.       </tr><tr class="strow">
    360. 

  360.         <td class="stentry">No title was found in the
    361. 

  361.           specified topic, so the table of contents will use the indicated fallback value for this topic.
    362. 

  362.           
    363. 

  363.           
    364. 

  364.         </td>
    365. 

  365.       </tr><tr class="strow">
    366. 

  366.         <td class="stentry">The conref attribute must be a
    367. 

  367.           URI reference to an existing DITA element. Please see the topic on <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank">URI-based addressing</a> in the DITA specification for details on the
    368. 

  368.           expected syntax. <span class="ph" id="errormessages__changeExtension">Note that the name of the file in this message may have be changed
    369. 

  369.             to use a standard dita topic file extension ('.dita' or '.xml'), instead of the original extension used by
    370. 

  370.             the file; it may also include a path to the temporary directory rather than to the original.</span>
    371. 

  371.           <p class="p">If the target element exists in your source file, check to make sure it is not filtered out of the build
    372. 

  372.             with a DITAVAL file (which will remove the target before conref processing runs).</p></td>
    373. 

  373.       </tr><tr class="strow">
    374. 

  374.         <td class="stentry">When pulling content with a
    375. 

  375.           conref attribute, you may only pull from a single element, but the target ID appears twice in the referenced
    376. 

  376.           topic. <span class="ph">Note that the name of the file in this message may have be changed
    377. 

  377.             to use a standard dita topic file extension ('.dita' or '.xml'), instead of the original extension used by
    378. 

  378.             the file; it may also include a path to the temporary directory rather than to the original.</span></td>
    379. 

  379.       </tr><tr class="strow">
    380. 

  380.         <td class="stentry">This message is deprecated and
    381. 

  381.           should no longer appear in any logs.</td>
    382. 

  382.       </tr><tr class="strow">
    383. 

  383.         <td class="stentry">This may appear if (for example)
    384. 

  384.           you have a <code class="keyword markupname xmlelement">&lt;ph&gt;</code> element that references another phrase, but that phrase itself contains
    385. 

  385.           a reference to the original. This will result in an infinite loop. The toolkit will stop following the conref
    386. 

  386.           trail when this is detected; you will need to correct the reference in your source files. <span class="ph">Note that the name of the file in this message may have be changed
    387. 

  387.             to use a standard dita topic file extension ('.dita' or '.xml'), instead of the original extension used by
    388. 

  388.             the file; it may also include a path to the temporary directory rather than to the original.</span></td>
    389. 

  389.       </tr><tr class="strow">
    390. 

  390.         <td class="stentry">The conref attribute must be a
    391. 

  391.           URI reference to a DITA element. Please see the topic on <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank">URI-based addressing</a> in the DITA specification for details on the
    392. 

  392.           expected syntax.</td>
    393. 

  393.       </tr><tr class="strow">
    394. 

  394.         <td class="stentry">The conref attribute must be a
    395. 

  395.           URI reference to a DITA element. Please see the topic on <a class="xref" href="http://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/uri-based-addressing.html#uri-based-addressing" target="_blank">URI-based addressing</a> in the DITA specification for details on the
    396. 

  396.           expected syntax. <span class="ph">Note that the name of the file in this message may have be changed
    397. 

  397.             to use a standard dita topic file extension ('.dita' or '.xml'), instead of the original extension used by
    398. 

  398.             the file; it may also include a path to the temporary directory rather than to the original.</span></td>
    399. 

  399.       </tr><tr class="strow">
    400. 

  400.         <td class="stentry">This warning is intended to
    401. 

  401.           catch instances where a non-DITA format setting unexpectedly cascades to a DITA topic, which will prevent the
    402. 

  402.           topic from being processed. To remove this message, set the format attribute directly on the indicated
    403. 

  403.           reference. <span class="ph">Note that the name of the file in this message may have be changed
    404. 

  404.             to use a standard dita topic file extension ('.dita' or '.xml'), instead of the original extension used by
    405. 

  405.             the file; it may also include a path to the temporary directory rather than to the original.</span></td>
    406. 

  406.       </tr><tr class="strow">
    407. 

  407.         <td class="stentry">Found a value such as &lt;xref
    408. 

  408.           href=""&gt;link text&lt;/xref&gt;. The empty href attribute is not serving a purpose and has caused problems with
    409. 

  409.           some tools in the past; you should remove the attribute entirely or specify a value.</td>
    410. 

  410.       </tr><tr class="strow">
    411. 

  411.         <td class="stentry">The type attribute in DITA is
    412. 

  412.           intended to describe the type of the target; for example, a reference to a concept topic may use
    413. 

  413.           type="concept". Generally, this attribute is optional, and the DITA-OT build will automatically determine the
    414. 

  414.           value during processing. In this case, the type attribute lists a more general type than what is actually
    415. 

  415.           found. This is not an error but may result in unexpected sorting for links to this topic.</td>
    416. 

  416.       </tr><tr class="strow">
    417. 

  417.         <td class="stentry">The type attribute in DITA is
    418. 

  418.           intended to describe the type of the target; for example, a reference to a concept topic may use
    419. 

  419.           type="concept". Generally, this attribute is optional, and the DITA-OT build will automatically determine the
    420. 

  420.           value during processing. In this case, the specified type value does not match the target, which may cause
    421. 

  421.           your links to sort inappropriately.</td>
    422. 

  422.       </tr><tr class="strow">
    423. 

  423.         <td class="stentry">DITA-OT is only able to
    424. 

  424.           dynamically retrieve titles when the target is a local (not peer or external) DITA resource.
    425. 

  425.         
    426. 

  426.         </td>
    427. 

  427.       </tr><tr class="strow">
    428. 

  428.         <td class="stentry">DITA-OT is only able to
    429. 

  429.           dynamically retrieve titles when the target is a local DITA resource.</td>
    430. 

  430.       </tr><tr class="strow">
    431. 

  431.         <td class="stentry">The build was unable to get a
    432. 

  432.           title from the referenced topic; instead, a navigation title will be created based on the specified
    433. 

  433.             <code class="keyword markupname xmlelement">&lt;linktext&gt;</code> element inside of <code class="keyword markupname xmlelement">&lt;topicmeta&gt;</code>.</td>
    434. 

  434.       </tr><tr class="strow">
    435. 

  435.         <td class="stentry">If the target is a local DITA
    436. 

  436.           topic, ensure the reference is correct and the topic is available. Otherwise, provide a navigation title, and
    437. 

  437.           ensure the scope and format attributes are set appropriately.</td>
    438. 

  438.       </tr><tr class="strow">
    439. 

  439.         <td class="stentry">DITA-OT is only able to
    440. 

  440.           dynamically retrieve titles and link text when the target is a local (not peer or external) DITA
    441. 

  441.           resource.</td>
    442. 

  442.       </tr><tr class="strow">
    443. 

  443.         <td class="stentry">DITA-OT is only able to
    444. 

  444.           dynamically retrieve titles when the target is a local DITA resource.
    445. 

  445.         </td>
    446. 

  446.       </tr><tr class="strow">
    447. 

  447.         <td class="stentry">The referenc to this document
    448. 

  448.           did not specify any link text for generated map-based links; the navigation title will be used as
    449. 

  449.           fallback.</td>
    450. 

  450.       </tr><tr class="strow">
    451. 

  451.         <td class="stentry">The referenced file did not
    452. 

  452.           specify any link text for generated map-based links, and no fallback text could be located. Any links
    453. 

  453.           generated from this reference will have incorrect link text.</td>
    454. 

  454.       </tr><tr class="strow">
    455. 

  455.         <td class="stentry">The link or cross reference has
    456. 

  456.           no target specified and will not generate a link.</td>
    457. 

  457.       </tr><tr class="strow">
    458. 

  458.         <td class="stentry">The type attribute in DITA is
    459. 

  459.           intended to describe the type of the target; for example, a reference to a concept topic may use
    460. 

  460.           type="concept". Generally, this attribute is optional, and the DITA-OT build will automatically determine the
    461. 

  461.           value during processing. In this case, the type attribute lists a more general type than what is actually
    462. 

  462.           found. This is not an error but may result in unexpected sorting for links to this topic.</td>
    463. 

  463.       </tr><tr class="strow">
    464. 

  464.         <td class="stentry">The type attribute in DITA is
    465. 

  465.           intended to describe the type of the target; for example, a reference to a concept topic may use
    466. 

  466.           type="concept". Generally, this attribute is optional, and the DITA-OT build will automatically determine the
    467. 

  467.           value during processing. In this case, the specified type value does not match the target, which may cause
    468. 

  468.           your links to sort inappropriately.</td>
    469. 

  469.       </tr><tr class="strow">
    470. 

  470.         <td class="stentry">The build attempted to access
    471. 

  471.           the specified file in order to retrive a title or short description, but the file could not be found. If the
    472. 

  472.           file exists, it is possible that a DITAVAL file was used to remove the file’s contents from the build. Be
    473. 

  473.           aware that the path information above may not match the link in your topic.</td>
    474. 

  474.       </tr><tr class="strow">
    475. 

  475.         <td class="stentry">When a link or cross reference
    476. 

  476.           does not have content, the build will attempt to pull the target’s title for use as link text. If the target
    477. 

  477.           is unavailable, be sure to set the scope attribute to an appropriate value. If the target does not have a
    478. 

  478.           title (such as when linking to a paragraph), be sure to provide link text inside the cross
    479. 

  479.           reference.</td>
    480. 

  480.       </tr><tr class="strow">
    481. 

  481.         <td class="stentry">An <code class="keyword markupname xmlelement">&lt;xref&gt;</code>
    482. 

  482.           element specifies type="li", which indicates a link to a list item, but the item number could not be
    483. 

  483.           determined to use as link text. Please specify link text inside the reference, or ensure that you are
    484. 

  484.           referencing an available list item.</td>
    485. 

  485.       </tr><tr class="strow">
    486. 

  486.         <td class="stentry">The cross reference goes to a
    487. 

  487.           list item in an unordered list. The process could not automatically generate link text because the list item
    488. 

  488.           is not numbered. Please provide link text within the cross reference.</td>
    489. 

  489.       </tr><tr class="strow">
    490. 

  490.         <td class="stentry">An <code class="keyword markupname xmlelement">&lt;xref&gt;</code>
    491. 

  491.           element specifies type="fn", which indicates a link to a footnote, but the footnote number could not be
    492. 

  492.           determined to use as link text. Please specify link text inside the reference, or ensure that you are
    493. 

  493.           referencing an available footnote.</td>
    494. 

  494.       </tr><tr class="strow">
    495. 

  495.         <td class="stentry">An <code class="keyword markupname xmlelement">&lt;xref&gt;</code>
    496. 

  496.           element specifies type="dlentry", which indicates a link to a definition list entry, but the term could not be
    497. 

  497.           located to use as link text. Please specify link text inside the reference, or ensure that you are referencing
    498. 

  498.           an available definition list entry</td>
    499. 

  499.       </tr><tr class="strow">
    500. 

  500.         <td class="stentry">No title was found for the
    501. 

  501.           current document, so the HTML output file will set the <code class="keyword markupname xmlelement">&lt;title&gt;</code> to "***". This value
    502. 

  502.           generally appears in the title bar at the top of a browser.</td>
    503. 

  503.       </tr><tr class="strow">
    504. 

  504.         <td class="stentry">The
    505. 

  505.             <code class="keyword markupname xmlelement">&lt;object&gt;</code> element in HTML does not support using longdescref for accessibility. To
    506. 

  506.           make the object accessible, you may need to add text before or after the element. You may also be able to
    507. 

  507.           handle it with a <code class="keyword markupname xmlelement">&lt;param&gt;</code> element inside the object.</td>
    508. 

  508.       </tr><tr class="strow">
    509. 

  509.         <td class="stentry">This message is generated when
    510. 

  510.           creating draft output in order to help you locate all topics that need to be cleaned up; the cleanup items
    511. 

  511.           will appear in your output with styling that makes it stand out. The content will be hidden when the draft
    512. 

  512.           parameter is not active.</td>
    513. 

  513.       </tr><tr class="strow">
    514. 

  514.         <td class="stentry">This message is generated when
    515. 

  515.           creating draft output in order to help you locate all topics that have draft comments. Each comment will
    516. 

  516.           appear in your HTML output; the comments will be hidden when the draft parameter is not active.</td>
    517. 

  517.       </tr><tr class="strow">
    518. 

  518.         <td class="stentry">Because of the way XML and DITA
    519. 

  519.           are defined, it is generally not possible to prohibit adding a second title to a section during editing (or to
    520. 

  520.           force that title to come first). However, the DITA specification states that only one title should be used in
    521. 

  521.           a section. When multiple titles are found, only the first one will appear in the output.</td>
    522. 

  522.       </tr><tr class="strow">
    523. 

  523.         <td class="stentry">If it is important to flag this
    524. 

  524.           piece of information, try placing a flag on the block element that contains your phrase. If you just want to
    525. 

  525.           have an image next to the phrase, you may place an image directly into the document.</td>
    526. 

  526.       </tr><tr class="strow">
    527. 

  527.         <td class="stentry">DITA-OT is able to remove
    528. 

  528.           duplicate links in most cases. However, if two links to the same resource use different attributes or link
    529. 

  529.           text, it is possible for them to appear together. For example, if the same link shows up with role="next" and
    530. 

  530.           again with no specified role, it may show up as both the "Next topic" link and as a related link. Note that
    531. 

  531.           links generated from a <code class="keyword markupname xmlelement">&lt;reltable&gt;</code> in a DITA map will have the role attribute set to
    532. 

  532.           "friend".
    533. 

  533.           
    534. 

  534.         </td>
    535. 

  535.       </tr><tr class="strow">
    536. 

  536.         <td class="stentry">The
    537. 

  537.             <code class="keyword markupname xmlelement">&lt;area&gt;</code> element in an image map must provide a link target for the specified area.
    538. 

  538.           Please add an <code class="keyword markupname xmlelement">&lt;xref&gt;</code> element as a child of <code class="keyword markupname xmlelement">&lt;area&gt;</code> and ensure
    539. 

  539.           that it specifies a link target.
    540. 

  540.         </td>
    541. 

  541.       </tr><tr class="strow">
    542. 

  542.         <td class="stentry">Cross reference text inside the
    543. 

  543.             <code class="keyword markupname xmlelement">&lt;area&gt;</code> element is used to provide accessibility for screen readers that can identify
    544. 

  544.           different areas of an image map. If text cannot be retrieved automatically by referencing a DITA element, it
    545. 

  545.           should be specified directly in the cross reference.</td>
    546. 

  546.       </tr><tr class="strow">
    547. 

  547.         <td class="stentry">The specified value was passed
    548. 

  548.           as-is through to the <code class="keyword markupname xmlelement">&lt;area&gt;</code> element in the HTML.</td>
    549. 

  549.       </tr><tr class="strow">
    550. 

  550.         <td class="stentry">The area element is intended to
    551. 

  551.           define a region in an image map; coordinates must be specified in order to define that region.</td>
    552. 

  552.       </tr><tr class="strow">
    553. 

  553.         <td class="stentry">The build will not look for peer
    554. 

  554.           or external topics before compiling your CHM file, so they may not be included. If you are referencing an
    555. 

  555.           actual HTML file that will not be available, it cannot be included in the project, and you should set the toc
    556. 

  556.           attribute to "no" on your topicref element. Otherwise, check to be sure your HTML file was included in the
    557. 

  557.           CHM; if it was not, you will need to place it in the correct location with your other output files and
    558. 

  558.           recompile.
    559. 

  559.           
    560. 

  560.         </td>
    561. 

  561.       </tr><tr class="strow">
    562. 

  562.         <td class="stentry">The PDF, ODT, and RTF output
    563. 

  563.           processes cannot automatically convert non-DITA content into DITA in order to merge it with the rest of your
    564. 

  564.           content. The referenced items are ignored.</td>
    565. 

  565.       </tr><tr class="strow">
    566. 

  566.         <td class="stentry">Eclipse requires that an ID be
    567. 

  567.           specified when creating an Eclipse Help project; the toolkit expects to locate that ID on the root element of
    568. 

  568.           your input map.</td>
    569. 

  569.       </tr><tr class="strow">
    570. 

  570.         <td class="stentry">The toolkit is attempting to add
    571. 

  571.           generated text, such as the string "Related information" that appears above links. The requested string could
    572. 

  572.           not be found in any language. Your output may contain a meaningful string, or it may contain a code that was
    573. 

  573.           intended to map to a string. This likely indicates an error in a plug-in or XSL override; either the string
    574. 

  574.           was requested incorrectly, or you will need to provide a mapping for the string in all of the languages you
    575. 

  575.           require.</td>
    576. 

  576.       </tr><tr class="strow">
    577. 

  577.         <td class="stentry">This will occur if a map
    578. 

  578.           references another map, and then that second map (or another further nested map) references the original map.
    579. 

  579.           The result is an infinite nesting of maps; please correct the chain of map references to remove circular
    580. 

  580.           reference.</td>
    581. 

  581.       </tr><tr class="strow">
    582. 

  582.         <td class="stentry">This will occur when a DITAVAL
    583. 

  583.           file contains multiple styling rules that apply to the same element.</td>
    584. 

  584.       </tr><tr class="strow">
    585. 

  585.         <td class="stentry">The "flagit" named template was
    586. 

  586.           deprecated in DITA-OT version 1.4, when the OASIS standard formalized the DITAVAL syntax. The template is
    587. 

  587.           removed in DITA-OT 1.6. Stylesheets that used this template need to be updated.</td>
    588. 

  588.       </tr><tr class="strow">
    589. 

  589.         <td class="stentry">The build attempted to access
    590. 

  590.           the specified file in order to retrive a title or short description, but the file could not be found. If the
    591. 

  591.           file exists, it is possible that a DITAVAL file was used to remove the file’s contents from the build. Another
    592. 

  592.           possibility is that the file is located outside of the scope of the main input directory, and was not
    593. 

  593.           available because the <a class="xref" href="../parameters/parameters-base.html" title="Certain parameters apply to all transformations that DITA Open Toolkit supports.">onlytopic.in.map</a> parameter was specified. Be aware
    594. 

  594.           that the path information above may not match the link in your topic.</td>
    595. 

  595.       </tr><tr class="strow">
    596. 

  596.         <td class="stentry">The link appears to use valid
    597. 

  597.           syntax to reference a DITA element, but that element cannot be found. Please verify that the element exists,
    598. 

  598.           and is not removed from the build by DITAVAL based filtering.</td>
    599. 

  599.       </tr><tr class="strow">
    600. 

  600.         <td class="stentry">Processing for terms, acronyms,
    601. 

  601.           or abbreviated forms will associate the key from the element’s keyref attribute with a glossentry (glossary
    602. 

  602.           entry) topic. This message will appear if the key was defined, but was not associated with a glossentry topic.
    603. 

  603.           The process will try to use the best available fallback (usually the title of the referenced topic).</td>
    604. 

  604.       </tr><tr class="strow">
    605. 

  605.         <td class="stentry">Processing for abbreviated form
    606. 

  606.           elements will associate the key from the element’s keyref attribute with a glossentry (glossary entry) topic.
    607. 

  607.           This message will appear if the key was defined, but was not associated with a glossentry topic. This element
    608. 

  608.           is only supported with keys that are associated with glossary topics; the element will not generate any
    609. 

  609.           output. Please correct the reference, or use a different element to reference your topic.</td>
    610. 

  610.       </tr><tr class="strow">
    611. 

  611.         <td class="stentry">According to the DITA
    612. 

  612.           Specification, references from maps should either go to DITA Maps, DITA Topics, or any non-DITA resource.
    613. 

  613.           References below the topic level should only be made from cross references (using
    614. 

  614.             <code class="keyword markupname xmlelement">&lt;xref&gt;</code> or similar) inside of a topic. For details, see the href attribute description
    615. 

  615.           in the OASIS standard’s definition of the <a class="xref" href="http://docs.oasis-open.org/dita/v1.2/os/spec/langref/topicref.html" target="_blank">topicref element</a>.</td>
    616. 

  616.       </tr><tr class="strow">
    617. 

  617.         <td class="stentry">This will appear when generating
    618. 

  618.           PDF or ODT output that includes a link to a local topic, but the referenced topic is not part of the map
    619. 

  619.           itself. This will result in a broken link. You should include the topic in your map or remove the link from
    620. 

  620.           the build.</td>
    621. 

  621.       </tr><tr class="strow">
    622. 

  622.         <td class="stentry">The copy-to attribute is used to
    623. 

  623.           copy a topic over a document that already exists. Please make sure that any copy-to attributes use a unique
    624. 

  624.           name so that the copy will not overwrite existing content.</td>
    625. 

  625.       </tr><tr class="strow">
    626. 

  626.         <td class="stentry">Two different topics are copied
    627. 

  627.           to the same location using copy-to; as a result, one of these files would be over-written. Only the first
    628. 

  628.           instance of this copy-to value will be recognized. Please correct the use of copy-to attributes.</td>
    629. 

  629.       </tr><tr class="strow">
    630. 

  630.         <td class="stentry">This message indicates that your
    631. 

  631.           custom XSLT or plug-ins rely on templates that will be removed in an upcoming release. Typically this occurs
    632. 

  632.           when a named template has been converted to a mode template; any code that uses the deprecated template should
    633. 

  633.           be updated.</td>
    634. 

  634.       </tr><tr class="strow">
    635. 

  635.         <td class="stentry">This PDF build uses generated
    636. 

  636.           text, such as the phrase "Related information" (which is generated above many link groups). The toolkit was
    637. 

  637.           unable to locate the string <var class="keyword varname">%1</var> for your specified language, so the string will appear in
    638. 

  638.           the default language. This generally indicates that the toolkit’s strings need to be updated to support your
    639. 

  639.           language, or that your language setting is incorrect.</td>
    640. 

  640.       </tr></tbody></table>
    641. 

  641.     <section class="section"><h2 class="title sectiontitle">Additional explanation for messages in the <span class="ph filepath">org.dita.pdf2</span> plugin</h2>
    642. 

  642.       
    643. 

  643.       <table class="simpletable"><colgroup><col style="width:100%"></colgroup><tbody><tr class="strow">
    644. 

  644.           <td class="stentry">The PDF index process relies
    645. 

  645.             on pre-defined letter headings when sorting terms. The specified term does not begin with a character that
    646. 

  646.             can be mapped to an existing heading. Typically this term would be placed in a "Special characters" group,
    647. 

  647.             but the current language did not specify such a group when setting up the index sort process.</td>
    648. 

  648.         </tr><tr class="strow">
    649. 

  649.           <td class="stentry">The PDF index process relies
    650. 

  650.             on pre-defined letter headings when sorting terms. The specified term does not begin with a character that
    651. 

  651.             can be mapped to an existing heading, so it has been placed under a heading for terms that begin with
    652. 

  652.             special characters such as punctuation. If this term should be sorted under a new or existing letter
    653. 

  653.             heading, please open an issue with DITA-OT to correct the sort.</td>
    654. 

  654.         </tr><tr class="strow">
    655. 

  655.           <td class="stentry">Found an
    656. 

  656.               <code class="keyword markupname xmlelement">&lt;index-see&gt;</code> element as a child of a term that also exists as a standalone index
    657. 

  657.             term, or as a term that also uses <code class="keyword markupname xmlelement">&lt;index-see-also&gt;</code>. When using
    658. 

  658.               <code class="keyword markupname xmlelement">&lt;index-see&gt;</code> with an index term, that term should not be used to create page
    659. 

  659.             references and should not reference additional terms. Treating the <code class="keyword markupname xmlelement">&lt;index-see&gt;</code> as
    660. 

  660.               <code class="keyword markupname xmlelement">&lt;index-see-also&gt;</code>.</td>
    661. 

  661.         </tr><tr class="strow">
    662. 

  662.           <td class="stentry"></td>
    663. 

  663.         </tr></tbody></table>
    664. 

  664.     </section>
    665. 

  665.   </div>
    666. 

  666. </article></main></body></html>
    667.