Skip to content

Commit 33c23fa

Browse files
committed
[css2] Added emphasis to make text about initial hyphen easier to read.
Added that @charset must be the literal, lowercase characters, not escaped. --HG-- extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402243
1 parent fe00b7d commit 33c23fa

1 file changed

Lines changed: 10 additions & 5 deletions

File tree

css2/syndata.src

Lines changed: 10 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
22
"http://www.w3.org/TR/1998/REC-html40-19980424/loose.dtd">
33
<html lang="en">
4-
<!-- $Id: syndata.src,v 2.102 2004-02-25 16:36:18 bbos Exp $ -->
4+
<!-- $Id: syndata.src,v 2.103 2004-03-08 18:40:14 bbos Exp $ -->
55
<head>
66
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
77
<title>Syntax and basic data types</title>
@@ -233,7 +233,7 @@ href="#parsing-errors">rules for handling parsing errors</a>. However, because t
233233
characters [A-Za-z0-9] and ISO 10646 characters <!--161--> U+00A1 and higher,
234234
plus the hyphen (-) and the underscore (_); they cannot start with a digit.
235235
Only properties, values, units, pseudo-classes,
236-
pseudo-elements, and at-rules may start with a hyphen (-); other
236+
pseudo-elements, and at-rules may <em>start</em> with a hyphen (-); other
237237
identifiers (e.g. element names, classes, or IDs) may not.
238238
Identifiers can also contain escaped characters and any ISO 10646
239239
character as a numeric code (see next item).
@@ -1204,9 +1204,9 @@ encoding</span> (from highest priority to lowest):
12041204
</ol>
12051205

12061206
<p>At most one @charset rule may appear in an external style sheet and
1207-
it must appear at the very start of the style sheet, not preceded by any
1208-
characters, except possibly a "BOM" (U+FEFF).
1209-
Any other @charset rules must be ignored by the UA.
1207+
it must appear at the very start of the style sheet or immediately
1208+
after a Byte Order Mark (BOM, U+FEFF) that is at the very start of the
1209+
style sheet. Any other @charset rules must be ignored by the UA.
12101210
</p>
12111211

12121212
<p>After "@charset", authors specify the name of a character encoding
@@ -1215,6 +1215,11 @@ Any other @charset rules must be ignored by the UA.
12151215

12161216
<pre class="example">@charset "ISO-8859-1";</pre>
12171217

1218+
<p>@charset must be written literally, i.e., the 10 characters
1219+
'@charset "' (lowercase, no backslash escapes), followed by the
1220+
encoding name, followed by '";'.
1221+
</p>
1222+
12181223
<p>The name must be a charset name as described in the IANA registry.
12191224
See [[-CHARSETS]] for a complete list of charsets. Authors should use
12201225
the charset names marked as "preferred MIME name" in the IANA

0 commit comments

Comments
 (0)