On Sat, 02 Oct 2010 23:26:54 +0200, [email protected] <[email protected]> wrote:
> I successfully tested my freshly written path data parser against the > paths found in the "paths-data-##-t.svg" files of the 1.2 Tiny test > suite. But I wonder whether I also have to take into account obscure > things like > > <path d="m0..0.1 2"> Right, parsing that should give you the coordinates: "0.", ".0", ".1" and "2". > I tested it with Firefox, Opera, Chrome, Batik/Squiggle, librsvg and > Inkscape. Only Chrome does not render it. Sounds like a bug in Chrome then. > If a path like this is legal, I think there should be a test case in the > test suite, shouldn't it? It's always nice to be thorough, sure. Have you found any other edge-cases like this one while writing your path parser? Cheers /Erik -- Erik Dahlstrom, Core Technology Developer, Opera Software Co-Chair, W3C SVG Working Group Personal blog: http://my.opera.com/macdev_ed ------------------------------------ ----- To unsubscribe send a message to: [email protected] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ----Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/svg-developers/join (Yahoo! ID required) <*> To change settings via email: [email protected] [email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
