/[pub]/test/html-webhacc/error-description.en.html.u8
Suika

Diff of /test/html-webhacc/error-description.en.html.u8

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.13 by wakaba, Wed Nov 7 11:29:46 2007 UTC revision 1.20 by wakaba, Sun May 18 07:24:04 2008 UTC
# Line 8  Web Document Conformance Checker (BETA)< Line 8  Web Document Conformance Checker (BETA)<
8  <body>  <body>
9  <h1>Description of Errors</h1>  <h1>Description of Errors</h1>
10    
11    <section id="character-encoding-layer">
12    <h2>Character Encoding Layer Errors</h2>
13    
14    <div class="section error-category-charset" id="m:illegal-octets-error"><h3>An illegal octet in the input stream.</h3></div>
15    </section>
16    
17    <section id="html5-character-encoding">
18    <h2>HTML5 Character Encoding Errors</h2>
19    
20    <div class="section format-charset must" id="m:character-encoding"><h3>Character encoding <code><var>$0</var></code>
21      is not allowed for <abbr>HTML</abbr> document.</h3>
22        <p>The character encoding used for the document is not allowed
23        for <abbr>HTML</abbr> document.  The document is non‐conforming.</p>
24      </div>
25    
26    <div class="section format-charset should" id="s:character-encoding"><h3>Character encoding <code><var>$0</var></code>
27      should not be used for <abbr>HTML</abbr> document.</h3>
28        <p>The character encoding used for the document is not recommended
29        for <abbr>HTML</abbr> document.  The document is non‐conforming
30        unless there is any good reason to use that encoding.</p>
31      </div>
32    
33    <div class="section format-charset warning" id="w:character-encoding"><h3>Use of UTF-8 is encouraged.</h3>
34        <p>Use of UTF-8 as the character encoding of the document is encouraged,
35        though the use of another character encoding is still conforming.</p>
36      </div>
37    
38    <div class="section format-charset unsupported" id="unsupported:character-encoding"><h3>Conformance for character encoding requirements
39      cannot be checked.</h3>
40        <p>The conformance checker cannot detect whether the input document
41        met the requirements on character encoding, since the document
42        is not inputed as a serialized byte sequence.  The document is
43        not conforming if it is not encoded in an appropriate character
44        encoding with appropriate labeling.</p>
45      </div>
46    
47    <div class="section format-charset error" id="m:no-character-encoding-declaration"><h3>There is no character encoding
48      declaration.</h3>
49        <p>The document does not contain a character encoding
50        declaration.  Unless the character encoding is explicitly
51        specified in lower‐level protocol, e.g. in <abbr>HTTP</abbr>,
52        or is implied by <abbr>BOM</abbr>, there must be a character
53        encoding declaration.  The document is non‐conforming.</p>
54    
55        <p>The long character encoding declaration syntax
56        <code class="html bad example">&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html; charset=<var>charset-name</var>&quot;&gt;</code>
57        is obsolete.  The new syntax is:</p>
58        <pre class="html example">
59    <code>&lt;meta charset=&quot;<var>charset-name</var>&quot;&gt;</code></pre>
60    
61        <p>Note that the <code>encoding</code> declaration in <abbr>XML</abbr>
62        declaration has no effect for <abbr>HTML</abbr> document.</p>
63      </div>
64    
65    <div class="section format-charset error" id="m:non-ascii-superset"><h3>No character encoding metadata is found
66      in lower‐level protocol nor is there <abbr>BOM</abbr>, while
67      character encoding <code><var>$0</var></code>
68      is not a superset of <abbr>ASCII</abbr>.</h3>
69        <p>The document is not labeled with character encoding name
70        in lower‐level protocol, e.g. in <abbr>HTTP</abbr>, and
71        the document is not begin with <abbr>BOM</abbr>.  In addition,
72        the character encoding of the document is not a superset of
73        <abbr>ASCII</abbr>.  The document is non‐conforming.</p>
74    
75        <p>Unless there is a <abbr>BOM</abbr>, the character encoding
76        for the document must be specified in e.g. <abbr>HTTP</abbr>‐level,
77        as:</p>
78        <pre class="http example">
79    <code>Content-Type: text/html; charset=<var>charset-name</var></code></pre>
80    
81        <p>Existence of <abbr>HTML</abbr> character encoding declaration, i.e.
82        <code class="html example">&lt;meta charset=&quot;<var>charset-name</var>&quot;&gt;</code>,
83        does not allow to omit <code>charset</code> parameter
84        for <abbr>HTML</abbr> document encoded in non‐<abbr>ASCII</abbr>
85        compatible encoding.</p>
86    
87        <p>Character encodings <code>Shift_JIS</code>, <code>Windows-31J</code>,
88        and <code>ISO-2022-JP</code> are <em>not</em> a superset of
89        <abbr>ASCII</abbr> for the purpose of <abbr>HTML</abbr> conformance.</p>
90      </div>
91    
92    <div class="section format-charset warning" id="w:charset-label-detected"><h3>While parsing the document as
93      <code><var>$0</var></code>, a character encoding declaration specifying
94      character encoding as <code><var>$1</var></code> is found.  The document
95      is reparsed.</h3>
96        <p>While parsing a document in a character encoding,
97        a character encoding declaration which declares the character
98        encoding of the document as another character encoding is found.
99        The occurence of this warning itself does not make the document
100        non‐conforming.  However, the failure of the first attempt to
101        to detect the character encoding might be a result of non‐conformance
102        of the document.</p>
103    
104        <p>The document will be reparsed from the beginning.  Some error
105        or warning might be reported again.</p>
106    
107        <p>These are suggestions to avoid this warning:</p>
108        <ul>
109        <li>Specify <code>charset</code> parameter in the <code>Content-Type</code>
110        field in the <abbr>HTTP</abbr> header, as:
111        <pre class="HTTP example">
112    <code>Content-Type: text/html; charset=&quot;<var>charset-name</var>&quot;</code></pre></li>
113        <li>Put the character encoding declaration
114        (<code class="html example">&lt;meta charset=&quot;<var>charset-name</var>&quot;&gt;</code>)
115        just after <code class="html example">&lt;head&gt;</code> start tag.</li>
116        <li>Use <code>UTF-8</code>.</li>
117        </ul>
118      </div>
119    </section>
120    
121  <section id="html5-tokenize-error">  <section id="html5-tokenize-error">
122  <h2>HTML5 Parse Errors in Tokenization Stage</h2>  <h2>HTML5 Parse Errors in Tokenization Stage</h2>
123    
# Line 33  Web Document Conformance Checker (BETA)< Line 143  Web Document Conformance Checker (BETA)<
143    </div>    </div>
144    
145  <div class="section tokenize-error" id="bare-ero"><h3>The <code>&amp;</code> character must  <div class="section tokenize-error" id="bare-ero"><h3>The <code>&amp;</code> character must
146    introduce a reference.</h3>    be escaped as <code class="html example">&amp;amp;</code>.</h3>
147      <p>An <code>&amp;</code> (<code>U+0026</code>      <p>An <code>&amp;</code> character which
     <code class="charname">AMPERSAND</code>) character which  
