Inkscape doesn't handle superfluous comma's in a path described by relative moves
Bug #683066 reported by
Diederik van Lierop
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Triaged
|
Undecided
|
Unassigned |
Bug Description
An SVG file (attached) created by a Python library called Polygon [1] contains paths like these:
M 35.2919, 188.178 L 255.35, 61.1274,L 220.058, 0,L 0, 127.051 z
As you can see it has some unnecessary comma's (before the second and third L), which are correctly handled by the preview in my file manager (Dolphin, Opensuse), but which apparently fool Inkscape. Inkscape only shows a line. If I remove the comma's then Inkscape displays the path properly. So this will work:
M 35.2919, 188.178 L 255.35, 61.1274 L 220.058, 0 L 0, 127.051 z
I believe that Inkscape should be more tolerant in such a case.
Using Inkscape r9882
tags: | added: svg |
Changed in inkscape: | |
status: | Confirmed → Triaged |
To post a comment you must log in.
Squiggle (Batik 1.7) doesn't render the SVG file at all:
> SVG Error: launchpadlibrar ian.net/ 59876151/ SuperfluousComm asInPath. svg:4
>
> http://
> The attribute "d" of the element <path> is invalid
… nor does Firefox 3.6.
OTOH, Safari 5.0, Opera 10.6 and rsvg-view 2.32 do display a red and a green, rotated rectangle.