| 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" |
| 1261 |
</d:desc> |
</d:desc> |
| 1262 |
</d:item> |
</d:item> |
| 1263 |
|
|
| 1264 |
|
<d:item name="XSLT-compat" |
| 1265 |
|
modules="HTML::Parser"> |
| 1266 |
|
<d:message xml:lang="en">The <code>DOCTYPE</code> legacy string is |
| 1267 |
|
used.</d:message> |
| 1268 |
|
<d:message xml:lang="ja"><code>DOCTYPE</code> |
| 1269 |
|
遺物文字列が使われています。</d:message> |
| 1270 |
|
<d:desc xml:lang="en"> |
| 1271 |
|
<p>The <code>DOCTYPE</code> with the <code>DOCTYPE</code> legacy |
| 1272 |
|
string, i.e. |
| 1273 |
|
<code class="html bad example"><!DOCTYPE HTML PUBLIC "XSLT-compat"></code> |
| 1274 |
|
is used.</p> |
| 1275 |
|
|
| 1276 |
|
<p>The <code>DOCTYPE</code> legacy string should not be used for documents |
| 1277 |
|
generated from XSLT transformation process. It is allowed only to enable |
| 1278 |
|
to use XSLT style sheets with the HTML output mode, which does not |
| 1279 |
|
support generation of the <code>DOCTYPE</code> with no <code>PUBLIC</code> |
| 1280 |
|
identifier. For other purposes, the <code>DOCTYPE</code> legacy |
| 1281 |
|
string, i.e. <code class="html bad example">PUBLIC "XSLT-compat"</code>, |
| 1282 |
|
is useless and should not be used.</p> |
| 1283 |
|
</d:desc> |
| 1284 |
|
</d:item> |
| 1285 |
|
|
| 1286 |
</section> |
</section> |
| 1287 |
|
|
| 1288 |
<section id="element-content-model-errors"> |
<section id="element-content-model-errors"> |
Parent Directory
| 
Revision Log
| 
Patch