https://bugs.kde.org/show_bug.cgi?id=367832
--- Comment #21 from wolthera <griffinval...@gmail.com> --- We aren't against toggling the default, but we are looking into what the exact bugs and end-user problems are to smoothen the cm workflow out further beyond the new default. * We have seen the firefox difference on a Ubuntu device. * We have NOT seen the firefox difference on either of 2 windows 10 devices and one osx device. * We have seen that Deevad on Linux Mint can get an exact match between firefox when he manages to stick his display profile(generated for his laptop) into the Krita RGB monitor list and selects that profile. * We have in the past seen that if we store the sRGB chunk into a png it will give EXACTLY the same result as a sRGB profile embedded into Firefox. * Boudewijn and Dmitry are currently busy profiling boud's widegamut device to compare Krita and Darktable, because the latter also uses LCMS instead of Firefox's QMS. * You say that images you for print make look washed out until someone changes the image with a non-krita application. As far as I can tell this is a completely different issue, with different things to diagnose. (Who did the conversion to cmyk, what program did the other program use, what was the original rgb profile, what was the final cmyk profile, what type of printer was the print printed on, do you use blackpoint compensation, I might be forgetting a few) -- You are receiving this mail because: You are watching all bug changes.
