Since 2geom is now part of Inkscape, can we move this bug up in priority or get it fixed? It's still present in 0.48.1. This is relevant to projects where an even seam is required between two adjacent paths.
Since 2geom is now part of Inkscape, can we move this bug up in priority or get it fixed? It's still present in 0.48.1. This is relevant to projects where an even seam is required between two adjacent paths.