- From: Richard Ishida <ishida@w3.org>
- Date: Fri, 13 Sep 2013 06:57:03 +0100
- To: John Daggett <jdaggett@mozilla.com>
- CC: W3C Style <www-style@w3.org>, www International <www-international@w3.org>
Sounds reasonable. RI On 13/09/2013 02:45, John Daggett wrote: > > Richard Ishida wrote: > >> 4.5. Character range: the unicode-range descriptor >> http://www.w3.org/TR/2013/WD-css-fonts-3-20130711/#unicode-range-desc >> >> 'Each <urange> value is a UNICODE-RANGE token made up of a "U+" or "u+" >> prefix followed by a codepoint range'. The U+ is not always needed >> before every codepoint value (eg. in a range). >> >> Why do we need the U+/u+ ? It would be easier to just use bare hex >> codepoints, especially for ranges, where U+ is only used at the start >> anyway. > > As Tab has already pointed out, the unicode range syntax was part of > CSS 2.1 syntax and the descriptor itself is already supported by > multiple implementations so it's not appropriate to make a change like > this at this point. > > Regards, > > John Daggett > -- Richard Ishida
Received on Friday, 13 September 2013 05:57:32 UTC