Creating a PDF from attached "sampple.odt" from "LibreOffice 3.3.1 RC1 - WIN7 Home Premium (64bit) German UI [OOO330m19 (build 7 / tag 3.3.1.1)]" using FeePDF XP cripples DRAW object showing an e-mail envelope. Works fine with LibO PDF export and OOo 3.1.1 + FreePDF Also a problem wiht OOo3.4-dev + FreePDF Problem also visible in a postscript file created with "Dell open print Driver PS" when I open "psresult.ps" with GSView4.9 and GS9.0 Please compare view of envelope in sample.odt and various .pdf export results (and in "psresult.ps") in my testkit.zip. Please ignore problem with missing logo in page header, that seems to be a FreePDF problem. @mathog: May be you can try to confirm this problem?
Created attachment 43285 [details] Pls. see original report
Confirmed. The issue seems to be that the gradients mess things up. In the next two attached files changing the gradient to solid seems to have eliminated the problem. LibreOffice 3.0. If I had to guess what the problem was it would be that the gradient objects are generated out of order, so they come out on top of the @ when they shouldn't. I also observed that in the original sample.odt if the drawing was exported to SVG it was messed up (not shown).
Created attachment 43342 [details] modified to eliminate gradient in copy of envelope image
Created attachment 43343 [details] postscript from modified version, modified envelope looks OK Postscript made by printing to a genicom Cl160 postscript printer, A4 portrait paper, and set "print to file" in options.
Due to Comment 2 -> NEW @mathog: Can you please file a new report concerning the SVG export problem?
SVG export bug reported here https://bugs.freedesktop.org/show_bug.cgi?id=34264
Created attachment 43347 [details] diagram taken apart to show bug
Created attachment 43348 [details] taken apart printed to postscript, gradients drawn incorrectly The problem is, or at least, part of the problem is, that the gradients are not staying within the LO object when drawn as postscript. Instead they extend to the rectangular boundary box.
This may be a case of "if you have a hammer, every problem looks like a nail", but... I know of one big compatibility problem in rendering the same object for Postsript vs. PDF: the latter supports transparency, the former does not. This also affects PDF output through "Postscript printer" devices on Windows because the program outputs Postscript even though the eventual result is PDF. Here I think what may be happening is that LO is constructing the envelope flaps via these render operations: 1. draw layer 1 rectangular gradient 2. draw layer 2 mask (uses transparency) 3. draw layer 3 black edge These are implicit - I did look at these objects and nowhere do they have transparency checked. When LO tries to send this verbatim to a Postscript device the transparency mask cannot be handled natively by the interface, and LO is probably doing a mixing operation to construct an image when it renders layer 2, which changes the desired shape from that of the mask to that of the gradient. This probably also explains the odd transparency effects noted in some of the PDF outputs. There is an image masking operation in Postscript 3 http://partners.adobe.com/public/developer/en/ps/sdk/TN5601.MaskedImages.pdf and that is probably what should be used instead. Effectively it is a stencil, either fully opaque or fully transparent, which should suffice for this sort of shaped gradient issue.
The transparency in PDF is handled by Imagetype 103, that in postscript (stencils) by Imagetype 3. In effect I think LO sees a transparency (even though 100%) knows there is no 103, and fails to fall back to 3.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Problem is still as described in 3.5.0b2. (on Windows XP).
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
in 3.5.5 still problem. Reopening
Is this still an issue in the latest stable (4.1.x) version?
Reproduced in 4.1.0 on Fedora RFR 64 bit Steps to reproduce: 0. Open sample.odt file form first attachment 1. Export it as PDF 2. open produced PDF and see on picture of envelope near top of first page But if we disable option "PDF/A-1a" then it exports correctly. IMHO it is not a bug. But some improvement is still needed.
** 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 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) 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: 2015-04-01
Reproduced with NitroPDF. Win 7 Pro 64-bit Version: 5.0.0.0.alpha1+ (x64) Build ID: f3375fa07f27bd2ade519af3c07d69040d10eaa9 TinderBox: Win-x86_64@42, Branch:master, Time: 2015-04-22_23:38:50 Locale: fi_FI
** 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.5 or 5.2.1 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-20160920
Dear Rainer Bielefeld Retired, 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 Rainer Bielefeld Retired, 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
Computers got faster in the last 13 years so the performance doesn't stink as much; but you still do have those gradients. In my recent world it *looks* right in the exportlibo.pdf reloaded. But yeh it's the 4 linear fills and ellipsoid fill (at the back) and Poppler is converting them into hundreds of elements.