[css2] New text about "preferred MIME name." Martin has to review it.

bert-github · bert-github · commit 2d33bf4250f9 · 2004-02-25T16:36:18.000Z
--HG--
extra : convert_revision : svn%3A73dc7c4b-06e6-40f3-b4f7-9ed1dbc14bfc/trunk%402235
diff --git a/css2/syndata.src b/css2/syndata.src
@@ -1,7 +1,7 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
         "http://www.w3.org/TR/1998/REC-html40-19980424/loose.dtd">
 <html lang="en">
-<!-- $Id: syndata.src,v 2.101 2004-02-23 21:59:03 bbos Exp $ -->
+<!-- $Id: syndata.src,v 2.102 2004-02-25 16:36:18 bbos Exp $ -->
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Syntax and basic data types</title>
@@ -1210,18 +1210,20 @@ Any other @charset rules must be ignored by the UA.
 </p>
 
 <p>After "@charset", authors specify the name of a character encoding
-(in quotes).
-The name must be a charset name as described in the IANA registry (See
-[[IANA]]. Also, see [[-CHARSETS]] for a complete list of charsets).
-For example:
+(in quotes). For example:
 </p>
 
 <pre class="example">@charset "ISO-8859-1";</pre>
 
-<p>This specification does not mandate which character encodings
-a user agent must support.
+<p>The name must be a charset name as described in the IANA registry.
+See [[-CHARSETS]] for a complete list of charsets. Authors should use
+the charset names marked as "preferred MIME name" in the IANA
+registry.
 </p>
 
+<p>This specification does not mandate which character encodings a
+user agent must support.
+
 <p>This specification does not specify what algorithm a UA must
 apply to derive the encoding from the BOM and the @charset. In
 particular, it does not specify the encoding to use if the BOM and the
