[Openicc] Printing Plans GhostScript / sRGB / ICC

[Jan-Peter Homann]

I believe printer vendors offering non ICC based RGB drivers has one 
main source:
They don´t want the users to control GCR, becuase, this would offer the 
users to easily to print with less ink, or to allow easily other media.
printer vendors make their money from selling ink and nor from selling 
printers...

I agree, that open source printer drivers with cannend ICC profiles have 
the potential to deliver out of the box a comparable quality to closed 
source drivers and open to the users much more potential usecases.

+++

The discussion on how to handle printing DeviceXXX spool data without 
applied "sRGB to printer profile transformtion" is in my eyes a little 
bit strange.

We only have to take care, that the pdftoraster filter can be easily 
configured to print straight forward. What should not be complicated 
both for GhostScript and poppler.

If we are able to transport printer specific options like e.g. duplex 
options beside the PDF spool file, we should also be able to transport a 
flag for turning colormanagement of in pdftoraster filter beside the PDF 
spool file. I don´t see any need to integrate a "color management of 
flag" directly into DeviceXXX PDF files.

best regards
Jan-Peter


Am 01.03.11 23:44, schrieb Chris Murphy:
> Keep in mind by default on Mac OS and Windows for printing, ICC based color management isn't really being used. Both platforms depend on the printer manufacturer supplying black box print drivers that assume some source space (usually sRGB) and internally converting that with proprietary tables. That's the better than 90% use case scenario on both platforms. We're talking about hundreds of millions of users who use these workflows and are generally satisfied. That does not mean no room for improvement, but improvement is not simply done. And the merit of this existing paradigm is that it is really quite simple for the quality you do get. Not perfect but it isn't all just about color.
>
> But it's amusing that it's not ICC based. There's no reason why we couldn't have parity with default ColorSync and ICM solution instead of driver proprietary color. It's just that the manufacturers appear to prefer a black box to do conversions in the driver rather than with ICC profiles in advance of the driver, for whatever reason.
>
>
> Chris Murphy
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc
>


-- 
----------  Please note the new adress --------------

homann colormanagement --------- fon +49 30 611 075 18
Jan-Peter Homann ------------ mobile +49 171 54 70 358
Cotheniusstr. 3 -------- http://www.colormanagement.de
10407 Berlin -------- mailto:homann at colormanagement.de