[Openicc] colord 0.1.0 released!
Jan-Peter Homann
homann at colormanagement.de
Sun Jan 16 12:18:18 PST 2011
Hello Richard,
I´m not a developer, so may be my questions are in some cases a little
bit simple:
What is a device ?
for colormanagement in the printing chain, the printer profile has to be
assigned to combination of device/ink, paper and driver settings. How do
you solve this with colord / CUPS ? (predifined CUPS queues for every
combination of (device/ink, paper and driver settings?)
Where to apply the color transformation from source profile to printer
profile ?
- colord ?
- CUPS ?
- OS ?
- Printer driver ?
Where is the rendering intent from source to printer profile specified ?
- colord ?
- CUPS ?
- OS ?
- Printer driver ?
What kind of data format is supported to be colormanaged in the printing
stream ?
- raster only
- PDF ?
If PDF, where are the color transformations for all PDF content parts
applied ?
Control slug possible ?
Is there any way to read, the current colord settings for a CUPS queue,
to create a control slug on the print out, to document the settings from
which the print has been created ?
Best regards
Jan-Peter
Am 13.01.11 13:29, schrieb Richard Hughes:
> First, some background: colord is a project I've been working on since
> Christmas.
>
> It is a simple system daemon that will be used by GCM and CUPS to
> manage per-system device-profile mapping.
>
> If you want to try it out with CUPS right now, you'll have to use our
> development tree http://gitorious.org/cups-colord and be sure to
> switch to the 'icc' branch. When we've got all the different options
> and overrides worked out we'll of course push the patchset back to
> CUPS upstream. Tim Waugh has been doing most of the CUPS work, whilst
> I've been working on the colord project.
>
> colord works a lot like colorsync on OSX, so the CUPS changes are
> really quite small.
>
> Checkout the code from http://gitorious.org/colord -- test it, and try
> to break it. The included cd-self-test program gives you some examples
> of what we're testing already. Tim has also built the cups-icc patch
> into Fedora rawhide, which might be an easier way for some people
> rather than to build the whole of CUPS.
>
> If you're only interested in pretty things, there's a screenshot of
> the admin tool here:
> http://gitorious.org/colord/master/blobs/master/doc/screenshot-devices.png
> -- note the admin tool is designed for developers and programmers,
> *not* end users :-)
>
> Comments (and patches!) welcome, thanks.
>
> Richard.
>
> Version 0.1.0
> ~~~~~~~~~~~~~
> Released: 2011-01-13
>
> Notes:
> - Colord is a simple system activated daemon that maps devices to color
> profiles.
> - It is used by gnome-color-manager for CUPS integration and is also
> used when there are no users logged in.
> - The only real user at the moment is CUPS, but GNOME Color Manager
> will start depending on colord when it is included in most mainstream
> distributions.
> - The DBus interface is not set in stone, and the libcolord library
> will have new API added to it as required. If colord needs to break
> public API at this stage for a specific use case, it will.
> - The persistent storage code is not written yet, but that will come
> with the next colord version.
>
> New Features:
> - Add a 'Kind' attribute to the device objects (Richard Hughes)
> - Add a libcolord shared library that can be used in the client tools
> (Richard Hughes)
> - Add an example spec file (Richard Hughes)
> - Add a simple colormgr man page (Richard Hughes)
> - Add a simple GTK test GUI for testing the DBus interfaces (Richard Hughes)
> - Add a simple script to create a test device (Richard Hughes)
> - Add basic DBus interface (Richard Hughes)
> - Add code for the DeleteDevice method (Richard Hughes)
> - Add DeleteProfile() on the main interface (Richard Hughes)
> - Add GetProfileForQualifier() code (Richard Hughes)
> - Add MakeProfileDefault() implementation to CdDevice (Richard Hughes)
> - Add qualifiers to profiles (Richard Hughes)
> - Allow clients to set properties on the objects using SetProperty
> (Richard Hughes)
> - Expose the device created time (Richard Hughes)
> - Fixed typo in ColorManager API description (Tim Waugh)
> - Open the profile using lcms2 after we set the profile filename
> (Richard Hughes)
> - Provide a method to assign an ICC profile to a profile object
> (Richard Hughes)
> - Provide methods for mapping the device ID to the object path (Richard Hughes)
> - Use seporate PolicyKit authorisations for each action type (Richard Hughes)
>
> Richard.
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc
>
--
---------- Please note the new adress --------------
homann colormanagement --------- fon +49 30 611 075 18
Jan-Peter Homann ------------ mobile +49 171 54 70 358
Cotheniusstr. 3 -------- http://www.colormanagement.de
10407 Berlin -------- mailto:homann at colormanagement.de
More information about the openicc
mailing list