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

On Thu, Nov 13, 2014 at 5:27 PM, Greg Whitworth <gwhit@microsoft.com> wrote:
>> 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.

That's implicit in the fact that I'm using the V&U grammar - the "u"
there denotes an ident, and is implicitly ASCII case-insensitive since
it's a language-defined ident.

~TJ

Received on Friday, 14 November 2014 01:30:04 UTC