[Openicc] GoSoC 2011: CPD and target printing

Hal V. Engel hvengel at gmail.com
Tue May 10 11:56:31 PDT 2011

On Monday, May 09, 2011 11:30:50 AM Alastair M. Robinson wrote:
> Hi,
> On 09/05/11 12:35, Jan-Peter Homann wrote:
> > http://www.freedesktop.org/wiki/OpenIcc/ColorMangedPrintingPath
> > 
> > It would be nice to get some comments on this proposal.
> Unfortunately I lack the time to "get my teeth into this" at the moment,
> but I'll make a few comments in passing if I may.
> Firstly, Print Spool File generation, you list QT printing API, but not
> GTK / Cairo.  Those two will account for the vast majority of "casual"
> printed documents.  PDFs coming directly from applications will, I
> expect, be largely from high-end apps such as Scribus.  Apps with less
> demanding printing needs that implement their own print path will, I
> imagine, continue to print in PostScript for some time to come.

Most of the tool kit print now support a PDF spool path and in most cases this 
path is currently not the default path.  At some point these will move to 
being PFD centric (IE. where PDF is used by default) and most software will be 
sending PDFs to the print servers even low end apps.

I think the distinction between high-end and ordinary app produced PDF spool 
files will be in how well CM is supported.  High-end apps like Scribus are 
capable of producing well formed PDF with full CM support where as ordinary Qt 
(as an example) apps using the standard print pipe line can not.  

> PDFtoRaster modules:
> Both Ghostscript and Poppler have working colour management now, for
> varying values of working.  CUPS has the CUPSICCProfile mechanism, which
> again works today.  Is the consensus that this mechanism isn't flexible
> enough for our needs, or should we design towards it?

The CUPSICCProfile mechanism is printer/driver vendor centric and is suited for 
setting up reasonable factory defaults.  But is lacks flexibility and is not 
well suited for local (IE. by the printer admins and users) use.   I think we 
need to design with extending it in mind so that users and admins have the 
tools needed to setup CM.  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openicc/attachments/20110510/68005703/attachment-0001.htm>

More information about the openicc mailing list