Re: Colorsync Utility Source vs Destination
Re: Colorsync Utility Source vs Destination
- Subject: Re: Colorsync Utility Source vs Destination
- From: John Gnaegy <email@hidden>
- Date: Wed, 14 Apr 2004 12:43:14 -0700
How does the system know what the source profile is?
Either the file has an embedded profile, or default profiles are chosen
depending on the color model (rgb, cmyk, lab). Preview, Safari, Mail,
and any Cocoa app using NSImage behaves that way.
In other words, if I want to color manage an application, say Quark 6
for example, but don't want to use Quark's built-in CMS (mostly
because it only handles tiffs and built-in colors)
Depends on how the app handles color so this will vary from app to app.
The behavior I described above applies to the standard behavior of
Cocoa apps.
Ok, now... so what is the difference between all of this and creating
a "filter" in the ColorSync utility?
The ColorSync Filter section of CSU creates filters which can be used
when printing. Filters aren't profiles. Profiles describe the
behavior of a device and/or tweak a device to behave a certain way,
they're tied conceptually to devices. A filter is more like collection
of manipulations you want to save and use again, not necessarily tied
to a certain device.
_______________________________________________
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.