[OpenICC] X and colour management

[Craig Bradney]

On Tuesday 08 February 2005 20:58, Bob Friesenhahn wrote:
> On Tue, 8 Feb 2005, Kai-Uwe Behrmann wrote:
> > Am 08.02.05, 12:37 -0600 schrieb Bob Friesenhahn:
> >> On Tue, 8 Feb 2005, Kai-Uwe Behrmann wrote:
> >>> Hardware information API in Xlib:
> >>>
> >>> Reading out the EDID information (as proposed by Egbert Eich) and
> >>> interprete it regarding model information, seems possible. I dont know
> >>> how
> >>> stable this is throughout different implementations.
> >>> I found no way, other than looking directly in the X config file, to
> >>> find out the model name of the grafic card + ID number over Xlib. An
> >>> dedicated API for this informations would be highly welcome.
> >>
> >> Is it really necessary to know the detailed information for the graphics
> >> card and display ID?  It seems to me that what is needed is a way to
> >> accurately
> >
> > My experience with laptops is stick an external monitor in and it should
> > run. As I understand You , the MAC adress is terminal specific. Ok thats
> > fine for static configurations. For the need of most flexibility, and
> > laptops are dayly experience, I expect there would be no way around some
> > kind of hardware identification.
>
> If the user uses different displays with the same model number (common
> occurance in large companies), then it seems that the EDID information
> will not help much.  The MAC address will at least positively identify
> the laptop since MAC addresses are required to be unique across the
> world.
>
> It seems to me that color management is primarily a benefit for well
> managed "static" configurations where all factors are known, and can't
> adequately handle ad-hoc mix-and-match combinations.

It would be reasonable however to expect multiple monitors connected to one 
system. Even with or without them being the same monitor type, each and every 
one of the connected displays would need a different profile if used in a 
colour critical environment.

Craig
Scribus