When printing handouts, any slides with bitmaps that overlap anything will be flattened entirely. This includes rasterizing text which is not overlapping or being overlapped by anything. Normally this isn't a problem, unless you're trying to use a PDF printer. Unfortunately, this PDF printers are currently the only way to export handouts as PDFs (see bug #45498, as well as the Impress user guide). This is inconsistent with printing slides, which will properly render text when given the same slides. Steps to reproduce: 1) Install a PDF printer, such as PDFCreator. 2) Start a new default presentation. 3) On the first slide, type 'test' into the title field. 4) In the body of the slide, enter some text or graphics. 5) Drag a bitmap image onto the slide so it overlaps the body but not the title. 6) Print the slides to your PDF printer. 7) Print the handout to your PDF printer. Expected results: In both PDFs, the word 'test' should be rendered as text and selectable even though the body is flattened. Actual results: 'test' is correctly rendered as text in the PDF of the slides, but incorrectly rasterized in the PDF of the handout. Notes: * This was tested on Windows 8 with PDFCreator and PNG bitmaps. * This problem also exists in OpenOffice 3.4.1.
@Rick Yorgason Please attach a testkit.zip with sample document and PDF print (Use Add an attachment (proposed patch, testcase, etc.) here on the page)
Created attachment 78053 [details] Example of problem document Adding zip with four files: input.odp - A document that exhibits the bug. output_slides_correct.pdf - An example of how printing as slides leaves the 'Selectable' text properly selectable. output_handouts_incorrect.pdf - An example of how printing as handouts fails to leave the 'Selectable' text intact. evilsmile.png - The bitmap used in the document.
Problem more or already [Reproducible] withreporter's sample, FreePDF printer and Server Installation of "LibreOffice 3.3.3 English UI/ German Locale [OOO330m19 (Build:301) tag libreoffice-3.3.3.1] on German WIN7 Home Premium (64bit) Steps how to reproduce: 1. Open Sample document from LibO Start center 2. Print with FreePDF to a PDF document 3. delete grim smiley 4. Print with FreePDF to a PDF document with different name as in Step 2 5. Open both documents in Adobe Reader X and compare text "Not selectable" with zoom 400% or so Expected: in both documents high resolution characters, Text can be selected as text and can be copied as text to text editor Actual: Text from step 2 with ugly artifacts, and not selectable as text All the same with 4.0.2.2 @Rick Yorgason I observe a much more general bug, not llmited to 4.0.2.2 and PDF printer, and "handout" (you did not mention this in your report step by step instruction). Did I misunderstand something or IS it a more general problem?
@Rainer Bielefeld To clarify, in my example document the "Selectable" and "Not selectable" text documents my expectations, not the actual results. It would be nice if the "Not selectable" text was selectable, but I understand why that part of the slide might have to be flattened, and at least it's consistent. The "Selectable" text, on the other hand, acts differently depending on whether you're printing slides or handouts. In the handouts, it flattens the entire slide, instead of just the parts of the slide with overlapping elements.
Already [Reproducible] with "LibreOffice 3.6.6.2 release " German UI/ German Locale [Build-ID: f969faf] {pull date 2013-04-03} on German WIN7 Home Premium (64bit), proceeding as per original report shows text "Selectable" in printedhandout.PDF not as text, but as raster picture, can not be selected as text. Already [Reproducible]with Server Installation of "LibreOffice 3.3.3 English UI/ German Locale [OOO330m19 (Build:301) tag libreoffice-3.3.3.1] on German WIN7 Home Premium (64bit). Same with AOOo 3.4.0 and OOo 3.1.1, so probably inherited from OOo. @Rick Yorgason: I'm sorry, I completely misunderstood the problem. I hope now everything is correct? Currently I only see this confirmed for WIN (although I expect it will be the same for other OS)?
@Rainer Bielefeld I expect this bug is OS-agnostic, but my Linux/Hackintosh box isn't working right now, so I haven't tested them on any OS but Windows.
** 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 (4.4.1.2 or later): 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-03
Still present in 4.4.1.2 on Windows 8 x64. (And still relevant as #45498 still isn't fixed.)
I am not sure if this is the same bug: when i copy/paste a drawing from Draw in a Wirter-document, and select text-wrap = follow contour and export this as PDF (or print it as PS), all the lines of text next to the drawing and the drawing itself (regardless if shapes or bitmaps) gets rasterized TOGETHER as ONE raster-image the resulting PDF. Lines of before and after the drawing are exported as text-spans in the PDF.
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Still present in 5.1.2.2 on Windows 10 x64. (And still relevant as #45498 still isn't fixed.)
** 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
I would be shocked if this bug is fixed, but I moved on from the project that hit this bug years ago, so I'm not going to bother with it anymore. It sucks that I put the work into the reproduction recipe for it to be ignored, but I don't feel like doing this busy work every year will make it any less ignored. If your system automatically closes the bug, so be it.
** 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
Dear Rick Yorgason, 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 Rick Yorgason, 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
On Linux, the postscript export of OpenOffice.Org 3.3 has no selectable text. However, I tested both version 5.1.2.2 and a recent trunk build and can't reproduce the issue (all text on slide can be selected in the printed-to-file handout PDF). I'm wondering if it's a limitation of the installed PDF tool on Windows. I assume the PDF printer on my system is printer-driver-cups-pdf 3.0.1-6. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b83f069101f1e6d8aaac09a805f02bbc4c619e7a CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded