https://bugs.kde.org/show_bug.cgi?id=434618
Robert Moerland <rmoerlan...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|4.4.3-beta2 |nightly build (please
| |specify the git hash!)
--- Comment #5 from Robert Moerland <rmoerlan...@gmail.com> ---
I think I can reproduce the behavior, but I'm not a 100% sure given that "jpg
file from the web" allows for some freedom.
I'm testing with Krita 5.3.0-prealpha-703c3eae on Windows 10 and a Dell U2713H
(wide gamut) monitor.
Steps that *did not* reproduce the issue:
- Import / drag and drop tagged sRGB image into Krita. Colors are the same as
(color managed) photo viewer and PS CS 6
- Import / drag and drop tagged AdobeRGB image into Krita. Colors are the same
as (color managed) photo viewer and PS CS 6
- Import / drag and drop untagged sRGB image into Krita. Colors are the same as
(color managed) photo viewer and PS CS 6
Step that *did* (?) reproduce the issue:
- Import / drag and drop untagged AdobeRGB image into Krita. Colors are duller
than the properly-tagged version. Rendering in other software depends on
implementation (assume sRGB profile or assume monitor profile).
My hesitation to fully confirm that I reproduced the bug stems from the fact
that the proposed workaround ("save the resulting image without incorporating
the icc") seems to actually trigger this behavior, if I understand the
workaround well.
--
You are receiving this mail because:
You are watching all bug changes.
