--- test/html-webhacc/error-description-source.xml 2007/07/16 13:56:26 1.4 +++ test/html-webhacc/error-description-source.xml 2007/07/21 04:58:17 1.6 @@ -68,13 +68,13 @@ A < character is not followed by tag name or by a ! character. -

A < (U+003C LESS-THAN - SIGN) character which is not part of any markup appears - in the input stream.

+

A < (U+003C + LESS-THAN SIGN) character which is not part + of any markup appears in the input stream.

The < character as a data character must be escaped as: - 

<lt;
+ 
&lt;

 @@ -92,7 +92,6 @@ The document is non-conforming.

The string &# must be the first two characters - NUMBER SIGN) character must be the first two characters of a reference:

Numeric character reference
@@ -107,7 +106,7 @@

To represent &# as data characters, use - named entity reference: + a named entity reference for the & character: 

&amp;#

@@ -129,7 +128,7 @@ of the code point of the character to be referenced.

To represent &#x as data characters, use - named entity reference: + a named entity reference for the & character: 

&amp;#x

@@ -154,7 +153,8 @@ - There are two attributes with same name. + There are two attributes with name + $0.

There are more than one attributes with the same name in a tag. The document is non-conforming.

@@ -183,6 +183,36 @@ + + + Processing instruction + (<?...?>) cannot be used. + +

Processing instructions (<?...?>), + including XML declaration (<?xml ...?>) + and XML style sheet PI + (<xml-stylesheet ...?>), are not allowed + in the HTML syntax. The document is non-conforming.

+ +

If it is necessary to embed a processing instruction + in the HTML document, you must use the XML syntax instead.

+ +

In the HTML syntax, XML declaration is not necessary.

+ +

Instead of XML style sheet, + PIs, you must + use the HTML link element whose rel + attribute is set to stylesheet (or + alternate stylesheet for an aleternate style sheet).

+ +

Web browsers will parse processing instructions as bogus + comments. Some legacy Web browsers, such as IE:mac and + some mobile browsers, will display processing instructions + as string.

+ + +
@@ -213,10 +243,22 @@ + + Anchor cannot be nested. + +

HTML a elements cannot be nested. + The document is non-conforming.

+ +

In the HTML syntax, a start tag of the a + implies the end tag of any opening a element.

+ + + Tag <$0> - is not allowed in body. + is not allowed in a body element.

The start or end tag of an element, which cannot be a descendant of body element, appears @@ -225,10 +267,24 @@ + + Start tag <head> + is not allowed in the head element. + +

There is a start tag <head> in the + <head> element. The document is non-conforming.

+ +

In an HTML document there must not be more than + one head element, therefore no more than one + start tag <head> can appear in the input stream.

+ + + Tag <$0> - is not allowed in table. + is not allowed in a table element.

The start or end tag of an element, which cannot be a child of table element, appears @@ -277,7 +333,7 @@ - This document does not start with the + This document does not start with a DOCTYPE.

The document does not start with a DOCTYPE. @@ -303,14 +359,32 @@ + + This <html> tag is not + the first start tag. + +

There is a start tag of the html element + that it not the first start tag in the input stream. + The document is non-conforming.

+ +

In an HTML document, there cannot be more than one + html element and therefore there cannot be + more than one <html> tag. In addition, + nothing can be placed before the <html> tag + except a DOCTYPE, white space characters, + and comments.

+ + + This document is written in an old version of HTML.

The document contains a DOCTYPE declaration - that is different from HTML5 DOCTYPE (i.e. <!DOCTYPE - HTML>). The document is non-conforming.

+ that is different from HTML5 DOCTYPE (i.e. + <!DOCTYPE HTML>). The document is non-conforming.

The document might or might not be conformant to some version of HTML. However, conformance to any HTML @@ -347,24 +421,20 @@ context. The document is non-conforming.

Possible causes: -

-
If the erred element is an inline-level element (such - as a or span)
-

A data character cannot be a child - of certain sectioning elements such as body, - section, and blockquote.

- -

Any inline-level content must be put - in e.g. paragraph element such as p.

-
If the erred element is a block-level element (such as - div or hn)
-

Though some elements such as div, - li, and td allow - either one of block-level or inline-level content - is allowed. If there is a block-level content, - any inline-level content must be put - in e.g. paragraph element such as p.

