1# 2# Automatically Generated by /usr/local/validator/misc/spmpp.pl 3# 4 5# 6# Special messages used globally. 7<msg nomsg> 8 verbose = <<.EOF. 9 <p class="helpwanted"> 10 <a 11 href="<!--#echo var="relroot" -->feedback.html?uri=<!--URI-->;errmsg_id=<!--MID-->#errormsg" 12 title="Suggest improvements on this error message through our feedback channels" 13 >✉</a> 14 </p> 15.EOF. 16</msg> 17 18# 19# OpenSP output. 20<msg 0> 21 original = "length of name must not exceed NAMELEN (%1)" 22</msg> 23<msg 1> 24 original = "length of parameter entity name must not exceed NAMELEN less the length of the PERO delimiter (%1)" 25</msg> 26<msg 2> 27 original = "length of number must not exceed NAMELEN (%1)" 28</msg> 29<msg 3> 30 original = "length of attribute value must not exceed LITLEN less NORMSEP (%1)" 31</msg> 32<msg 4> 33 original = "a name group is not allowed in a parameter entity reference in the prolog" 34</msg> 35<msg 5> 36 original = "an entity end in a token separator must terminate an entity referenced in the same group" 37</msg> 38<msg 6> 39 original = "character %1 invalid: only %2 and token separators allowed" 40</msg> 41<msg 7> 42 original = "a parameter separator is required after a number that is followed by a name start character" 43</msg> 44<msg 8> 45 original = "character %1 invalid: only %2 and parameter separators allowed" 46</msg> 47<msg 9> 48 original = "an entity end in a parameter separator must terminate an entity referenced in the same declaration" 49</msg> 50<msg 10> 51 original = "an entity end is not allowed in a token separator that does not follow a token" 52</msg> 53<msg 11> 54 original = "%1 is not a valid token here" 55</msg> 56<msg 12> 57 original = "a parameter entity reference can only occur in a group where a token could occur" 58</msg> 59<msg 13> 60 original = "token %1 has already occurred in this group" 61</msg> 62<msg 14> 63 original = "the number of tokens in a group must not exceed GRPCNT (%1)" 64</msg> 65<msg 15> 66 original = "an entity end in a literal must terminate an entity referenced in the same literal" 67</msg> 68<msg 16> 69 original = "character %1 invalid: only minimum data characters allowed" 70</msg> 71<msg 18> 72 original = "a parameter literal in a data tag pattern must not contain a numeric character reference to a non-SGML character" 73</msg> 74<msg 19> 75 original = "a parameter literal in a data tag pattern must not contain a numeric character reference to a function character" 76</msg> 77<msg 20> 78 original = "a name group is not allowed in a general entity reference in a start tag" 79</msg> 80<msg 21> 81 original = "a name group is not allowed in a general entity reference in the prolog" 82</msg> 83<msg 22> 84 original = "%1 is not a function name" 85</msg> 86<msg 23> 87 original = "%1 is not a character number in the document character set" 88</msg> 89<msg 24> 90 original = "parameter entity %1 not defined" 91</msg> 92<msg 25> 93 original = "general entity %1 not defined and no default entity" 94 verbose <<.EOF. 95 <div class="ve mid-25"> 96 <p> 97 This is usually a cascading error caused by a an undefined entity 98 reference or use of an unencoded ampersand (&) in an URL or body 99 text. See the previous message for further details. 100 </p> 101 </div> 102.EOF. 103</msg> 104<msg 26> 105 original = "RNI delimiter must be followed by name start character" 106</msg> 107<msg 28> 108 original = "unterminated comment: found end of entity inside comment" 109 verbose <<.EOF. 110 <div class="ve mid-28"> 111 <p> 112 Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. 113 This error may appear if you forget the last "--" to close one comment, therefore including the rest 114 of the content in your comment. 115 </p> 116 </div> 117.EOF. 118 119</msg> 120<msg 29> 121 original = "comment started here" 122</msg> 123<msg 30> 124 original = "only one type of connector should be used in a single group" 125</msg> 126<msg 31> 127 original = "%1 is not a reserved name" 128</msg> 129<msg 32> 130 original = "%1 is not allowed as a reserved name here" 131</msg> 132<msg 33> 133 original = "length of interpreted minimum literal must not exceed reference LITLEN (%1)" 134</msg> 135<msg 34> 136 original = "length of tokenized attribute value must not exceed LITLEN less NORMSEP (%1)" 137</msg> 138<msg 35> 139 original = "length of system identifier must not exceed LITLEN (%1)" 140</msg> 141<msg 36> 142 original = "length of interpreted parameter literal must not exceed LITLEN (%1)" 143</msg> 144<msg 37> 145 original = "length of interpreted parameter literal in data tag pattern must not exceed DTEMPLEN (%1)" 146</msg> 147<msg 38> 148 original = "literal is missing closing delimiter" 149 verbose <<.EOF. 150 <div class="ve mid-38"> 151 <p> 152 Did you forget to close a (double) quote mark? 153 </p> 154 </div> 155.EOF. 156</msg> 157<msg 39> 158 original = "%1 invalid: only %2 and parameter separators are allowed" 159 <div class="ve mid-39"> 160 <p> 161 This error is typical of a typo or error in the DOCTYPE declaration at the top 162 of your document's markup. 163 </p> 164 <p> 165 In most cases, it is safer not to type or edit the DOCTYPE declaration at all, 166 and preferable to let a tool include it, or copy and paste it from a 167 <a href="http://www.w3.org/QA/2002/04/valid-dtd-list.html">trusted list of DTDs</a>. 168 </p> 169 </div> 170.EOF. 171 172</msg> 173<msg 40> 174 original = "%1 invalid: only %2 and token separators are allowed" 175</msg> 176<msg 41> 177 original = "%1 invalid: only %2 and token separators are allowed" 178</msg> 179<msg 42> 180 original = "unknown declaration type %1" 181 verbose <<.EOF. 182 <div class="ve mid-42"> 183 <p> 184 This error may appear if you are using a bad syntax for your comments, such as "<!invalid comment>" 185 The proper syntax for comments is <!-- your comment here -->. 186 </p> 187 </div> 188.EOF. 189</msg> 190<msg 43> 191 original = "%1 declaration not allowed in DTD subset" 192</msg> 193<msg 44> 194 original = "character %1 not allowed in declaration subset" 195</msg> 196<msg 45> 197 original = "end of document in DTD subset" 198</msg> 199<msg 46> 200 original = "character %1 not allowed in prolog" 201</msg> 202<msg 47> 203 original = "end of document in prolog" 204 verbose <<.EOF. 205<div class="ve mid-47"> 206 <p> 207 This error may appear when the validator receives an empty document. Please make sure that the document you are uploading is not empty, and <a href="<!--#echo var="relroot" -->feedback.html">report</a> any discrepancy. 208 </p> 209</div> 210.EOF. 211</msg> 212<msg 48> 213 original = "%1 declaration not allowed in prolog" 214</msg> 215<msg 49> 216 original = "%1 used both a rank stem and generic identifier" 217</msg> 218<msg 50> 219 original = "omitted tag minimization parameter can be omitted only if OMITTAG NO is specified" 220</msg> 221<msg 51> 222 original = "element type %1 already defined" 223</msg> 224<msg 52> 225 original = "entity reference with no applicable DTD" 226</msg> 227<msg 53> 228 original = "invalid comment declaration: found %1 outside comment but inside comment declaration" 229</msg> 230<msg 54> 231 original = "comment declaration started here" 232</msg> 233<msg 55> 234 original = "%1 declaration not allowed in instance" 235</msg> 236<msg 56> 237 original = "non-SGML character not allowed in content" 238</msg> 239<msg 57> 240 original = "no current rank for rank stem %1" 241</msg> 242<msg 58> 243 original = "duplicate attribute definition list for notation %1" 244</msg> 245<msg 59> 246 original = "duplicate attribute definition list for element %1" 247</msg> 248<msg 60> 249 original = "entity end not allowed in end tag" 250</msg> 251<msg 61> 252 original = "character %1 not allowed in end tag" 253</msg> 254<msg 62> 255 original = "%1 invalid: only S separators and TAGC allowed here" 256</msg> 257<msg 63> 258 original = "character data is not allowed here" 259 verbose <<.EOF. 260 <div class="ve mid-63"> 261 <p> 262 You have used character data somewhere it is not permitted to appear. 263 Mistakes that can cause this error include: 264 </p> 265 <ul> 266 <li>putting text directly in the body of the document without wrapping 267 it in a container element (such as a <p>aragraph</p>), or</li> 268 <li>forgetting to quote an attribute value 269 (where characters such as "%" and "/" are common, but cannot appear 270 without surrounding quotes), or</li> 271 <li>using XHTML-style self-closing tags (such as <meta ... />) 272 in HTML 4.01 or earlier. To fix, remove the extra slash ('/') 273 character. For more information about the reasons for this, see 274 <a href="http://www.cs.tut.fi/~jkorpela/html/empty.html">Empty 275 elements in SGML, HTML, XML, and XHTML</a>. 276 </li> 277 </ul> 278 </div> 279.EOF. 280</msg> 281<msg 64> 282 original = "document type does not allow element %1 here" 283 verbose <<.EOF. 284 <div class="ve mid-64"> 285 <p> 286 The element named above was found in a context where it is not allowed. 287 This could mean that you have incorrectly nested elements -- such as a 288 "style" element in the "body" section instead of inside "head" -- or 289 two elements that overlap (which is not allowed). 290 </p> 291 <p> 292 One common cause for this error is the use of XHTML syntax in HTML 293 documents. Due to HTML's rules of implicitly closed elements, this error 294 can create cascading effects. For instance, using XHTML's "self-closing" 295 tags for "meta" and "link" in the "head" section of a HTML document may 296 cause the parser to infer the end of the "head" section and the 297 beginning of the "body" section (where "link" and "meta" are not 298 allowed; hence the reported error). 299 </p> 300 </div> 301.EOF. 302</msg> 303<msg 65> 304 original = "document type does not allow element %1 here; missing one of %2 start-tag" 305 verbose <<.EOF. 306 <div class="ve mid-65"> 307 <p> 308 The mentioned element is not allowed to appear in the context in which 309 you've placed it; the other mentioned elements are the only ones that 310 are both allowed there <em>and</em> can contain the element mentioned. 311 This might mean that you need a containing element, or possibly that 312 you've forgotten to close a previous element. 313 </p> 314 <p> 315 One possible cause for this message is that you have attempted to put a 316 block-level element (such as "<p>" or "<table>") inside an 317 inline element (such as "<a>", "<span>", or "<font>"). 318 </p> 319 </div> 320.EOF. 321</msg> 322<msg 66> 323 original = "document type does not allow element %1 here; assuming missing %2 start-tag" 324</msg> 325<msg 67> 326 original = "no start tag specified for implied empty element %1" 327</msg> 328<msg 68> 329 original = "end tag for %1 omitted, but its declaration does not permit this" 330 verbose <<.EOF. 331 <div class="ve mid-68"> 332 <ul> 333 <li>You forgot to close a tag, or</li> 334 <li>you used something inside this tag that was not allowed, and the validator 335 is complaining that the tag should be closed before such content can be allowed.</li> 336 </ul> 337 <p> 338 The next message, "<code class="inline">start tag was here</code>" 339 points to the particular instance of the tag in question); the 340 positional indicator points to where the validator expected you to close the 341 tag. 342 </p> 343 </div> 344.EOF. 345</msg> 346<msg 69> 347 original = "start tag was here" 348 verbose <<.EOF. 349 <div class="ve mid-69"> 350 <p> 351 This is not an error, but rather a pointer to the start tag of the element 352 the previous error referred to. 353 </p> 354 </div> 355.EOF. 356</msg> 357<msg 70> 358 original = "end tag for %1 omitted, but OMITTAG NO was specified" 359 verbose <<.EOF. 360 <div class="ve mid-70"> 361 <p> 362 You may have neglected to close an element, or perhaps you meant to 363 "self-close" an element, that is, ending it with "/>" instead of ">". 364 </p> 365</div> 366.EOF. 367</msg> 368<msg 71> 369 original = "start tag was here" 370 verbose <<.EOF. 371 <div class="ve mid-71"> 372 <p> 373 This is not an error, but rather a pointer to the start tag of the element 374 the previous error referred to. 375 </p> 376 </div> 377.EOF. 378 379</msg> 380<msg 72> 381 original = "start tag omitted for element %1 with declared content" 382</msg> 383<msg 73> 384 original = "end tag for %1 which is not finished" 385 verbose <<.EOF. 386 <div class="ve mid-73"> 387 <p> 388 Most likely, you nested tags and closed them in the wrong order. For 389 example <p><em>...</p> is not acceptable, as <em> 390 must be closed before <p>. Acceptable nesting is: 391 <p><em>...</em></p> 392 </p> 393 <p> 394 Another possibility is that you used an element which requires 395 a child element that you did not include. Hence the parent element 396 is "not finished", not complete. For instance, in HTML the <head> 397 element must contain a <title> child element, lists require 398 appropriate list items (<ul> and <ol> require <li>; 399 <dl> requires <dt> and <dd>), and so on. 400 </p> 401 </div> 402.EOF. 403</msg> 404<msg 74> 405 original = "start tag for %1 omitted, but its declaration does not permit this" 406</msg> 407<msg 75> 408 original = "number of open elements exceeds TAGLVL (%1)" 409</msg> 410<msg 76> 411 original = "element %1 undefined" 412 verbose <<.EOF. 413 <div class="ve mid-76"> 414 <p> 415 You have used the element named above in your document, but the 416 document type you are using does not define an element of that name. 417 This error is often caused by: 418 </p> 419 <ul> 420 <li>incorrect use of the "Strict" document type with a document that 421 uses frames (e.g. you must use the "Frameset" document type to get 422 the "<frameset>" element),</li> 423 <li>by using vendor proprietary extensions such as "<spacer>" 424 or "<marquee>" (this is usually fixed by using CSS to achieve 425 the desired effect instead).</li> 426 <li>by using upper-case tags in XHTML (in XHTML attributes and elements 427 must be all lower-case).</li> 428 </ul> 429 </div> 430.EOF. 431</msg> 432<msg 77> 433 original = "empty end tag but no open elements" 434</msg> 435<msg 78> 436 original = "%1 not finished but containing element ended" 437</msg> 438<msg 79> 439 original = "end tag for element %1 which is not open" 440 verbose <<.EOF. 441 <div class="ve mid-79"> 442 <p> 443 The Validator found an end tag for the above element, but that element is 444 not currently open. This is often caused by a leftover end tag from an 445 element that was removed during editing, or by an implicitly closed 446 element (if you have an error related to an element being used where it 447 is not allowed, this is almost certainly the case). In the latter case 448 this error will disappear as soon as you fix the original problem. 449 </p> 450 <p> 451 If this error occurred in a script section of your document, you should probably 452 read this <a href="<!--#echo var="relroot" -->docs/help.html#faq-javascript">FAQ entry</a>. 453 </p> 454 </div> 455.EOF. 456</msg> 457<msg 80> 458 original = "internal parameter entity %1 cannot be CDATA or SDATA" 459</msg> 460<msg 81> 461 original = "character %1 not allowed in attribute specification list" 462</msg> 463<msg 82> 464 original = "an attribute value must be a literal unless it contains only name characters" 465 verbose <<.EOF. 466 <div class="ve mid-82"> 467 <p> 468 You have used a character that is not considered a "name character" in an 469 attribute value. Which characters are considered "name characters" varies 470 between the different document types, but a good rule of thumb is that 471 unless the value contains <em>only</em> lower or upper case letters in the 472 range a-z you must put quotation marks around the value. In fact, unless 473 you have <em>extreme</em> file size requirements it is a very very good 474 idea to <em>always</em> put quote marks around your attribute values. It 475 is never wrong to do so, and very often it is absolutely necessary. 476 </p> 477 </div> 478.EOF. 479</msg> 480<msg 83> 481 original = "entity end not allowed in attribute specification list except in attribute value literal" 482</msg> 483<msg 84> 484 original = "external parameter entity %1 cannot be CDATA, SDATA, NDATA or SUBDOC" 485</msg> 486<msg 85> 487 original = "duplicate declaration of entity %1" 488</msg> 489<msg 86> 490 original = "duplicate declaration of parameter entity %1" 491</msg> 492<msg 87> 493 original = "a reference to a PI entity is allowed only in a context where a processing instruction could occur" 494</msg> 495<msg 88> 496 original = "a reference to a CDATA or SDATA entity is allowed only in a context where a data character could occur" 497</msg> 498<msg 89> 499 original = "a reference to a subdocument entity or external data entity is allowed only in a context where a data character could occur" 500</msg> 501<msg 90> 502 original = "a reference to a subdocument entity or external data entity is not allowed in replaceable character data" 503</msg> 504<msg 91> 505 original = "the number of open entities cannot exceed ENTLVL (%1)" 506</msg> 507<msg 92> 508 original = "a reference to a PI entity is not allowed in replaceable character data" 509</msg> 510<msg 93> 511 original = "entity %1 is already open" 512</msg> 513<msg 94> 514 original = "short reference map %1 not defined" 515</msg> 516<msg 95> 517 original = "short reference map in DTD must specify associated element type" 518</msg> 519<msg 96> 520 original = "short reference map in document instance cannot specify associated element type" 521</msg> 522<msg 97> 523 original = "short reference map %1 for element %2 not defined in DTD" 524</msg> 525<msg 98> 526 original = "%1 is not a short reference delimiter" 527</msg> 528<msg 99> 529 original = "short reference delimiter %1 already mapped in this declaration" 530</msg> 531<msg 100> 532 original = "no document element" 533</msg> 534<msg 102> 535 original = "entity end not allowed in processing instruction" 536</msg> 537<msg 103> 538 original = "length of processing instruction must not exceed PILEN (%1)" 539</msg> 540<msg 104> 541 original = "missing PIC delimiter" 542</msg> 543<msg 105> 544 original = "an attribute specification must start with a name or name token" 545 verbose <<.EOF. 546 <div class="ve mid-105"> 547 <p> 548 An attribute name (and some attribute values) must start with one of 549 a restricted set of characters. This error usually indicates that 550 you have failed to add a closing quotation mark on a previous 551 attribute value (so the attribute value looks like the start of a 552 new attribute) or have used an attribute that is not defined 553 (usually a typo in a common attribute name). 554 </p> 555 </div> 556.EOF. 557</msg> 558<msg 106> 559 original = "%1 is not a member of a group specified for any attribute" 560</msg> 561<msg 107> 562 original = "the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified" 563 verbose <<.EOF. 564 <div class="ve mid-107"> 565 <p>"VI delimiter" is a technical term for the equal sign. This error message 566 means that the name of an attribute and the equal sign cannot be omitted 567 when specifying an attribute. A common cause for this error message is 568 the use of "Attribute Minimization" in document types where it is not allowed, 569 in <a href="http://www.w3.org/TR/xhtml1/#h-4.5">XHTML</a> for instance.</p> 570 <p>How to fix: For attributes such as compact, checked or selected, do not write 571 e.g <option selected ... but rather <option selected="selected" ... 572 </p> 573 </div> 574.EOF. 575</msg> 576<msg 108> 577 original = "there is no attribute %1" 578 verbose <<.EOF. 579 <div class="ve mid-108"> 580 <p> 581 You have used the attribute named above in your document, but the 582 document type you are using does not support that attribute for this 583 element. This error is often caused by incorrect use of the "Strict" 584 document type with a document that uses frames (e.g. you must use 585 the "Transitional" document type to get the "target" attribute), or 586 by using vendor proprietary extensions such as "marginheight" (this 587 is usually fixed by using CSS to achieve the desired effect instead). 588 </p> 589 <p> 590 This error may also result if the element itself is not supported in 591 the document type you are using, as an undefined element will have no 592 supported attributes; in this case, see the element-undefined error 593 message for further information. 594 </p> 595 <p> 596 How to fix: check the spelling and case of the element and attribute, 597 (Remember XHTML is all lower-case) and/or 598 check that they are both allowed in the chosen document type, and/or 599 use CSS instead of this attribute. If you received this error when using the 600 <embed> element to incorporate flash media in a Web page, see the 601 <a href="<!--#echo var="relroot" -->docs/help.html#faq-flash">FAQ item on valid flash</a>. 602 </p> 603 </div> 604.EOF. 605</msg> 606<msg 109> 607 original = "an attribute value specification must start with a literal or a name character" 608</msg> 609<msg 110> 610 original = "length of name token must not exceed NAMELEN (%1)" 611</msg> 612<msg 111> 613 original = "an attribute value literal can occur in an attribute specification list only after a VI delimiter" 614 verbose <<.EOF. 615 <div class="ve mid-111"> 616 <p> 617 Have you forgotten the "equal" sign marking the separation 618 between the attribute and its declared value? 619 Typical syntax is <code>attribute="value"</code>. 620 </p> 621 </div> 622.EOF. 623</msg> 624<msg 112> 625 original = "duplicate specification of attribute %1" 626 verbose <<.EOF. 627 <div class="ve mid-112"> 628 <p> 629 You have specified an attribute more than once. Example: Using 630 the "<code class="inline">height</code>" attribute twice on the same 631 "<code class="inline">img</code>" tag. 632 </p> 633 </div> 634.EOF. 635</msg> 636<msg 113> 637 original = "duplicate definition of attribute %1" 638</msg> 639<msg 114> 640 original = "data attribute specification must be omitted if attribute specification list is empty" 641</msg> 642<msg 115> 643 original = "marked section end not in marked section declaration" 644</msg> 645<msg 116> 646 original = "number of open marked sections must not exceed TAGLVL (%1)" 647</msg> 648<msg 117> 649 original = "missing marked section end" 650</msg> 651<msg 118> 652 original = "marked section started here" 653</msg> 654<msg 119> 655 original = "entity end in character data, replaceable character data or ignored marked section" 656</msg> 657<msg 120> 658 original = "normalized length of attribute value literal must not exceed LITLEN (%1); length was %2" 659 verbose <<.EOF. 660 <div class="ve mid-120"> 661 <p> 662 This error almost always means that you've forgotten a closing quote on an attribute value. For instance, 663 in: 664 </p> 665 <code class="block"> 666 <img src="fred.gif><br /> 667 <!-- 50 lines of stuff --><br /> 668 <img src="joe.gif"> 669 </code> 670 <p> 671 The "<code class="inline">src</code>" value for the first 672 <code class="inline"><img></code> is the entire 673 fifty lines of stuff up to the next double quote, which probably 674 exceeds the <a href="sgml.html#sgml"><abbr 675 title="Standard Generalized Markup Language">SGML</abbr></a>-defined 676 length limit for <abbr title="HyperText Markup Language">HTML</abbr> 677 string literals. Note that the position indicator in the error 678 message points to where the attribute value <em>ended</em> — in 679 this case, the <code class="inline">"joe.gif"</code> line. 680 </p> 681 </div> 682.EOF. 683</msg> 684<msg 121> 685 original = "syntax of attribute value does not conform to declared value" 686 verbose <<.EOF. 687 <div class="ve mid-121"> 688 <p> 689 The value of an attribute contained something that is not allowed by 690 the specified syntax for that type of attribute. For instance, the 691 “<code class="inline">selected</code>” attribute must be 692 either minimized as “<code class="inline">selected</code>” 693 or spelled out in full as “<code 694 class="inline">selected="selected"</code>”; the variant 695 “<code class="inline">selected=""</code>” is not allowed. 696 </p> 697 </div> 698.EOF. 699</msg> 700<msg 122> 701 original = "character %1 is not allowed in the value of attribute %2" 702 verbose <<.EOF. 703 <div class="ve mid-122"> 704 <p> 705 It is possible that you violated the naming convention for this attribute. 706 For example, <code>id</code> and <code>name</code> attributes must begin with 707 a letter, not a digit. 708 </p> 709 </div> 710.EOF. 711</msg> 712<msg 123> 713 original = "value of attribute %1 must be a single token" 714 verbose <<.EOF. 715 <div class="ve mid-123"> 716 <p> 717 This attribute cannot take a space-separated list of words as a value, but only one word ("token"). 718 This may also be caused by the use of a space for the value of an attribute which does not permit it. 719 </p> 720 </div> 721.EOF. 722</msg> 723<msg 124> 724 original = "value of attribute %2 invalid: %1 cannot start a number token" 725 verbose <<.EOF. 726 <div class="ve mid-124"> 727 <p> 728 The value of this attribute should be a number, and you probably used a wrong syntax. 729 </p> 730 </div> 731.EOF. 732</msg> 733<msg 125> 734 original = "value of attribute %2 invalid: %1 cannot start a name" 735 verbose <<.EOF. 736 <div class="ve mid-125"> 737 <p> 738 It is possible that you violated the naming convention for this attribute. 739 For example, <code>id</code> and <code>name</code> attributes must begin with 740 a letter, not a digit. 741 </p> 742 </div> 743.EOF. 744</msg> 745<msg 126> 746 original = "non-impliable attribute %1 not specified but OMITTAG NO and SHORTTAG NO" 747</msg> 748<msg 127> 749 original = "required attribute %1 not specified" 750 verbose <<.EOF. 751 <div class="ve mid-127"> 752 <p> 753 The attribute given above is required for an element that you've used, 754 but you have omitted it. For instance, in most HTML and XHTML document 755 types the "type" attribute is required on the "script" element and the 756 "alt" attribute is required for the "img" element. 757 </p> 758 <p> 759 Typical values for <code>type</code> are 760 <code>type="text/css"</code> for <code><style></code> 761 and <code>type="text/javascript"</code> for <code><script></code>. 762 </p> 763 </div> 764.EOF. 765</msg> 766<msg 128> 767 original = "first occurrence of CURRENT attribute %1 not specified" 768</msg> 769<msg 129> 770 original = "%1 is not a notation name" 771</msg> 772<msg 130> 773 original = "%1 is not a general entity name" 774</msg> 775<msg 131> 776 original = "value of attribute %2 cannot be %1; must be one of %3" 777 verbose <<.EOF. 778 <div class="ve mid-131"> 779 <p> 780 The value of the attribute is defined to be one of a list of possible 781 values but in the document it contained something that is not allowed 782 for that type of attribute. For instance, the “<code 783 class="inline">selected</code>” attribute must be either 784 minimized as “<code class="inline">selected</code>” 785 or spelled out in full as “<code 786 class="inline">selected="selected"</code>”; a value like 787 “<code class="inline">selected="true"</code>” is not 788 allowed. 789 </p> 790 </div> 791.EOF. 792</msg> 793<msg 132> 794 original = "%1 is not a data or subdocument entity" 795</msg> 796<msg 133> 797 original = "content model is ambiguous: when no tokens have been matched, both the %2 and %3 occurrences of %1 are possible" 798</msg> 799<msg 134> 800 original = "content model is ambiguous: when the current token is the %2 occurrence of %1, both the %4 and %5 occurrences of %3 are possible" 801</msg> 802<msg 135> 803 original = "content model is ambiguous: when the current token is the %2 occurrence of %1 and the innermost containing AND group has been matched, both the %4 and %5 occurrences of %3 are possible" 804</msg> 805<msg 136> 806 original = "content model is ambiguous: when the current token is the %2 occurrence of %1 and the innermost %3 containing AND groups have been matched, both the %5 and %6 occurrences of %4 are possible" 807</msg> 808<msg 137> 809 original = "invalid comment declaration: found character %1 outside comment but inside comment declaration" 810 verbose <<.EOF. 811 <div class="ve mid-137"> 812 <p> 813 Check that you are using a proper syntax for your comments, e.g: <!-- comment here -->. 814 This error may appear if you forget the last "--" to close one comment, and later open another. 815 </p> 816 </div> 817.EOF. 818</msg> 819<msg 138> 820 original = "comment declaration started here" 821</msg> 822<msg 139> 823 original = "non SGML character number %1" 824 verbose <<.EOF. 825 <div class="ve mid-139"> 826 <p> 827 You have used an illegal character in your text. 828 <abbr title="HyperText Markup Language">HTML</abbr> uses the standard 829 <a href="http://www.unicode.org/">UNICODE Consortium</a> character repertoire, 830 and it leaves undefined (among others) 65 character codes (0 to 31 inclusive and 127 to 159 831 inclusive) that are sometimes used for typographical quote marks and similar in 832 proprietary character sets. The validator has found one of these undefined 833 characters in your document. The character may appear on your browser as a 834 curly quote, or a trademark symbol, or some other fancy glyph; on a different 835 computer, however, it will likely appear as a completely different 836 character, or nothing at all. 837 </p> 838 <p> 839 Your best bet is to replace the character with the nearest equivalent 840 ASCII character, or to use an appropriate <a 841 href="http://www.w3.org/MarkUp/html3/latin1.html">character 842 entity</a>. 843 <!-- 844 http://groups.google.com/group/uk.net.web.authoring/browse_frm/thread/54c97b9c6fb89751 845 http://www.w3.org/mid/45EFC85A.1000706@dorward.me.uk 846 --> 847 For more information on Character Encoding on the web, see Alan 848 Flavell's excellent <a 849 href="http://web.archive.org/web/20060425191748/ppewww.ph.gla.ac.uk/~flavell/charset/">HTML Character 850 Set Issues</a> reference. 851 </p> 852 <p> 853 This error can also be triggered by formatting characters embedded in 854 documents by some word processors. If you use a word processor to edit 855 your <abbr title="HyperText Markup Language">HTML</abbr> documents, be sure to use the "Save as ASCII" or similar 856 command to save the document without formatting information. 857 </p> 858 </div> 859.EOF. 860 861</msg> 862<msg 140> 863 original = "data or replaceable character data in declaration subset" 864</msg> 865<msg 141> 866 original = "ID %1 already defined" 867 verbose <<.EOF. 868 <div class="ve mid-141"> 869 <p> 870 An "id" is a unique identifier. Each time this attribute is used in a document 871 it must have a different value. If you are using this attribute as a hook for 872 style sheets it may be more appropriate to use classes (which group elements) 873 than id (which are used to identify exactly one element). 874 </p> 875 </div> 876.EOF. 877</msg> 878<msg 142> 879 original = "ID %1 first defined here" 880</msg> 881<msg 143> 882 original = "value of fixed attribute %1 not equal to default" 883</msg> 884<msg 144> 885 original = "character %1 is not significant in the reference concrete syntax and so cannot occur in a comment in the SGML declaration" 886</msg> 887<msg 145> 888 original = "minimum data of first minimum literal in SGML declaration must be ""ISO 8879:1986"" or ""ISO 8879:1986 (ENR)"" or ""ISO 8879:1986 (WWW)"" not %1" 889</msg> 890<msg 146> 891 original = "parameter before LCNMSTRT must be NAMING not %1" 892</msg> 893<msg 147> 894 original = "unexpected entity end in SGML declaration: only %1, S separators and comments allowed" 895</msg> 896<msg 148> 897 original = "%1 invalid: only %2 and parameter separators allowed" 898</msg> 899<msg 149> 900 original = "magnitude of %1 too big" 901</msg> 902<msg 150> 903 original = "character %1 is not significant in the reference concrete syntax and so cannot occur in a literal in the SGML declaration except as the replacement of a character reference" 904</msg> 905<msg 151> 906 original = "%1 is not a valid syntax reference character number" 907</msg> 908<msg 152> 909 original = "a parameter entity reference cannot occur in an SGML declaration" 910</msg> 911<msg 153> 912 original = "%1 invalid: only %2 and parameter separators are allowed" 913</msg> 914<msg 154> 915 original = "cannot continue because of previous errors" 916</msg> 917<msg 155> 918 original = "SGML declaration cannot be parsed because the character set does not contain characters having the following numbers in ISO 646: %1" 919</msg> 920<msg 156> 921 original = "the specified character set is invalid because it does not contain the minimum data characters having the following numbers in ISO 646: %1" 922</msg> 923<msg 157> 924 original = "character numbers declared more than once: %1" 925</msg> 926<msg 158> 927 original = "character numbers should have been declared UNUSED: %1" 928</msg> 929<msg 159> 930 original = "character numbers missing in base set: %1" 931</msg> 932<msg 160> 933 original = "characters in the document character set with numbers exceeding %1 not supported" 934</msg> 935<msg 161> 936 original = "invalid formal public identifier %1: missing //" 937</msg> 938<msg 162> 939 original = "invalid formal public identifier %1: no SPACE after public text class" 940</msg> 941<msg 163> 942 original = "invalid formal public identifier %1: invalid public text class" 943</msg> 944<msg 164> 945 original = "invalid formal public identifier %1: public text language must be a name containing only upper case letters" 946</msg> 947<msg 165> 948 original = "invalid formal public identifer %1: public text display version not permitted with this text class" 949</msg> 950<msg 166> 951 original = "invalid formal public identifier %1: extra field" 952</msg> 953<msg 167> 954 original = "public text class of public identifier in notation identifier must be NOTATION" 955</msg> 956<msg 168> 957 original = "base character set %1 is unknown" 958</msg> 959<msg 169> 960 original = "delimiter set is ambiguous: %1 and %2 can be recognized in the same mode" 961</msg> 962<msg 170> 963 original = "characters with the following numbers in the syntax reference character set are significant in the concrete syntax but are not in the document character set: %1" 964</msg> 965<msg 171> 966 original = "there is no unique character in the document character set corresponding to character number %1 in the syntax reference character set" 967</msg> 968<msg 172> 969 original = "there is no unique character in the internal character set corresponding to character number %1 in the syntax reference character set" 970</msg> 971<msg 173> 972 original = "the character with number %1 in ISO 646 is significant but has no representation in the syntax reference character set" 973</msg> 974<msg 174> 975 original = "capacity set %1 is unknown" 976</msg> 977<msg 175> 978 original = "capacity %1 already specified" 979</msg> 980<msg 176> 981 original = "value of capacity %1 exceeds value of TOTALCAP" 982</msg> 983<msg 177> 984 original = "syntax %1 is unknown" 985</msg> 986<msg 178> 987 original = "UCNMSTRT must have the same number of characters as LCNMSTRT" 988</msg> 989<msg 179> 990 original = "UCNMCHAR must have the same number of characters as LCNMCHAR" 991</msg> 992<msg 180> 993 original = "number of open subdocuments exceeds quantity specified for SUBDOC parameter in SGML declaration (%1)" 994</msg> 995<msg 181> 996 original = "entity %1 declared SUBDOC, but SUBDOC NO specified in SGML declaration" 997</msg> 998<msg 182> 999 original = "a parameter entity referenced in a parameter separator must end in the same declaration" 1000</msg> 1001<msg 183> 1002 original = "reference to non-existent ID %1" 1003 verbose <<.EOF. 1004 <div class="ve mid-183"> 1005 <p>This error can be triggered by:</p> 1006 <ul> 1007 <li>A non-existent input, select or textarea element</li> 1008 <li>A missing id attribute</li> 1009 <li>A typographical error in the id attribute</li> 1010 </ul> 1011 <p>Try to check the spelling and case of the id you are referring to.</p> 1012 </div> 1013.EOF. 1014</msg> 1015<msg 184> 1016 original = "generic identifier %1 used in DTD but not defined" 1017</msg> 1018<msg 185> 1019 original = "%1 not finished but document ended" 1020</msg> 1021<msg 186> 1022 original = "cannot continue with subdocument because of previous errors" 1023</msg> 1024<msg 187> 1025 original = "no document type declaration; will parse without validation" 1026 verbose <<.EOF. 1027 <div class="ve mid-187"> 1028 <p>The document type could not be determined, because the document had no correct DOCTYPE declaration. The document does not look like HTML, therefore automatic fallback could not be performed, and the document was only checked against basic markup syntax.</p> 1029 <p>Learn <a href="<!--#echo var="relroot" -->docs/help.html#faq-doctype">how to add a doctype to your document</a> 1030 from our <acronym title="Frequently Asked Questions">FAQ</acronym>, or use the validator's 1031 <code>Document Type</code> option to validate your document against a specific Document Type.</p> 1032 </div> 1033.EOF. 1034</msg> 1035<msg 188> 1036 original = "no internal or external document type declaration subset; will parse without validation" 1037</msg> 1038<msg 189> 1039 original = "this is not an SGML document" 1040</msg> 1041<msg 190> 1042 original = "length of start-tag before interpretation of literals must not exceed TAGLEN (%1)" 1043</msg> 1044<msg 191> 1045 original = "a parameter entity referenced in a token separator must end in the same group" 1046</msg> 1047<msg 192> 1048 original = "the following character numbers are shunned characters that are not significant and so should have been declared UNUSED: %1" 1049</msg> 1050<msg 193> 1051 original = "there is no unique character in the specified document character set corresponding to character number %1 in ISO 646" 1052</msg> 1053<msg 194> 1054 original = "length of attribute value must not exceed LITLEN less NORMSEP (-%1)" 1055</msg> 1056<msg 195> 1057 original = "length of tokenized attribute value must not exceed LITLEN less NORMSEP (-%1)" 1058</msg> 1059<msg 196> 1060 original = "concrete syntax scope is INSTANCE but value of %1 quantity is less than value in reference quantity set" 1061</msg> 1062<msg 197> 1063 original = "public text class of formal public identifier of base character set must be CHARSET" 1064</msg> 1065<msg 198> 1066 original = "public text class of formal public identifier of capacity set must be CAPACITY" 1067</msg> 1068<msg 199> 1069 original = "public text class of formal public identifier of concrete syntax must be SYNTAX" 1070</msg> 1071<msg 200> 1072 original = "when there is an MSOCHAR there must also be an MSICHAR" 1073</msg> 1074<msg 201> 1075 original = "character number %1 in the syntax reference character set was specified as a character to be switched but is not a markup character" 1076</msg> 1077<msg 202> 1078 original = "character number %1 was specified as a character to be switched but is not in the syntax reference character set" 1079</msg> 1080<msg 203> 1081 original = "character numbers %1 in the document character set have been assigned the same meaning, but this is the meaning of a significant character" 1082</msg> 1083<msg 204> 1084 original = "character number %1 assigned to more than one function" 1085</msg> 1086<msg 205> 1087 original = "%1 is already a function name" 1088</msg> 1089<msg 206> 1090 original = "characters with the following numbers in ISO 646 are significant in the concrete syntax but are not in the document character set: %1" 1091</msg> 1092<msg 207> 1093 original = "general delimiter %1 consists solely of function characters" 1094</msg> 1095<msg 208> 1096 original = "letters assigned to LCNMCHAR, UCNMCHAR, LCNMSTRT or UCNMSTRT: %1" 1097</msg> 1098<msg 209> 1099 original = "digits assigned to LCNMCHAR, UCNMCHAR, LCNMSTRT or UCNMSTRT: %1" 1100</msg> 1101<msg 210> 1102 original = "character number %1 cannot be assigned to LCNMCHAR, UCNMCHAR, LCNMSTRT or UCNMSTRT because it is RE" 1103</msg> 1104<msg 211> 1105 original = "character number %1 cannot be assigned to LCNMCHAR, UCNMCHAR, LCNMSTRT or UCNMSTRT because it is RS" 1106</msg> 1107<msg 212> 1108 original = "character number %1 cannot be assigned to LCNMCHAR, UCNMCHAR, LCNMSTRT or UCNMSTRT because it is SPACE" 1109</msg> 1110<msg 213> 1111 original = "separator characters assigned to LCNMCHAR, UCNMCHAR, LCNMSTRT or UCNMSTRT: %1" 1112</msg> 1113<msg 214> 1114 original = "character number %1 cannot be switched because it is a Digit, LC Letter or UC Letter" 1115</msg> 1116<msg 215> 1117 original = "pointless for number of characters to be 0" 1118</msg> 1119<msg 216> 1120 original = "%1 cannot be the replacement for a reference reserved name because it is another reference reserved name" 1121</msg> 1122<msg 217> 1123 original = "%1 cannot be the replacement for a reference reserved name because it is the replacement of another reference reserved name" 1124</msg> 1125<msg 218> 1126 original = "replacement for reserved name %1 already specified" 1127</msg> 1128<msg 219> 1129 original = "%1 is not a valid name in the declared concrete syntax" 1130</msg> 1131<msg 220> 1132 original = "%1 is not a valid short reference delimiter because it has more than one B sequence" 1133</msg> 1134<msg 221> 1135 original = "%1 is not a valid short reference delimiter because it is adjacent to a character that can occur in a blank sequence" 1136</msg> 1137<msg 222> 1138 original = "length of delimiter %1 exceeds NAMELEN (%2)" 1139</msg> 1140<msg 223> 1141 original = "length of reserved name %1 exceeds NAMELEN (%2)" 1142</msg> 1143<msg 224> 1144 original = "character numbers assigned to both LCNMCHAR or UCNMCHAR and LCNMSTRT or UCNMSTRT: %1" 1145</msg> 1146<msg 225> 1147 original = "when the concrete syntax scope is INSTANCE the syntax reference character set of the declared syntax must be the same as that of the reference concrete syntax" 1148</msg> 1149<msg 226> 1150 original = "end-tag minimization should be O for element with declared content of EMPTY" 1151</msg> 1152<msg 227> 1153 original = "end-tag minimization should be O for element %1 because it has CONREF attribute" 1154</msg> 1155<msg 228> 1156 original = "element %1 has a declared content of EMPTY and a CONREF attribute" 1157</msg> 1158<msg 229> 1159 original = "element %1 has a declared content of EMPTY and a NOTATION attribute" 1160</msg> 1161<msg 230> 1162 original = "declared value of data attribute cannot be ENTITY, ENTITIES, ID, IDREF, IDREFS or NOTATION" 1163</msg> 1164<msg 231> 1165 original = "default value of data attribute cannot be CONREF or CURRENT" 1166</msg> 1167<msg 232> 1168 original = "number of attribute names and name tokens (%1) exceeds ATTCNT (%2)" 1169</msg> 1170<msg 233> 1171 original = "if the declared value is ID the default value must be IMPLIED or REQUIRED" 1172</msg> 1173<msg 234> 1174 original = "the attribute definition list already declared attribute %1 as the ID attribute" 1175</msg> 1176<msg 235> 1177 original = "the attribute definition list already declared attribute %1 as the NOTATION attribute" 1178</msg> 1179<msg 236> 1180 original = "token %1 occurs more than once in attribute definition list" 1181</msg> 1182<msg 237> 1183 original = "no attributes defined for notation %1" 1184</msg> 1185<msg 238> 1186 original = "notation %1 for entity %2 undefined" 1187</msg> 1188<msg 239> 1189 original = "entity %1 undefined in short reference map %2" 1190</msg> 1191<msg 240> 1192 original = "notation %1 is undefined but had attribute definition" 1193</msg> 1194<msg 241> 1195 original = "length of interpreted parameter literal in bracketed text plus the length of the bracketing delimiters must not exceed LITLEN (%1)" 1196</msg> 1197<msg 242> 1198 original = "length of rank stem plus length of rank suffix must not exceed NAMELEN (%1)" 1199</msg> 1200<msg 243> 1201 original = "document instance must start with document element" 1202</msg> 1203<msg 244> 1204 original = "content model nesting level exceeds GRPLVL (%1)" 1205</msg> 1206<msg 245> 1207 original = "grand total of content tokens exceeds GRPGTCNT (%1)" 1208</msg> 1209<msg 246> 1210 original = "unclosed start-tag requires SHORTTAG YES" 1211 verbose <<.EOF. 1212 <div class="ve mid-246"> 1213 <p> 1214 The construct <foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) 1215 but <a href="http://www.w3.org/TR/html4/appendix/notes.html#h-B.3.7">its use is not recommended</a>. 1216 In most cases, this is a typo that you will want to fix. If you really want to use shorttags, 1217 be aware that they are not well implemented by browsers. 1218 </p> 1219 </div> 1220 .EOF. 1221</msg> 1222<msg 247> 1223 original = "NET-enabling start-tag requires SHORTTAG YES" 1224 verbose <<.EOF. 1225 <div class="ve mid-247"> 1226 <p> 1227 For the current document, the validator interprets strings like 1228 <code class="inline"><FOO /></code> according to legacy rules that 1229 break the expectations of most authors and thus cause confusing warnings 1230 and error messages from the validator. This interpretation is triggered 1231 by HTML 4 documents or other SGML-based HTML documents. To avoid the 1232 messages, simply remove the "/" character in such contexts. NB: If you 1233 expect <code class="inline"><FOO /></code> to be interpreted as an 1234 XML-compatible "self-closing" tag, then you need to use XHTML or HTML5. 1235 </p> 1236 <p> 1237 This warning and related errors may also be caused by an unquoted 1238 attribute value containing one or more "/". Example: 1239 <code class="inline"><a href=http://w3c.org>W3C</a></code>. 1240 In such cases, the solution is to put quotation marks around the value. 1241 </p> 1242 </div> 1243.EOF. 1244</msg> 1245<msg 248> 1246 original = "unclosed end-tag requires SHORTTAG YES" 1247 verbose <<.EOF. 1248 <div class="ve mid-248"> 1249 <p> 1250 The construct </foo<bar> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) 1251 but <a href="http://www.w3.org/TR/html4/appendix/notes.html#h-B.3.7">its use is not recommended</a>. 1252 In most cases, this is a typo that you will want to fix. If you really want to use shorttags, 1253 be aware that they are not well implemented by browsers. 1254 </p> 1255 </div> 1256 .EOF. 1257</msg> 1258<msg 249> 1259 original = "DTDs other than base allowed only if CONCUR YES or EXPLICIT YES" 1260</msg> 1261<msg 250> 1262 original = "end of entity other than document entity after document element" 1263</msg> 1264<msg 251> 1265 original = "%1 declaration illegal after document element" 1266</msg> 1267<msg 252> 1268 original = "character reference illegal after document element" 1269</msg> 1270<msg 253> 1271 original = "entity reference illegal after document element" 1272</msg> 1273<msg 254> 1274 original = "marked section illegal after document element" 1275</msg> 1276<msg 255> 1277 original = "the %1 occurrence of %2 in the content model for %3 cannot be excluded at this point because it is contextually required" 1278</msg> 1279<msg 256> 1280 original = "the %1 occurrence of %2 in the content model for %3 cannot be excluded because it is neither inherently optional nor a member of an OR group" 1281</msg> 1282<msg 257> 1283 original = "an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified" 1284</msg> 1285<msg 258> 1286 original = "value cannot be specified both for notation attribute and content reference attribute" 1287</msg> 1288<msg 259> 1289 original = "notation %1 already defined" 1290</msg> 1291<msg 260> 1292 original = "short reference map %1 already defined" 1293</msg> 1294<msg 261> 1295 original = "first defined here" 1296</msg> 1297<msg 262> 1298 original = "general delimiter role %1 already defined" 1299</msg> 1300<msg 263> 1301 original = "number of ID references in start-tag must not exceed GRPCNT (%1)" 1302</msg> 1303<msg 264> 1304 original = "number of entity names in attribute specification list must not exceed GRPCNT (%1)" 1305</msg> 1306<msg 265> 1307 original = "normalized length of attribute specification list must not exceed ATTSPLEN (%1); length was %2" 1308</msg> 1309<msg 266> 1310 original = "short reference delimiter %1 already specified" 1311</msg> 1312<msg 267> 1313 original = "single character short references were already specified for character numbers: %1" 1314</msg> 1315<msg 268> 1316 original = "default entity used in entity attribute %1" 1317</msg> 1318<msg 269> 1319 original = "reference to entity %1 uses default entity" 1320</msg> 1321<msg 270> 1322 original = "entity %1 in short reference map %2 uses default entity" 1323</msg> 1324<msg 271> 1325 original = "no DTD %1 declared" 1326</msg> 1327<msg 272> 1328 original = "LPD %1 has neither internal nor external subset" 1329</msg> 1330<msg 273> 1331 original = "element types have different link attribute definitions" 1332</msg> 1333<msg 274> 1334 original = "link set %1 already defined" 1335</msg> 1336<msg 275> 1337 original = "empty result attribute specification" 1338</msg> 1339<msg 276> 1340 original = "no source element type %1" 1341</msg> 1342<msg 277> 1343 original = "no result element type %1" 1344</msg> 1345<msg 278> 1346 original = "end of document in LPD subset" 1347</msg> 1348<msg 279> 1349 original = "%1 declaration not allowed in LPD subset" 1350</msg> 1351<msg 280> 1352 original = "ID link set declaration not allowed in simple link declaration subset" 1353</msg> 1354<msg 281> 1355 original = "link set declaration not allowed in simple link declaration subset" 1356</msg> 1357<msg 282> 1358 original = "attributes can only be defined for base document element (not %1) in simple link declaration subset" 1359</msg> 1360<msg 283> 1361 original = "a short reference mapping declaration is allowed only in the base DTD" 1362</msg> 1363<msg 284> 1364 original = "a short reference use declaration is allowed only in the base DTD" 1365</msg> 1366<msg 285> 1367 original = "default value of link attribute cannot be CURRENT or CONREF" 1368</msg> 1369<msg 286> 1370 original = "declared value of link attribute cannot be ID, IDREF, IDREFS or NOTATION" 1371</msg> 1372<msg 287> 1373 original = "only fixed attributes can be defined in simple LPD" 1374</msg> 1375<msg 288> 1376 original = "only one ID link set declaration allowed in an LPD subset" 1377</msg> 1378<msg 289> 1379 original = "no initial link set defined for LPD %1" 1380</msg> 1381<msg 290> 1382 original = "notation %1 not defined in source DTD" 1383</msg> 1384<msg 291> 1385 original = "result document type in simple link specification must be implied" 1386</msg> 1387<msg 292> 1388 original = "simple link requires SIMPLE YES" 1389</msg> 1390<msg 293> 1391 original = "implicit link requires IMPLICIT YES" 1392</msg> 1393<msg 294> 1394 original = "explicit link requires EXPLICIT YES" 1395</msg> 1396<msg 295> 1397 original = "LPD not allowed before first DTD" 1398</msg> 1399<msg 296> 1400 original = "DTD not allowed after an LPD" 1401</msg> 1402<msg 297> 1403 original = "definition of general entity %1 is unstable" 1404</msg> 1405<msg 298> 1406 original = "definition of parameter entity %1 is unstable" 1407</msg> 1408<msg 299> 1409 original = "multiple link rules for ID %1 but not all have link attribute specifications" 1410</msg> 1411<msg 300> 1412 original = "multiple link rules for element type %1 but not all have link attribute specifications" 1413</msg> 1414<msg 301> 1415 original = "link type %1 does not have a link set %2" 1416</msg> 1417<msg 302> 1418 original = "link set use declaration for simple link process" 1419</msg> 1420<msg 303> 1421 original = "no link type %1" 1422</msg> 1423<msg 304> 1424 original = "both document type and link type %1" 1425</msg> 1426<msg 305> 1427 original = "link type %1 already defined" 1428</msg> 1429<msg 306> 1430 original = "document type %1 already defined" 1431</msg> 1432<msg 307> 1433 original = "link set %1 used in LPD but not defined" 1434</msg> 1435<msg 308> 1436 original = "\#IMPLIED already linked to result element type %1" 1437</msg> 1438<msg 309> 1439 original = "number of active simple link processes exceeds quantity specified for SIMPLE parameter in SGML declaration (%1)" 1440</msg> 1441<msg 310> 1442 original = "only one chain of explicit link processes can be active" 1443</msg> 1444<msg 311> 1445 original = "source document type name for link type %1 must be base document type since EXPLICIT YES 1" 1446</msg> 1447<msg 312> 1448 original = "only one implicit link process can be active" 1449</msg> 1450<msg 313> 1451 original = "sorry, link type %1 not activated: only one implicit or explicit link process can be active (with base document type as source document type)" 1452</msg> 1453<msg 314> 1454 original = "name missing after name group in entity reference" 1455</msg> 1456<msg 315> 1457 original = "source document type name for link type %1 must be base document type since EXPLICIT NO" 1458</msg> 1459<msg 316> 1460 original = "link process must be activated before base DTD" 1461</msg> 1462<msg 317> 1463 original = "unexpected entity end while starting second pass" 1464</msg> 1465<msg 318> 1466 original = "type %1 of element with ID %2 not associated element type for applicable link rule in ID link set" 1467</msg> 1468<msg 319> 1469 original = "DATATAG feature not implemented" 1470</msg> 1471<msg 320> 1472 original = "generic identifier specification missing after document type specification in start-tag" 1473</msg> 1474<msg 321> 1475 original = "generic identifier specification missing after document type specification in end-tag" 1476</msg> 1477<msg 322> 1478 original = "a NET-enabling start-tag cannot include a document type specification" 1479</msg> 1480<msg 323> 1481 original = "DTD did not contain element declaration for document type name" 1482 verbose <<.EOF. 1483 <div class="ve mid-323"> 1484 <p> 1485 A DOCTYPE declares the version of the language used, as well as what the root 1486 (top) element of your document will be. For example, if the top element 1487 of your document is <html>, the DOCTYPE declaration 1488 will look like: "<!DOCTYPE html". 1489 </p> 1490 <p> 1491 In most cases, it is safer not to type or edit the DOCTYPE declaration at all, 1492 and preferable to let a tool include it, or copy and paste it from a 1493 <a href="http://www.w3.org/QA/2002/04/valid-dtd-list.html">trusted list of DTDs</a>. 1494 </p> 1495 </div> 1496.EOF. 1497</msg> 1498<msg 324> 1499 original = "invalid default SGML declaration" 1500</msg> 1501<msg 325> 1502 original = "reference to entity %1 for which no system identifier could be generated" 1503 verbose <<.EOF. 1504 <div class="ve mid-325"> 1505 <p> 1506 This is usually a cascading error caused by a an undefined entity 1507 reference or use of an unencoded ampersand (&) in an URL or body 1508 text. See the previous message for further details. 1509 </p> 1510 </div> 1511.EOF. 1512</msg> 1513<msg 326> 1514 original = "entity was defined here" 1515</msg> 1516<msg 327> 1517 original = "content model is mixed but does not allow \#PCDATA everywhere" 1518</msg> 1519<msg 328> 1520 original = "start or end of range must specify a single character" 1521</msg> 1522<msg 329> 1523 original = "number of first character in range must not exceed number of second character in range" 1524</msg> 1525<msg 330> 1526 original = "delimiter cannot be an empty string" 1527</msg> 1528<msg 331> 1529 original = "too many characters assigned same meaning with minimum literal" 1530</msg> 1531<msg 332> 1532 original = "earlier reference to entity %1 used default entity" 1533</msg> 1534<msg 333> 1535 original = "empty start-tag" 1536 verbose <<.EOF. 1537 <div class="ve mid-334"> 1538 <p> 1539 The construct <> is sometimes valid in HTML (it is an example of the rather obscure “Shorttags” feature) 1540 but <a href="http://www.w3.org/TR/html4/appendix/notes.html#h-B.3.7">its use is not recommended</a>. 1541 In most cases, this is a typo that you will want to fix. If you really want to use shorttags, 1542 be aware that they are not well implemented by browsers. 1543 </p> 1544 </div> 1545.EOF. 1546</msg> 1547<msg 334> 1548 original = "empty end-tag" 1549 verbose <<.EOF. 1550 <div class="ve mid-334"> 1551 <p> 1552 The construct </> is valid in HTML (it is an example of the rather obscure “Shorttags” feature) 1553 but <a href="http://www.w3.org/TR/html4/appendix/notes.html#h-B.3.7">its use is not recommended</a>. 1554 In most cases, this is a typo that you will want to fix. If you really want to use shorttags, 1555 be aware that they are not well implemented by browsers. 1556 </p> 1557 </div> 1558.EOF. 1559</msg> 1560<msg 335> 1561 original = "unused short reference map %1" 1562</msg> 1563<msg 336> 1564 original = "unused parameter entity %1" 1565</msg> 1566<msg 337> 1567 original = "cannot generate system identifier for public text %1" 1568</msg> 1569<msg 338> 1570 original = "cannot generate system identifier for general entity %1" 1571 verbose <<.EOF. 1572 <div class="ve mid-338"> 1573 <p> 1574 An entity reference was found in the document, but there is no reference 1575 by that name defined. Often this is caused by misspelling the reference 1576 name, unencoded ampersands, or by leaving off the trailing semicolon (;). 1577 <strong>The most common cause of this error is unencoded ampersands in 1578 URLs</strong> as described by the <a 1579 href="http://www.htmlhelp.com/">WDG</a> in "<a 1580 href="http://www.htmlhelp.com/tools/validator/problems.html#amp">Ampersands 1581 in URLs</a>". 1582 </p> 1583 <p> 1584 Entity references start with an ampersand (&) and end with a 1585 semicolon (;). If you want to use a literal ampersand in your document 1586 you must encode it as "&amp;" (<em>even inside URLs!</em>). Be 1587 careful to end entity references with a semicolon or your entity 1588 reference may get interpreted in connection with the following text. 1589 Also keep in mind that named entity references are case-sensitive; 1590 &Aelig; and &aelig; are different characters. 1591 </p> 1592 <p> 1593 If this error appears in some markup generated by PHP's session handling 1594 code, <a href="http://www.w3.org/QA/2005/04/php-session" 1595 title="Ampersands, PHP Sessions and Valid HTML">this article</a> has 1596 explanations and solutions to your problem. 1597 </p> 1598 <p> 1599 Note that in most documents, errors related to entity references will 1600 trigger up to 5 separate messages from the Validator. Usually these 1601 will all disappear when the original problem is fixed. 1602 </p> 1603 </div> 1604.EOF. 1605</msg> 1606<msg 339> 1607 original = "cannot generate system identifier for parameter entity %1" 1608</msg> 1609<msg 340> 1610 original = "cannot generate system identifier for document type %1" 1611</msg> 1612<msg 341> 1613 original = "cannot generate system identifier for link type %1" 1614</msg> 1615<msg 342> 1616 original = "cannot generate system identifier for notation %1" 1617</msg> 1618<msg 343> 1619 original = "element type %1 both included and excluded" 1620</msg> 1621<msg 344> 1622 original = "no document type declaration; implying %1" 1623 verbose <<.EOF. 1624 <div class="ve mid-344"> 1625 <p> 1626 The checked page did not contain a document type ("DOCTYPE") declaration. 1627 The Validator has tried to validate with a fallback DTD, 1628 but this is quite likely to be incorrect and will generate a large number 1629 of incorrect error messages. It is highly recommended that you insert the 1630 proper DOCTYPE declaration in your document -- instructions for doing this 1631 are given above -- and it is necessary to have this declaration before the 1632 page can be declared to be valid. 1633 </p> 1634 </div> 1635.EOF. 1636</msg> 1637<msg 345> 1638 original = "minimum data of AFDR declaration must be ""ISO/IEC 10744:1997"" not %1" 1639</msg> 1640<msg 346> 1641 original = "AFDR declaration required before use of AFDR extensions" 1642</msg> 1643<msg 347> 1644 original = "ENR extensions were used but minimum literal was not ""ISO 8879:1986 (ENR)"" or ""ISO 8879:1986 (WWW)""" 1645</msg> 1646<msg 348> 1647 original = "illegal numeric character reference to non-SGML character %1 in literal" 1648</msg> 1649<msg 349> 1650 original = "cannot convert character reference to number %1 because description %2 unrecognized" 1651</msg> 1652<msg 350> 1653 original = "cannot convert character reference to number %1 because character %2 from baseset %3 unknown" 1654</msg> 1655<msg 351> 1656 original = "character reference to number %1 cannot be converted because of problem with internal character set" 1657</msg> 1658<msg 352> 1659 original = "cannot convert character reference to number %1 because character not in internal character set" 1660</msg> 1661<msg 353> 1662 original = "Web SGML adaptations were used but minimum literal was not ""ISO 8879:1986 (WWW)""" 1663</msg> 1664<msg 354> 1665 original = "token %1 can be value for multiple attributes so attribute name required" 1666</msg> 1667<msg 355> 1668 original = "length of hex number must not exceed NAMELEN (%1)" 1669</msg> 1670<msg 356> 1671 original = "%1 is not a valid name in the declared concrete syntax" 1672</msg> 1673<msg 357> 1674 original = "CDATA declared content" 1675</msg> 1676<msg 358> 1677 original = "RCDATA declared content" 1678</msg> 1679<msg 359> 1680 original = "inclusion" 1681</msg> 1682<msg 360> 1683 original = "exclusion" 1684</msg> 1685<msg 361> 1686 original = "NUMBER or NUMBERS declared value" 1687</msg> 1688<msg 362> 1689 original = "NAME or NAMES declared value" 1690</msg> 1691<msg 363> 1692 original = "NUTOKEN or NUTOKENS declared value" 1693</msg> 1694<msg 364> 1695 original = "CONREF attribute" 1696</msg> 1697<msg 365> 1698 original = "CURRENT attribute" 1699</msg> 1700<msg 366> 1701 original = "TEMP marked section" 1702</msg> 1703<msg 367> 1704 original = "included marked section in the instance" 1705</msg> 1706<msg 368> 1707 original = "ignored marked section in the instance" 1708</msg> 1709<msg 369> 1710 original = "RCDATA marked section" 1711</msg> 1712<msg 370> 1713 original = "processing instruction entity" 1714</msg> 1715<msg 371> 1716 original = "bracketed text entity" 1717</msg> 1718<msg 372> 1719 original = "internal CDATA entity" 1720</msg> 1721<msg 373> 1722 original = "internal SDATA entity" 1723</msg> 1724<msg 374> 1725 original = "external CDATA entity" 1726</msg> 1727<msg 375> 1728 original = "external SDATA entity" 1729</msg> 1730<msg 376> 1731 original = "attribute definition list declaration for notation" 1732</msg> 1733<msg 377> 1734 original = "rank stem" 1735</msg> 1736<msg 378> 1737 original = "no system id specified" 1738 verbose <<.EOF. 1739 <div class="ve mid-378"> 1740 <p> 1741 Your document includes a DOCTYPE declaration with a public identifier 1742 (e.g. "-//W3C//DTD XHTML 1.0 Strict//EN") but no system identifier 1743 (e.g. "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"). This is 1744 authorized in HTML (based on SGML), but not in XML-based languages. 1745 </p> 1746 <p> 1747 If you are using a standard XHTML document type, it is recommended to use exactly 1748 one of the DOCTYPE declarations from the 1749 <a href="http://www.w3.org/QA/2002/04/valid-dtd-list.html">recommended list on the W3C QA Website</a>. 1750 </p> 1751 </div> 1752.EOF. 1753 1754</msg> 1755<msg 379> 1756 original = "comment in parameter separator" 1757</msg> 1758<msg 380> 1759 original = "named character reference" 1760</msg> 1761<msg 381> 1762 original = "AND group" 1763</msg> 1764<msg 382> 1765 original = "attribute value not a literal" 1766</msg> 1767<msg 383> 1768 original = "attribute name missing" 1769</msg> 1770<msg 384> 1771 original = "element declaration for group of element types" 1772</msg> 1773<msg 385> 1774 original = "attribute definition list declaration for group of element types" 1775</msg> 1776<msg 386> 1777 original = "empty comment declaration" 1778</msg> 1779<msg 387> 1780 original = "S separator in comment declaration" 1781 verbose <<.EOF. 1782 <div class="ve mid-387"> 1783 <p> 1784 This may happen if you have consecutive comments but did not close one of them properly. 1785 The proper syntax for comments is <!-- my comment -->. 1786 </p> 1787 </div> 1788.EOF. 1789</msg> 1790<msg 388> 1791 original = "multiple comments in comment declaration" 1792</msg> 1793<msg 389> 1794 original = "no status keyword" 1795</msg> 1796<msg 390> 1797 original = "multiple status keywords" 1798</msg> 1799<msg 391> 1800 original = "parameter entity reference in document instance" 1801</msg> 1802<msg 392> 1803 original = "CURRENT attribute" 1804</msg> 1805<msg 393> 1806 original = "element type minimization parameter" 1807</msg> 1808<msg 394> 1809 original = "reference not terminated by REFC delimiter" 1810 verbose <<.EOF. 1811 <div class="ve mid-394"> 1812 <p> 1813 If you meant to include an entity that starts with "&", then you should 1814 terminate it with ";". Another reason for this error message is that 1815 you inadvertently created an entity by failing to escape an "&" 1816 character just before this text. 1817 </p> 1818 </div> 1819.EOF. 1820</msg> 1821<msg 395> 1822 original = "\#PCDATA not first in model group" 1823</msg> 1824<msg 396> 1825 original = "\#PCDATA in SEQ group" 1826</msg> 1827<msg 397> 1828 original = "\#PCDATA in nested model group" 1829</msg> 1830<msg 398> 1831 original = "\#PCDATA in model group that does not have REP occurrence indicator" 1832</msg> 1833<msg 399> 1834 original = "name group or name token group used connector other than OR" 1835</msg> 1836<msg 400> 1837 original = "processing instruction does not start with name" 1838</msg> 1839<msg 401> 1840 original = "S separator in status keyword specification in document instance" 1841</msg> 1842<msg 402> 1843 original = "reference to external data entity" 1844</msg> 1845<msg 403> 1846 original = "reference to external entity in attribute value" 1847 verbose <<.EOF. 1848 <div class="ve mid-403"> 1849 <p> 1850 This is generally the sign of an ampersand that was not properly escaped for inclusion 1851 in an attribute, in a href for example. You will need to escape all instances of '&' 1852 into '&amp;'. 1853 </p> 1854 </div> 1855.EOF. 1856</msg> 1857<msg 404> 1858 original = "character %1 is the first character of a delimiter but occurred as data" 1859 verbose <<.EOF. 1860 <div class="ve mid-404"> 1861 <p> 1862 This message may appear in several cases: 1863 </p> 1864 <ul> 1865 <li>You tried to include the "<" character in your page: you should escape it as "&lt;"</li> 1866 <li>You used an unescaped ampersand "&": this may be valid in some contexts, 1867 but it is recommended to use "&amp;", which is always safe.</li> 1868 <li>Another possibility is that you forgot to close quotes in a previous tag.</li> 1869 </ul> 1870 </div> 1871.EOF. 1872</msg> 1873<msg 405> 1874 original = "SGML declaration was not implied" 1875</msg> 1876<msg 406> 1877 original = "marked section in internal DTD subset" 1878</msg> 1879<msg 407> 1880 original = "NET-enabling start-tag not immediately followed by null end-tag" 1881verbose <<.EOF. 1882 <div class="ve mid-407"> 1883 <p> 1884 This error may occur when there is a mistake in how a self-closing tag is closed, e.g '.../ >'. 1885 The proper syntax is '... />' (note the position of the space). 1886 </p> 1887 </div> 1888.EOF. 1889</msg> 1890<msg 408> 1891 original = "entity end in different element from entity reference" 1892</msg> 1893<msg 409> 1894 original = "NETENABL IMMEDNET requires EMPTYNRM YES" 1895</msg> 1896<msg 410> 1897 original = "reference to non-SGML character" 1898 verbose <<.EOF. 1899 <div class="ve mid-410"> 1900 <p> 1901 You've included a character reference to a character that is not defined 1902 in the document type you've chosen. This is most commonly caused by 1903 numerical references to characters from vendor proprietary 1904 character repertoires. Often the culprit will be fancy or typographical 1905 quote marks from either the Windows or Macintosh character repertoires. 1906 </p> 1907 <p> 1908 The solution is to reference UNICODE characters instead. A list of 1909 common characters from the Windows character repertoire and their 1910 UNICODE equivalents can be found in the document "<a 1911 href="http://www.cs.tut.fi/~jkorpela/www/windows-chars.html#list" 1912 >On the use of some MS Windows characters in HTML</a>" maintained by 1913 <a href="http://www.cs.tut.fi/~jkorpela/">Jukka Korpela</a> 1914 <<a href="mailto:jkorpela@cs.tut.fi">jkorpela@cs.tut.fi</a>>. 1915 </p> 1916 </div> 1917.EOF. 1918</msg> 1919<msg 411> 1920 original = "declaration of default entity" 1921</msg> 1922<msg 412> 1923 original = "reference to parameter entity in parameter separator in internal subset" 1924</msg> 1925<msg 413> 1926 original = "reference to parameter entity in token separator in internal subset" 1927</msg> 1928<msg 414> 1929 original = "reference to parameter entity in parameter literal in internal subset" 1930</msg> 1931<msg 415> 1932 original = "cannot generate system identifier for SGML declaration reference" 1933</msg> 1934<msg 416> 1935 original = "public text class of formal public identifier of SGML declaration must be SD" 1936</msg> 1937<msg 417> 1938 original = "SGML declaration reference was used but minimum literal was not ""ISO 8879:1986 (WWW)""" 1939</msg> 1940<msg 418> 1941 original = "member of model group containing \#PCDATA has occurrence indicator" 1942</msg> 1943<msg 419> 1944 original = "member of model group containing \#PCDATA is a model group" 1945</msg> 1946<msg 420> 1947 original = "reference to non-predefined entity" 1948</msg> 1949<msg 421> 1950 original = "reference to external entity" 1951</msg> 1952<msg 422> 1953 original = "declaration of default entity conflicts with IMPLYDEF ENTITY YES" 1954</msg> 1955<msg 423> 1956 original = "parsing with respect to more than one active doctype not supported" 1957</msg> 1958<msg 424> 1959 original = "cannot have active doctypes and link types at the same time" 1960</msg> 1961<msg 425> 1962 original = "number of concurrent document instances exceeds quantity specified for CONCUR parameter in SGML declaration (%1)" 1963</msg> 1964<msg 426> 1965 original = "datatag group can only be specified in base document type" 1966</msg> 1967<msg 427> 1968 original = "element not in the base document type can't have an empty start-tag" 1969</msg> 1970<msg 428> 1971 original = "element not in base document type can't have an empty end-tag" 1972</msg> 1973<msg 429> 1974 original = "immediately recursive element" 1975</msg> 1976<msg 430> 1977 original = "invalid URN %1: missing "":""" 1978</msg> 1979<msg 431> 1980 original = "invalid URN %1: missing ""urn:"" prefix" 1981</msg> 1982<msg 432> 1983 original = "invalid URN %1: invalid namespace identifier" 1984</msg> 1985<msg 433> 1986 original = "invalid URN %1: invalid namespace specific string" 1987</msg> 1988<msg 434> 1989 original = "invalid URN %1: extra field" 1990</msg> 1991<msg 435> 1992 original = "prolog can't be omitted unless CONCUR NO and LINK EXPLICIT NO and either IMPLYDEF ELEMENT YES or IMPLYDEF DOCTYPE YES" 1993</msg> 1994<msg 436> 1995 original = "can't determine name of \#IMPLIED document element" 1996</msg> 1997<msg 437> 1998 original = "can't use \#IMPLICIT doctype unless CONCUR NO and LINK EXPLICIT NO" 1999</msg> 2000<msg 438> 2001 original = "Sorry, \#IMPLIED doctypes not implemented" 2002</msg> 2003<msg 439> 2004 original = "reference to DTD data entity ignored" 2005</msg> 2006<msg 440> 2007 original = "notation %1 for parameter entity %2 undefined" 2008</msg> 2009<msg 441> 2010 original = "notation %1 for external subset undefined" 2011</msg> 2012<msg 442> 2013 original = "attribute %1 can't be redeclared" 2014</msg> 2015<msg 443> 2016 original = "\#IMPLICIT attributes have already been specified for notation %1" 2017</msg> 2018<msg 444> 2019 original = "a name group is not allowed in a parameter entity reference in a start tag" 2020</msg> 2021<msg 445> 2022 original = "name group in a parameter entity reference in an end tag (SGML forbids them in start tags)" 2023</msg> 2024<msg 446> 2025 original = "if the declared value is NOTATION a default value of CONREF is useless" 2026</msg> 2027<msg 447> 2028 original = "Sorry, \#ALL and \#IMPLICIT content tokens not implemented" 2029</msg> 2030<msg no-xmlns> 2031 original = "Missing xmlns attribute for element %1. The value should be: %2" 2032 verbose <<.EOF. 2033 <div class="ve no-xmlns"> 2034 <p> 2035 Many Document Types based on XML need a mandatory <code>xmlns</code> attribute on the root element. For example, the root element for <a href="http://www.w3.org/TR/xhtml1/#strict">XHTML</a> might look like:<br /> 2036 <code><html xmlns="http://www.w3.org/1999/xhtml"></code> 2037 </p> 2038 </div> 2039 .EOF. 2040</msg> 2041