Yes, but in the same way profiles are very static and some apps need to be able to dynamically create gamut mappings and render into devicespace.<div><br></div><div>Edmund<br><br><div class="gmail_quote">On Fri, May 13, 2011 at 8:48 PM, Kai-Uwe Behrmann <span dir="ltr"><<a href="mailto:ku.b@gmx.de">ku.b@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Am 13.05.2011 11:46, schrieb Jan-Peter Homann:<br>
<div class="im">> Comments inline<br>
><br>
> Am 13.05.11 16:35, schrieb Kai-Uwe Behrmann:<br>
>> Am 13.05.2011 07:09, schrieb Jan-Peter Homann:<br>
</div><div><div></div><div class="h5">>>> 4) What are the roles of Colormanagement Frameworks like e.g. Oyranos<br>
>>> or g-c-m / colord when it comes to the creation, exchange, download<br>
>>> and GUI representation of printing presets with assigned ICC-profiles ?<br>
>>><br>
>>> Jan-Peter:<br>
>>> So far as I now, both Oyranos and g-c-m / colord have till today not<br>
>>> published a concept for a direct interface to the printing GUI<br>
>>> concerning media and color options. (Please correct me, if I´m wrong..)<br>
>> Hmm<br>
>> <a href="http://www.freedesktop.org/wiki/OpenIcc#PPDcolouring" target="_blank">http://www.freedesktop.org/wiki/OpenIcc#PPDcolouring</a> was proposed to<br>
>> mark colour options as is now supported by Gutenprint and used by the<br>
>> Oyranos CUPS module,<br>
>> the ICC meta tag, which among others I reviewed, It's part of the<br>
>> specification since a while and Oyranos makes extensive use of that<br>
>> since quite a while,<br>
>> <a href="http://www.oyranos.org/wiki/index.php?title=Device_Settings#Printing" target="_blank">http://www.oyranos.org/wiki/index.php?title=Device_Settings#Printing</a> for<br>
>> architecture plans including usability constraints and schemes<br>
>> a GSoC project to distribute the ICC device profiles over the<br>
>> internet and<br>
>> an other one to integrate these concepts into CPD, both are mentored<br>
>> by me<br>
>><br>
>> What else do you miss?<br>
><br>
> Jan-Peter<br>
> So far as I understand the mentioned documents, the Oyranos workflow<br>
> is based on the PPDs describing the available settings for the printer.<br>
> In the printing GUI (e.g. CPD) the PPD is parsed and the aviailable<br>
> options are presented to the end user.<br>
<br>
</div></div>To actual my knowledge, this is all what can be obtained from the print<br>
configuration through CUPS.<br>
<div class="im"><br>
> Frm my experience, the PPD concept is a very static concept and it is<br>
> very hard to implement a workflow, where the use can download and<br>
> install ICC-printer profiles with assigned driver settings and sees<br>
> the result instantly in the printing GUI (e.g. CPD)<br>
<br>
</div>We will just rely on the PPD for obtaining enough meta data and possibly<br>
adapt the PPD options to match the actual selected ICC profile.<br>
<div class="im"><br>
>>> We have to consider, that both Oyranos and g-c-m/colord are mainly<br>
>>> "color management per computer" concepts. Printing is often a "color<br>
>>> management in the network" process, where e.g.<br>
>> How does you come to this impression?<br>
>> I have always prefered existing standards and usage of the actual<br>
>> systems capabilities.<br>
>> For Xorg it means that by using Xatoms we preserve network transparency.<br>
>> For PDF printing by adhering to PDF/X3 we are in theory not bound to a<br>
>> single host.<br>
>> These decisions where specially considered to preserve network<br>
>> capabilities.<br>
>><br>
><br>
> Jan-Peter<br>
> I currently see not a concept for Oyranos, if driver settings and<br>
> printer profiles are updated on print server application, that this<br>
> information can be routed to all Oaranos instances on clients for the<br>
> print server.<br>
<br>
</div>Oyranos can have system settings for all users on a local host or a<br>
local network. The internet repository is targeted at sharing worldwide.<br>
<div class="im"><br>
>>> printer-settings with assigned ICC-profiles ("ICC-driversettings") are<br>
>>> installed at the print server side and should be available to all<br>
>>> printing clients without the need for manual installation.<br>
>>> On the other hand, we have often the case, that print client and print<br>
>>> server are running only on one local machine.<br>
>>> For handling both use cases, I would recommend, that installation and<br>
>>> management of "ICC-driversettings" are made always at the print server<br>
>>> side.<br>
>> While that sounds at first not that bad, it brings a lot of requirements<br>
>> and makes that not easy except for vendor profiles.<br>
>><br>
><br>
> Jan-Peter<br>
> If it works with vendor profiles / settings, it should work in the<br>
> same way for profiles / setting which are installed later on the print<br>
> server.<br>
<br>
</div>This would need editing the CUPS server side PPD.<br>
<div class="im"><br>
> So far as I understand the IPP concepts from PWG, we already have a<br>
> dafted standard how a print server commicates the installed profiles<br>
> and settings to a client without the usage of a PPD.<br>
<br>
</div>reads good<br>
<div class="im"><br>
>>> The role of CPD is to create a GUI for the media and color options<br>
>>> build from "ICC-driversettings" available at the print server and to<br>
>>> connect to Oyaranos or g-c-m/colord for communicating the choosen<br>
>>> "ICC-driversetting.<br>
>> The server options are generated typically from the PPD. The local<br>
>> interaction is mainly for per user interaction and ICC settings.<br>
> Jan-Peter<br>
> I want to get rid of the PPDs for color and media settings, because I<br>
> think they are not flexible enough<br>
<br>
</div>Having the spool PDF completely self contained would be really great.<br>
<div class="im"><br>
kind regards<br>
Kai-Uwe<br>
--<br>
@LGM<br>
_______________________________________________<br>
</div><div><div></div><div class="h5">openicc mailing list<br>
<a href="mailto:openicc@lists.freedesktop.org">openicc@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/openicc" target="_blank">http://lists.freedesktop.org/mailman/listinfo/openicc</a><br>
</div></div></blockquote></div><br></div>