Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: [Digital BW] Re: Tonal range and linearization

2004-12-08 by Steve Kale

To keep a sense of perspective in this conversation, I ask some basic
questions:

1.  Do we agree that the need to "colour manage" (broadly defined) results
because two devices don't have the exact same colour space?  (In this case,
our image file on the computer and our printer)

2.  Do we agree that if our printer and our computer did share the same
colour space (or at least all the parts we care about) this whole
conversation would be redundant?

3. Do we agree that we have abandoned an automated method for managing the
difference between the two colour spaces (ie something like colorsync)?

4.  Do we agree that if our printer and our computer have overlapping colour
spaces that we would just have to decide what to do with the points that
didn't overlap and that such decision may or may not mean we decide to alter
the entire image to maintain a sense of relativity?

5.  Do we agree that more overlap is better than less?


I believe there is no reason for our workspace and printer not to share the
exact same "density" (which I will define as colour less hue) space for much
of the workspace range.  Specifically, for example, 16<=L=>96 for printing
to EEM and around 6<=L=>96 for printing on EPSG.

At the moment they share no common ground.  A simple image that is well
within the capability of the printer will not print properly out of the box
- instead it requires a _visual_ soft proof aid to get it to look right and
even then it may not print right.

If they did share the good proportion of common ground they are capable,
deciding what to do about of gamut values would be easy and very intuitive.
Because they don't it is complex and not obvious, requiring the use of a
soft proof and "fiddling to match".

This is all I am pressing on.

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.