Using version 4.2.8.2 on Ubuntu (Bug does not occur on Windows!) When using the free Code-128 truetype font from Deutscher Zoll (German customs): http://www.zoll.de/SharedDocs/Downloads/DE/Links-fuer-Inhaltseiten/Fachthemen/Zoelle/Atlas/code_128.zip;jsessionid=A20DAD2281332DA76D68A2D97AAF1349.live0482?__blob=publicationFile&v=8 everything works fine on screen and when exporting a PDF file. However, if I try to print a document, anything that uses the Code-128 font will be moved down. This shows in the actual print, but also in print preview, so it's probably not a driver issue. Prepare for reproducing: - download the font, install it - open Calc / new document - write any string into cell A1 (e.g. "Hello world") - write any other string into cell A2 (e.g. "Line2") - show print preview: Strings show in correct order, as expected. To reproduce: - Change font to Code-128 in cell A1 only, leave A2 unchanged - show print preview again: Bar code will overlap with the "Line2" string To make it worse (and maybe get a hint why this is happening): - format cell A1 to vertically align text to the top - show print preview: Bar code is almost below the "line2" string, as if the vertical position had been inverted. To work around, you need to increase the height of line 1. Very annoying, as it wastes valuable print space. I wrote myself a few macros that generate proper Code-128 barcodes, and they work great since summer 2013. Sometime in 2015, I upgraded the computer and Ubuntu version, then had to tinker with the very-high cell in order to have the bar code on the printed sheet. Unfortunately, I can't remember the old LO version that printed the code properly.
Updated FreeType package to see if there's any change, but bug remains.
Could you test with version 5 to see, if the problem still persists? https://launchpad.net/~libreoffice/+archive/ubuntu/ppa http://www.webupd8.org/2015/08/install-libreoffice-50-in-ubuntu-or.html Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Created attachment 121755 [details] file created with the steps I described in "preparation". Code-128 truetype font must be installed!
Tried with version 5, but bug remains exactly the same, including the step "top alignment moves printout further down". Set back to UNCONFIRMED.
Noticed that the font download link contains a session ID, which may lead to problems. Click on the 4th link from top on this page: http://www.zoll.de/DE/Fachthemen/Zoelle/ATLAS/ATLAS-Publikationen/Sonstiges/sonstiges.html If you don't speak German, just do a text search for "Font".
Could reproduce in Ubuntu 15.10 (64-bit). Version: 5.0.5.2 Build ID: 1:5.0.5~rc2-0ubuntu2-GL Locale: en-US (en_US.UTF-8) However, if a different version of the same font that is attached to bug 88021 is installed (instead of, or alongside the one mentioned in comment 5), then the print preview looks fine. So make sure the right font is in the system when testing this bug. This is the other Code 128 font: https://bugs.documentfoundation.org/attachment.cgi?id=111719
** 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.7 or 5.3.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-20170522
Dear Jens, 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 Jens, 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