All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Kai-Uwe Behrmann <ku.b@gmx.de>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
	Joseph Simon <jsimon383@gmail.com>
Subject: Re: [Printing-architecture] Colour Management Schemes for Printing
Date: Fri, 29 Apr 2011 11:34:14 +0200	[thread overview]
Message-ID: <4DBA8616.8000200@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1104290726130.4105@roma.rasena>

Great! This is a really nice overview about how printing color 
managament should look like and what we have now. Also nice to have all 
the links to bug reports, mailing list postings, ...

    Till

On 04/29/2011 07:33 AM, Kai-Uwe Behrmann wrote:
> In preparation of several events I created some slides. Two of them summarise
> usability and design objectives for colour managed general
> printing, which where collectively worked out during OpenICC discussions.
>
> The core of the CMS schemes boils down to
> * avoid asking any questions to users,
> * adhere to existing standards and no new special commands,
> * be compact and modular,
> * use a robust opt-out of colour management and
> * honour device colour calibration state
>
> The slides are in the Printing section of the Device page on ColourWiki. They
> show decision policies during local spool file preparation and highlight the
> device profile selection. The scheme is somewhat wrapped around the Oyranos
> CMS, but should otherwise adhere to the above general principles.
>
> The vendor profile mechanism is not the specific focus in these schemes as that
> is already covered by previous work and in parts in the CUPS documentation. The
> schemes integrate with vendor profiles flawless.
>
> https://www.oyranos.org/wiki/index.php?title=Device_Settings#Printing
>
>
> The original Inkscape drawings are provided below the schemes for easy editing.
> Please consider to share your edits to improve the schemes.
>
>
> Btw. Joseph Simon will obtain a stipend from the Google Summer of Code
> programm to work specifically on a sample implementation for end to end
> print colour management "Color Management for the Common Printing Dialog
> (CPD)".
> http://oyranos-cms.blogspot.com/2011/04/google-summer-of-code-2011-students.html
>
>
> kind regards
> Kai-Uwe Behrmann


      reply	other threads:[~2011-04-29  9:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29  5:33 [Printing-architecture] Colour Management Schemes for Printing Kai-Uwe Behrmann
2011-04-29  9:34 ` Till Kamppeter [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DBA8616.8000200@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=jsimon383@gmail.com \
    --cc=ku.b@gmx.de \
    --cc=printing-architecture@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.