ðòïåëôù 


  áòèé÷ 


Apache-Talk @lexa.ru 

Inet-Admins @info.east.ru 

Filmscanners @halftone.co.uk 

Security-alerts @yandex-team.ru 

nginx-ru @sysoev.ru 

  óôáôøé 


  ðåòóïîáìøîïå 


  ðòïçòáííù 



ðéûéôå
ðéóøíá












     áòèé÷ :: Filmscanners
Filmscanners mailing list archive (filmscanners@halftone.co.uk)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[filmscanners] Re: OT: RE: Get a Mac... or a VAX?



On Tue, 22 Oct 2002 06:12:40 +0100  Major A (andras@users.sourceforge.net)
wrote:

> That's right, you can see that even if you just think of
> ColorSync. It's been there in MacOS for a long time. Now look at
> Microsoft -- they are member of the ICC, therefore they are OBLIGED to
> implement ICC software at the OS level (according to the ICC
> agreement), which to this day they have failed to do. Instead, each
> image program, each scanner and printer driver brings along its own
> copy of a colour management system.

Not really true nowadays. Windows (since 98SE, NT excepted) does have CM at
the OS level, but what is also built in is Windows default Sophist
assumption that all untagged images are sRGB. This enables modern s/w and
printers and scanners to all work to a common colourspace by default. You
can override it and use another space if you wish. However some 'default
sRGB' devices can only do sRGB.

I can see why MS did this, as the only way to belatedly tack CM on to a
system which has masses of legacy s/w and h/w which knows nothing of CM.
But it is not kosher.

Regards

Tony Sleep - http://www.halftone.co.uk
Online portfolio & exhibit + film scanner info & comparisons
----------------------------------------------------------------------------------------
Unsubscribe by mail to listserver@halftone.co.uk, with 'unsubscribe 
filmscanners'
or 'unsubscribe filmscanners_digest' (as appropriate) in the message title or 
body



 




Copyright © Lexa Software, 1996-2009.