W3C home > Mailing lists > Public > www-style@w3.org > November 2014

RE: [css-syntax] Removed <unicode-range-token>, please review

From: Greg Whitworth <gwhit@microsoft.com>
Date: Fri, 14 Nov 2014 01:27:28 +0000
To: Tab Atkins Jr. <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Message-ID: <bc5a95e3051e45bca93bf7a35517625c@BN3PR0301MB0868.namprd03.prod.outlook.com>
> One significant change is that the <urange> production is much looser than the <unicode-range-token> parsing previously defined.  <urange> does not attempt to ensure that the refs have at most 6 digits (or 6 total digits + question marks), as that would have made the speccing and implementation much more difficult.  
While I was against the looser definition when it was a token, as a microsyntax (which is only recognized when it's specifically called for) I'm fine with it being a little loose.  This has no effect on its use in practice; it just means that you can write things like U+0000000 (7 digits) that weren't previously allowed.

Not sure it's necessary here since you're wanting the syntax looser, but I think it's worth noting that the U is not case sensitive. This is stated with the @font-face[1] rule but it may be worth putting here as well.

[1] http://dev.w3.org/csswg/css-fonts-3/#unicode-range-desc


> ~TJ

Received on Friday, 14 November 2014 01:27:56 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:26 UTC