/[pub]/test/html-webhacc/error-description-source.xml
Suika

Diff of /test/html-webhacc/error-description-source.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.41 by wakaba, Sat Aug 30 16:10:07 2008 UTC revision 1.45 by wakaba, Sun Sep 14 03:09:23 2008 UTC
# Line 56  Line 56 
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> &#x2014; 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    
# Line 177  Line 214 
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"
# Line 227  Line 287 
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="HTML::Parser">
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="unicode deprecated"
325        modules="Charset::UnicodeChecker">
326      <d:message xml:lang="en">Use of character <code><var>{text}</var></code>
327      is deprecated.</d:message>
328    </d:item>
329    
330    <d:item name="unicode discouraged"
331        modules="Charset::UnicodeChecker">
332      <d:message xml:lang="en">Use of character <code><var>{text}</var></code>
333      is discouraged.</d:message>
334    </d:item>
335    
336    <d:item name="unicode not preferred"
337        modules="Charset::UnicodeChecker">
338      <d:message xml:lang="en">Code point <code><var>{text}</var></code>
339      is not the preferred representation of that character.</d:message>
340    </d:item>
341    
342    <d:item name="unicode should"
343        modules="Charset::UnicodeChecker">
344      <d:message xml:lang="en">Character <code><var>{text}</var></code>
345      should not be used in many cases.</d:message>
346    </d:item>
347    
348  </section>  </section>
349    
350  <section id="html5-tokenize-error">  <section id="html5-tokenize-error">
# Line 760  p { Line 865  p {
865  <section id="html5-parse-errors">  <section id="html5-parse-errors">
866  <h2>HTML5 Parse Errors in Tree Construction Stage</h2>  <h2>HTML5 Parse Errors in Tree Construction Stage</h2>
867    
868    <d:item name="after after frameset"
869        modules="HTML::Parser">
870      <d:message xml:lang="en">There is a start tag
871      <code>&lt;<var>{text}</var>></code> is after the <code>html</code> element
872      is closed.</d:message>
873      <d:message xml:lang="ja"><code>html</code> 要素が閉じられた後に開始タグ
874      <code>&lt;<var>{text}</var>></code> があります。</d:message>
875    </d:item>
876    
877    <d:item name="after after frameset:/"
878        modules="HTML::Parser">
879      <d:message xml:lang="en">There is an end tag
880      <code>&lt;/<var>{text}</var>></code> is after the <code>html</code> element
881      is closed.</d:message>
882      <d:message xml:lang="ja"><code>html</code> 要素が閉じられた後に終了タグ
883      <code>&lt;/<var>{text}</var>></code> があります。</d:message>
884    </d:item>
885    
886  <d:item name="after body"  <d:item name="after body"
887      modules="HTML::Parser">      modules="HTML::Parser">
888    <d:message xml:lang="en">Start tag <code>&lt;<var>{text}</var>></code> is    <d:message xml:lang="en">Start tag <code>&lt;<var>{text}</var>></code> is
# Line 1183  p { Line 1306  p {
1306    </d:desc>    </d:desc>
1307  </d:item>  </d:item>
1308    
1309    <d:item name="XSLT-compat"
1310        modules="HTML::Parser">
1311      <d:message xml:lang="en">The <code>DOCTYPE</code> legacy string is
1312      used.</d:message>
1313      <d:message xml:lang="ja"><code>DOCTYPE</code>
1314      遺物文字列が使われています。</d:message>
1315      <d:desc xml:lang="en">
1316        <p>The <code>DOCTYPE</code> with the <code>DOCTYPE</code> legacy
1317        string, i.e.
1318        <code class="html bad example">&lt;!DOCTYPE HTML PUBLIC "XSLT-compat"></code>
1319        is used.</p>
1320    
1321        <p>The <code>DOCTYPE</code> legacy string should not be used for documents
1322        <em>not</em> generated from XSLT transformation process.  It is allowed
1323        only to enable to use XSLT style sheets with the HTML output mode, which
1324        does not support generation of the <code>DOCTYPE</code> with no
1325        <code>PUBLIC</code>
1326        identifier.  For other purposes, the <code>DOCTYPE</code> legacy
1327        string, i.e. <code class="html bad example">PUBLIC "XSLT-compat"</code>,
1328        is useless and should not be used.</p>
1329      </d:desc>
1330    </d:item>
1331    
1332  </section>  </section>
1333    
1334  <section id="element-content-model-errors">  <section id="element-content-model-errors">
# Line 1452  p { Line 1598  p {
1598    
1599  <d:item name="element not allowed:meta charset"  <d:item name="element not allowed:meta charset"
1600      modules="ContentChecker::HTML">      modules="ContentChecker::HTML">
1601    <d:message xml:lang="en">The character encoding declaration must be the    <d:message xml:lang="en">The character encoding declaration is not the
1602    first element in the <code>head</code> element.</d:message>    first child element in the <code>head</code> element.</d:message>
1603      <d:message xml:lang="ja">文字符号化宣言が <code>head</code>
1604      要素の最初の子要素ではありません。</d:message>
1605      <d:desc xml:lang="en">
1606        <p>The character encoding declaration
1607        (<code class="html example">&lt;meta charset="<var>...</var>"></code> or
1608        <code class="html example">&lt;meta http-equiv=Content-Type content="text/html; charset=<var>...</var>"></code>
1609        must be the first child element in the <code>head</code> element.</p>
1610    
1611        <p>The character encoding declaration have to occur near the beginning
1612        of the document to ensure that Web browsers can be determine the
1613        character encoding of the document.</p>
1614    
1615        <p>The <code>title</code> element and other metadata elements must
1616        appear after any character encoding declaration is processed.</p>
1617      </d:desc>
1618  </d:item>  </d:item>
1619    
1620  <d:item name="element not allowed:metadata"  <d:item name="element not allowed:metadata"
# Line 1537  p { Line 1698  p {
1698  <d:item name="element not defined"  <d:item name="element not defined"
1699      modules="ContentChecker">      modules="ContentChecker">
1700    <d:message xml:lang="en">This element is not defined.</d:message>    <d:message xml:lang="en">This element is not defined.</d:message>
1701      <d:message xml:lang="ja">この要素は定義されていません。</d:message>
1702      <d:desc xml:lang="en">
1703        <p>The element is not one of elements allowed
1704        in the latest version of relevant specifications.</p>
1705    
1706        <p>The element cannot be used.</p>
1707    
1708        <dl class="switch">
1709        <dt><code>event-source</code> element</dt>
1710            <dd>The element was renamed as <em><code>eventsource</code>
1711            element</em> (no hyphen).</dd>
1712        <dt><code>m</code> element</dt>
1713            <dd>The element was renamed as <em><code>mark</code>
1714            element</em>.</dd>
1715        </dl>
1716      </d:desc>
1717  </d:item>  </d:item>
1718    
1719  <d:item name="no significant content"  <d:item name="no significant content"
# Line 1661  p { Line 1838  p {
1838  <d:item name="attribute not defined"  <d:item name="attribute not defined"
1839      modules="ContentChecker">      modules="ContentChecker">
1840    <d:message xml:lang="en">This attribute is not defined.</d:message>    <d:message xml:lang="en">This attribute is not defined.</d:message>
1841      <d:message xml:lang="ja">この属性は定義されていません。</d:message>
1842    <d:desc xml:lang="en">    <d:desc xml:lang="en">
1843      <p>The attribute is not one of attributes allowed for the element      <p>The attribute is not one of attributes allowed for the element
1844      in the latest version of relevant specifications.</p>      in the latest version of relevant specifications.</p>
1845    
1846      <p>The attribute cannot be used.</p>      <p>The attribute cannot be used.</p>
1847    
1848      <dl>      <dl class="switch">
1849        <dt><code>align</code> attribute (various HTML elements)</dt>
1850        <dt><code>border</code> attribute (various HTML elements)</dt>
1851          <dd>These attributes are no longer part of HTML.  You can use CSS
1852          properties to control the presentation of the element.</dd>
1853      <dt><code>autosubmit</code> attribute (<code>menu</code> element)</dt>      <dt><code>autosubmit</code> attribute (<code>menu</code> element)</dt>
1854        <dd>The attribute was part of HTML5 draft but then dropped.        <dd>The attribute was part of HTML5 draft but then dropped.
1855        Similar functionality can be implemented by scripts.</dd>        Similar functionality can be implemented by scripts.</dd>
1856        <dt><code>language</code> attribute (<code>script</code> element)</dt>
1857          <dd>The attribute is no longer the standard way to specify the
1858          scripting language.  If you are using JavaScript, then no explicit
1859          specification of the scripting language is necessary, so you can
1860          write the element like:
1861            <p><code class="html example code">&lt;script><br/><!--
1862            --> /* JavaScript code */<br/><!--
1863            -->&lt;/script></code></p>
1864          If you are using different scripting language from JavaScript, or
1865          you want to declare the scripting language explicitly, you should
1866          use the <code>type</code> attribute, as follows:
1867            <dl class="switch">
1868            <dt>JavaScript</dt>
1869              <dd>Use
1870              <code class="html example">&lt;script type="text/javascript"></code>.</dd>
1871            <dt>VBScript</dt>
1872              <dd>Use
1873              <code class="html example">&lt;script type="text/vbscript"></code>.</dd>
1874            </dl>
1875          </dd>
1876      </dl>      </dl>
1877    </d:desc>    </d:desc>
1878  </d:item>  </d:item>
# Line 2037  p { Line 2239  p {
2239    
2240  <d:item name="empty attribute value"  <d:item name="empty attribute value"
2241      modules="ContentChecker::HTML">      modules="ContentChecker::HTML">
2242    <d:message xml:lang="en">The attribute value must not be empty.</d:message>    <d:message xml:lang="en">The attribute value is empty.</d:message>
2243      <d:message xml:lang="ja">属性値が空です。</d:message>
2244    </d:item>
2245    
2246    <d:item name="empty style sheet title"
2247        modules="ContentChecker::HTML">
2248      <d:message xml:lang="en">The value of the <code>title</code> attribute
2249      is empty.</d:message>
2250      <d:message xml:lang="ja"><code>title</code> 属性の値が空です。</d:message>
2251      <d:desc xml:lang="en">
2252        <p>The <code>title</code> attribute value of the <code>link</code>
2253        element that defines an alternate style sheet is an empty value.</p>
2254    
2255        <p>A <code>link</code> element whose <code>rel</code> attribute
2256        is <code>alternate stylesheet</code> defines an alternate style sheet.
2257        An alternate style sheet must be associated with a name using the
2258        <code>title</code> attribute.  The name cannot be empty.</p>
2259      </d:desc>
2260  </d:item>  </d:item>
2261    
2262  <d:item name="float:out of range"  <d:item name="float:out of range"
# Line 2465  p { Line 2684  p {
2684      modules="IMTChecker">      modules="IMTChecker">
2685    <d:message xml:lang="en">An obsolete Internet Media Type    <d:message xml:lang="en">An obsolete Internet Media Type
2686    <code><var>{value}</var></code> is used.</d:message>    <code><var>{value}</var></code> is used.</d:message>
2687    <d:item xml:lang="en">    <d:message xml:lang="ja">廃止されたインターネット媒体型
2688      <p>The specified Internet Media Type is registered with status    <code><var>{value}</var></code> が使われています。</d:message>
2689      of <i>OBSOLETE</i>.</p>    <d:desc xml:lang="en">
2690        <p>The specified Internet Media Type is registered with its intended
2691        usage as <i>OBSOLETE</i>.</p>
2692            
2693      <dl class="swtich">      <dl class="swtich">
2694      <dt>Media type <code>text/ecmascript</code></dt>      <dt>Media type <code>text/ecmascript</code></dt>
2695        <dd>Media type <code>text/ecmascript</code> is obsoleted in        <dd>Media type <code>text/ecmascript</code> is obsoleted in
2696        favor of <code>application/ecmascript</code>.  Note that        favor of <code>application/ecmascript</code>.  Note that
2697        <code>text/javascript</code> would be better alternative        <em><code>text/javascript</code></em> would be the better alternative
2698        for many cases.</dd>        in many cases.</dd>
2699      <dt>Media type <code>text/javascript</code></dt>      <dt>Media type <code>text/javascript</code></dt>
2700        <dd>Media type <code>text/javascript</code> is obsoleted by        <dd>Media type <code>text/javascript</code> is obsoleted by
2701        <abbr>IETF</abbr> with backward incompatible alternate        <abbr>IETF</abbr> with backward incompatible alternate
2702        <code>application/javascript</code> for architectural        <code>application/javascript</code> for architectural
2703        purity.<!-- @@ ref? -->  Realist may ignore this warning.</dd>        purity.<!-- @@ ref? -->  Those who prefer reality to academic
2704          purity <em>may ignore</em> this warning.</dd>
2705      </dl>      </dl>
2706    </d:item>    </d:desc>
2707  </d:item>  </d:item>
2708    
2709  <d:item name="IMT:parameter missing"  <d:item name="IMT:parameter missing"
# Line 3782  p { Line 4004  p {
4004    <d:text xml:lang="ja">位置不明</d:text>    <d:text xml:lang="ja">位置不明</d:text>
4005  </d:cat>  </d:cat>
4006    
4007  <d:cat name="(Unknown)">  <d:cat name="(unknown)">
4008    <d:text xml:lang="en">(Unknown)</d:text>    <d:text xml:lang="en">(Unknown)</d:text>
4009    <d:text xml:lang="ja">(不明)</d:text>    <d:text xml:lang="ja">(不明)</d:text>
4010  </d:cat>  </d:cat>

Legend:
Removed from v.1.41  
changed lines
  Added in v.1.45

[email protected]
ViewVC Help
Powered by ViewVC 1.1.24