32 |
<section id="character-encoding-layer"> |
<section id="character-encoding-layer"> |
33 |
<h2>Character Encoding Layer Errors</h2> |
<h2>Character Encoding Layer Errors</h2> |
34 |
|
|
35 |
<div class="section" id="illegal-octets-error"><h3>An illegal octet in the input stream.</h3></div> |
<div class="section" id="fallback-char-error"><h3>Octet sequence <code><var>{octets}</var></code> |
36 |
|
is not an allowed representation of the character |
37 |
|
<code><var>{char}</var></code> — character reference |
38 |
|
<code><var>{char:hexref}</var></code> should be used instead.</h3></div> |
39 |
|
|
40 |
|
<div class="section" id="fallback-unassigned-error"><h3>No character is assigned to octet sequence |
41 |
|
<code><var>{octets}</var></code>.</h3></div> |
42 |
|
|
43 |
|
<div class="section" id="illegal-octets-error"><h3>Octet sequence <code><var>{octets}</var></code> |
44 |
|
is illegal.</h3></div> |
45 |
|
|
46 |
|
<div class="section" id="invalid-state-error"><h3>The input stream is broken.</h3> |
47 |
|
<p>The input stream is encoded in <code>ISO-2022-JP</code> |
48 |
|
or its variant but is partially broken.</p> |
49 |
|
|
50 |
|
<p>Note that an <code>ISO-2022-JP</code> stream must end in the ASCII |
51 |
|
state.</p> |
52 |
|
</div> |
53 |
|
|
54 |
|
<div class="section" id="unassigned-code-point-error"><h3>No character is assigned to octet sequence |
55 |
|
<code><var>{octets}</var></code>.</h3></div> |
56 |
</section> |
</section> |
57 |
|
|
58 |
<section id="html5-character-encoding"> |
<section id="html5-character-encoding"> |
141 |
for the character encoding of this document is found in the transfer |
for the character encoding of this document is found in the transfer |
142 |
procotol headers.</h3></div> |
procotol headers.</h3></div> |
143 |
|
|
144 |
<div class="section" id="chardecode:fallback"><h3>Since no decoder for the document character |
<div class="section" id="chardecode:fallback"><h3>Results might be <em>wrong</em>, since the |
145 |
encoding is found, decoder for the character encoding |
conformance checker cannot find an appropriate decoder for the character |
146 |
<code><var>{text}</var></code> is used. Checking results might be |
encoding used for the document.</h3> |
147 |
<em>wrong</em>.</h3></div> |
<p>The conformance checker cannot find an appropriate decoder for |
148 |
|
the character encoding used to encode characters in the document.</p> |
149 |
|
|
150 |
|
<p>This error is raised if:</p> |
151 |
|
<ul> |
152 |
|
<li>the conformance checker cannot find any decoder for the character |
153 |
|
encoding in use, but it knows that the encoding is similar to another |
154 |
|
character encoding, such that it uses the decoder for that character |
155 |
|
encoding, and therefore some octets might be interpreted incorrectly, |
156 |
|
or,</li> |
157 |
|
<li>the conformance checker find a decoder for the character encoding |
158 |
|
in use, but it does not know whether the decoder is conforming to the |
159 |
|
relevant specification or not, and therefore some octets might be |
160 |
|
interpreted incorrectly.</li> |
161 |
|
</ul> |
162 |
|
|
163 |
|
<p>In either case, the result shown by the conformance checker might |
164 |
|
contain wrong errors caused by errorneous decoder or might not contain |
165 |
|
errors that should be raised if an appropriate decoder is used.</p> |
166 |
|
|
167 |
|
<!-- TODO: add advise that either install relevant modules or |
168 |
|
join the developmenet of the modules... --> |
169 |
|
</div> |
170 |
|
|
171 |
<div class="section" id="chardecode:no-error"><h3>Conformance error checking for the character |
<div class="section" id="chardecode:no-error"><h3>Conformance error checking for the character |
172 |
encoding <code><var>{text}</var></code> is not supported.</h3></div> |
encoding <code><var>{text}</var></code> is not supported.</h3></div> |
905 |
</dl> |
</dl> |
906 |
</div> |
</div> |
907 |
|
|
908 |
|
<div class="section" id="XSLT-compat"><h3>The <code>DOCTYPE</code> legacy string is |
909 |
|
used.</h3> |
910 |
|
<p>The <code>DOCTYPE</code> with the <code>DOCTYPE</code> legacy |
911 |
|
string, i.e. |
912 |
|
<code class="html bad example"><!DOCTYPE HTML PUBLIC "XSLT-compat"></code> |
913 |
|
is used.</p> |
914 |
|
|
915 |
|
<p>The <code>DOCTYPE</code> legacy string should not be used for documents |
916 |
|
generated from XSLT transformation process. It is allowed only to enable |
917 |
|
to use XSLT style sheets with the HTML output mode, which does not |
918 |
|
support generation of the <code>DOCTYPE</code> with no <code>PUBLIC</code> |
919 |
|
identifier. For other purposes, the <code>DOCTYPE</code> legacy |
920 |
|
string, i.e. <code class="html bad example">PUBLIC "XSLT-compat"</code>, |
921 |
|
is useless and should not be used.</p> |
922 |
|
</div> |
923 |
|
|
924 |
</section> |
</section> |
925 |
|
|
926 |
<section id="element-content-model-errors"> |
<section id="element-content-model-errors"> |