W3C home > Mailing lists > Public > www-style@w3.org > February 2004

Re: [CSS21] response to issue 115 (and 44)

From: Chris Lilley <chris@w3.org>
Date: Mon, 23 Feb 2004 01:14:51 +0100
Message-ID: <841472796.20040223011451@w3.org>
To: Bert Bos <bert@w3.org>
Cc: "WWW Style" <www-style@w3.org>

On Sunday, February 22, 2004, 2:22:43 PM, Bert wrote:

BB> Boris Zbarsky writes:
>> I'll start maybe believing that when the W3C site sheets happen to have some
>> encoding information attached to them.... 

BB> Working on it... :-)

BB> Note that HTML files are correctly labeled on the W3C site and have
BB> been for a long time. I already asked internally if it is feasable for
BB> CSS files as well.

I suggested internally that writing a script to prepend an @charset
onto any CSS file that does not have it is not difficult, and then
calling this script from 'find' is an easy way to do a site-wide

The advantage of this method is that one does not need to change the
server config, and also the CSS files continue to work correctly when
read over the filesystem instead of HTTP (for example, when making a
zipped version of all the files in a specification).

BB> Anybody knows what browsers will break if we send a "charset="
BB> parameter after the "text/css" MIME type?. And if there would be any
BB> work-arounds?

The CSS 2.1 testsuite will presumably test this?

 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 Member, W3C Technical Architecture Group
Received on Sunday, 22 February 2004 19:14:51 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:11 UTC