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