On Sun, 6 Feb 2005 12:31:21 +0100 (CET), christian@...693... <christian@...693...> wrote:
librsvg bug with some details here: http://bugzilla.gnome.org/show_bug.cgi?id=166385
Summary: Yes this file is broken, but the source of the problem is either Sodipodi or an early version of Inkscape, not modern Inkscape. Modern Inkscape is only guilty of trying to be Sodipodi-compatible more than SVG-compatible, and this must be fixed. You cannot create a similarly broken file with a modern Inkscape if you start from scratch.
Details: This file uses a <polygon> to represent the star. For some reason unknown, the SVG attribute points= went out of sync with the Sodipodi attributes (sodipodi:cx, etc). (I remember we had a Sodipodi-inherited bug of points= not being updated properly in some situations, but it was fixed long ago.) Now, Sodipodi and Inkscape (including the most recent version of Inkscape) obeys the sodipodi: attributes, but all other renderers obey the points= attribute and therefore display the star differently.
An additional complication is that we have long ago switched from using <polygon> to using <path> for stars (because we added rounded stars which can only be shown as paths). Therefore, modern Inkscape lacks code for updating points= attribute (which is only allowed on <polygin>) and updates only the d= of <path>. So, even if you load that file into modern Inkscape and edit the star, it will remain <polygon> and its points= will not be updated. And this is the problem which we need to fix.
Proposal: I think that if we see a polygon with sodipodi:type="star", we must treat it as a polygon, not as a Sodipodi/Inkscape star object. As a result, this file will look broken in Inkscape too, but this is correct. As for this particular file, to fix it you can either save as plain SVG or just convert that star to path (Ctrl+Shift+C) and save as usual.
