Hello, I'm a 31 years old developer from Italy and I've been using Inkscape for years. I've just subscribed to this mailing list and.. yeah... I'm already here with a bug report :P
Recently I experienced a strange behaviour with KDE 4 preview system and svg/svgz files saved with the last version of inkscape (both stable and devel version) so I decided to contact you.
I hate duplicate/unclear bug reports so I would like to discuss this thing a bit with you before filing a bug to launchpad.
So, let's try to explain what I've found
System: Kubuntu 9.10 with KDE 4.3.2 Inkscape: devel version and 0.46 (See below) Reproducible: yes
These are the steps I did:
1) I drew a simple icon with inkscape (a circle and a polygon) 2) I save it as svg or svgz (get the file here [1]) 3) The preview on my kubuntu 9.10 looks crazy (get the preview here [2]) as if nodes position has been screwed
4) I open the svg file with Inkscape 0.46 5) I change the color of an element and save again 6) The preview still looks crazy
7) I open the file again with Inkscape 0.46 but this time I move the polygon around, then I place it in the old position and save 8) The preview looks perfect, as if nodes position has been restored (get the file and the preview here [3][4])
I can't really understand what's going on here but seems that KDE 4 has troubles when previewing svg/svgz files saved with inkscape > 0.46 This happens also using ksvgtopng to convert an svg file to a png
Could this possibly be related to bug 170049 [5] ?
If you need more experiments just ask :-)
Thank you
Claudio Canavese (CoD)
1: http://cod-web.net/inkscape/devel.svgz 2: http://cod-web.net/inkscape/devel.png 3: http://cod-web.net/inkscape/046.svgz 4: http://cod-web.net/inkscape/046.png 5: https://bugs.launchpad.net/inkscape/+bug/170049
On 31/3/10 16:32, CoD wrote:
System: Kubuntu 9.10 with KDE 4.3.2 Inkscape: devel version and 0.46 (See below) Reproducible: yes
These are the steps I did:
- I drew a simple icon with inkscape (a circle and a polygon)
- I save it as svg or svgz (get the file here [1])
- The preview on my kubuntu 9.10 looks crazy (get the preview here [2])
as if nodes position has been screwed
I open the svg file with Inkscape 0.46
I change the color of an element and save again
The preview still looks crazy
I open the file again with Inkscape 0.46 but this time I move the
polygon around, then I place it in the old position and save 8) The preview looks perfect, as if nodes position has been restored (get the file and the preview here [3][4])
I can't really understand what's going on here but seems that KDE 4 has troubles when previewing svg/svgz files saved with inkscape > 0.46 This happens also using ksvgtopng to convert an svg file to a png
Could this possibly be related to bug 170049 [5] ?
I think it could be similar to bug #458388 “Rendering errors in QtSvgRenderer due to changed SVG output in Inkscape 0.47”: https://bugs.launchpad.net/inkscape/+bug/458388
«issue is optimized path data. Files saved in Inkscape 0.47 are incorrectly rendered in QtSvgRenderer of KDE 4.5 (straight line segments are omitted). unconfirmed workaround: 'Force Repeat Commands'»
You could test it by changing the preferences of 'SVG output > Path data' whether forcing repeated commands or not allowing relative coordinates creates SVG files that are rendered without error in KDE's svg previewer (you'll have to create a new icon or move all paths of an existing drawing to have the path data rewritten with the changed preferences - that's what happened when you opened the 0.47 file in Inkscape 0.46 and moved the polygon around)
hth, ~suv
Thank You
I think it could be similar to bug #458388 “Rendering errors in QtSvgRenderer due to changed SVG output in Inkscape 0.47”: https://bugs.launchpad.net/inkscape/+bug/458388
The qt rendering system was my second guess...
unconfirmed workaround: 'Force Repeat Commands'»
I can confirm: forcing not to use relative coordinates partially solved the problem. It came back with another drawing so I set up Force Repeat Commands and now everything works.
This confirms what I've always thought: before file a bug always talk to a human being... assuming that developers are human beings :P
Cheers
CoD
participants (2)
-
CoD
-
~suv