- From: Simon Sapin <simon.sapin@kozea.fr>
- Date: Thu, 24 Jan 2013 21:57:49 +0100
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- CC: www-style list <www-style@w3.org>
Le 24/01/2013 21:46, Bjoern Hoehrmann a écrit : > * Simon Sapin wrote: >> css3-syntax defines "non-ASCII character" as "A character with a >> codepoint equal to or greater than U+00A0 NO-BREAK SPACE." >> >> Could we change that to "… equal to or greater than U+0080"? In other >> words, having the whole block of C1 control characters be considered >> non-ASCII. I don’t think that more than a tiny amount of existing >> content would be affected, but I don’t have any data to support that. > Changing the definition of a specification-level concept like "non-ASCII > character" does not have to affect anything outside the specification. It changes the tokenization (and thus parsing) of some character sequences. C1 control character that were previously delim tokens would become part of a ident, at-keyword, hash, function or dimension token. -- Simon Sapin
Received on Thursday, 24 January 2013 20:58:14 UTC