Created attachment 174910 [details] Command sequences Z L L and Z M L Open attached document. It has two custom shapes. The used enhanced-path is cited on the right side. The "close path" command Z makes the "current point" not invalid, but sets it to the initial point of the closed path. And following commands uses this as "current point" as long as they do not set themselves a "current point". In the examples the closed path is the triangle. Its initial point has the coordinates (0|0). Therefore in shape A there should be a line from point (0|0) to point (80|60) which is the parameter of the first L (lineto) command. Shape B does not have such line, because the command M (moveto) sets a "current point". I think, there should be no concerns to fix it. This bug-report is not about the path object and its svg:d attribute, where users have a UI to manipulate points. But it is about the enhanced-path attribute of custom-shapes. The reported situation does not exists in import or export with predefined shapes. It happens only, if someone creates own custom-shapes by editing the markup in file or using macros. Current ODF 1.3 is not explicit about current point after Z. But SVG, from which the path commands were inspired, has this rule and ODF 1.4 will have it explicitly too.
Moving to NEW
Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
The problem is not solved in Version: 26.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 7f4868348c14b305fcd75744e1e3544d0d3a5d61 CPU threads: 32; OS: Windows 11 X86_64 (build 26100); UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: threaded In the meantime, LO uses ODF 1.4 as default version. So this should be fixed now. It is specified in "Table 10 - Enhanced path commands" in section "19.145 draw:enhanced-path" in part 3 of ODF 1.4. https://docs.oasis-open.org/office/OpenDocument/v1.4/cs01/part3-schema/OpenDocument-v1.4-cs01-part3-schema.html#attribute-draw_enhanced-path