- From: Chris Lilley <chris@w3.org>
- Date: Fri, 21 Apr 2006 16:53:29 +0200
- To: www-svg@w3.org
- Cc: Bjoern Hoehrmann <derhoermi@gmx.net>
Hello www-svg, Bjoern Hoehrmann <derhoermi@gmx.net> wrote: >>-------- >>The native implementations must support the following simplifications or >>canonicalization of path segments. Any simplifications should be >>lossless. >> >> * Relative commands (c, h, l, m, q, s, t, and v) must be converted >>to their absolute counterparts. >> * Horizontal and Vertical lines (H, h, V, and v) must be converted >>to general lines (L and l). >> * Translate command S to command C. >> * Translate command T to command Q >>-------- > > This is actually not an absolute requirement in the draft but rather > an optional step which is then later an absolute requirement for the > SVGPath interface. Which, again, is not a contradiction. On, say, getAttributeNS, an implementation might return the specified value or it might return a normalized value. So in that case, its an optional step. When comparing paths to see if they are animatable, then to avoid needless false negatives, the paths are normalized before comparison. There is no contradiction there. -- Chris Lilley mailto:chris@w3.org Interaction Domain Leader Chair, W3C SVG Working Group W3C Graphics Activity Lead Co-Chair, W3C Hypertext CG
Received on Friday, 21 April 2006 14:53:39 UTC