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:27:56 -0400
Message-ID: <CAGN7qDBRBMATAMutZHsjYU_KsCWqdQutKN-yLF0AfWfSOZ++FA@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: www-svg@w3.org
Hi Cameron,

thanks for writing up a proposal.
I have a couple of remarks:
1. It would be better if you can get the outline of each glyph instead of
the outlines of all glyphs. The current approach will cause problems with
filling if glyphs overlap.
2. As a follow-on to this, maybe it would be better if given a string of
text, you define an API that returns the used glyphs with their positions.
Then, using the API of step 1, you can get the outline of each glyph. You
can then decide yourself how you will draw with these outlines
3. There should be a rule that says that the returned glyph outlines can be
drawn with either evenodd or nonzero fill rules
4. you need to define an API that checks for permissions. Not all fonts
allow you to convert to outlines.


On Fri, Oct 21, 2011 at 2:18 PM, Cameron McCormack <cam@mcc.id.au> wrote:

> 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<http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Text_to_path_API>
> Comments welcome.
Received on Saturday, 22 October 2011 22:28:24 UTC

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