On Mon, 2011-01-17 at 09:56 -0500, Robert Krawitz wrote: > The real issue here is making sure that CUPS and its filter chain > don't modify color data on the way down unless they're told to, and > when they do so, it must be predictable. That's the problem on OS X: > there doesn't seem to be any way to ensure that data from the > application reaches the printer (or driver) unmodified. In other > words, if we send an RGB tuple (97, 38, 108) from an application, we > have no way to guarantee that Gutenprint sees that same RGB value. Isn't that just an issue with the CUPS Raster format? The intended use of colord in the CUPS filter chain is to modify pstoraster so that it asks colord which ICC filename ghostscript should be told to use. All colord is doing is delaying the association between a set of print options and an ICC file so that the user can override whatever comes pre-set in the PPD file. Tim. */
Attachment:
signature.asc
Description: This is a digitally signed message part