One thing we are working on at Adobe, that fits into this work, is a standard way to have printer manufacturers provide an actual ICC profile for their device that can be used as a real world "Output Intent". Without such a profile, and with the increase usage around host-based CM, we are finding too many color shifting issues on various devices that expect colors to be "left alone". In addition, we believe that information about rendering intent preference are also useful.<div> <br></div><div>So before you go hacking around the PPD format, you probably want to involve the various printer manufacturers and folks such as us, who are producing the PPDs that are distributed with the various OS platforms and devices, and whose applications also need to work with them.</div> <div><br></div><div>Leonard Rosenthol</div><div>Adobe Systems<br><div><br></div><div><br><div class="gmail_quote">On Sun, May 16, 2010 at 6:03 AM, 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;">Hello,<br> <br> the CUPS backend needs to tell Oyranos, which PPD colour related entries a PPD has. These entries are used to select a meaningful user configured ICC profile.<br> <br> Could you imagine a PPD entry, which solely lists all colour related entries? Something like:<br> *colourKeyWords: "ColorModel;StpColorPrecision;MediaType;StpQuality;Resolution;StpInkSet;StpInkType;StpBrightness;StpFineBrightness;StpContrast;StpFineContrast;StpSaturation;StpFineSaturationStpImageType"<br> Note this example is incomplete.<br> <br> A disadvantage might by that it has to be included into every PPD. For a driver with a large number of supperted printers and hence many PPDs like the Gutenprint one, it would mean to repeat that stuff. The advantage is a included PPD entry would be very simple to parse along the CUPS delivered PPD.<br> <br> Would this path be acceptable for foomatic, Gutenprint and hplib and other vendors?<div class="im"><br> <br> <br> kind regards<br> Kai-Uwe Behrmann<br> -- <br> developing for colour management <a href="http://www.behrmann.name" target="_blank">www.behrmann.name</a> + <a href="http://www.oyranos.org" target="_blank">www.oyranos.org</a><br> <br> <br></div> Am 19.08.09, 11:59 +0200 schrieb Kai-Uwe Behrmann:<div><div></div><div class="h5"><br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Am 19.08.09, 11:16 +0200 schrieb Till Kamppeter:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Kai-Uwe Behrmann wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> What I do not know is, how to distinct the colour related PPD options from<br> the non relevant to make selection dependent on say "gamma" but not on<br> "paper size". Would you know a way how to select ppd_attr_t attributes<br> according to their influence on colour?<br> </blockquote> <br> Principally one cannot read from a PPD option whether it influences color or<br> not.<br> </blockquote> <br> This will it make harder to get PPD to ICC profile mapping outside of the<br> CUPS cupsICCProfile scheme. The need of root access to do proper colour<br> management is yet clearly a limit.<br> <br> On the other side Oyranos needs to know if a PPD option or attribute is<br> relevant for colour or not to do CM configuration outside of the<br> cupsICCProfile scheme.<br> <br> E.g. a user printing to remote printer or on a system without root rights<br> she can not locally assign a ICC profile to a given PPD in the Oyranos<br> DB and keep flexibility without complicated tweaking. But exactly that was<br> the goal we where aiming at in this years GSoC projects.<br> <br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> ICC profiles can be associated to choices of up to three options, by default<br> to ColorModel, MediaType, and Resolution:<br> <br> *cupsICCProfile ColorModel.MediaType.Resolution/Description: "filename"<br> *cupsICCProfile RGB.GlossyPhoto.1200dpi/High-Quality Photo on Glossy Photo<br> Paper: "Acme-PhotoStar-RGB-GlossyPhoto-1200.icc"<br> <br> Instead of MediaType and Resolution two other options can be used with<br> definitions like:<br> <br> *cupsICCQualifier2: Quality<br> *cupsICCQualifier3: ImageType<br> <br> See <a href="http://www.cups.org/documentation.php/doc-1.4/spec-ppd.html" target="_blank">http://www.cups.org/documentation.php/doc-1.4/spec-ppd.html</a><br> </blockquote> <br> Yes thats the next stage to support in order get the backend functional<br> with cupsICCProfile.<br> </blockquote></div></div><div><div></div><div class="h5"> _______________________________________________<br> openicc mailing list<br> <a href="mailto:openicc@lists.freedesktop.org" target="_blank">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></div>