Re: Re(6): embedded profiles in PDF/Postscript
Re: Re(6): embedded profiles in PDF/Postscript
- Subject: Re: Re(6): embedded profiles in PDF/Postscript
- From: Roger Breton <email@hidden>
- Date: Sun, 06 Jun 2004 20:12:24 -0400
>
It's metadata. Those who care and can make effective use of it can do
>
so. Those who aren't as sophisticated will ignored it, occasionally at
>
their own peril. But for the most part PDF/X-1a is very safe by itself,
>
the OutputIntent is just an extra piece of data that could have been
>
optional, but I prefer it required. If the job printed wrong, and it
>
was traced to the job only being soft proofed and approved on that
>
basis, and then determined that it was because the OutputIntent was set
>
incorrectly, there is an implicit liability by the party that created
>
the PDF/X-1a document as they set the OutputIntent incorrectly. I do
>
think it's good it's required, even if it gets abused.
>
>
Chris Murphy
I agree we have to leave it in, regardless of the fact that it gets used or
not downstream. The fact that all color data in a PDF/X-1a is considered in
DeviceCMYK guarantees that there couldn't be any unforeseen conversions of
any kind on any RIP unless someone explicitely triggers a DeviceCMYK to
DeviceX conversion -- for some reason.
Roger Breton | Laval, Canada | email@hidden
http://pages.infinit.net/graxx
_______________________________________________
colorsync-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/colorsync-users
Do not post admin requests to the list. They will be ignored.