RE: The MESS at the PRESS campaign
RE: The MESS at the PRESS campaign
- Subject: RE: The MESS at the PRESS campaign
- From: Henrik Holmegaard <email@hidden>
- Date: Sun, 11 Apr 2004 11:27:50 +0200
"Darrian A. Young" <email@hidden> writes :
>There is no reason to involve either the rest of the workflow or
PDF/X-3
>into the discussion of the simulation to printer transform. They are
>completely unrelated issues.
Because a device link is device dependent in and device dependent out
and thus takes the numbers in the data space while disregarding their
color appearance, and because a device link either does not contain
correct metadata about the names of the device profiles in the original
concatenation written into the Profile Sequence tag or does not contain
the Profile Sequence tag at all, then it follows that a device link is
as caring of precision conversion as a T Rex is of carving meat. In
other words a device link lunges blindly at anything and everything
(rather like a List debate -:)).
Pre-document Positioning :
Because a device link will literally tear into anything in sight, then
if you place it in front of the page design you get blind (double)
conversions for objects in the data space of the first data space in
the link sequence (and not for objects in other data spaces whether
untagged or tagged with ICC device profiles or PostScript Color Space
Arrays).
Document Positioning :
Because a device link will ignore device to PCS information and will
not remap device values to PCS, Open File dialogs will not be able to
show a preview of the disk-based data and after the CMM has completed
its calculation the RAM-based object cannot be displayed on the studio
monitor or studio printer.
Post-document Positioning :
Because a device link will ignore the AtoBx backward rendering
information in ICC device profiles (and the ToCIE forward rendering
information in PostScript Color Space Arrays) CIEBased which includes
ICCBased is ignored in PDF 1.3+ and CIEBased is ignored in PostScript
which is to say that you get the Texas Chain Saw Massacre.
>Regarding Bill Whitfield's concerns - please do not interpret my
message
>as some sort of anti-ICC campaign - I do a lot of work with ICC
>solutions.
>Regarding Steve Upton's concerns, some are answered in the above, but
>there are a couple of things I would like to include.
I believe the European Color Initiative project is affiliated to the
International Color Consortium and I also believe the charter says
something about speaking up for open standards device independent
workflows. For this reason it is useful to recapitulate the basic
differences between ICC device profiles, ICC device link profiles,
PostScript Color Space Arrays and Color Rendering Dictionaries, and
proprietary device links. I still don't see in your post a technical
understanding of these differences and the deployment differences they
entail.
So I will maintain that there are many companies offering proprietary
solutions who are not coming clean about the capabilities of their
products, and I will maintain that this applies both to companies
offering proprietary technologies and to prepress and printing
companies deploying proprietary technologies to rip off (no pun
intended) studio image designers and studio page designers who work in
ICC application software.
When I began researching in the late 1990s, it used to be the whispered
with dismay among ICC developers in Germany that customers could not
obtain an advertising job for high volume rotogravure unless the
customer owned an Iris and a "4D transform proofing interpreter". Today
there are ICC profiles for rotogravure printing on the European Color
Initiative web, ISO 12647-4 has been extended to cover rotogravure, and
the carpet has been pulled from under the proprietary people even in
the rotogravure market to make way for open standards workflows from
the image design studio through the page design studio to the prepress
and press manager's Adobe PostScript 3 proofing and production
interpreter. Let's have a bit more enligthenment in other regions of
the world, including California and Colorado -:).
Thanks,
Henrik
_______________________________________________
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.