Created attachment 119906 [details] Some pixels in the text of the embedded SVG image is cut off on certain zoom levels When inserting an SVG-image containing text to Writer, some pixels from the text is cut off from the display. Mainly few top pixel lines and pixels from the last character. This bug is dependent on the zoom-level. On some zoom levels less of the text is cut off than on others. A certain combination of letters is also needed to trigger the bug. For example combination of letters "ks" seems to often trigger the bug. This does not happen when viewing the image on other programs as Firefox, IE and Inkscape.
Created attachment 119907 [details] Original svg image Original SVG image triggering the bug
Created attachment 119908 [details] Gif image showing the bug on different zoom levels.
Confirming On Windows 10 Pro 64-bit en-US with Version: 5.0.3.1 (x64) Build ID: fd8cfc22f7f58033351fcb8a83b92acbadb0749e Locale: en-US (en_US) and on a recent master Version: 5.1.0.0.alpha1+ (x64) Build ID: 7323190456c2ed4ec9f092f8e69ba12ce41587cd TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2015-10-20_22:44:48 Locale: en-US (en_US) Export to PDF is also affected by issue, same clipping of extents--in addition to differences in on screen rendering at the various zoom levels.
I just tested this bug on Linux (Ubuntu 14.04 LTS and LibreOffice 4.2.8.2) and same bug is exists there also. It does not manifest it self exactly the same as on windows platform and is triggered by different combination of letters. I suspect it has something do with the fonts that are used. I will attach an .odt document and the original svg image that illustrates this bug on Linux.
Created attachment 120039 [details] .odt document illustrating the bug on Linux
Created attachment 120040 [details] Original svg image triggering the bug on linux
** 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.1.6 or 5.2.3 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-20161108
Confirming that the bug is still present on LO 5.2.3 SVG-import was introduced in LO 3.4, so the bug is not inherited from OOo.
After exploring the problem a little bit, I discovered that the bug can be circumvented to some extent by removing clipPath-elements from the SVG-file. <clipPath clipPathUnits="userSpaceOnUse" id="clipPath1"> <path d="M0 0 L150 0 L150 195 L0 195 L0 0 Z"/> </clipPath> Apparently each line of text in an svg file is accomplished by its own clipPath-element, which restricts the region to which paint can be applied. It seems that LO-does not scale the clipPath-element (or internal LO-object it is mapped to) correctly. Other alternative is that the text layout is not scaled correctly. For many simple SVG-images, like UML diagrams, the clipPath-element is not really needed to paint the image correctly. If you are affected by this bug and really need to use SVG-images in your .odt-document, you can try removing these clipPath-elements in a text editor. For my purposes this proved to be an effective work around. TIP: This regular expression can be used to remove these elements from the SVG source: <clipPath(.|\n)*?</clipPath> replace all matches with empty strings.
** 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
still repro in LibreOffice 6.1 beta 2
Dear devseppala, 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 devseppala, 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
I can still reproduce one of the aspect of this bug in LibreOffice 7.2.2, but it seems that the problem is less severe than before (compared to the example gif). Currently only the topmost pixel line seems to be cut off from the first text line in couple zoom levels in couple text boxes in the example document. Letters at end of the text lines in the example document don't seem to be cut off at any zoom level anymore. I think there have been some svg library changes in LibreOffice in the past years that may have improved the text scaling in svg images.
I can't reproduce it in Version: 7.5.0.0.alpha0+ / LibreOffice Community Build ID: a0bc0cc81b597aa81189355a8125753d6b873cce CPU threads: 8; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: es-ES (es_ES.UTF-8); UI: en-US Calc: threaded Anyone able to reproduce this issue yet ?
Created attachment 184387 [details] Lo 7.5 RC1 100% zoom. Third text box has pixels missing from top of the fonts
This is not a svg import issue
I can't reproduce either. devseppala, can you please share your full version information from Help > About LibreOffice? Does it also happen in safe mode? Version: 5.4.0.3 Build ID: 92c2794a7c181ba4c1c5053618179937228ed1fb CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group Version: 7.5.7.1 (X86_64) / LibreOffice Community Build ID: 47eb0cf7efbacdee9b19ae25d6752381ede23126 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded