> It seems like we should be able to grep the web for all @charset rules
> in .css files and see if they're ever set to something other than
> utf8. Hixie would know how to do that, I know he did a lot of such
> "grepping" when writing HTML5.
Conversation revealed that Eric thought I was proposing removing
@charset functionality entirely. I'm not; given that we have to deal
with charsets anyway (they inherit from the document that linked the
stylesheet), the code savings would be almost zero.
A quick grep of a CSS archive by Christian Biesinger supports that we
probably can't remove it - 11.6% of the files he searched have a
@charset directive. Now, 10.2% of them have it set to "utf-8", but
that means there's still 1.4% of the archive that is setting it to
something different (and this is a large archive, so that percentage
represents a large number of stylesheets). Without further analysis, I
wouldn't be comfortable trying to kill @charset.
~TJ