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

Re: [css3-lists] glyphs in single string

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 24 Nov 2011 19:17:36 -0800
Message-ID: <CAAWBYDD60HeJ2eKFuNPxkt8pa=H5OjX5+yFTTo_YX+kG3j4cvg@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style@w3.org
On Wed, Nov 23, 2011 at 7:47 PM, fantasai <fantasai.lists@inkedblade.net> wrote:
> On 11/23/2011 03:43 PM, Tab Atkins Jr. wrote:
>> On Wed, Nov 23, 2011 at 3:31 PM, fantasai<fantasai.lists@inkedblade.net>
>>> Why have the functional notation at all? Just put the glyphs in
>>> the property directly.
>>>
>>> @counter-style lower-norwegian {
>>>   type: alphabetic;
>>>   glyphs: a b c d e f g h i j k l m n o p q r s t u v w x y z æ ø å;
>>> }
>>
>> Then you can't distinguish an<image>  from a glyph that just happens
>> to look remarkably like url(foo).
>
> If you're using unquoted values, you definitely should be restricting
> them to identifiers only (or, at most, IDENT, NUMBER, and DIMEN).
>
> And, as Peter Moulder says, allow quoted strings for hard-to-escape cases.

This seems completely reasonable.  I'm totally fine with allowing
IDENT, NUMBER, DIMEN, <string>s, and <image>s.  This has none of the
weaknesses of the other proposals, while being maximally compact.

Hakon, does this sound good to you too?

~TJ
Received on Friday, 25 November 2011 03:18:27 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:46 GMT