Inkscape doesn't handle superfluous comma's in a path described by relative moves

Bug #683066 reported by Diederik van Lierop on 2010-11-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone

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: svg Edit Tag help
su_v (suv-lp) on 2010-11-30
tags: added: svg
su_v (suv-lp) wrote :

Squiggle (Batik 1.7) doesn't render the SVG file at all:

> SVG Error:
> 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.

The Polygon library has been fixed, so no more superfluous comma's coming from that source. Would still be nice to have Inkscape more robust.

Changed in inkscape:
status: New → Confirmed
Beluga (buovjaga) wrote :

Still confirmed.

Arch Linux 64-bit, KDE Plasma 5
Inkscape 0.92pre1 15054 (GTK3)

jazzynico (jazzynico) on 2016-08-15
Changed in inkscape:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers