[Openicc] Printing Plans GhostScript / sRGB / ICC
James Cloos
cloos at jhcloos.com
Fri Mar 4 12:05:11 PST 2011
>>>>> "CM" == Chris Murphy <lists at colorremedies.com> writes:
CM> I'm just shaking my head...I don't have a coherent response to a PPD
CM> that looks like such utter bollocks.
All of the postscript colour lasers I looked into work that way.
And the docs show that the (usually pcl-generating) doze drivers offer
the same options.
CM> If this is a common PPD, we have our work cut out for us on another
CM> front which is what options should and and should not appear in PPDs.
Why shouldn’t they? The out of box defaults are sane for most users.
The ability to choose between expensive CMY or inexpensive K for RGB
gray is clearly a feature demanded by users (using CMY for gray costs
more than five times as much USD than using K, but gives noticeably
better results in photographs and the like).
Remember that papers (usually, I’m sure, due to author naïveté)
frequently use images where a vecotr graphic should have been used.
And when so they are essentially always in DeviceRGB. So you can’t
just say «use CMY for images and K for graphics». The users need
to be able to set a default, but still override that default on a
per job basis.
The manuacturers of RIP printers have now had, what, twenty years or
so to figure out what controls the users want and how to present them.
And for cups-based print flows, the only way *to* do those per-job
overrides is via PPD options.
(The PPDs use setpagedevice postscript snippets; the printers generally
also support using PJL to set those options.)
I just do not understand the complaint....
-JimC
--
James Cloos <cloos at jhcloos.com> OpenPGP: 1024D/ED7DAEA6
More information about the openicc
mailing list