[Openicc] [Gimp-print-devel] Looking ahead to 5.3
Hal V. Engel
hvengel at astound.net
Sun Oct 19 12:37:37 PDT 2008
On Sunday 19 October 2008 07:50:03 Till Kamppeter wrote:
> Robert Krawitz wrote:
> > From: "Hal V. Engel" <hvengel at astound.net>
> > Date: Sat, 18 Oct 2008 09:28:34 -0700
> >
snip
> > Also work is underway to add CM to the print work flow in a way
> > that makes it driver independent. It will take a while for this to
> > appear and then more time for it to mature but it will eventually
> > be part of the new PDF based printing work flow. Once that is in
> > place CM printing will become available to all applications running
> > on *nix platforms.
> >
> > I think it's time we determine exactly what role Gutenprint (or the
> > driver, in general) should take in the overall color processing
> > workflow -- what our responsibilities should be and what features we
> > should offer.
snip
> > So the big question I think we need to answer is, exactly what
> > facilities should Gutenprint provide, what (if anything) it should
> > completely hide from the user, and what should applications (or at
> > least the CMS) do?
>
> Color management should get standard part of the printing subsystem of
> Linux. So we should discuss it at OpenPrinting, with participation of
> printer manufacturers, Mike Sweet, Ghostscript developers, application
> developers, ...
>
> Till
I agree with Till that this should be worked on the OpenPrinting list. There
are some parts of this that should be part of the general printing system and
it's UI and also parts that belong to those who are writing the drivers and
those who work on the color management end. For example the drivers should
eventually supply a set of base profiles for each device much like Epson does
for their printers for Windows/Mac users (IE. the ones you can download from
their web site). Another example of work that needs to be done outside of
the printing system is that we currently do not have a way to create n-color
(where n > 4) profiles/separations for optimal handling of printers with >4
inks (Graeme from ArgyllCMS is working on this but it is a complex issue)
although lcms can currently handle n-color profiles. The various parts of the
CM printing work flow need to be defined and responsibility for each part
needs to be worked out (IE. what is a general thing that needs to be part of
the base printing system and what do the drivers need to do/supply to make
that work...). I will encourage those interested that are part of OpenICC to
join the OpenPrinting list so that there is participation by the CM community.
Till,
A side note. One of the OpenICC guys, Kai-Uwe Behrmann, started looking at
the GhostScript issue you ran into and was having difficulties getting a
handle on the code (complex interface and not much documentation). I
suggested that he contact you. Just in case he has not could you follow up
with him?
Hal
More information about the openicc
mailing list