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

Re: [css3-lists] glyphs in single string

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 23 Nov 2011 19:47:22 -0800
Message-ID: <4ECDBE4A.6030104@inkedblade.net>
To: www-style@w3.org
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>  wrote:
>> On 11/23/2011 10:36 AM, Tab Atkins Jr. wrote:
>>> What if we used a function as the quotes instead?
>>> @counter-style lower-norwegian {
>>>    type: alphabetic;
>>>    glyphs: 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 æ ø
>>> å);
>>> }
>>> We'd tokenize the contents of the glyphs() function by spaces, and
>>> only require that the various brace characters ()[]{} be escaped
>>> within it.
>> 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.

Received on Thursday, 24 November 2011 03:48:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:07 UTC