Skip to content

Commit 16b00da

Browse files
committed
[css2] Better text for BOM errata.
--HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%403277
1 parent 06aa751 commit 16b00da

1 file changed

Lines changed: 13 additions & 8 deletions

File tree

css2/syndata.src

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
22
<html lang="en">
3-
<!-- $Id: syndata.src,v 2.194 2013-05-02 14:01:28 bbos Exp $ -->
3+
<!-- $Id: syndata.src,v 2.195 2013-05-02 16:00:15 bbos Exp $ -->
44
<head>
55
<title>Syntax and basic data types</title>
66
<!--script src="http://www.w3c-test.org/css/harness/annotate.js#CSS21_DEV" type="text/javascript" defer></script-->
@@ -1446,13 +1446,13 @@ class="index-inst">UTF-8</span> encoding.
14461446
</p>
14471447

14481448
<p>If rule 1 above (an HTTP "charset" parameter or similar) yields a
1449-
character encoding and it is one of UTF-8, UTF-16, UTF-16BE, UTF-16LE,
1450-
UTF-32, UTF-32BE or UTF-32LE, then a BOM, if any, at the start of the
1451-
file overrides that character encoding, as follows:
1449+
character encoding and it is one of UTF-8, UTF-16 or UTF-32, then a
1450+
BOM, if any, at the start of the file overrides that character
1451+
encoding, as follows:
14521452

14531453
<table>
14541454
<thead>
1455-
<th><th>First bytes (hexadecimal) <th>Resulting encoding
1455+
<tr><th>First bytes (hexadecimal) <th>Resulting encoding
14561456
<tbody>
14571457
<tr><td>00 00 FE FF <td>UTF-32, big-endian
14581458
<tr><td>FF FE 00 00 <td>UTF-32, little-endian
@@ -1461,9 +1461,14 @@ file overrides that character encoding, as follows:
14611461
<tr><td>EF BB BF <td>UTF-8
14621462
</table>
14631463

1464-
<p class=note>Note that, if rule 1 yields UTF-16BE, UTF-16LE, UTF-32BE
1465-
or UTF-32LE, a BOM at the start of the file is an error. (Unicode
1466-
forbids a BOM in such files).
1464+
<p>If rule 1 yields a character encoding of UTF-16BE, UTF-16LE,
1465+
UTF-32BE or UTF-32LE, then it is an error if the file starts with a
1466+
BOM. A CSS UA must recover by ignoring the specified encoding and
1467+
using the table above.
1468+
1469+
<p class=note>Note that the fact that a BOM at the start of a file is
1470+
en error in UTF-16BE, UTF-16LE, UTF-32BE or UTF-32LE is specified by
1471+
[[UNICODE]].
14671472

14681473
<p>User agents must ignore any @charset rule not at the beginning of the
14691474
style sheet. When user agents detect the character encoding using the

0 commit comments

Comments
 (0)