Inkscape 0.47 didn't render some text. Inkscape 0.42.2 and Adobe svg render it.

[narcix]

I have some .svg files used for realization of rubber stamps.
Inkscape 0.42.2 and Adobe SVG viewer open them without problem but Inkscape 0.47 don't render some text.
I tried on Windows XP and Windows 7.
I attach one file as example (bottom text on path is not rendered in 0.47).

[su_v (suv-lp)]

reproduced with Inkscape 0.47 and 0.47+devel r9172 on OS X 10.5.8
not reproduced with Inkscape 0.46 -> regression

[su_v (suv-lp)]

bitmap export with Inkscape 0.46

[narcix (office-stamp)]

This bug is still present in inkscape 0.48.1.
I am still using 0.46 because all new versions didn't render bottom text on path.

[jazzynico (jazzynico)]

Reproduced on Windows XP, Inkscape trunk revision 11649.
Also fails with Batik-Sqiggle 1.7, but works correctly with Firefox 13.0.1.

Additionally, Inkscape crashes when trying to edit the text paths (pathcerc1 and path26) and outputs the following console error:

terminate called after throwing an instance of 'Geom::ContinuityError'
  what(): lib2geom exception: Non-contiguous path (src/2geom/path.cpp:99)

[jazzynico (jazzynico)]

Applying a stroke color to the text paths prevents the crash, but doesn't solve the rendering issue. At least, you can modify it so that the stamp looks good with the new versions.

[jazzynico (jazzynico)]

@Johan - The bug seems to be related to 2geom. Would you be willing to investigate?

[jazzynico (jazzynico)]

Tested again on Windows XP with revision 12688. Now Inkscape doesn't render (and export) any text, but I still see the two circles.

[Jonathan Hofinger (jhofinger)]

The reason for this is that the text is put on a very badly formed path. The path has the coordinates

M1,0 A1,1 0 1 1 0.99999999999999999999999 -0.00000000000000001

https://www.w3.org/TR/SVG/paths.html#ArcOutOfRangeParameters says "If the endpoint (x, y) of the segment is identical to the current point (e.g., the endpoint of the previous segment), then this is equivalent to omitting the elliptical arc segment entirely." which is, except for rounding errors, the case. It seems like Inkscape is forgiving enough to render the path.

The second path has the data

M1,0 A1,1 0 1 0 0.99999999999999999999999 -0.00000000000000001

so the only difference is the sweep-flag. Apparently, the internal rounding is slightly different in this case.

So the bug mainly is that the first path _is_ rendered, not that the second path _is not_ rendered. This led to https://gitlab.com/inkscape/inbox/-/issues/2006.

See attached file for a fix, I just truncated a few digits away to prevent rounding.

[Jonathan Hofinger (jhofinger)]

Closed by: https://gitlab.com/jhofinger