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

Re: [css-fonts-3] i18n-ISSUE-295: U+ in unicode-range descriptor

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 12 Sep 2013 13:01:05 -0700
Message-ID: <CAAWBYDA0p8d2g=Y5qvEp70YvyU5jPGxSncy53-PcpvtcYQfxag@mail.gmail.com>
To: Richard Ishida <ishida@w3.org>
Cc: W3C Style <www-style@w3.org>, www International <www-international@w3.org>
On Thu, Sep 12, 2013 at 10:59 AM, Richard Ishida <ishida@w3.org> 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.

The <unicode-range> token has a 10+ year history, I believe, so it's
firmly ensconced in this descriptor.  As well, this particular syntax
is widely recognized as representing unicode codepoints or ranges.

Received on Thursday, 12 September 2013 20:01:52 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:32 UTC