If anyone wonders why the colors look washed out, inverted, or whatever, it's because this image uses the CMYK colorspace instead of the sRGB and not all image viewers handle this difference gracefully.

Btw, it might be beneficial to add a (warning) tag for images using a non-sRGB colorspace, in the same vein as jpeg_artifacts.

Roadi said:
If anyone wonders why the colors look washed out, inverted, or whatever, it's because this image uses the CMYK colorspace instead of the sRGB and not all image viewers handle this difference gracefully.

Btw, it might be beneficial to add a (warning) tag for images using a non-sRGB colorspace, in the same vein as jpeg_artifacts.

Added cmyk.

moonian said:
Added cmyk.

I think CMYK colorspace is more of a 'fault' than anything, so shouldn't the tag type be changed to reflect this?

Roadi said:
I think CMYK colorspace is more of a 'fault' than anything, so shouldn't the tag type be changed to reflect this?

It isn't a problem at all for an image to be saved in CMYK colorspace.

moonian said:
It isn't a problem at all for an image to be saved in CMYK colorspace.

Neither are jpeg artifacts a problem, per se; they are just a result of the lossy compression algorithm, after all. :P
But anyway, I get your point.

Roadi said:
Neither are jpeg artifacts a problem, per se; they are just a result of the lossy compression algorithm, after all. :P
But anyway, I get your point.

Lossy is a fault, as the result is irreversible.

moonian said:
Lossy is a fault, as the result is irreversible.

Idd.
Perhaps uncompressed_file would make a better case.

CMYK image is still discouraged regardless the status of the tag.

We do also have non-standard_color_space (but it's very underused).