W3C home > Mailing lists > Public > www-svg@w3.org > November 2013

Re: SVG fonts: [ was RE: minutes, SVG WG TPAC F2F 2014, day 2]

From: Erik Dahlstrom <ed@opera.com>
Date: Mon, 18 Nov 2013 11:02:23 +0100
To: "David Dailey" <ddailey@zoominternet.net>, "Robert O'Callahan" <robert@ocallahan.org>
Cc: "Cameron McCormack" <cam@mcc.id.au>, www-svg <www-svg@w3.org>
Message-ID: <op.w6qot9iogeuyw5@gnorps>
On Mon, 18 Nov 2013 03:03:40 +0100, Robert O'Callahan  
<robert@ocallahan.org> wrote:

> On Fri, Nov 15, 2013 at 3:39 AM, David Dailey  
> <ddailey@zoominternet.net>wrote:
>> ChrisL
>>  ... I propose that we get rid of SVG Fonts completely from SVG
>>     2
>>     cyril: what is problematic with removing this is making them on
>>     the fly
>>     ChrisL: have you seen roc's font workshop page?
>>     cyril: no...
>> Am not sure if the font workshop page resolves Cyril's question or not.
>> Does it?
> Yes.
> http://people.mozilla.com/~roc/animated-SVG-glyphs.webm
> https://github.com/rocallahan/svg-opentype-workshop
> Losing the ability to define new fonts on the fly, client-side would
>> present a major crippling of current functionality.
> You're not losing it. svg-opentype-workshop provides an MPL2-licensed JS
> library for reading and writing the SVG glyph data in an OpenType font
> (client-side). Creating a complete font from scratch would require a  
> little
> more work but nothing particularly difficult.

To be fair this does mean that easy client-side manipulation of an svg  
font that exists inline in the svg itself is lost, because the  
SVG-in-OpenType fonts offer no direct DOM access to the svg parts at all.

That said, I think it's fine to use a js lib to provide that  
functionality. Such a lib could probably even mimic the SVG DOM if need be.

Another concern however, is the potential difference in what is supported  
in SVG glyphs if glyph rendering will be handled not by the browser  
itself, but by a third-party font library. There's also the risk that the  
format used in SVG glyphs over time diverges from "normal" SVG such that  
it causes extensibility issues for SVG. These are separate issues that  
should be addressed by the SVG-in-OpenType spec, in close cooperation with  
the SVG WG.

Erik Dahlstrom, Web Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Received on Monday, 18 November 2013 10:03:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:54:47 UTC