-
+
    +

  • A data character cannot be a child + of certain sectioning elements such as body, + section, and blockquote.

    + +

    Any inline-level content must be put + in e.g. paragraph element such as p.

    • +

  • Though some elements such as div, + li, and td allow + either one of block-level or inline-level content + is allowed. If there is a block-level content, + any inline-level content must be put + in e.g. paragraph element such as p.

    • +

@@ -413,24 +483,32 @@ not support form elements yet.

Possible causes: -

-
If the erred element is an inline-level element (such - as a or span)
+
+
If the element with the error is an inline-level element, + such as a, progress, or img

An inline-level element cannot be a child of certain sectioning elements such as body, section, and blockquote.

Any inline-level content must be put in e.g. paragraph element such as p.

-
If the erred element is a block-level element (such as - div or hn)
+
If the element with the error is a block-level element, + such as div, hn, or + section

Though some elements such as div, li, and td allow either one of block-level or inline-level content is allowed. If there is a block-level content, any inline-level content must be put in e.g. paragraph element such as p.

-
If the erred element is the root html element
+
If the element with the error is a noscript element
+
The noscript element is allowed only in the context + where a block-level or inline-level content is expected + and in the head element. + It cannot be used in e.g. ul, table, + or select.
+
If the element with the error is the html element + that is the root element of an XHTML document

In an XHTML document, the root html element must have an xmlns attribute whose value is set to @@ -440,6 +518,19 @@ + + There is no $0 + element before this element. + +

There must be an element before another element, but there + is not. The document is non-conforming.

+ +

For example, there must be a dt element + before any dd element.

+ + +
@@ -476,6 +567,13 @@

To specify natural language information in HTML document, use lang attribute instead.

+ +

XHTML 1.0 Appendix C was encouraged to specify both + lang and xml:lang attributes with + the same value. Such a duplication has no effect in practice. + Use only one of lang (in HTML) or xml:lang (in + XML).

+ @@ -536,7 +634,8 @@ This attribute only allow a limited set of - values and the specified value is not one of them. + values and the specified value {@} is not one + of them. ? --> - The link type $0 cannot be specified for this element. @@ -568,18 +667,29 @@ The link type $0 is non-conforming. -

The specified link type is non-conforming. The entire document - is non-conforming.

+

The specified link type is non-conforming, and therefore + the document is non-conforming.

-

For example, in place of non-conforming link type copyright - you must use link type license.

+
+
Link type contents
+
Use link type index.
+
Link type copyright
+
Use link type license.
+
Link type home
+
Use link type index.
+
Link type start
+
Use link type first.
+
Link type toc
+
Use link type index.
+
- This browsing context name is reserved. - + Browsing context name + {@} is reserved. +

The specified browsing context name is reserved. The document is non-conforming.

@@ -592,7 +702,7 @@ browsing context names _blank, _main, and _replace. However, they are not conforming attribute values.

- +
@@ -636,6 +746,28 @@ th) in the last row. + + This rowspan attribute + results in creating a table row that does not contain + any cell anchored to it. + +

The rowspan attribute value of the cell + is so specified that it extends a table in the row axis. + However, the extended row does not contain any cell by itself. + The document is non-conforming.

+ +

For example, the table below is non-conforming: + 

<table>
+<tbody>
+<tr><td rowspan=2></td></tr>
+</tbody>
+</table>
+ ... is non-conforming, since the second row contains only + a cell that spans the first and the second rows.

+ + +
@@ -643,18 +775,20 @@ - An obsolete subtype is used. + {@}: An obsolete + subtype is used. - A private (x- or x.) - subtype is used. + {@}: A private + (x- or x.) subtype is used. - The subtype is not registered to IANA. + {@}: The subtype is + not registered to IANA. @@ -665,7 +799,21 @@ - This string is not an IRI syntactically. + The specified value is syntactically not an IRI + reference. + +

The specified value does not satisfy the syntactical requirements + for IRI references. The document is non-conforming.

+ +

Possible causes: +

    +
  • The string might contain one or more white space characters. + Especially, the (U+0020 + SPACE) character cannot be + used in IRI references.
    • +
+

+
@@ -717,6 +865,26 @@ + + URI scheme name is in uppercase. + +

The scheme part of the IRI is written in uppercase letter.

+ +

Uppercase scheme names are not required to be processed + correctly.

+ + + +
@@ -813,6 +981,6 @@ and/or modify it under the same terms as Perl itself.

- + \ No newline at end of file