Created attachment 55499 [details] Test pdf, exported from Inkscape PDF with opacity exported from Inkscape. Looks OK in PDF viewers. When LODraw imports there is a black rectangle the size of the entire drawing for each opaque object. In this example there are 3 such rectangles. Delete them and only two of the circles remain (not sure why). This is with 3.4.4 release.
Created attachment 55500 [details] Original SVG file, from which the PDF was created.
This is a specific problem peeled out of bug 43806
Behavior is unchanged in 3.5.0b2 on Windows.
behavior is unchanged in 3.5.0r1 on Windows
Reproduced with LOdev 3.5.0beta3 e40af8c-10029e3-615e522-88673a2-727f724 Ubuntu 10.04.3 x86 Linux 2.6.32-37-generic Russian UI
Confirmed on LO 4.2.3.3 / Win7 64-bit.
Created attachment 98041 [details] New opacity test (PDF) To implement PDF opacity features correctly we need to support opacity value setting not only per-object, but also per-group. Actually, we need masking, but per-group opacity will be good too. For example, we have 3 circles drawn one on top of each other. Then opacity applied to this group. Result will differ if we draw one circle with opacity, then draw second circle, then draw third one. Here are examples in SVG and PDF.
Created attachment 98042 [details] New opacity test (SVG)
** 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.3 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-06-08
Confirmed Version: 5.2.0.0.alpha0+ Build ID: 6b232aeecc55f1715bc111e636e36a8e24827efb CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-01-26_07:40:04 Locale: de-DE (de_DE)
** 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
5.4.3.2 x64 win10 confirmed, bug is present
some changes in view in 6.1.0.3 to previous version 6.0.x and before. but bugs are present in svg and pdf.
Created attachment 153607 [details] opcacity import in LO 6.3.0.4 circles in window are not complete, but export to pdf is with full circle and ok in LO 6.3.0.4
Created attachment 153608 [details] import opacity svg in 6.3.0.4 and export to pdf opacity.svg in 6.3.0.4 pdf is now ok in export to pdf
Created attachment 153609 [details] import opacity-test3 svg in 6.3.0.4 and export to pdf svg import of test3 to 6.3.0.4 and export to pdf is ok
color in opacity-test3.svg import in 6.3.0.4 and in pdf is not same like in acro reader and firefox
Dear mathog, 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
Repro 7.3+.
Dear mathog, 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
Essentially an opacity subtest from tdf#43806
As per comment 7, this is using PDFs transparency group feature, which is all very complex; but in this case we've got two symptoms: a) The colour of the overlayed circles b) The big black square My reading of the PDF code is that it: 1) Sets up a graphics state by rendering a 50% black full size rectangle as a softmask - that mask is marked with /S /Alpha - which means it should only ever influence the alpha value. This is marked as a transparency group at one level 2) It then sets the current colour to a pattern consisting of the filled/stroked circle - that's non-transparent; then does a rectangle that happens to be filled with that pattern of the circle - which seems crazy complex. But somehow this pair marked as transparency groups is supposed to come together as the transparent circles. But the symptom (b) of the big black square is I think a screwup in (1) - where the creation of that softmask shouldn't do anything except change transparency; so perhaps we can cure (b) without fully fixing the group setup.
Dr. David Alan Gilbert committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f365a63a4ade102edcaab4fb14b942f169bbd26e tdf#44729 sdext,pdfimport: Pass begin/end Transparency Group It will be available in 26.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.
Dr. David Alan Gilbert committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/56d8b1a916d82df3a8ad32ed4c8f65c3b8c78d45 tdf#44729 sdext,pdfimport: Route transparency group down It will be available in 26.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.
Dr. David Alan Gilbert committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/e7503531396fd7d47eae4887422a61bb4da5d58e tdf#44729 sdext,pdfimport: Add Group elements It will be available in 26.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.
Dr. David Alan Gilbert committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2383fae366c787bc6e08cf5439521674d52fd8c1 tdf#44729 sdext,pdfimport: Hide transparency groups 'for soft mask' It will be available in 26.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.
The black backgrounds are now gone with the patch I've just put in. That patch: a) Hides the rendering of soft masks (which should never have been directly visible) b) Stores a 'group' node marked as transparency - we don't yet do anything with that node to actually get any transparency. Anyway, given the blackness has gone, I'll close this one, and we can follow more on 43806.