Created attachment 118080 [details] screenshots of reported problem SVG file generated by Gnuplot (a plot) displays correctly in inkscape (or risretto) but there are glitches while embedding into LO Draw (screen-shots attached to this report). When some text has non-default formatting (superscript or italics) is misplaced relatively to rest of the text. Generating a plot without this formatting and thed adding it inside Inkscape does not solve the problem. For me this bug is quite annoing, becouse I prefer to use vector graphics in order to reduce document file. And if I do this I'm stuck with incorrect formatting (mathematical expressions needs to be written using italics).
Please attach an actual svg instead of a screenshot. Marking as NEEDINFO - once you add it mark as UNCONFIRMED. Thanks
Also this is not a MAJOR bug - please don't overprioritize your own bugs. It being annoying to you is not the objective criteria that we prioritize based on. This is just a normal every day bug. Marking as such.
Created attachment 118095 [details] SVG file, that works incorrectly
Marked unconfirmed as requested. Sorry for overrating this bug, I'm pretty new here and I had not enough experience to choose proper option. BTW, I'm quite interesting on the origins of this error.
@Sawik - Thanks! Confirmed Ubuntu 15.04 x64 LibreOffice 4.4.5.2 & 5.0.0.5 Setting Component to LibreOffice because it's any component that you insert it into. Updating version - version is oldest version that demonstrates the issue. Setting as: New - Normal - can prevent high quality work; Low - This isn't going to impact a ton of users, it's specific to particular types of svg files. Already inserting images are not going to be incredibly common, inserting svg's less common, inserting svg's that have the characteristics of this file, less common. Please know that these settings don't prevent developers from taking interest, it's just an objective criteria that we use to indicate how many users are affected and how serious the bug is (loss of data, etc..). One useful thing would be to determine if this is a regression by going through older versions of LibreOffice: http://downloadarchive.documentfoundation.org/libreoffice/old/
** 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 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
Bug is still present on version: 5.3.6.1 Build ID: 1:5.3.6~rc1-0ubuntu0.16.04.1~lo0
still repro in LibreOffice 6.1 beta 2
Dear Sawik, 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 Sawik, 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://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 Sawik, 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 is mostly fixed after https://cgit.freedesktop.org/libreoffice/core/commit/?id=2795a230464aea3a792e67b5625fce2a0c01d547 The only remaining problem is exponent symbol that is shifted to the right
Created attachment 188963 [details] simplify document
The content of attachment 188963 [details] has been deleted
Created attachment 188970 [details] simplify document
Xisco Fauli committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/5cfd31e505b4d1b4f9d2e21b0f9f8aac22539f47 tdf#93583: use getTextWidth to calculate line's width It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Thanks, Sawik for reporting this bug, and Xisco for fixing it. Verified with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6c06c8a2be3d8cbbcb8ab1aaaeb04db95114dfcb CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Is bad in (for comparison reason) Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Xisco Fauli committed a patch related to this issue. It has been pushed to "libreoffice-7-6": https://git.libreoffice.org/core/commit/12eb15a9fac58fe2fb5baeeb35f8c43ba21b2e1e tdf#93583: use getTextWidth to calculate line's width It will be available in 7.6.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Hi All, thank you for your time and effort in fixing this issue. It seems to be working correctly now (an exponent is still a little bit off to the right, but i think it's due to the lack of a used font in my system)
(In reply to Sawik from comment #19) > Hi All, > > thank you for your time and effort in fixing this issue. > > It seems to be working correctly now (an exponent is still a little bit off > to the right, but i think it's due to the lack of a used font in my system) tested on Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 60(Build:1) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: pl-PL (pl_PL.utf8); UI: en-US 7.6.2-3 Calc: threaded