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

RE: text to path conversion API proposal

From: David Dailey <ddailey@zoominternet.net>
Date: Sun, 23 Oct 2011 13:17:40 -0400
To: "'Cameron McCormack'" <cam@mcc.id.au>, "'Charles Pritchard'" <chuck@jumis.com>
Cc: "'Dirk Schulze'" <vbs85@gmx.de>, "'Rik Cabanier'" <cabanier@gmail.com>, <www-svg@w3.org>
Message-ID: <001701cc91a7$ab729180$0257b480$@net>
Some examples of remarkably inconsistent cross-browser rendering of decorated text can be seen at

http://srufaculty.sru.edu/david.dailey/svg/TopAlignBrowsers.png (illustrating http://granite.sru.edu/~ddailey/svg/tspanmeasure4.svg ) 

http://srufaculty.sru.edu/david.dailey/svg/text/textplay.svg

and

http://srufaculty.sru.edu/david.dailey/svg/text/verticalText.svg


A whole mess (the technical term) of text effects is at http://srufaculty.sru.edu/david.dailey/svg/text/ in case one wants a compendium of "up your acid tests" for SVG and text.

Some were presented at SVG Open (http://cs.sru.edu/%7Eddailey/svg/GeometricAccessibility.html ) but each contains some effects the other doesn't.

The word SVG word puns are at  
http://cs.sru.edu/%7Eddailey/svg/2011/simplePuns.svg

http://granite.sru.edu/%7Eddailey/svg/2011/svgPuns.svg

http://cs.sru.edu/%7Eddailey/svg/2011/heavyPuns.svg

and 
http://srufaculty.sru.edu/david.dailey/svg/text/texteffects2.htm 

with the original bitmaps (some of which can't be done nicely as text in SVG yet) at 
http://cs.sru.edu/%7Eddailey/svg/TypographicPuns1.jpg 
and
http://cs.sru.edu/~ddailey/svg/TypographicPuns2.jpg

good luck!
David

-----Original Message-----
From: www-svg-request@w3.org [mailto:www-svg-request@w3.org] On Behalf Of Cameron McCormack
Sent: Sunday, October 23, 2011 12:37 PM
To: Charles Pritchard
Cc: Dirk Schulze; Rik Cabanier; www-svg@w3.org
Subject: Re: text to path conversion API proposal

On 23/10/11 12:24 PM, Charles Pritchard wrote:
> What's the question being asked?

The question is whether it is acceptable for implementations to return 
different path data from this API for the same font/text being rendered.

> I agree about decorations, they're hard to get right. Having additional
> information from the font, such as baseline offsets, is a big help in
> implementing underline, but it'd be nice to save that added work when
> possible.

CSS3 Text also does not specify exact thickness or position of line 
decorations.  If an author wants to perform some funky text warping 
effect of underlined text, and they want it to match what the browser 
would be rendering, then the API will need to expose the decorations as 
paths.
Received on Sunday, 23 October 2011 17:18:07 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:49 GMT