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: Wed, 23 Nov 2011 17:18:46 -0800
Message-ID: <CAAWBYDBh4AGW3GkxMDYrv8+0iTq4avUaZxJ6qs6bStQje5E9QA@mail.gmail.com>
To: Håkon Wium Lie <howcome@opera.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, www-style@w3.org
On Wed, Nov 23, 2011 at 4:09 PM, Håkon Wium Lie <howcome@opera.com> wrote:
> Also sprach Tab Atkins Jr.:
>
>  > > @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).
>
> We could just say that they can't be combined. The use cases seem
> slim, and the amount of work to get interoperable implementations
> (e.g., getting SVGs to interoperably co-exist, size-wise and
> position-wise, with glyphs) seems high.

Actually, that should be trivial.  Both of those are well-defined.
That said, I agree that there's not much use in combining them.

> Then we could do:
>
>  @counter-style lower-norwegian-glyphs {
>   alphabetic: 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 æ ø å;
>  }
>
>  @counter-style lower-norwegian-images {
>   images: url(a.svg) url(b.svg) url(c.svg); /* etc */
>  }

That seems fine, with the caveat in your next post about escaping
spaces.  I'd forgotten you can do that!

~TJ
Received on Thursday, 24 November 2011 01:19:35 GMT

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