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

Re: text to path conversion API proposal

From: Charles Pritchard <chuck@jumis.com>
Date: Sun, 23 Oct 2011 12:18:00 -0700
Message-Id: <5BFB0AD5-250A-4885-BB7F-3227BD9D6C6D@jumis.com>
Cc: David Dailey <ddailey@zoominternet.net>, Cameron McCormack <cam@mcc.id.au>, Dirk Schulze <vbs85@gmx.de>, Rik Cabanier <cabanier@gmail.com>, "www-svg@w3.org" <www-svg@w3.org>
To: "Frost, Jon A." <frostjo@missouri.edu>




On Oct 23, 2011, at 11:20 AM, "Frost, Jon A." <frostjo@missouri.edu> wrote:

> I would just add that I know of a few recent business discussions that resulted in deciding against using the SVG technology on the client-side because of the continued browser inconsistencies, particularly in the areas of text and filters.
> 
> Things are getting better to be sure, but server-side projects like Batik and SVG# will likely be necessary for some time unfortunately.
> 
> Jon


We continue to use Canvas on the client-side to render SVG scenes and effects. Unfortunately there are holes in the accessibility APIs.

At this point, SVG over Flash is still the most reliable and accessible manner of handling things.

-Charles
Received on Sunday, 23 October 2011 19:18:31 GMT

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