No subject

-- its right there in the Print Preview
screen.  If you are doing soft-proofing you must do it in Photoshop.
Creating custom ICC profiles
is the other major difficulty -- this used to work just perfectly.
Why break the existing workflows?

The OS centric point of view that the OS will handle it means you have
to go into ColorSync Utility
and try to find out how to associate a custom ICC profile with a
device.   There's no straightforward
way to do this.

On Sat, Nov 14, 2009 at 12:59 PM, Michael Sweet <msweet at apple.com> wrote:
> On Nov 14, 2009, at 2:10 AM, Chris Murphy wrote:
>
> ...
>
> Well if Apple didn't operate like the KGB, as though everything is such a
> huge fricking secret, and clearly and thoroughly documented how things ar=
e
> supposed to work, it would at least make it easier to identify what is
> incorrect behavior, and whose bugs these are.
>
> I'll be the first to admit that our printing documentation isn't up-to-da=
te;
> we're working on it. That said, we try to make as much sample code availa=
ble
> as possible that demonstrates the "right way" to do things on Mac OS X.
> That said, *every* Mac developer and printer vendor has access to Apple's
> engineering expertise via the Apple Developer Connection, so if the exist=
ing
> documentation or sample code isn't enough, please let us know!
>

I've asked quite explicitly via ADC what is the protocol to print with No C=
olor
Management and Application Color Management but haven't gotten answers.
I was able to crawl through header files and find the AP_ColorMatchingMode
flag but there is no documentation.

>
> So, presently we're unable to reliably print profile targets from Photosh=
op,
> using No Color Management (in Photoshop) and Off (No Color Adjustement) i=
n a
> wide assortment of newer Epson drivers. What happens is, I get a complete=
ly
> borked profile target in printed form. Inspection of the PDF spool file
> indicates source=E2=89=A0destination, and thus ColorSync is going to come=
 riding in
> to convert the job.
>
> We are working with both Adobe and Epson on this issue...
>
> Michael, yes, I have no doubt about that. The problem is that these sorts=
 of
> color problems with printing are recurring themes. Epson is not the only =
one
> who has had problems, although they very well may be the worst offender. =
But
> we don't have these kinds of problems on Windows. That should be a WTF
> moment for Apple. Sane people have started to wonder, rationally, if ther=
e
> is something fwrong with the architecture when there are so many recurrin=
g
> problems of this sort, through multiple major revisions of the operating
> system. We've experienced color related problems with Tioga drivers too.
>
> Windows doesn't provide the same level of support for color as Mac OS X, =
and
> to say that Windows doesn't have these problems is a lie - they are just
> hidden from most users since there isn't a "use this profile" option star=
ing
> you in the face every time you print.
> In any case, venting here won't fix things in Mac OS X. =C2=A0Please file=
 bugs
> with Apple so that any issues get escalated and dealt with:
> =C2=A0=C2=A0 =C2=A0http://bugreport.apple.com

I've used the bug report system.  See bug 6503221 that I submitted in Jan 2=
009.
After quite a few emails back and forth, all seemed to agree that there was=
 a
problem.  "Apple and Adobe are working on it" is all since then.  It just
sits as an open issue.

Simple question:  As an "Apple Senior Printing System Engineer" can you fin=
d out
how the No Color Management should work?

Thanks,
Roy Harrington

ps:  I do a third party print driver for Epson printers and various
ICC profiling for this.
I'm familiar with the printing system from the driver point of view as
well as from
application point of view.


>
> ___________________________________________________
> Michael Sweet, Senior Printing System Engineer
>