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

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

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Sat, 21 Feb 2004 14:12:58 -0500
Message-Id: <200402211912.i1LJCwul004907@department-of-alchemy.mit.edu>
To: Bert Bos <bert@w3.org>
Cc: "WWW Style" <www-style@w3.org>

> I don't mind having that rule. I was just wondering if it was worth
> adding. XHTML 2, e.g., doesn't have CHARSET on LINK anymore.

But see also <http://www.w3.org/TR/xml-stylesheet/>, which _does_ define the
pseudo-attr "charset"....

> I haven't thought about the CSSOM. I just meant "remove" in the sense
> that the CSS parser may start parsing after the @charset, since it has
> already been dealt with (namely by ignoring it).

Ah, ok.  That's not so bad, then.  ;)

> What goes into the CSSOM I don't know. Does @charset belong in the

It's useful for saving stylesheets (eg the "save page, complete" functionality
some browsers support which saves all the associated images, sheets, etc).

> > >   2e) If the first bytes are FE FF xx, where xx is not 00, use UTF-16-BE.
> > >       Remove the first two bytes. If they are followed by "@charset
> > >       <anything>;", remove that as well.
> > 
> > "xx" corresponds to two bytes here, I assume?
> One byte is enough, I think.

Note that I asked this for UTF-16BE.  In almost all cases, that next byte
_will_ be 0 in this encoding.

God does not play dice with the universe: he plays an
ineffable game of his own devising, which might be
compared, from the perspective of any of the other
players, to being involved in an obscure and complex
version of poker in a pitch-dark room, with blank
cards, for infinite stakes, with a dealer who won't
tell you the rules, and who smiles all the time.

  -- Good Omens: The Nice and Accurate Prophecies of
     Agnes Nutter, Witch, by Neil Gaiman and Terry Pratchett
Received on Saturday, 21 February 2004 14:25:05 UTC

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