W3C home > Mailing lists > Public > www-svg@w3.org > October 2011

Re: text to path conversion API proposal

From: Rik Cabanier <cabanier@gmail.com>
Date: Sat, 22 Oct 2011 18:35:33 -0400
Message-ID: <CAGN7qDCcKFHfPWs3zm_ce+DFQr+oYPZQRAb_QQ1BLLYuY9+PEQ@mail.gmail.com>
To: Dirk Schulze <vbs85@gmx.de>
Cc: Cameron McCormack <cam@mcc.id.au>, www-svg@w3.org
I agree that it is hard, but it's not impossible. We (= Adobe) can do it for
almost all font types (except maybe bitmap fonts which are not used very

Doesn't WebKit rely on the OS for font layout. The hard part for you would
be to match your calculated outlines with the OS's.


On Fri, Oct 21, 2011 at 2:59 PM, Dirk Schulze <vbs85@gmx.de> wrote:

> This should work independent of the used font / font type? WOFF, SVG Fonts,
> OpenType,... for all types? Should this work with texts on paths as well?
> What do you expect for benefits, when do we need that? I know that Gecko
> supports it for HTML Canvas, but I never saw an example that uses that. I
> should mention that it would be very hard to implement it in WebKit and some
> ports may never be able to use that. How do you determine the path segments
> of a glyph? It must be transformed to SVG Path syntax somehow and I am not
> sure how we get similar results across implementations for SVGPathSegList.
> Greetings
> Dirk
> Am 21.10.2011 um 20:18 schrieb Cameron McCormack:
> > I started writing up a proposal for an SVG text to path conversion API:
> >
> > http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Text_to_path_API
> >
> > Comments welcome.
> >
Received on Saturday, 22 October 2011 22:36:01 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:26 UTC