[Openicc] meta data in test chart

[Kai-Uwe Behrmann]

Am 21.01.11, 08:09 -0700 schrieb Chris Murphy:
> On Jan 20, 2011, at 10:00 PM, Kai-Uwe Behrmann wrote:
>> I think we have to do a cut here. IMO it would be straight forward to 
>> just care about settings being colour related. After all that sounds to 
>> me like what you want with the calibration "recipe".
>
> I think restricted the shareable package to that of just strict color 
> related settings is a mistake. If someone is using a thick media, then 
> paper feed or platen adjustments are obviously necessary to properly 
> reproduce the proper printing condition. If such settings are straight 
> out not in scope for embedding in the output device profile, then I'd

It is possible to embed even non color data. But not as a replacement 
for a full PPD. The transportation inside the meta tag is completely 
neutral. So some few additional "paper feed or platen adjustments" are not 
a problem. The profile selection is triggerd by the ranking table from the 
driver dedicated component inside the CMS. The "paper feed or platen 
adjustments" would be just ignored.

> And really, a particular set of settings is only valid for a particular 
> PPD. Maybe nothing changes as the PPD version changes, but perhaps

If the version changes and is color related then the ranking table decides 
if thats important or less interessting.

> something does change that relates to color and then the settings aren't 
> valid. So again I think the package that contains PPD, settings, ICC 
> profile, calibration, is a better way to transport and share. It's 
> easier, more intuitive, more reliable. Otherwise you get situations 
> where users have the correct settings, different driver version, don't 
> have a calibration file, and now they can't actually reproduce the 
> printing conditions.

For me printer setup, read actual PPDs, and ICC profiles do not belong 
into one package in the CMS level. There are situation, when it makes 
sense to have both independently installed, ... for instance a custom 
paper profiled for a already installed printer.

If someone likes optionally to share all related data, inclusive scripts 
to run in the end Argyll for profiling, inside a distribution package, 
thats fine but not much related to the methods used inside a CMS to 
automatically select a ICC profile for a given device.

> Chris Murphy

kind regards
Kai-Uwe Behrmann
-- 
developing for colour management 
www.behrmann.name + www.oyranos.org