[Openicc] Google Summer of Code 2011: The Common Printing Dialog and Color Management
Hal V. Engel
hvengel at gmail.com
Mon May 16 10:41:36 PDT 2011
On Monday, May 16, 2011 12:10:55 AM James Cloos wrote:
> >>>>> "HE" == Hal V Engel <hvengel at gmail.com> writes:
> HE> In addition, if the user is using a remote print server there is no
> HE> way to get the profiles used by CUPS without doing some tricks in
> HE> the servers installation/configuration to make this possible.
> How does this fail?
There is an API for getting a list of profiles (and other info) that are
configured in the PPD. There is no API call to get the actual profile for soft
proofing or any other purpose.
> Or, instead of "a remote print server", do you mean
> to write "a chain of print servers"?
No any print server not located on the users machine is a remote server. On
the users machine profiles can be retrieved by simply reading them from the file
system. This is not possible on a remote server.
> There is no good reason to point cups clients at localhost if the spool
> is actually on another box. lpoptions should specify the remote spool
> as one's default printer in such cases. And with that, both the CUPS
> API and http over port 631 should give direct access to the PPD.
Direct access to the PPD is already supported and this makes it possible to
get a list of CUPS configure profiles (IE. CUPSICCProfile entries). Oyranos
apready does this. But on remote print servers there is no way to retrieve
one of these profiles for things like proofing. HTTP over port 631 does not
expose the profiles unless you create a sym-link from the dirrectory that is
visible using http and port 631 to the profiles directory. At best this is a
hack but it would allow us to create a "retrieve proofing profile" API for
prototyping purposes without too much effort so that how all of this works from
a user prespective could be tested.
Hope that helps.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openicc