[Openicc] Actually getting color managed printing to work

[edmund ronald]

Richard,

 I think the profile stuff happens in CUPS upstream from Gutenprint - this
is a raster driver which doesn't know about colorspaces. So Gutenprint
won't be reading profiles. Robert may have something different to say.

 My belief, confirmed by today's phone conversations is that CUPS knows a
lot about profiles though, and performs profile conversions on input data
when asked nicely.

 More pertinently , if Gutenprint writes XML (dumps its presets), it is
probably being called to print a target which means that the image is
DeviceRGB o DeviceCMYK -no input profilein sight and indeed none available
yet.

 Of course you could want Gutenprint to embed the written XML in some
available profile, but that is a long time after the print has dried and
been measured, so you have no reason to print again, so why ask Gutenprint?

Edmund


On Sat, Jan 28, 2012 at 10:04 PM, Richard Hughes <hughsient at gmail.com>wrote:

> On 28 January 2012 19:56, edmund ronald <edmundronald at gmail.com> wrote:
> > So, my suggestion would be that you write the code to embed and to
> unembed
> > the XML in profiles, and you task us structure the XML itself in ways
> which
> > would help you, but let  us momentarily define a way we can work now with
> > "naked" XML and no superstructure when no profiles are involved.
>
> Sounds like a fair deal. Do you want a library to use, or just provide
> a couple of lcms2 example snippets that can be licenced as
> BSD/GPL/whatever for copy/pasting? Maybe a command line utility might
> be easier. The cd-fix-profile utility already allows you to add random
> metadata to profiles, although a simpler utility might be better. Let
> me know what you would prefer.
>
> Richard.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openicc/attachments/20120128/8577a4ce/attachment.html>