Description: So if I convert a file via Microsoft Office the pdf looks different from the one produced by Libreoffice Steps to Reproduce: 1.Open powerpoint File 2.Convert to PDF Actual Results: PDF should look the same as the one produced by microsoft office Expected Results: The PDF looks different than the one produced by MicroSoft Office Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Created attachment 190184 [details] The pdf file produced by LibreOffice
Created attachment 190185 [details] The pdf file produced by Microsoft Office
Created attachment 190186 [details] Original File
The issue is with Impress opening that file, those images renders bad. Not exporting to PDF. But opening with PowerPoint, seems something is wrong with the contrast of those images, they render more light, but they have a negative contrast. Changing the contrast to 0, looks like in Impress. Seems Impress import it like 0 contrast. And there are a lot of objects of the same type with the same name. Please, @Regina could you take a look.
The objects, which render wrong, are rectangles with bitmap fill. The values for contrast and brightness belong to the "a:lum" attribute in ooxml. They are correctly read to maBlipProps in FillProperties. But they are not evaluated in FillProperties::pushToPropMap() in https://opengrok.libreoffice.org/xref/core/oox/source/drawingml/fillproperties.cxx?r=5fd0d769#409 These values should be applied to the graphic in case XML_blipFill, but they are not. There exist no attributes for these values for the rectangle, so they have to be applied to the graphic directly. It is likely, that something similar to lclGreysScaleGraphic in line 579-580 has to be done for contrast and brightness too.
Dear zarifahnaf, 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