summaryrefslogtreecommitdiff
path: root/src/eom-metadata-reader-png.c
AgeCommit message (Collapse)AuthorFilesLines
2020-01-09enable wayland supportWu Xiaotian1-8/+17
2019-07-14EomMetadataReaderPng: Use built-in SRGB profile for matching cHRM/gAMAVictor Kareh1-5/+40
The values used for sRGB in cHRM and gAMA chunks do not compute to a profile that exactly matches the built-in profile. Catch this case and use the built-in profile instead to avoid color differences. upstream commit: https://gitlab.gnome.org/GNOME/eog/commit/9589430c
2019-07-14EomMetadataReaderPNG: Only build profile from cHRM if gAMA is presentVictor Kareh1-9/+4
It's more likely that such an image had a (stripped) sRGB profile or chunk. And thus rather than trying to build a profile from only half the necessary information, eom should not. https://bugzilla.gnome.org/show_bug.cgi?id=725359 upstream commit: https://gitlab.gnome.org/GNOME/eog/commit/78c0153e
2018-07-17Convert to G_DEFINE_TYPE_WITH_PRIVATE part 2Felix Riemann1-8/+4
origin commits: https://gitlab.gnome.org/GNOME/eog/commit/ffc4137 https://gitlab.gnome.org/GNOME/eog/commit/ad8c963 https://gitlab.gnome.org/GNOME/eog/commit/afa0dc8 https://gitlab.gnome.org/GNOME/eog/commit/119a768 https://gitlab.gnome.org/GNOME/eog/commit/7725a55 https://gitlab.gnome.org/GNOME/eog/commit/80cf422
2013-09-26Migration to lcms2Stefano Karapetsas1-5/+3
Closes #25 https://github.com/mate-desktop/mate-image-viewer/issues/25 See https://git.gnome.org/browse/eog/commit/?id=3c3a835
2012-09-04Fixed incorrect fsf addresses. Closes #4.Steve Zesch1-1/+1
2011-11-06inicialPerberos1-0/+648
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-11 18:13:25 +0000