29 |
though the use of another character encoding is conforming.</p> |
though the use of another character encoding is conforming.</p> |
30 |
</div> |
</div> |
31 |
|
|
32 |
|
<div class="section format-charset unsupported" id="unsupported:character-encoding"><h3>Conformance for character encoding requirements |
33 |
|
cannot be checked.</h3> |
34 |
|
<p>The conformance checker cannot detect whether the input document |
35 |
|
met the requirements on character encoding, since the document |
36 |
|
is not inputed as a serialized byte sequence. The document is |
37 |
|
not conforming if it is not encoded in an appropriate character |
38 |
|
encoding with appropriate labeling.</p> |
39 |
|
</div> |
40 |
|
|
41 |
<div class="section format-charset error" id="m:no-character-encoding-declaration"><h3>There is no character encoding |
<div class="section format-charset error" id="m:no-character-encoding-declaration"><h3>There is no character encoding |
42 |
declaration.</h3> |
declaration.</h3> |
43 |
<p>The document does not contain a character encoding |
<p>The document does not contain a character encoding |
44 |
declaration. Unless the character encoding is explicitly |
declaration. Unless the character encoding is explicitly |
45 |
specified in upper‐level protocol, e.g. in <abbr>HTTP</abbr>, |
specified in lower‐level protocol, e.g. in <abbr>HTTP</abbr>, |
46 |
or is implied by <abbr>BOM</abbr>, there must be a character |
or is implied by <abbr>BOM</abbr>, there must be a character |
47 |
encoding declaration. The document is non‐conforming.</p> |
encoding declaration. The document is non‐conforming.</p> |
48 |
|
|
57 |
</div> |
</div> |
58 |
|
|
59 |
<div class="section format-charset error" id="m:non-ascii-superset"><h3>No character encoding metadata is found |
<div class="section format-charset error" id="m:non-ascii-superset"><h3>No character encoding metadata is found |
60 |
in upper‐level protocol nor is there <abbr>BOM</abbr>, while |
in lower‐level protocol nor is there <abbr>BOM</abbr>, while |
61 |
character encoding <code><var>$0</var></code> |
character encoding <code><var>$0</var></code> |
62 |
is not a superset of <abbr>ASCII</abbr>.</h3> |
is not a superset of <abbr>ASCII</abbr>.</h3> |
63 |
<p>The document is not labeled with character encoding name |
<p>The document is not labeled with character encoding name |
64 |
in upper‐level protocol, e.g. in <abbr>HTTP</abbr>, and |
in lower‐level protocol, e.g. in <abbr>HTTP</abbr>, and |
65 |
the document is not begin with <abbr>BOM</abbr>. In addition, |
the document is not begin with <abbr>BOM</abbr>. In addition, |
66 |
the character encoding of the document is not a superset of |
the character encoding of the document is not a superset of |
67 |
<abbr>ASCII</abbr>. The document is non‐conforming.</p> |
<abbr>ASCII</abbr>. The document is non‐conforming.</p> |
859 |
<section id="attribute-value-errors"> |
<section id="attribute-value-errors"> |
860 |
<h2>Attribute Value Errors</h2> |
<h2>Attribute Value Errors</h2> |
861 |
|
|
862 |
|
<div class="section attribute-value-warning warning" id="w:charset:not-registered"><h3>Character encoding name <code><var>$0</var></code> |
863 |
|
is not registered.</h3> |
864 |
|
<p>The specified character encoding name is not registered to |
865 |
|
<abbr>IANA</abbr>. Use of registered character encoding name |
866 |
|
is a good practice to facilitate interoperability.</p> |
867 |
|
|
868 |
|
<dl class="switch"> |
869 |
|
<dt><code>EUC-TW</code></dt> |
870 |
|
<dd><code>EUC-TW</code> is not registered. Unfortunately, there |
871 |
|
is no registered name for that character encoding. Use |
872 |
|
Big5 encoding with character encoding name <code>Big5</code> |
873 |
|
if it is enough to represent the document.</dd> |
874 |
|
<dt><code>ISO-2022-JP-1</code></dt> |
875 |
|
<dd><code>ISO-2022-JP-1</code> is not registered, nevertheless |
876 |
|
this character encoding name is documented in |
877 |
|
<a href="urn:ietf:rfc:2237"><abbr>RFC</abbr> 2237</a>. Use |
878 |
|
<code>ISO-2022-JP-2</code> instead, since that character encoding |
879 |
|
is a superset of ISO-2022-JP-1.</dd> |
880 |
|
<dt><code>ISO-2022-JP-3</code>, <code>ISO-2022-JP-3-plane1</code></dt> |
881 |
|
<dd>These names are not registered and obsoleted in favor of |
882 |
|
<code>ISO-2022-JP-2004</code> and |
883 |
|
<code>ISO-2022-JP-2004-plane1</code>.</dd> |
884 |
|
<dt><code>ISO-2022-JP-2003</code>, |
885 |
|
<code>ISO-2022-JP-2003-plane1</code></dt> |
886 |
|
<dd>These names are not registered and corrected to |
887 |
|
<code>ISO-2022-JP-2004</code> and |
888 |
|
<code>ISO-2022-JP-2004-plane1</code>.</dd> |
889 |
|
<dt><code>ISO-2022-JP-2004</code>, |
890 |
|
<code>ISO-2022-JP-2004-plane1</code></dt> |
891 |
|
<dd>These names are not registered. Unfortunately, there is |
892 |
|
no registered name for these character encodings.</dd> |
893 |
|
<dt><code>UTF-8N</code></dt> |
894 |
|
<dd><code>UTF-8N</code> is not registered. Character encoding |
895 |
|
name <code>UTF-8</code> represents UTF-8 encoding with or |
896 |
|
without <abbr>BOM</abbr>.</dd> |
897 |
|
</dl> |
898 |
|
|
899 |
|
<p><strong>WARNING</strong>: This error might be raised for |
900 |
|
a registered character encoding name, since the character encoding |
901 |
|
name database of the conformance checker is not complete yet.</p> |
902 |
|
</div> |
903 |
|
|
904 |
|
<div class="section attribute-value-warning warning" id="w:charset:private"><h3><code><var>$0</var></code> is a private |
905 |
|
character encoding name.</h3> |
906 |
|
<p>The specified character encoding name is a private name and |
907 |
|
not registered to <abbr>IANA</abbr>. Use of registered character |
908 |
|
encoding name is a good practice to facilitate interoperability.</p> |
909 |
|
|
910 |
|
<dl class="switch"> |
911 |
|
<dt><code>x-euc-jp</code></dt> |
912 |
|
<dd>Use <code>EUC-JP</code> for the Japanese <abbr>EUC</abbr> |
913 |
|
character encoding.</dd> |
914 |
|
<dt><code>x-sjis</code></dt> |
915 |
|
<dd>Use <code>Shift_JIS</code> for standard Shift encoding scheme of |
916 |
|
<abbr>JIS</abbr> coded character set, or <code>Windows-31J</code> |
917 |
|
for Microsoft standard character set as implemented by |
918 |
|
Microsoft Windows.</dd> |
919 |
|
</dl> |
920 |
|
</div> |
921 |
|
|
922 |
|
<div class="section attribute-value-error" id="m:charset:syntax-error"><h3>The specified value is syntactically not a |
923 |
|
character encoding name.</h3> |
924 |
|
<p>The attribute value must be a character encoding name. However, |
925 |
|
the specified value is not a character encoding name syntactically. |
926 |
|
The document is non‐conforming.</p> |
927 |
|
<p>Character encoding name is a string of <abbr>ASCII</abbr> |
928 |
|
printable characters, up to 40 characters.</p> |
929 |
|
</div> |
930 |
|
|
931 |
<div class="section attribute-value-error" id="enumerated:invalid"><h3>This attribute only allow a limited set of |
<div class="section attribute-value-error" id="enumerated:invalid"><h3>This attribute only allow a limited set of |
932 |
values and the specified value <code><var>{@}</var></code> is not one |
values and the specified value <code><var>{@}</var></code> is not one |
933 |
of them.</h3> |
of them.</h3> |
1006 |
</dl> |
</dl> |
1007 |
</div> |
</div> |
1008 |
|
|
1009 |
|
<div class="section attribute-value-error" id="m:mismatched-charset-name"><h3>Character encoding name <code><var>$1</var></code> |
1010 |
|
is different from document character encoding |
1011 |
|
<code><var>$0</var></code>.</h3> |
1012 |
|
<p>The specified character encoding name is different from |
1013 |
|
the character encoding of the document. The document |
1014 |
|
is non‐conforming.</p> |
1015 |
|
</div> |
1016 |
|
|
1017 |
<div class="section attribute-value-error" id="reserved-browsing-context-name"><h3>Browsing context name |
<div class="section attribute-value-error" id="reserved-browsing-context-name"><h3>Browsing context name |
1018 |
<code><var>{@}</var></code> is reserved.</h3> |
<code><var>{@}</var></code> is reserved.</h3> |
1019 |
<p>The specified browsing context name is reserved. |
<p>The specified browsing context name is reserved. |