path: root/config
diff options
authorDoug Newgard <>2013-06-22 13:21:35 +0900
committerCarsten Haitzler (Rasterman) <>2013-06-22 13:21:35 +0900
commitf6527c70d63844850e442da0b44689fcaf52d128 (patch)
tree60421d2811cbbd09c40558e57361f7e7f4f827f7 /config
parent216b8932dafbd8cae58dfc117412ded88adfd31c (diff)
fix png's with icc profile oddness
I'm sure some of you have seen the warnings generated by libpng 1.6: "known incorrect sRGB profile". Now, this is no big deal, it's just a warning, but I still wanted to look into it further. By my count, there are 800 png files in Enlightenment, of which only 6 have embedded iCC profiles, all from HP. The rest are sRGB colorspace, but do not include a profile. There are some good arguments for this ( and since this seems to be the default, I've attached the 6 files with the profiles stripped out. As you can see, it doesn't change the image or the colorspace, it just leaves the calibration up to the end user's system. I haven't been able to find just what's wrong with the HP iCC profile being used that the authors of libpng don't like, but it makes sense to standardize the way profiles are handled anyway. And it has the nice side effect of silencing warnings, even if the Debian/Ubuntu users aren't likely to see them for a couple of years. I can just change the iCC profile instead if you would prefer. I've seen multiple people recommend the Argyll sRGB profile, which is still "sRGB IEC61966-2.1" and is public domain.
Diffstat (limited to 'config')
-rw-r--r--config/default/enlightenment-default.pngbin9183 -> 6871 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/config/default/enlightenment-default.png b/config/default/enlightenment-default.png
index 9c08ee2a5..1f33694ac 100644
--- a/config/default/enlightenment-default.png
+++ b/config/default/enlightenment-default.png
Binary files differ