[Openicc] GoSoC 2011: CPD and ... Mike Sweet workflow
rlk at alum.mit.edu
Fri May 13 05:39:36 PDT 2011
On Thu, 12 May 2011 21:28:09 -0700, Michael Sweet wrote:
> On May 12, 2011, at 8:09 PM, Graeme Gill wrote:
>> Michael Sweet wrote:
>>> What is the use case for this? Accurate profiling requires a stable target print, which
>>> requires some amount of drying/curing time. This isn't an ad-hoc process...
>> The main user case is that it always be possible to calibrate and profile
>> a printer. If this is a "special application", then it won't get maintained
>> or tested.
> It MUST be a specialized application - OpenOffice isn't going to
> print a target, take measurements, or make an ICC profile. Giving
> the user a control that turns off color management doesn't make
> color managed workflows any more accessible but DOES lead to a
> really bad (and frustrating) print experience.
Really? I could at least conceive of a spreadsheet being used to
generate (algorithmically) a color grid, which becomes a target.
Sure, it's a stretch, but deliberately withholding a capability
because some user might find it and get themselves confused just rubs
me the wrong way. Present things more intelligently, warn people if
they're about to do something they probably won't like, OK. But to
deliberately withhold a capability that already exists (by telling the
already-coded print dialog not to make certain options available) just
isn't the right way to go about doing things.
Robert Krawitz <rlk at alum.mit.edu>
Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- http://ProgFree.org
Project lead for Gutenprint -- http://gimp-print.sourceforge.net
"Linux doesn't dictate how I work, I dictate how Linux works."
More information about the openicc