W3C home > Mailing lists > Public > www-style@w3.org > October 2012

Re: [css3-fonts][css-variables][css-counter-styles-3][css3-values] Case sensitivity of user-defined identifiers

From: Brian Kardell <bkardell@gmail.com>
Date: Wed, 3 Oct 2012 10:58:17 -0400
Message-ID: <CADC=+je-wy9q2p=MR3Z=T95fv+i+XF4+sbFWrAUzm=8Eyc-7aw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-style@w3.org
Because as tab said, lots of existing sheets use things like Red or RED

Brian Kardell :: @bkardell :: hitchjs.com
On Oct 3, 2012 10:53 AM, "Boris Zbarsky" <bzbarsky@mit.edu> wrote:
>
> On 10/3/12 7:35 AM, Jonathan Kew wrote:
>>
>> Are we happy to accept that the Web should embed this Anglo-centric
>> weirdness, based on text encoding practices from the last century, into
>> its core specifications; or do we want to press for a more inclusive
>> platform that aims to treat all languages and writing systems on an
>> equal footing for authors, as far as the Unicode encoding model permits?
>
>
> The way HTML handles this is that matching for user-defined stuff is
effectively always case-sensitive.  The ASCII case-insensitive bits are
only for things the spec defines (tag and attribute names), which are
already ASCII-only.
>
> Here's a question.  Can we get there in CSS?  This seems like it would be
doable for color names, certainly.  Same for other CSS keywords.  Are font
names an issue?  Where _exactly_ do issues come in with variables here?
>
> I have to admit I don't understand why we can't just make variable names
case-sensitive...
>
> -Boris
>
Because as tab said, lots of existing sheets use things like Red or RED

Brian Kardell :: @bkardell :: hitchjs.com
Received on Wednesday, 3 October 2012 14:58:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:01 GMT