Comment 0 for bug 1190808

Revision history for this message
Geoff Adams (gsadams) wrote :

I have a reasonably simple SVG file with two paths. One of the paths contains a coordinate with fairly small values (0.0001,0.077). I then combine the two paths together, and Inkscape generates a combined path with very small values with unnecessarily high precision: -5.9211895e-16 6.46875.

I understand that the math may produce exactly these numbers, but is there any use to such precise, small numbers? It's hard to imagine the magnification that would be required to distinguish -5.9211895e-16 from 0, much less from -5.9211896e-16, and the precision of these numbers is substantially higher than the two significant digits in the input. To the precision of the input coordinates, that number is 0.

Worse for my use, the SVG parser I'm using is unable to handle the exponentiation syntax, so I have to convert these numbers manually to 0. (I know, that's not Inkscape's problem, since the spec allows this. But I do wonder how widespread this is.) It would be nice if Inkscape would limit the output precision to not much more than the input precision to avoid these problems.

It's also interesting that Inkscape rewrites the 0.0001 to 10e-4 when saving, but leaves 0.0077 as 0.0077.

The original and unioned-path SVG files can be found here:
    http://www.avernus.com/~gadams/dingbats/two-paths.svg
    http://www.avernus.com/~gadams/dingbats/two-paths-combined.svg