[Openicc] colord 0.1.0 released!

[Graeme Gill]

Leonard Rosenthol wrote:
> There is NO DeviceRGB allowed in a PDF/X-3/4/5 file - all RGB data MUST be
> associated with an ICC profile.  You can have DeviceCMYK and DeviceGray -
> though they are actually only device values for the embedded OutputIntent.
> The only "true" device-dependent colors in a PDF/X file are Spot/Separation
> colors, since they are resolved independently on each device.

Perhaps the simplest approach is to say that PDF/X-3/4/5 are not suitable
profile or calibration test chart formats. It shouldn't make any difference
to the profiling of the device if a PDF chart is used to profile the PDF
printing path, as long as the underlying color machinery of PDF/X-3/4/5
is the same.

>> Is there a need for an immutable "off" flag for ensuring objects aren't
>> color managed no matter what?
>
> It's been suggested at least twice to the ISO 32000 committee and both times
> it's been rejected, because it's not clear what it means in all contexts.
>   For example, does it used when rendering to screen?  What about if the
> screen is simulating a printer (aka "Overprint Preview")??   etc. etc. etc.

It wouldn't seem all that hard, if the clear purpose is to facilitate
profiling.

If there are rendered elements that don't apply (because they are not
in the intended device profiling space, or the actual device space
is not the intended device profiling space), you have the usual options:

	Reject the file.
	Ignore those elements (don't render them).

You could re-render them (and that would be OK in a "preview" mode),
but it's a bad idea to re-render anything in the actual chart,
since there is no clear indication that the result is not an actual
test chart then.

Graeme Gill.