Incorrectly rendered path
Merged from https://bugs.launchpad.net/inkscape/+bug/167278
Wow, action on an eight year old bug report!
Inkscape is not updating the calculated path data correctly ('d'). This bug still exists in trunk (0.91).
I've just tested Opera (Presto), Chrome, Firefox, Squiggle, and rsvg. All render the test image the same way and correctly according to the path data ('d' attribute).
The file contains three paths. One path is an offset linked to another path that itself is an offset of a path that is a star. I've tested that the problem exists even with one level of linked offset.
Inkscape 0.48 is generating a crazy path for the outer-linked path while trunk (0.91) is doing something more reasonable.
A copy of the original path data is being saved. This should not be necessary as the data is available from the linked path. Perhaps this was to allow reuse of the code from 'Dynamic Offset'.
Each path is linked via 'xlink:href' and 'inkscape:href'. 'xlink:href" is being misused; it has a definite meaning in SVG however, removing it breaks the linking in 0.48 and trunk. 'inkscape:href' does not appear to be used in either 0.48 and trunk but this is the correct way the paths should be linked. The test file dates back to 0.43. As it contains 'inkscape:href', we should be able to delete the 'xlink:href' and only use the 'inkscape:href' without breaking content.
The SVG file: