Re: Panther, sRGB, web browsers
Re: Panther, sRGB, web browsers
- Subject: Re: Panther, sRGB, web browsers
- From: Uli Zappe <email@hidden>
- Date: Sat, 13 Dec 2003 16:56:24 +0100
Am 13.12.2003 um 15:17 schrieb Roger Breton:
So, maybe your right, after all, and I did not understand your choice
of words in the first place? It looks like, in your parlance, the
monitor profiles does correct for individual deviation of my display
from the virtual neutral state that sRGB (for argument sake) describe.
Conceptually, this is right.
Hm, yes, that was what I was trying to say, I don't even see where I
failed to do it, but maybe that's because English is not my native
language. :-/
This is a cold, mathematical process with no intent to correct for any
'ideal' condition. It only gives you a path to go from one metric to
another.
Not sure what you're trying to say here - I didn't talk about anything
"ideal". And trying to convert into a neutral, default state is of
course done by a "cold, mathematical process" - that's what computers
do...
What I mean is simply this:
If I calibrate an input device, let's say my scanner, none of my other
equipment (monitor, printer, ...) plays any role. The calibration
software just compares what the scanner delivers from the IT-8 target
and compares it to what it "should" be numerically. So it takes care
that scanning my images creates "neutral" representations on my
computer.
That doesn't mean I *see* them correctly on my display, though, since
this has its own kind of deviations that the display profile is
supposed to take care of. But the display profile does *not* correct
the raw data of the scanner, but builds on the "neutral" state the
scanner profile creates. So there's two paths involved "to go from one
metric to another", A > B > C. The same is true for my printer with
it's own profile.
This being said, Safari, as a bona fide ColorSync application, should
elect
to make color management in a more explicit way: we should not have to
reverse engineer it to understand how it process colors. If the intent
is to
hide complexity from the average user then it's a success. But that
should
not be the goal. Best example is Photoshop where all color conversions
are
made explicit and under the control of the user.
The things that are the very reason for needing ColorSync at all are
all - imperfect - *hardware* devices (scanners, displays, printers ...)
Nothing about these devices is application specific, so why should a
specific application deal with it? This is a system level thing, so it
should be dealt with on the operating system level. I want correct
colors not only from Photoshop, I also want them from all the other
apps I have. Photoshop still does it in this archaic way where
applications tried to do system-level things because operating systems
weren't evolved enough. Those times should be hopefully gone now.
I can see the need in Photoshop in case you use it for very specific
work flows that are not the default on your computer. But for a web
browser IMHO this would be overkill.
What could possibly be a situation where you'd need these kinds of
settings?
Bye
Uli
________________________________________________________
Uli Zappe, Solmsstra_e 5, D-65189 Wiesbaden, Germany
http://www.ritual.org
Fon: +49-700-ULIZAPPE
Fax: +49-700-ZAPPEFAX
________________________________________________________
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.