[RFC wayland-protocols] Color management protocol
Graeme Gill
graeme2 at argyllcms.com
Wed Dec 14 07:27:13 UTC 2016
Carsten Haitzler (The Rasterman) wrote:
> On Mon, 12 Dec 2016 18:18:21 +1100 Graeme Gill <graeme2 at argyllcms.com> said:
>> The correct approach to avoiding such issues is simply
>> to make both aspects Wayland (extension) protocols, so
>> that Wayland color management and color sensitive applications
>> have the potential to work across all Wayland systems,
>> rather than being at best balkanized, or at worst, not
>> supported.
>
> "not supported" == sRGB (gamma).
No, not supported = native device response = not color managed.
> render appropriately.
> most displays are not
> capable of wide gammuts so you'll HAVE to handle this case no matter what.
I've no idea what you mean.
> either compositor will fake it and reduce your colors down to sRGB, or your
> apps produce sRGB by default and have code paths for extended colorspace
> support *IF* it exists AND different colorspaces are natively supported by the
> display hardware.
No compositor is involved. If the application doesn't know
the output display profile, then it can't do color management.
Graeme Gill.
More information about the wayland-devel
mailing list