- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 03 Oct 2012 10:51:24 -0400
- To: www-style@w3.org
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
Received on Wednesday, 3 October 2012 14:52:00 UTC