• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Remote proofing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Remote proofing


  • Subject: Re: Remote proofing
  • From: Henrik Holmegaard <email@hidden>
  • Date: Sun, 14 Mar 2004 09:08:27 +0100

Bye the bye after wrapping up on the Mac I dropped by the basement carpentry yesterday evening to clear the workbench and frame the second quote.

The first quote dates from the last disagreement in 2001 when the U.S. position for Encapsulated PostScript came to light.

So now there are two quotes, the first asking that EPS be made to work and the second asking that multiple destination spaces be made to work.

From 1998 to 2004 the List positions are little changed, except for David who seems to me to have moved from a raster pipeline to a PS / PDF pipeline view.

It's useful to hold on to technology positioning statements because it helps track the MyPhotoshop / MyInkjet / OS RGB pipeline line of argument over time.

In reality this line of argument works the same as the argument for EPS DCS with OPI, that is, the upstream color separator knows best.

The argument has always hamstrung the page designer and the press operator who are powerless to reconcile the upstream color separators' wildly different opinions about the best definition of the printing condition. The upstream color separators are too many and too headstrong to play on the team, and the result of all the opinions of all these headstrong aesthetes is that the page geometry goes south in an anarchy of ink limits and black replacements. And when the page geometry goes south the color separators stalk away saying, I told you late binding doesn't work.

At this point I have to agree with the ECI EN list and with the developer teams that color management is in effect only for the scientific community. One reason is that color separators trained a decade ago are defining the quality criteria without having the remotest idea about the way Adobe and GretagMacbeth application software in fact works. This is why U.S. consultants, U.S. users and a good many developers are all for device links, multiple destinations and other fun stuff. Another reason is that color marketing simply does not want explanations of how things work, of course.

The color separators, if they have it their way, will have Adobe produce implementations which so far outstrip the understanding of those who demand them these features that it is comparable to placing a child in the pilot seat of a moon shuttle. We just ran a thread on the abc of device links, and how many caught the basics? The iQueue manual is a lot more specific about how things really work than any other manual I have ever read, and still there are questions.

On a closing note, a while back Heidelberg research showed that the mode of sharpening had an impact on color appearance, though not a measurable impact. So we will now have an insistent demand from the color separators for the controls to customize the black replacement by image content and by sharpening parameter -:).

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.


  • Prev by Date: Re: Remote proofing
  • Next by Date: Re: Remote proofing
  • Previous by thread: Re: Remote proofing
  • Next by thread: Re: Remote proofing
  • Index(es):
    • Date
    • Thread