https://issues.apache.org/ooo/show_bug.cgi?id=125349
--- Comment #2 from Armin Le Grand <[email protected]> --- Works as expected, issue 125300 still fixed. Also the chrome.svg example converts to metafile seamingless. This 1st optimization is valid and even a speedup. It does not solve the numerical problem when the polyPolygons would not be clipped against a range but another polyPolygon, this would require a 2nd step and much more work. It looks as if exactly that numerically critical cases are the ones that use reanges a lot. This can be explained by realizing that the 2nd clip *is* a rectangular gradient clipped against the form to-be filled. These cases lead to ranges and polyPolygons with the same bound regions - which may lead to these problems. It would still be good to evtl. add a task for this 2nd step. To do so it should be possible to form a pair of SVG polygons - one the SVG range itself but as path element and one the upper right red element and clip these against each other. Preparing commit of current solution... -- You are receiving this mail because: You are watching all issue changes.
