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: Robert O'Callahan <robert@ocallahan.org>
Date: Sun, 17 Nov 2013 18:03:40 -0800
Message-ID: <CAOp6jLb9N8oYTmT3baGU4n-Jvm+H9bOfjHMC2jUczfLzEYnRJw@mail.gmail.com>
To: David Dailey <ddailey@zoominternet.net>
Cc: Cameron McCormack <cam@mcc.id.au>, www-svg <www-svg@w3.org>
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?


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.

If svg-in-opentype gives some mechanism for providing for client-side
> generation of fonts that include color, gradients, animation, patterns,
> (namely the whole ball of wax that SVG fonts provides) then I'm cool.

Good, you're cool :-).

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w
Received on Monday, 18 November 2013 02:04:08 UTC

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