Created attachment 59246 [details] W3C SVG test suite "path-data-18-f" LO Draw doesn't pass W3C SVG test suite 'path-data-18-f' test (see attached file). "Test passes if no red is visible."
Chr. Rossmanith committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=bef8e358b6940fd4a976cb346dfd829643e581b8 fdo#48068 fix parsing of path d-attribute
The patch only fixes the buggy parsing not the buggy anisotropic scaled stroke width.
Created attachment 62019 [details] Fixed test document The test document in the comment #0 was broken. It created the 5th black line on another Y coordinate (110 vs. 120). I did the following change: --- paths-data-18-f.svg.old +++ paths-data-18-f-fixed.svg @@ -63,7 +63,7 @@ <path d="M 20 100 H 40" stroke-width="4" stroke="black"/> <path d="M 20 120 H 40.5 0.6" stroke-width="2" stroke="red"/> - <path d="M 20 110 H 40.5.6" stroke-width="4" stroke="black"/> + <path d="M 20 120 H 40.5.6" stroke-width="4" stroke="black"/> <path d="M 20 140 h 10 -20" stroke-width="2" stroke="red"/> <path d="M 20 140 h 10-20" stroke-width="4" stroke="black"/>
Chr. Rossmanith committed a patch related to this issue. It has been pushed to "libreoffice-3-5": http://cgit.freedesktop.org/libreoffice/core/commit/?id=de4b790fa928f92bf40b2e2b2c2acb622f9ebd8b&g=libreoffice-3-5 fdo#48068 fix parsing of path d-attribute It will be available in LibreOffice 3.5.5.
Created attachment 87635 [details] W3C SVG test suite "path-data-18-f"
Petr is right, the test document had an error. I've uploaded the original one from the test suite. There is no red visible anymore, but a new problem pops up: There are no yellow boxes visible. Libo only has black boxes.
Created attachment 104761 [details] Omitted zero in path data I have written a corresponding issue in OpenOffice with another test document (attached here too). https://issues.apache.org/ooo/show_bug.cgi?id=125447 LibreOffice is wrong in LO4.2 same as OpenOffice, and with additional errors in trunk version.
Black boxes problem still present in Version: 5.0.0.5 Build ID: 1b1a90865e348b492231e1c451437d7a15bb262b Locale: es-ES (es_ES) on Windows 7 (64-bit)
Looks like the problem is in the Y value of scale(8, 2). it's easy to see if it's changed to scale(8, 0.5). I'll take a look
Created attachment 123304 [details] Example without missing zeros The attached example shows, that somewhere width and height are exchanged. Currently the stroke-width changes, when scaled in x-direction; and the stroke-width does not change, when scaled in y-direction. This is an error independent from zero values and should become its own issue. The rendering is correct in AOO.
@Xisco: I think the wrong rendering in regard to the scale-transformation is unrelated to the number problem in this issue. I have written bug 98451 for the wrong scaling of the line. Please use that issue, if you work on the problem.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Dear Valek Filippov, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Valek Filippov, 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
This issue seems to be fixed since LibreOffice 6.2. Closing