In fact I'm not sure on how to handle the sentence that "PDF context
has no colorspace". This is true because PDF contexts can embed for
example multiple images with each image having a different color
space.
Very true. I don't dispute the validity of the statement regarding
PDFs, I'm merely disappointed that there's no way to obtain the actual
destination space through the imaging system that will eventually have
to dig that info up anyway. Even more disappointed that there's not a
simple off switch for an almost fully deprecated API that still relies
on FSSpecs. I'm beginning to see why Adobe's the only one out there
doing this ;)
As far as I remember for your problem, you're using that for your own
purpose (debugging) ? so you can find the colorspace associated to
your printer in the colorsync profile utility, with its path beside it
(or dig it from the device list like you said, but maybe manually
should be enough ?)
Nope, not for debugging; for printer profiling. The space must be
obtained programatically on behalf of non-savvy users, so it looks
like it's going to be incredibly messy.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartz-dev/email@hidden
