Re: Alternatives to altGlyph for non-SVG fonts

On 28/09/14 11:08, Cameron McCormack wrote:
> I don't know that CSS is the right level to support this.  Still, I
> could see a couple of places where you could make this work:
>
>    tspan.symbols { content: glyph(123) glyph(456); }

Skimming http://www.w3.org/TR/2014/WD-dpub-latinreq-20140930/ I notice 
that that is pretty much what Prince supports ("prince-glyph-index" 
rather than "glyph").

Received on Wednesday, 1 October 2014 01:57:15 UTC