| 56 |
<section id="character-encoding-layer"> |
<section id="character-encoding-layer"> |
| 57 |
<h2>Character Encoding Layer Errors</h2> |
<h2>Character Encoding Layer Errors</h2> |
| 58 |
|
|
| 59 |
<d:item name="illegal-octets-error" class="error-category-charset" level="m"> |
<d:item name="fallback-char-error" |
| 60 |
<d:message xml:lang="en">An illegal octet in the input stream.</d:message> |
modules="Charset::DecodeHandle"> |
| 61 |
|
<d:message xml:lang="en">Octet sequence <code><var>{octets}</var></code> |
| 62 |
|
is not an allowed representation of the character |
| 63 |
|
<code><var>{char}</var></code> — character reference |
| 64 |
|
<code><var>{char:hexref}</var></code> should be used instead.</d:message> |
| 65 |
|
<!-- HTML5 parse error --> |
| 66 |
|
</d:item> |
| 67 |
|
|
| 68 |
|
<d:item name="fallback-unassigned-error" |
| 69 |
|
modules="Charset::DecodeHandle"> |
| 70 |
|
<d:message xml:lang="en">No character is assigned to octet sequence |
| 71 |
|
<code><var>{octets}</var></code>.</d:message> |
| 72 |
|
<!-- HTML5 parse error --> |
| 73 |
|
</d:item> |
| 74 |
|
|
| 75 |
|
<d:item name="illegal-octets-error" |
| 76 |
|
modules="Charset::DecodeHandle"> |
| 77 |
|
<d:message xml:lang="en">Octet sequence <code><var>{octets}</var></code> |
| 78 |
|
is illegal.</d:message> |
| 79 |
|
</d:item> |
| 80 |
|
|
| 81 |
|
<d:item name="invalid-state-error" |
| 82 |
|
modules="Charset::DecodeHandle::ISO2022JP"> |
| 83 |
|
<!-- TODO: more user-friendly error message is desired... --> |
| 84 |
|
<d:message xml:lang="en">The input stream is broken.</d:message> |
| 85 |
|
<d:desc xml:lang="en"> |
| 86 |
|
<p>The input stream is encoded in <code>ISO-2022-JP</code> |
| 87 |
|
or its variant but is partially broken.</p> |
| 88 |
|
|
| 89 |
|
<p>Note that an <code>ISO-2022-JP</code> stream must end in the ASCII |
| 90 |
|
state.</p> |
| 91 |
|
</d:desc> |
| 92 |
|
</d:item> |
| 93 |
|
|
| 94 |
|
<d:item name="unassigned-code-point-error" |
| 95 |
|
modules="Charset::DecodeHandle"> |
| 96 |
|
<d:message xml:lang="en">No character is assigned to octet sequence |
| 97 |
|
<code><var>{octets}</var></code>.</d:message> |
| 98 |
</d:item> |
</d:item> |
| 99 |
</section> |
</section> |
| 100 |
|
|
| 214 |
|
|
| 215 |
<d:item name="chardecode:fallback" |
<d:item name="chardecode:fallback" |
| 216 |
modules="HTML::Parser"> |
modules="HTML::Parser"> |
| 217 |
<d:message xml:lang="en">Since no decoder for the document character |
<d:message xml:lang="en">Results might be <em>wrong</em>, since the |
| 218 |
encoding is found, decoder for the character encoding |
conformance checker cannot find an appropriate decoder for the character |
| 219 |
<code><var>{text}</var></code> is used. Checking results might be |
encoding used for the document.</d:message> |
| 220 |
<em>wrong</em>.</d:message> |
<d:desc xml:lang="en"> |
| 221 |
|
<p>The conformance checker cannot find an appropriate decoder for |
| 222 |
|
the character encoding used to encode characters in the document.</p> |
| 223 |
|
|
| 224 |
|
<p>This error is raised if:</p> |
| 225 |
|
<ul> |
| 226 |
|
<li>the conformance checker cannot find any decoder for the character |
| 227 |
|
encoding in use, but it knows that the encoding is similar to another |
| 228 |
|
character encoding, such that it uses the decoder for that character |
| 229 |
|
encoding, and therefore some octets might be interpreted incorrectly, |
| 230 |
|
or,</li> |
| 231 |
|
<li>the conformance checker find a decoder for the character encoding |
| 232 |
|
in use, but it does not know whether the decoder is conforming to the |
| 233 |
|
relevant specification or not, and therefore some octets might be |
| 234 |
|
interpreted incorrectly.</li> |
| 235 |
|
</ul> |
| 236 |
|
|
| 237 |
|
<p>In either case, the result shown by the conformance checker might |
| 238 |
|
contain wrong errors caused by errorneous decoder or might not contain |
| 239 |
|
errors that should be raised if an appropriate decoder is used.</p> |
| 240 |
|
|
| 241 |
|
<!-- TODO: add advise that either install relevant modules or |
| 242 |
|
join the developmenet of the modules... --> |
| 243 |
|
</d:desc> |
| 244 |
</d:item> |
</d:item> |
| 245 |
|
|
| 246 |
<d:item name="chardecode:no error" |
<d:item name="chardecode:no error" |
| 287 |
</ul> |
</ul> |
| 288 |
</d:desc> |
</d:desc> |
| 289 |
</d:item> |
</d:item> |
| 290 |
|
</section> |
| 291 |
|
|
| 292 |
|
<section id="character-set-layer"> |
| 293 |
|
<h2>Coded Character Set Layer Errors</h2> |
| 294 |
|
|
| 295 |
<d:item name="NULL" |
<d:item name="NULL" |
| 296 |
modules="HTML::Parser"> |
modules="HTML::Parser"> |
| 297 |
|
<!-- HTML5 Parse Error --> |
| 298 |
<d:message xml:lang="en">The <code class="charname">NULL</code> character |
<d:message xml:lang="en">The <code class="charname">NULL</code> character |
| 299 |
is not allowed.</d:message> |
is not allowed.</d:message> |
| 300 |
</d:item> |
</d:item> |
| 301 |
|
|
| 302 |
<d:item name="control char" |
<d:item name="control char" |
| 303 |
modules="HTML::Parser"> |
modules="Charset::UnicodeChecker"> |
| 304 |
|
<!-- HTML5 Parse Error --> |
| 305 |
<d:message xml:lang="en">Code point <code><var>{text}</var></code> is |
<d:message xml:lang="en">Code point <code><var>{text}</var></code> is |
| 306 |
not allowed.</d:message> |
not allowed.</d:message> |
| 307 |
</d:item> |
</d:item> |
| 308 |
|
|
| 309 |
|
<d:item name="nonchar" |
| 310 |
|
modules="Charset::UnicodeChecker"> |
| 311 |
|
<d:message xml:lang="en">Noncharacter <code><var>{text}</var></code> |
| 312 |
|
is found in the input stream.</d:message> |
| 313 |
|
<d:desc xml:lang="en"> |
| 314 |
|
<p>Noncharacter code points are used in the input stream.</p> |
| 315 |
|
|
| 316 |
|
<p>Noncharacter code points are reserved for internal processings. |
| 317 |
|
Their use for information interchanges are forbidden.</p> |
| 318 |
|
|
| 319 |
|
<p>In addition, they are not allowed in HTML document.</p> |
| 320 |
|
<!-- "permanently undefined Unicode characters" in HTML5. --> |
| 321 |
|
</d:desc> |
| 322 |
|
</d:item> |
| 323 |
|
|
| 324 |
|
<d:item name="non unicode" |
| 325 |
|
modules="Charset::UnicodeChecker"> |
| 326 |
|
<d:message xml:lang="en">Character <code><var>{text}</var></code> is not |
| 327 |
|
a Unicode character.</d:message> |
| 328 |
|
</d:item> |
| 329 |
|
|
| 330 |
|
<d:item name="unicode deprecated" |
| 331 |
|
modules="Charset::UnicodeChecker"> |
| 332 |
|
<d:message xml:lang="en">Use of character <code><var>{text}</var></code> |
| 333 |
|
is deprecated.</d:message> |
| 334 |
|
</d:item> |
| 335 |
|
|
| 336 |
|
<d:item name="unicode discouraged" |
| 337 |
|
modules="Charset::UnicodeChecker"> |
| 338 |
|
<d:message xml:lang="en">Use of character <code><var>{text}</var></code> |
| 339 |
|
is discouraged.</d:message> |
| 340 |
|
</d:item> |
| 341 |
|
|
| 342 |
|
<d:item name="unicode not preferred" |
| 343 |
|
modules="Charset::UnicodeChecker"> |
| 344 |
|
<d:message xml:lang="en">Code point <code><var>{text}</var></code> |
| 345 |
|
is not the preferred representation of that character.</d:message> |
| 346 |
|
</d:item> |
| 347 |
|
|
| 348 |
|
<d:item name="unicode should" |
| 349 |
|
modules="Charset::UnicodeChecker"> |
| 350 |
|
<d:message xml:lang="en">Character <code><var>{text}</var></code> |
| 351 |
|
should not be used in many cases.</d:message> |
| 352 |
|
</d:item> |
| 353 |
|
|
| 354 |
</section> |
</section> |
| 355 |
|
|
| 356 |
<section id="html5-tokenize-error"> |
<section id="html5-tokenize-error"> |
| 1312 |
</d:desc> |
</d:desc> |
| 1313 |
</d:item> |
</d:item> |
| 1314 |
|
|
| 1315 |
|
<d:item name="XSLT-compat" |
| 1316 |
|
modules="HTML::Parser"> |
| 1317 |
|
<d:message xml:lang="en">The <code>DOCTYPE</code> legacy string is |
| 1318 |
|
used.</d:message> |
| 1319 |
|
<d:message xml:lang="ja"><code>DOCTYPE</code> |
| 1320 |
|
遺物文字列が使われています。</d:message> |
| 1321 |
|
<d:desc xml:lang="en"> |
| 1322 |
|
<p>The <code>DOCTYPE</code> with the <code>DOCTYPE</code> legacy |
| 1323 |
|
string, i.e. |
| 1324 |
|
<code class="html bad example"><!DOCTYPE HTML PUBLIC "XSLT-compat"></code> |
| 1325 |
|
is used.</p> |
| 1326 |
|
|
| 1327 |
|
<p>The <code>DOCTYPE</code> legacy string should not be used for documents |
| 1328 |
|
<em>not</em> generated from XSLT transformation process. It is allowed |
| 1329 |
|
only to enable to use XSLT style sheets with the HTML output mode, which |
| 1330 |
|
does not support generation of the <code>DOCTYPE</code> with no |
| 1331 |
|
<code>PUBLIC</code> |
| 1332 |
|
identifier. For other purposes, the <code>DOCTYPE</code> legacy |
| 1333 |
|
string, i.e. <code class="html bad example">PUBLIC "XSLT-compat"</code>, |
| 1334 |
|
is useless and should not be used.</p> |
| 1335 |
|
</d:desc> |
| 1336 |
|
</d:item> |
| 1337 |
|
|
| 1338 |
</section> |
</section> |
| 1339 |
|
|
| 1340 |
<section id="element-content-model-errors"> |
<section id="element-content-model-errors"> |