[Openicc] GoSoC 2011: CPD and Color Management

[Ann McCarthy]

So you are proposing that 'ink settings' are one of the printer setup
characteristics that exist in a workflow data container, and then also can
be pulled into a profile as it is built using the particular ink settings.

How about a function that supports "selectively initialize the printer setup
for this new profile - including ink settings -- from this x existing
profile"?

Best regards,
Ann L McCarthy
Imaging Systems R&D
Lexmark International, Inc.



On Tue, May 3, 2011 at 4:50 PM, edmund ronald <edmundronald at gmail.com>wrote:

> Ann,
>
>  I have no problem with a profile "containing" ink settings, as you
> wisely recommend. In fact I consider it to a most excellent idea that
> will simplify workflows, and prevent many current user errors.
>
>  However I do think ink settings ALSO need to be able to exist without
> the profile since the ink settings precede the profile, and since it
> is extremely advantageous to be able to adopt the ink settings from
> some known paper as a quick starting point to work with another paper.
> Ink settings, as we agree do precede profiles, and therefore need to
> be able to exist and be invoked independently of profiles.
>
> Edmund
>
> On Tue, May 3, 2011 at 5:14 PM, Ann McCarthy <almccart at lexmark.com> wrote:
> > Edmund,
> >
> > Although the ink settings precede the profile, and may be the same in
> more
> > than one profile, it is still important for correct profile usage to
> record
> > in each profile the ink settings that are correct for that profile.
> > The ink settings are part of the underpinning of a profile determining
> its
> > correct use.
> >
> > Best regards,
> > Ann L McCarthy
> > Imaging Systems R&D
> > Lexmark International, Inc.
> >
> >
> > On Mon, May 2, 2011 at 5:39 PM, edmund ronald <edmundronald at gmail.com>
> > wrote:
> >>
> >> I would recommend finding a way to pass the ink settings independently
> >> of a profile.
> >>
> >> Because:
> >> The settings describe device linearisation and used choices (eg. dpi
> >> setting) and thus PRECEDE the profile in time.
> >> In this way the first prints -Targets- will be made with a given
> >> setting by printing to DeviceSpace for profiling.
> >> Many profiles can be made for a given set of settings, indeed some of
> >> these can refer to different paper types for which it is convenient to
> >> reuse a given ink setting.
> >>
> >> My Reasoning
> >> Is that settings are quite independent of profiles, and should thus
> >> not be bound to any one setting.
> >> Indeed Robert generates settings but AFAIK has never made a profile.
> >>
> >> Edmund
> >>
> >>
> >> On Mon, May 2, 2011 at 10:43 PM, Kai-Uwe Behrmann <ku.b at gmx.de> wrote:
> >> > I am searching a way to unambigously pass settings from the print
> client
> >> > (CPD, lpr) to the CUPS server and print driver (rastertoprinter).
> >> > There are two ways possible. Embedd the device calibration settings
> >> > always
> >> > into the print ICC profile. Or pass these settings independently.
> >> _______________________________________________
> >> openicc mailing list
> >> openicc at lists.freedesktop.org
> >> http://lists.freedesktop.org/mailman/listinfo/openicc
> >
> >
> > _______________________________________________
> > openicc mailing list
> > openicc at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/openicc
> >
> _______________________________________________
> openicc mailing list
> openicc at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/openicc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/openicc/attachments/20110503/d9355dab/attachment.htm>