8 |
<body> |
<body> |
9 |
<h1>Description of Errors</h1> |
<h1>Description of Errors</h1> |
10 |
|
|
11 |
|
<section id="html5-character-encoding"> |
12 |
|
<h2>HTML5 Character Encoding Errors</h2> |
13 |
|
|
14 |
|
<div class="section format-charset must" id="m:character-encoding"><h3>Character encoding <code><var>$0</var></code> |
15 |
|
is not allowed for <abbr>HTML</abbr> document.</h3> |
16 |
|
<p>The character encoding used for the document is not allowed |
17 |
|
for <abbr>HTML</abbr> document. The document is non‐conforming.</p> |
18 |
|
</div> |
19 |
|
|
20 |
|
<div class="section format-charset should" id="s:character-encoding"><h3>Character encoding <code><var>$0</var></code> |
21 |
|
should not be used for <abbr>HTML</abbr> document.</h3> |
22 |
|
<p>The character encoding used for the document is not recommended |
23 |
|
for <abbr>HTML</abbr> document. The document is non‐conforming |
24 |
|
unless there is any good reason to use that encoding.</p> |
25 |
|
</div> |
26 |
|
|
27 |
|
<div class="section format-charset warning" id="w:character-encoding"><h3>Use of UTF-8 is encouraged.</h3> |
28 |
|
<p>Use of UTF-8 as the character encoding of the document is encouraged, |
29 |
|
though the use of another character encoding is conforming.</p> |
30 |
|
</div> |
31 |
|
|
32 |
|
<div class="section format-charset error" id="m:no-character-encoding-declaration"><h3>There is no character encoding |
33 |
|
declaration.</h3> |
34 |
|
<p>The document does not contain a character encoding |
35 |
|
declaration. Unless the character encoding is explicitly |
36 |
|
specified in upper‐level protocol, e.g. in <abbr>HTTP</abbr>, |
37 |
|
or is implied by <abbr>BOM</abbr>, there must be a character |
38 |
|
encoding declaration. The document is non‐conforming.</p> |
39 |
|
|
40 |
|
<p>The long character encoding declaration syntax |
41 |
|
<code class="html bad example"><meta http-equiv="Content-Type" content="text/html; charset=<var>charset-name</var>"></code> |
42 |
|
is obsolete. The new syntax is:</p> |
43 |
|
<pre class="html example"> |
44 |
|
<code><meta charset="<var>charset-name</var>"></code></pre> |
45 |
|
|
46 |
|
<p>Note that the <code>encoding</code> declaration in <abbr>XML</abbr> |
47 |
|
declaration has no effect for <abbr>HTML</abbr> document.</p> |
48 |
|
</div> |
49 |
|
|
50 |
|
<div class="section format-charset error" id="m:non-ascii-superset"><h3>No character encoding metadata is found |
51 |
|
in upper‐level protocol nor is there <abbr>BOM</abbr>, while |
52 |
|
character encoding <code><var>$0</var></code> |
53 |
|
is not a superset of <abbr>ASCII</abbr>.</h3> |
54 |
|
<p>The document is not labeled with character encoding name |
55 |
|
in upper‐level protocol, e.g. in <abbr>HTTP</abbr>, and |
56 |
|
the document is not begin with <abbr>BOM</abbr>. In addition, |
57 |
|
the character encoding of the document is not a superset of |
58 |
|
<abbr>ASCII</abbr>. The document is non‐conforming.</p> |
59 |
|
|
60 |
|
<p>Unless there is a <abbr>BOM</abbr>, the character encoding |
61 |
|
for the document must be specified in e.g. <abbr>HTTP</abbr>‐level, |
62 |
|
as:</p> |
63 |
|
<pre class="http example"> |
64 |
|
<code>Content-Type: text/html; charset=<var>charset-name</var></code></pre> |
65 |
|
|
66 |
|
<p>Existence of <abbr>HTML</abbr> character encoding declaration, i.e. |
67 |
|
<code class="html example"><meta charset="<var>charset-name</var>"></code>, |
68 |
|
does not allow to omit <code>charset</code> parameter |
69 |
|
for <abbr>HTML</abbr> document encoded in non‐<abbr>ASCII</abbr> |
70 |
|
compatible encoding.</p> |
71 |
|
|
72 |
|
<p>Character encodings <code>Shift_JIS</code>, <code>Windows-31J</code>, |
73 |
|
and <code>ISO-2022-JP</code> are <em>not</em> a superset of |
74 |
|
<abbr>ASCII</abbr> for the purpose of <abbr>HTML</abbr> conformance.</p> |
75 |
|
</div> |
76 |
|
|
77 |
|
<div class="section format-charset warning" id="w:charset-label-detected"><h3>While parsing the document as |
78 |
|
<code><var>$0</var></code>, a character encoding declaration specifying |
79 |
|
character encoding as <code><var>$1</var></code> is found. The document |
80 |
|
is reparsed.</h3> |
81 |
|
<p>While parsing a document in a character encoding, |
82 |
|
a character encoding declaration which declares the character |
83 |
|
encoding of the document as another character encoding is found. |
84 |
|
The occurence of this warning itself does not make the document |
85 |
|
non‐conforming. However, the failure of the first attempt to |
86 |
|
to detect the character encoding might be the result of non‐conformance |
87 |
|
of the document.</p> |
88 |
|
|
89 |
|
<p>The document will be reparsed from the beginning. Some error |
90 |
|
or warning might be reported again.</p> |
91 |
|
|
92 |
|
<p>These are suggestions to avoid this warning:</p> |
93 |
|
<ul> |
94 |
|
<li>Specify <code>charset</code> parameter in the <code>Content-Type</code> |
95 |
|
field in the <abbr>HTTP</abbr> header, as: |
96 |
|
<pre class="HTTP example"> |
97 |
|
<code>Content-Type: text/html; charset="<var>charset-name</var>"</code></pre></li> |
98 |
|
<li>Put the character encoding declaration |
99 |
|
(<code class="html example"><meta charset="<var>charset-name</var>"></code>) |
100 |
|
just after <code class="html example"><head></code> start tag.</li> |
101 |
|
<li>Use <code>UTF-8</code>.</li> |
102 |
|
</ul> |
103 |
|
</div> |
104 |
|
</section> |
105 |
|
|
106 |
<section id="html5-tokenize-error"> |
<section id="html5-tokenize-error"> |
107 |
<h2>HTML5 Parse Errors in Tokenization Stage</h2> |
<h2>HTML5 Parse Errors in Tokenization Stage</h2> |
108 |
|
|
878 |
</dl> |
</dl> |
879 |
</div> |
</div> |
880 |
|
|
881 |
<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 |
882 |
<code class="html bad example"><meta http-equiv="Content-Type" content="text/html; charset=<var>charset-name</var>"></code> |
<code class="html bad example"><meta http-equiv="Content-Type" content="text/html; charset=<var>charset-name</var>"></code> |
883 |
is obsolete.</h3> |
is obsolete.</h3> |
884 |
<p>Old long charset declaration syntax |
<p>Old long character encoding declaration syntax |
885 |
<code class="html bad example"><meta http-equiv="Content-Type" content="text/html; charset=<var>charset-name</var>"></code> |
<code class="html bad example"><meta http-equiv="Content-Type" content="text/html; charset=<var>charset-name</var>"></code> |
886 |
is in use. The document is non‐conforming.</p> |
is in use. The document is non‐conforming.</p> |
887 |
|
|
888 |
<p>The new charset declaration syntax is: |
<p>The new character encoding declaration syntax is: |
889 |
<pre class="html example"> |
<pre class="html example"> |
890 |
<code><meta charset="<var>charset-name</var>"></code></pre> |
<code><meta charset="<var>charset-name</var>"></code></pre> |
891 |
</p> |
</p> |