10155 2006-07-29 15:07:11 -0700 CSS2: @charset is not supported 2006-09-01 12:31:07 -0700 1 1 1 Unclassified WebKit CSS 419.x Mac OS X 10.4 RESOLVED FIXED http://amd.co.at/pat/webkit/ P2 Normal --- 1 pat webkit-unassigned ap oldest_to_newest 51124 0 pat 2006-07-29 15:07:11 -0700 If you set the charset encoding of a external CSS file using either one of the following methods, it gets ignored: @charset in the css file Content-Type: text/css; charset=utf-8 or Content-Encoding: utf-8 As soon as you specify the charset in the <link> itself, it works as expected. Please see the above mentioned URL. With nonworking.html, the <link> does not specify the charset, but test.css starts with '@charset "utf-8";' and the Content-Type is set to 'text/css; charset=utf-8'. working.html references the same test.css, but specifies the charset in the <link>. 51137 1 ap 2006-07-30 00:00:57 -0700 Specifying a charset in Content-Type works in current WebKit, you can verify this with a nightly build from <http://nightly.webkit.org>. Do any browsers honor a charset specified in the Content-Encoding header? The only registered options are gzip, compress, deflate and identity: <http://www.iana.org/assignments/http-parameters>. Spec for @charset: <http://www.w3.org/TR/CSS21/syndata.html#x60>. Renaming the bug to track this single issue. 54575 2 ap 2006-09-01 12:31:07 -0700 Fixed in bug 5620, r16175.