[dbaron revision history] Decisions of todays telecon. (date: 2003/04/01 04:08:13)

Author: dbaron

css3-syntax/Overview.src.html

@@ -150,24 +150,16 @@ <h2>CSS style sheet representation</h2>
 <ol>
 <li>A character set specified by a higher level protocol (e.g., the
 "charset" parameter to the MIME type specified in an HTTP "Content-Type"
-field).
+field).</li>
 <li>The <span class="index-def" title="@charset">@charset</span>
-at-rule.
-<li>Mechanisms of the language of the
-referencing document (e.g., in HTML, the "charset"
-attribute of the LINK element).
+at-rule.</li>
+<li>Assume that the stylesheet is UTF-8.</li>
 </ol>
 
-<p class="issue">As a practical matter, we should probably
-recommend what to do if there's no character encoding information in any
-of these three sources of information.  Should the style sheet be assumed
-to be in a default encoding (ISO-8859-1 or UTF-8?) or should the
-encoding of the document be used (which in turn might have some default
-or might be "sniffed")?  The latter has been observed to break some
-existing style sheets. <!-- Mozilla bug 72658 --></p>
-
-<p class="issue">We should probably have a MUST requirement for
-authors to tighten things up (2003-02-24 telecon).</p>
+<p>Since the third point differs from CSS1 and CSS2, authors should not
+rely on user agents to assume that stylesheets without encoding
+information are UTF-8 encoded.  Authors should specify the encoding
+using one of the first two methods.</p>
 
 <p>At most one @charset rule may appear in an external
 style sheet -- it must <em>not</em> appear in an embedded style sheet