https://issues.apache.org/ooo/show_bug.cgi?id=123465
--- Comment #5 from Armin Le Grand <[email protected]> --- ALG: You are probably right with closeWithGeometryChange; it has historical reasons and is originally based on the transition from tools:Polygon classes to basegfx classes; the tools:Polygon class had no internal possibility to express that it is closed, it used the 1st == last point paradigm, making it impossible to have open polygons with 1st and last point being equal. closeWithGeometryChange is sued in the converters between these two polygon classes to solve this; mainly used in im/exporters and binfilter, short: in places where it was not possible to get away from tools:polygon yet. I already thought about that one as a possible reason; for SVG it might indeed be the best solution to just not do that. This might lead to one problem, though: - import a svg:d not closed, 1st and last points equal - break (to no longer have it as original SVG) and save as ODF: In the UNO API it needs to be converted to sequences of points which also do have no possibility to express a polygon with 1st == last point and not closed (maybe with the polygon type, need to check). Thus: This type of polygon might get lost... -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.