148      is not part of any reference appears in the input stream.      is not part of any reference appears in the input stream.
149      The document is non-conforming.</p>      The document is non‐conforming.</p>
150    
151      <p><strong>Any <code>&amp;</code> character in URI (or IRI)      <p><em>Any <code>&amp;</code> character in URI (or IRI)
152      must be escaped as <code>&amp;amp;</code>.</strong></p>      must be escaped as <code class="example">&amp;amp;</code>.</em></p>
153    
154      <p>The <code>&amp;</code> character must      <p>The <code>&amp;</code> character must
155      be the first character of a reference:      be the first character of a reference:
156        <dl>        <dl class="switch">
157        <dt>Named entity reference</dt>        <dt>Named entity reference</dt>
158            <dd><pre class="html example">            <dd><pre class="html example">
159  <code>&amp;<var>entity-name</var>;</code></pre>  <code>&amp;<var>entity-name</var>;</code></pre>
# Line 114  Web Document Conformance Checker (BETA)< Line 223  Web Document Conformance Checker (BETA)<
223    
224      <p>The string <code>&amp;#</code> must be the first two characters      <p>The string <code>&amp;#</code> must be the first two characters
225      of a reference:      of a reference:
226        <dl>        <dl class="switch">
227        <dt>Numeric character reference</dt>        <dt>Numeric character reference</dt>
228            <dd><pre class="html example">            <dd><pre class="html example">
229  <code>&amp;#<var>d</var>;</code></pre>  <code>&amp;#<var>d</var>;</code></pre>
# Line 166  Web Document Conformance Checker (BETA)< Line 275  Web Document Conformance Checker (BETA)<
275    
276      <dl class="switch">      <dl class="switch">
277      <dt>Comments</dt>      <dt>Comments</dt>
278        <dd>In HTML documents, comments must be introduced by        <dd>In HTML document, comments must be introduced by
279        <code>&lt;!--</code> (<code>&lt;!</code> <em>immediately</em> followed        <code class="example">&lt;!--</code> (<code>&lt;!</code>
280          <em>immediately</em> followed
281        by <em>two</em> <code>-</code>s) and must be terminated by        by <em>two</em> <code>-</code>s) and must be terminated by
282        <code>--&gt;</code>.  Strings <code>&lt;!</code> not followed        <code class="example">--&gt;</code>.
283          Strings <code>&lt;!</code> not followed
284        by <code>--</code> and <code>&lt;!-</code> not followed by        by <code>--</code> and <code>&lt;!-</code> not followed by
285        <code>-</code> are not valid open delimiters for comments.</dd>        <code>-</code> are not valid open delimiters for comments.</dd>
286      <dt>Marked sections, including <code>CDATA</code> sections</dt>      <dt>Marked sections, including <code>CDATA</code> sections</dt>
287        <dd>Marked sections are not allowed in HTML documents.</dd>        <dd>Marked sections are not allowed in HTML document.</dd>
288      <dt>Markup declarations</dt>      <dt>Markup declarations</dt>
289        <dd>Markup declarations, except <code>DOCTYPE</code>        <dd>Markup declarations, except for <code>DOCTYPE</code>
290        and comment declarations, are not allowed in HTML documents.</dd>        and comment declarations, are not allowed in HTML document.</dd>
291      <dt>String <code>&lt;!</code></dt>      <dt>String <code>&lt;!</code></dt>
292        <dd>String <code>&lt;!</code> must be escaped as        <dd>String <code>&lt;!</code> must be escaped as
293        <code>&amp;lt;!</code>.</dd>        <code class="example">&amp;lt;!</code>.</dd>
294      </dl>      </dl>
295    </div>    </div>
296    
# Line 239  Web Document Conformance Checker (BETA)< Line 350  Web Document Conformance Checker (BETA)<
350      <dt><code>&lt;script/&gt;</code></dt>      <dt><code>&lt;script/&gt;</code></dt>
351          <dd><p>The polytheistic slash cannot be used for <code>script</code>          <dd><p>The polytheistic slash cannot be used for <code>script</code>
352          element.  Even for an empty <code>script</code> element,          element.  Even for an empty <code>script</code> element,
353          there must be an explicit end tag <code>&lt;/script&gt;</code>.</p>          there must be an explicit end tag
354            <code class="html example">&lt;/script&gt;</code>.</p>
355    
356          <p><strong>NOTE</strong>: Though some user agents interpret          <p><strong>NOTE</strong>: Though some user agents interpret
357          polytheistic slash for <code>script</code> element as the          polytheistic slash for <code>script</code> element as the
# Line 256  Web Document Conformance Checker (BETA)< Line 368  Web Document Conformance Checker (BETA)<
368          to allow polytheistic slash for these elements.</dd>          to allow polytheistic slash for these elements.</dd>
369      <dt><code>&lt;a/&gt;</code>, <code>&lt;p/&gt;</code></dt>      <dt><code>&lt;a/&gt;</code>, <code>&lt;p/&gt;</code></dt>
370          <dd>These elements are not always empty and therefore          <dd>These elements are not always empty and therefore
371          polytheistic slash is not allowed.</dd>          polytheistic slash is not allowed.  Use explicit end tag
372            to represent empty element as:
373              <pre class="example html">
374    <code>&lt;p&gt;&lt;/p&gt;</code></pre>
375            </dd>
376      </dl>      </dl>
377    
378      <p>Note that, unlike in XML, the polytheistic slash has      <p>Note that, unlike in XML, the polytheistic slash has
# Line 277  Web Document Conformance Checker (BETA)< Line 393  Web Document Conformance Checker (BETA)<
393        <dd>An <abbr>XBL</abbr> binding cannot be associated by        <dd>An <abbr>XBL</abbr> binding cannot be associated by
394        <abbr title="processing instruction">PI</abbr> in <abbr>HTML</abbr>        <abbr title="processing instruction">PI</abbr> in <abbr>HTML</abbr>
395        document.  Use <code>binding</code> property in <abbr>CSS</abbr>        document.  Use <code>binding</code> property in <abbr>CSS</abbr>
396        style sheet.</dd>        style sheet as:
397            <pre class="html example">
398    <code>&lt;style&gt;
399    p {
400      binding: url(binding.xbl);
401    }
402    &lt;/style&gt;</code></pre>
403          </dd>
404      <dt><code>&lt;?xml?&gt;</code> (XML declaration)</dt>      <dt><code>&lt;?xml?&gt;</code> (XML declaration)</dt>
405          <dd>XML declaration is unnecessary for HTML documents.</dd>          <dd>XML declaration is unnecessary for HTML documents.</dd>
406      <dt><code>&lt;?xml-stylesheet?&gt;</code> (XML style sheet      <dt><code>&lt;?xml-stylesheet?&gt;</code> (XML style sheet
# Line 285  Web Document Conformance Checker (BETA)< Line 408  Web Document Conformance Checker (BETA)<
408          <dd>Use HTML <code>link</code> element with <code>rel</code>          <dd>Use HTML <code>link</code> element with <code>rel</code>
409          attribute set to <code>stylesheet</code> (or,          attribute set to <code>stylesheet</code> (or,
410          <code>alternate stylesheet</code> for an alternate style          <code>alternate stylesheet</code> for an alternate style
411          sheet).</dd>          sheet).
412              <pre class="example html">
413    <code>&lt;link rel=stylesheet href=&quot;path/to/stylesheet.css&quot;&gt;</code></pre>
414            </dd>
415      <dt><code>&lt;?php?&gt;</code> or      <dt><code>&lt;?php?&gt;</code> or
416      <code>&lt;? <var>... <abbr>PHP</abbr> code ...</var> ?&gt;</code>      <code>&lt;? <var>... <abbr>PHP</abbr> code ...</var> ?&gt;</code>
417      (<abbr>PHP</abbr> code)</dt>      (<abbr>PHP</abbr> code)</dt>
# Line 425  Web Document Conformance Checker (BETA)< Line 551  Web Document Conformance Checker (BETA)<
551        <dd>Though the element is void in earlier versions of Safari,        <dd>Though the element is void in earlier versions of Safari,
552        the <code>canvas</code> element is <em>no</em> longer        the <code>canvas</code> element is <em>no</em> longer
553        defined as empty.  There must be an end tag        defined as empty.  There must be an end tag
554        <code>&lt;/canvas&gt;</code>.</dd>        <code class="html example">&lt;/canvas&gt;</code>.</dd>
555      </dl>      </dl>
556    
557      <p>Note that misnesting tags, such as      <p>Note that misnesting tags, such as
# Line 451  Web Document Conformance Checker (BETA)< Line 577  Web Document Conformance Checker (BETA)<
577    HTML.</h3>    HTML.</h3>
578      <p>The document contains a <code>DOCTYPE</code> declaration      <p>The document contains a <code>DOCTYPE</code> declaration
579      that is different from HTML5 <code>DOCTYPE</code> (i.e.      that is different from HTML5 <code>DOCTYPE</code> (i.e.
580      <code>&lt;!DOCTYPE HTML&gt;</code>).  The document is non-conforming.</p>      <code class="example html">&lt;!DOCTYPE HTML&gt;</code>).
581        The document is non‐conforming.</p>
582    
583      <p>The document might or might not be conformant to      <p>The document might or might not be conformant to
584      some version of HTML.  However, conformance to any HTML      some version of HTML.  However, conformance to any HTML
# Line 563  Web Document Conformance Checker (BETA)< Line 690  Web Document Conformance Checker (BETA)<
690                    block-level content, any inline-level content must be                    block-level content, any inline-level content must be
691                    put in e.g. paragraph element such as <code>p</code>.</p>                    put in e.g. paragraph element such as <code>p</code>.</p>
692                    <p>For example, an HTML document fragment                    <p>For example, an HTML document fragment
693                    <code class="bad example">&lt;div&gt;&lt;p&gt;Hello!&lt;/p&gt; World!&lt;/div&gt;</code>                    <code class="html bad example">&lt;div&gt;&lt;p&gt;Hello!&lt;/p&gt; World!&lt;/div&gt;</code>
694                    is non-conforming, since a word <q>World!</q> does not belong                    is non-conforming, since a word <q>World!</q> does not belong
695                    to any paragraph.  (If not part of any paragraph, what is                    to any paragraph.  (If not part of any paragraph, what is
696                    it!?)  A conforming example would be:                    it!?)  A conforming example would be:
697                      <pre class="example">                      <pre class="html example">
698  <code>&lt;div&gt;&lt;p&gt;Hello!&lt;/p&gt; &lt;p&gt;World!&lt;/p&gt;&lt;/div&gt;</code></pre>  <code>&lt;div&gt;&lt;p&gt;Hello!&lt;/p&gt; &lt;p&gt;World!&lt;/p&gt;&lt;/div&gt;</code></pre>
699                    </p></dd>                    </p></dd>
700                <dt>If the parent element does <em>not</em> allow                <dt>If the parent element does <em>not</em> allow
# Line 608  Web Document Conformance Checker (BETA)< Line 735  Web Document Conformance Checker (BETA)<
735    
736      <dl class="switch">      <dl class="switch">
737      <dt><code>html</code> element in an XHTML document</dt>      <dt><code>html</code> element in an XHTML document</dt>
738          <dd><p>In an XHTML document, the root <code>html</code>          <dd><p>In <abbr>XHTML</abbr> document, the root <code>html</code>
739          element must have an <code>xmlns</code> attribute          element must have an <code>xmlns</code> attribute as:
740          whose value is set to            <pre class="xml example">
741          <code>http://www.w3.org/1999/xhtml</code>.</p></dd>  <code>&lt;html xmlns=&quot;http://www.w3.org/1999/xhtml&quot;&gt;</code></pre></p></dd>
742      <dt><code>rss</code> element</dt>      <dt><code>rss</code> element</dt>
743          <dd><p>The document is written in some version of RSS.</p>          <dd><p>The document is written in some version of RSS.</p>
744          <p>The conformance checker does not support any version          <p>The conformance checker does not support any version
745          of RSS.  Use Atom 1.0 for feed documents.</p></dd>          of RSS.  Use Atom 1.0 for feed documents.</p></dd>
746      <dt><code>feed</code> element</dt>      <dt><code>feed</code> element</dt>
747          <dd><p>The Atom <code>feed</code> element must be          <dd><p>The Atom <code>feed</code> element must be
748          in the <code>http://www.w3.org/2004/Atom</code>          in the <code>http://www.w3.org/2005/Atom</code>
749          namespace.</p>          namespace as:
750              <pre class="xml example">
751    <code>&lt;feed xmlns=&quot;http://www.w3.org/2005/Atom&quot;&gt;</code></pre>
752            </p>
753          <p>The conformance checker does not support Atom 0.3.          <p>The conformance checker does not support Atom 0.3.
754          Use Atom 1.0 for feed documents.</p></dd>          Use Atom 1.0 for feed documents.</p></dd>
755      </dl>      </dl>
# Line 735  Web Document Conformance Checker (BETA)< Line 865  Web Document Conformance Checker (BETA)<
865  <section id="attribute-value-errors">  <section id="attribute-value-errors">
866  <h2>Attribute Value Errors</h2>  <h2>Attribute Value Errors</h2>
867    
868    <div class="section attribute-value-warning warning" id="w:charset:not-registered"><h3>Character encoding name <code><var>$0</var></code>
869      is not registered.</h3>
870        <p>The specified character encoding name is not registered to
871        <abbr>IANA</abbr>.  Use of registered character encoding name
872        is a good practice to facilitate interoperability.</p>
873    
874        <dl class="switch">
875        <dt><code>EUC-TW</code></dt>
876          <dd><code>EUC-TW</code> is not registered.  Unfortunately, there
877          is no registered name for that character encoding.  Use
878          Big5 encoding with character encoding name <code>Big5</code>
879          if it is enough to represent the document.</dd>
880        <dt><code>ISO-2022-JP-1</code></dt>
881          <dd><code>ISO-2022-JP-1</code> is not registered, nevertheless
882          this character encoding name is documented in
883          <a href="urn:ietf:rfc:2237"><abbr>RFC</abbr> 2237</a>.  Use
884          <code>ISO-2022-JP-2</code> instead, since that character encoding
885          is a superset of ISO-2022-JP-1.</dd>
886        <dt><code>ISO-2022-JP-3</code>, <code>ISO-2022-JP-3-plane1</code></dt>
887          <dd>These names are not registered and obsoleted in favor of
888          <code>ISO-2022-JP-2004</code> and
889          <code>ISO-2022-JP-2004-plane1</code>.</dd>
890        <dt><code>ISO-2022-JP-2003</code>,
891        <code>ISO-2022-JP-2003-plane1</code></dt>
892          <dd>These names are not registered and corrected to
893          <code>ISO-2022-JP-2004</code> and
894          <code>ISO-2022-JP-2004-plane1</code>.</dd>
895        <dt><code>ISO-2022-JP-2004</code>,
896        <code>ISO-2022-JP-2004-plane1</code></dt>
897          <dd>These names are not registered.  Unfortunately, there is
898          no registered name for these character encodings.</dd>
899        <dt><code>UTF-8N</code></dt>
900          <dd><code>UTF-8N</code> is not registered.  Character encoding
901          name <code>UTF-8</code> represents UTF-8 encoding with or
902          without <abbr>BOM</abbr>.</dd>
903        </dl>
904    
905        <p><strong>WARNING</strong>: This error might be raised for
906        a registered character encoding name, since the character encoding
907        name database of the conformance checker is not complete yet.</p>
908      </div>
909    
910    <div class="section attribute-value-warning warning" id="w:charset:private"><h3><code><var>$0</var></code> is a private
911      character encoding name.</h3>
912        <p>The specified character encoding name is a private name and
913        not registered to <abbr>IANA</abbr>.  Use of registered character
914        encoding name is a good practice to facilitate interoperability.</p>
915    
916        <dl class="switch">
917        <dt><code>x-euc-jp</code></dt>
918          <dd>Use <code>EUC-JP</code> for the Japanese <abbr>EUC</abbr>
919          character encoding.</dd>
920        <dt><code>x-sjis</code></dt>
921          <dd>Use <code>Shift_JIS</code> for standard Shift encoding scheme of
922          <abbr>JIS</abbr> coded character set, or <code>Windows-31J</code>
923          for Microsoft standard character set as implemented by
924          Microsoft Windows.</dd>
925        </dl>
926      </div>
927    
928    <div class="section attribute-value-error" id="m:charset:syntax-error"><h3>The specified value is syntactically not a
929      character encoding name.</h3>
930        <p>The attribute value must be a character encoding name.  However,
931        the specified value is not a character encoding name syntactically.
932        The document is non‐conforming.</p>
933        <p>Character encoding name is a string of <abbr>ASCII</abbr>
934        printable characters, up to 40 characters.</p>
935      </div>
936    
937  <div class="section attribute-value-error" id="enumerated:invalid"><h3>This attribute only allow a limited set of  <div class="section attribute-value-error" id="enumerated:invalid"><h3>This attribute only allow a limited set of
938    values and the specified value <code><var>{@}</var></code> is not one    values and the specified value <code><var>{@}</var></code> is not one
939    of them.</h3>    of them.</h3>
# Line 744  Web Document Conformance Checker (BETA)< Line 943  Web Document Conformance Checker (BETA)<
943    
944      <dl>      <dl>
945      <dt>HTML <code>meta</code> element, <code>http-equiv</code> attribute</dt>      <dt>HTML <code>meta</code> element, <code>http-equiv</code> attribute</dt>
946          <dd><p>Only <code>Default-Style</code> and <code>Refresh</code>          <dd><p>Only values <code>Default-Style</code> and <code>Refresh</code>
947          is allowed.</p>          are allowed.</p>
948          <p>Value <code>Content-Type</code> is obsolete; for charset          <p>Value <code>Content-Type</code> is obsolete; for charset
949          declaration, the <code>charset</code> attribute can be used as:          declaration, the <code>charset</code> attribute can be used as:
950          <pre class="html example">          <pre class="html example">
# Line 763  Web Document Conformance Checker (BETA)< Line 962  Web Document Conformance Checker (BETA)<
962      </dl>      </dl>
963    </div>    </div>
964    
965  <div class="section attribute-value-error" id="enumerated:invalid:http-equiv:content-type"><h3>Charset declaration syntax  <div class="section attribute-value-error" id="enumerated:invalid:http-equiv:content-type"><h3>Character encoding declaration syntax
966    <code>&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html; charset=<var>charset-name</var>&quot;&gt;</code>    <code class="html bad example">&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html; charset=<var>charset-name</var>&quot;&gt;</code>
967    is obsolete.</h3>    is obsolete.</h3>
968      <p>Old long charset declaration syntax      <p>Old long character encoding declaration syntax
969      <code>&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html; charset=<var>charset-name</var>&quot;&gt;</code>      <code class="html bad example">&lt;meta http-equiv=&quot;Content-Type&quot; content=&quot;text/html; charset=<var>charset-name</var>&quot;&gt;</code>
970      is in use.  The document is non‐conforming.</p>      is in use.  The document is non‐conforming.</p>
971    
972      <p>The new charset declaration syntax is:      <p>The new character encoding declaration syntax is:
973        <pre>        <pre class="html example">
974  <code>&lt;meta charset=&quot;<var>charset-name</var>&quot;&gt;</code></pre>  <code>&lt;meta charset=&quot;<var>charset-name</var>&quot;&gt;</code></pre>
975      </p>      </p>
976    </div>    </div>
# Line 813  Web Document Conformance Checker (BETA)< Line 1012  Web Document Conformance Checker (BETA)<
1012      </dl>      </dl>
1013    </div>    </div>
1014    
1015    <div class="section attribute-value-error" id="m:mismatched-charset-name"><h3>Character encoding name <code><var>$1</var></code>
1016      is different from document character encoding
1017      <code><var>$0</var></code>.</h3>
1018        <p>The specified character encoding name is different from
1019        the character encoding of the document.  The document
1020        is non‐conforming.</p>
1021      </div>
1022    
1023  <div class="section attribute-value-error" id="reserved-browsing-context-name"><h3>Browsing context name  <div class="section attribute-value-error" id="reserved-browsing-context-name"><h3>Browsing context name
1024    <code><var>{@}</var></code> is reserved.</h3>    <code><var>{@}</var></code> is reserved.</h3>
1025      <p>The specified browsing context name is reserved.      <p>The specified browsing context name is reserved.
# Line 869  Web Document Conformance Checker (BETA)< Line 1076  Web Document Conformance Checker (BETA)<
1076      The document is non-conforming.</p>      The document is non-conforming.</p>
1077    
1078      <p>For example, the table below is non-conforming:      <p>For example, the table below is non-conforming:
1079        <pre class="html non-conforming example">        <pre class="html bad example">
1080  <code>&lt;table&gt;  <code>&lt;table&gt;
1081  &lt;tbody&gt;  &lt;tbody&gt;
1082  &lt;tr&gt;&lt;td rowspan=2&gt;&lt;/td&gt;&lt;/tr&gt;  &lt;tr&gt;&lt;td rowspan=2&gt;&lt;/td&gt;&lt;/tr&gt;
# Line 976  Web Document Conformance Checker (BETA)< Line 1183  Web Document Conformance Checker (BETA)<
1183      <code>text/cache-manifest</code> must contain a cache manifest.</p>      <code>text/cache-manifest</code> must contain a cache manifest.</p>
1184    
1185      <p>A cache manifest must start with a line whose content is      <p>A cache manifest must start with a line whose content is
1186      <code>CACHE MANIFEST</code> (exactly one space character between      <code class="manifest example">CACHE MANIFEST</code>
1187        (exactly one space character between
1188      <code>CACHE</code> and <code>MANIFEST</code>).</p>      <code>CACHE</code> and <code>MANIFEST</code>).</p>
1189    </div>    </div>
1190  </section>  </section>
1191    
1192    <section id="information">
1193    <h2>Stability Information</h2>
1194    
1195    <div class="section level-i" id="i:status:cr:element"><h3>This element is in the
1196      <strong>call for implementation</strong> stage.</h3>
1197        <p>The element is in the call for implementation stage.</p>
1198        
1199        <p>Usually, using the element is safe.  However, it is a new feature
1200        so that it might not be implemented correctly.  If it is found that
1201        the feature is hard or impossible to implement, the feature
1202        might be revised, or in some case it might be dropped.</p>
1203    
1204        <p>Elements defined by Atom 1.0 (IETF Proposed Standard), and XBL 2.0
1205        (W3C Candidate Recommendation) belong to this class.</p>
1206      </div>
1207    
1208    <div class="section level-i" id="i:status:lc:element"><h3>This element is in the <strong>last
1209      call for comments</strong> stage.</h3>
1210        <p>The element is in the last call for comments stage.</p>
1211        
1212        <p>The element is relatively mature, though the standardization
1213        is not done yet.  It may be used for experiments.  Since it is a new
1214        feature, it might not be implemented correctly or at all.  If it is
1215        found that the feature is hard or impossible to implement, the feature
1216        might be revised or might be dropped.</p>
1217    
1218        <p>Elements defined by Web Forms 2.0 as well as some elements
1219        defined by HTML5 belong to this class.</p>
1220      </div>
1221    
1222    <div class="section level-i" id="i:status:wd:element"><h3>This element is documented in a <strong>working
1223      draft</strong>.</h3>
1224        <p>The element is documented in a working or editor's draft
1225        and not yet completed.</p>
1226        
1227        <p>The element should not be used for any practical purpose.
1228        The feature might be drastically changed later or might be
1229        entirely removed.</p>
1230    
1231        <p>Most of new elements defined by HTML5 belong to this class.</p>
1232      </div>
1233    
1234    <div class="section level-i" id="i:status:non-standard:element"><h3>This element is <strong>not part of any
1235      standard</strong> the conformance checker knows.</h3>
1236        <p>The element is not part of any standard or draft the conformance
1237        checker is aware of.</p>
1238        
1239        <p>The element should not be used for any practical purpose unless
1240        there is really a standard that defines the element.</p>
1241      </div>
1242    </section>
1243    
1244  <section id="unsupported-messages">  <section id="unsupported-messages">
1245  <h2><i>Unsupported</i> Messages</h2>  <h2><i>Unsupported</i> Messages</h2>
1246    
# Line 1072  to solve a problem in a confusing or pos Line 1332  to solve a problem in a confusing or pos
1332  It does not affect to the conformance of the document, and  It does not affect to the conformance of the document, and
1333  may sometimes be inappropriate.</td>  may sometimes be inappropriate.</td>
1334  </tr>  </tr>
1335  <tr class="level-unsupported" id="level-unsupported">  <tr class="level-i" id="level-i">
1336    <th scope="row">Information</th>
1337    <td>Conforming.</td>
1338    <td>An informational message just provides an additional information
1339    on the feature used in the document or the status of the retrieval
1340    or so on.
1341    It does not affect to the conformance of the document.</td>
1342    </tr>
1343    <tr class="level-u" id="level-u">
1344  <th scope="row">Not supported</th>  <th scope="row">Not supported</th>
1345  <td><em>Unknown</em>.</td>  <td><em>Unknown</em>.</td>
1346  <td>Some feature that is not supported by the conformance checker  <td>Some feature that is not supported by the conformance checker
# Line 1085  is used in the document.</td> Line 1353  is used in the document.</td>
1353  <section id="license">  <section id="license">
1354  <h2>License of This Document</h2>  <h2>License of This Document</h2>
1355    
1356  <p>Copyright <time>2007</time>  <p>Copyright <time>2007</time>‐<time>2008</time>
1357  <a href="http://suika.fam.cx/~wakaba/who?" rel="author" xml:lang="ja">Wakaba</a>  <a href="http://suika.fam.cx/~wakaba/who?" rel="author" xml:lang="ja">Wakaba</a>
1358  <code class="mail">&lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</code>.</p>  <code class="mail">&lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</code>.</p>
1359    
Legend:
Removed from v.1.13  
changed lines
  Added in v.1.20
[email protected]
 ViewVC Help
Powered by ViewVC 1.1.24