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

> >Bjoern, why is it not implementable?
> 
> Note that in auto-detect mode Internet Explorer for Windows considers
> the second example us-ascii encoded and renders "Bjvrn" and considers
> the third example as UTF-7 and renders "Björn", this does not match
> Mozilla's or Opera's behaivour, but Internet Explorer's behaivour makes
> among those most sense to me.

I'm not sure this answers my question... that was "why is it not possible to
implement using the encoding of the document linking to the sheet as a fallback
for the sheet's encoding?"

> Also note that a number of HTML processors try to circumvent these
> encoding issues and treat documents as us-ascii compatible encoded
[etc, etc]

None of that answers that question either...

> Documents that trigger strict mode in recent browsers that reference a
> style sheet that contains non-utf-8 sequences that is delivered without
> any encoding information are probably way less than 1% of the web...

Yes... but 1% of the web is a _lot_ of pages.  I'm willing to be convinced here
given some hard data, but given how many bugs I saw filed when Mozilla was
being _much_ more lenient than this suggestion (though not quite as lenient as
IE or Opera, hence the bugs) this will take some _hard_ data.

> And among those, if the specification said something to the effect that all
> style sheets should have a proper @charset, I could go and spread the word
> through the W3C CSS Validator...

I'll start maybe believing that when the W3C site sheets happen to have some
encoding information attached to them.... 

Boris
-- 
An experiment may be considered a success if no more
than half of your data must be discarded to obtain
correspondence with your theory.

Received on Sunday, 22 February 2004 01:48:57 UTC