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

Re: text to path conversion API proposal

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Sun, 23 Oct 2011 14:23:10 -0400
Message-ID: <4EA45B8E.8040507@mit.edu>
To: www-svg@w3.org
On 10/23/11 12:36 PM, Cameron McCormack wrote:
> 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.

The alternative is to embed a definition of all the details of shaping, 
kerning, etc, etc, in the spec, yes?  And then wait for UAs to actually 
implement it all.  Assuming they want to.

Or restrict the API to font formats that don't support any of that 
stuff, of course.  But that makes it unusable for some text, of course.

A related question: what are the actual use cases for the API?  Is 
compatibility of the metrics returned with actual text rendering by the 
browser important, say?  If so, then you can't require path data 
uniformity, since browsers do not in fact render things identically.

Received on Sunday, 23 October 2011 18:23:55 UTC

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