[Openicc] Suggested update to "ICC Profiles in X Specification 0.4"

Graeme Gill graeme at argyllcms.com
Wed Nov 16 21:56:03 UTC 2016


Kai-Uwe Behrmann wrote:

> Oyranos maps outputs to Xinerama dimensions. Comparing EDIDs might be a
> better way. An other way would be to describe a API priority in the
> spec. E.g. when Xinerama is available use that numbering, else use
> active XRandR outputs. I would like to see that topic clearer than with 0.4.

I'm currently thinking that I should simply set root window
_ICC_PROFILE atoms only for X11 Screens or Xinerama Screens
if Xinerama is available, and not try and force XRANDR Outputs
into this scheme at all, relying instead on setting the Output
_ICC_PROFILE property. My assumption then is that applications
do one of three things:

 Use XRANDR and the Output _ICC_PROFILE property.
 Use Xinerama and _ICC_PROFILE/_ICC_PROFILE_xxx for the corresponding Screen.
 Use default X11 and _ICC_PROFILE/_ICC_PROFILE_xxx for the corresponding Screen.

(i.e. my current code is set as either XRANDR or
 Xinerama, whereas perhaps I should enumerate both,
 using EDID to match the two in my user display list,
 while the  ICC Profiles in X Specification should
 keep the ICC profile registration completely separate ?)

Graeme Gill.



More information about the openicc mailing list