- From: Charles Pritchard <chuck@jumis.com>
- Date: Thu, 03 Jun 2010 10:04:40 -0700
- To: robert@ocallahan.org
- CC: Alex Danilo <alex@abbra.com>, "Dr. Olaf Hoffmann" <Dr.O.Hoffmann@gmx.de>, www-svg@w3.org
- Message-ID: <4C07E0A8.9080307@jumis.com>
Currently, Canvas doesn't have a concept of a path string.
It'd be helpful in some minor situations (to be able to run..
fillPath("M0 0..... ", x,y), strokePath,);
but it's just syntactic sugar.
I'd love to see a text to path data API for Fonts.
Such APIs are often intentionally obscured to protect the copy rights of
font authors.
getGlyphOutline a la java.awt, or something like it, would certainly
satisfy my needs
for font manipulation.
Is there any precedence in current SVG drafts for such data handling?
Is that something more of a computed style, in CSS?
<text id="test">String</text>
pathData = test.getComputedStyle('svgpath');
Any chance of us firming up an API while we're here?
-Charles
On 6/3/2010 12:42 AM, Robert O'Callahan wrote:
> On Thu, Jun 3, 2010 at 6:00 PM, Charles Pritchard <chuck@jumis.com
> <mailto:chuck@jumis.com>> wrote:
>
> I see no technical barrier for SVG-to-canvas solutions in the future.
> Is it an unnecessary use-case, that a person may want to apply a
> "filter"
> to the paths in an font? Path filters can't access the underlying
> data of a binary font, without a descriptive API above the font.
>
> Any chance of getting more data than "width" for WOFF?
>
>
> Most graphics APIs offer a way to convert text to path data. I think
> canvas and SVG should too.
>
> Rob
> --
> "He was pierced for our transgressions, he was crushed for our
> iniquities; the punishment that brought us peace was upon him, and by
> his wounds we are healed. We all, like sheep, have gone astray, each
> of us has turned to his own way; and the LORD has laid on him the
> iniquity of us all." [Isaiah 53:5-6]
Received on Thursday, 3 June 2010 17:05:25 UTC