[Openicc] Proposed "ucmm" display profile configuration convention used by ArgyllCMS.

Hal V. Engel hvengel at astound.net
Mon Jun 2 10:07:41 PDT 2008

On Monday 02 June 2008 09:11:35 am Graeme Gill wrote:
> Kai-Uwe Behrmann wrote:
> > The printer driver does typically not provide a preview. So it is up to a
> > higher level to do that; e.g. kprinter or the application itself.
> But having users navigate to the profiles is poor U/I - they should
> just be able to nominate the printer, just the same was as they shouldn't
> have to specify the display profile all the time (it's implicit
> in the choice of system connected device).

Long term this should be our goal.  Short term our printing systems are not 
advanced enough to support this.  In spite of this we should be designing this 
based on the desired end state rather than designing this to let other 
software fix issues that are caused by shortcomings in the current printing 
software suite.  If we put together a design based on the desired end state 
the shortcoings of the current software will be corrected over time.

> > In case you have the CUPS profiles in mind, applications want access to
> > those printing queue profiles.
> Same argument as above. The names and location of the system connected
> printers profiles is a detail that the user shouldn't have to know in
> the normal course of events.

Again the reason that "applications want access to those printing queue 
profilesapplications want access to those printing queue profiles" is because 
the current printing tools chain does not correctly support color management 
and the applications are doing this work on their behalf.   Long term this 
should become a non-issue.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freedesktop.org/archives/openicc/attachments/20080602/dac7c9f9/attachment-0001.htm 

More information about the openicc mailing list