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

Boris Zbarsky writes:

> > > >   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.

You're right. There should be no condition on the third byte.

Another bug is that the bytes FE FF do not actually guarantee that the
encoding is UTF-16. They might be two characters in an 8-bit encoding.
(If only we could forbid the BOM in CSS style sheets... :-( )

I don't see how to avoid that, though. The spec will have to point it
out and say that it is better, when possible, to not rely on a BOM,
but to configure the server properly.



Bert
-- 
  Bert Bos                                ( W 3 C ) http://www.w3.org/
  http://www.w3.org/people/bos/                              W3C/ERCIM
  bert@w3.org                             2004 Rt des Lucioles / BP 93
  +33 (0)4 92 38 76 92            06902 Sophia Antipolis Cedex, France

Received on Saturday, 21 February 2004 18:41:14 UTC