- From: Erik Dahlstrom <ed@opera.com>
- Date: Thu, 20 Dec 2012 11:32:36 +0100
- To: www-svg@w3.org
On Thu, 20 Dec 2012 08:37:44 +0100, Dirk Schulze <dschulze@adobe.com> wrote: > > On Dec 19, 2012, at 6:51 PM, Dirk Schulze <dschulze@adobe.com> wrote: > >> >> On Dec 19, 2012, at 6:41 PM, Cameron McCormack <cam@mcc.id.au> wrote: >> >>> On 20/12/12 1:59 AM, Stephen Chenney wrote: >>>> It seems that no browser supports arbitrary geometry inside a <glyph> >>>> element. Only path data in the "d" attribute of the glyph is >>>> supported, >>>> and then only on Opera and WebKit (as far as I can tell). There are no >>>> W3C tests for non-path glyphs that I could find. >>>> >>>> I propose we drop the container aspect of glyph and insist on path >>>> data >>>> only. The complexity of implementing arbitrary geometry inside <glyph> >>>> makes it unlikely to be supported. > > Opera supports the font module from SVG 1.2 Tiny, which just allows the > d attribute. IIRC we couldn't find another viewer with full SVG 1.1 > fonts support and decided to use the limited font module from SVG 1.2 > Tiny instead of SVG 1.1 for SVG2. This would actually address your > concerns. Cameron/Erik please correct me if I am mistaken. I think Batik and the viewer from Abbra are the only implementations I've used that supports (probably a subset of) full SVG Fonts, as in child elements in <glyph>. AFAIK no web browsers support arbitrary child elements in <glyph>. -- Erik Dahlstrom, Core Technology Developer, Opera Software Co-Chair, W3C SVG Working Group Personal blog: http://my.opera.com/macdev_ed
Received on Thursday, 20 December 2012 10:33:07 UTC