W3C home > Mailing lists > Public > www-svg@w3.org > September 2010

Re: normalizedPathSegList in SVGPathElement

From: Erik Dahlstrom <ed@opera.com>
Date: Sat, 04 Sep 2010 10:10:17 +0200
To: "Dirk Schulze" <vbs85@gmx.de>, www-svg@w3.org
Message-ID: <op.vih0zfp6geuyw5@dhcpwifi-23-133.enst.fr>
On Fri, 03 Sep 2010 20:38:06 +0200, Dirk Schulze <vbs85@gmx.de> wrote:

> Hi www-svg,
>
> I am working on an implementation for normalizedPathSegList for WebKit.
...
> I think normalizedPathSegList is much more useful, if all
> implementations create the same normalizedPathSegList, because
> pathSegList and normalizedPathSegList need to be synchronized.

Agreed, it would be nice if we could align on a particular normalization.  
As you note, for arcs in particular the normalization isn't defined.

...
> Can the specification provide a more detailed algorithm how to
> flatten/normalize a path, and how to synchronize both types of segment
> lists?

There are path normalization requirements[1] in SVG Tiny 1.2, which is  
what Opera tries to follow (note that svgtiny doesn't allow arc segments  
in paths).

Synchronization between the lists, that's something that might be nice to  
define too. Batik and Opera are the only implementations I know of that  
implement the SVG 1.1 path DOM interfaces at the moment, and there are  
some minor differences IIRC.

Cheers
/Erik

[1] http://www.w3.org/TR/SVGTiny12/svgudom.html#Attribute_Normalization

-- 
Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Saturday, 4 September 2010 08:10:54 GMT

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