Created attachment 123819 [details] pptx file, screenshots with both office and libreoffice when I open one office pptx file with libreoffice 5.1.1.3,the color of image included in my pptx file seems to be degraded to 256 color depth.I attached related pptx file and screen shots for your reference.
Confirmed. It seems the PPTX has some kind of color filter applied. We have to find out what it is. There might be a duplicate report, we have to find the keyword. 64-bit, KDE Plasma 5 Build ID: 5.1.1.3 Arch Linux build-2 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8)
Reproduced in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
It is the image itself, which generates problems. Unpack the pptx file and find the image in ppt/media. Open the image in other application. My old PaintShopPro 5 shows the image in same bright way as LibreOffice, whereas Paint.net shows it same as PowerPoint 2010. The reason is, that the image is 32-bit in CMYK color space. There a no filter involved, neither in PowerPoint nor in LibreOffice.
(In reply to Regina Henschel from comment #3) > The reason is, that the image is > 32-bit in CMYK color space. Eek, you are right. I can see the CMYK in Krita: Image - Properties, but the color depth is 8-bit. Regina: what do you think we should do? I could not find a report about general CMYK support. I did find this report about a specific case: bug 102928
The problems with CMYK images are inherited from OpenOffice. I'm no image or color space expert, but to my knowledge a color profile would be needed to get a visual correct conversion. But such profile is individual to a special monitor-printer combination. So a general solution can only be a compromise. And you have to keep in mind, that it is not only a problem, how the image looks on the screen, but you have to consider printing and pdf-export as well.
** 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 dinghao, 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 dinghao, 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
*** Bug 120549 has been marked as a duplicate of this bug. ***
A possible option could be to (re?)use the http://www.openjpeg.org/ library, which seems to me having some level of support for CYMK support[1] since quite some time (2014), and has 2-clauses BSD license[2]. [1] https://github.com/uclouvain/openjpeg/pull/559/files [2] https://github.com/uclouvain/openjpeg/blob/master/LICENSE @Tomaz: any thought on this direction?
(In reply to Gabor Kelemen (allotropia) from comment #10) > A possible option could be to (re?)use the http://www.openjpeg.org/ library, > which seems to me having some level of support for CYMK support[1] since > quite some time (2014), and has 2-clauses BSD license[2]. > > [1] https://github.com/uclouvain/openjpeg/pull/559/files > [2] https://github.com/uclouvain/openjpeg/blob/master/LICENSE > > @Tomaz: any thought on this direction? libjpeg-turbo also supports CMYK, but it leaves colour management as an exercise for the user: https://github.com/libjpeg-turbo/libjpeg-turbo/blob/895287572db62318332a78395a0c07eb86137fd8/turbojpeg.h#L289 "In order to convert between CMYK and RGB, it is necessary to use a color management system (CMS.) A CMS will attempt to map colors within the printer's gamut to perceptually similar colors in the display's gamut and vice versa, but the mapping is typically not 1:1 or reversible, nor can it be defined with a simple formula. Thus, such a conversion is out of scope for a codec library." In that openjpeg commit I see they use liblcms2, which we also have as a dependency.
OpenJPEG is a library for Jpeg2000 images, not JPEG(1). What we probably need is iccjpeg [1] and qcms [2] to properly correct. [1] https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/third_party/iccjpeg/ [2] https://chromium.googlesource.com/chromium/src.git/+/refs/heads/main/third_party/qcms/