W3C home > Mailing lists > Public > www-style@w3.org > January 2013

Re: [css3-syntax] Making U+0080 to U+009F "non-ASCII"?

From: Simon Sapin <simon.sapin@kozea.fr>
Date: Sun, 27 Jan 2013 10:33:57 +0100
Message-ID: <5104F485.9090307@kozea.fr>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
CC: www-style list <www-style@w3.org>
Le 27/01/2013 02:55, Bjoern Hoehrmann a écrit :
> As a matter of good governance, the CSS Working Group should stick
> with the syntax that it promises will never ever change, as much as is
> possible at least, and even if there was no such promise, it shouldn't
> make changes to the syntax for no reason (you have not shown that there
> is a valid reason);

I agree on the principle, but why keep a promise when three of four 
major implementations do something else, and probably always have? 
U+0080 is already non-ASCII in WebKit, Presto, and Trident:

http://lists.w3.org/Archives/Public/www-archive/2013Jan/att-0039/U_0080_as_non-ASCII.html
http://lists.w3.org/Archives/Public/www-archive/2013Jan/att-0039/U_007F_as_non-ASCII.html


> one reason is that a change as proposed might lead
> to arguments with I18N Core about the merits of C1 control characters as
> initial character in identifiers, which does not seem to be a good use
> of either Working Group's time.

As I said in a previous email, let’s not go there. I’m certainly not 
trying to have that discussion.

-- 
Simon Sapin
Received on Sunday, 27 January 2013 09:34:20 GMT

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