No subject

The profile that is the value of the DestOutputProfile key shall be an
Output Device Profile (Device Class =3D =93prtr=94) as defined in ICC.1:199=
8-09,
ICC.1:2001-12, ICC.1:2003-09 or ISO 15076-1:2005 and shall be interpreted a=
s
representing the intended printing condition.


ICC spec (7.2.5) identifies 'prtr' as an "Output Device" profile.  So if yo=
u
really do an RGB-based output device, then you could have a 'prtr' profile
for it - but I am not aware of any in actual use.



> I ask this because somewhere I was given the distinct impression that
> PDF/X-3 does allow RGB OutputIntents, in which case objects could be
> /DeviceRGB.
>

IF you had an actual RGB-based OutputIntent, that is true - but not in
actual practice.

Leonard

--00032557474ebfb058049a3e8fe2
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 19, 2011 at 9:29 PM, Chris Murphy <span dir=3D"ltr">&lt;<a href=
=3D"mailto:lists at colorremedies.com">lists at colorremedies.com</a>&gt;</span> =
wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style=3D"word-wrap:break-word"><div><div class=3D"im"><blockquote type=
=3D"cite"><div class=3D"gmail_quote"><div>There is NO DeviceRGB allowed in =
a PDF/X-3/4/5 file - all RGB data MUST be associated with an ICC profile. =
=A0You can have DeviceCMYK and DeviceGray - though they are actually only d=
evice values for the embedded OutputIntent. =A0 The only &quot;true&quot; d=
evice-dependent colors in a PDF/X file are Spot/Separation colors, since th=
ey are resolved independently on each device.</div>
</div></blockquote><div><br></div></div><div>OK at the expense of embarrass=
ing myself, I&#39;m going to ask it anyway: are you sure?</div><div><br></d=
iv></div></div></blockquote><div><br></div><div>From PDF/X-3 (ISO 15930-3, =
6.2.2):</div>
</div><blockquote class=3D"webkit-indent-blockquote" style=3D"margin: 0 0 0=
 40px; border: none; padding: 0px;"><div class=3D"gmail_quote"><div><div>Th=
e profile that is the value of the DestOutputProfile key, if present, shall=
 be an Output Device Profile (Device Class =3D=A0=91prtr=92) as defined in =
ICC.1.</div>
</div></div></blockquote><div class=3D"gmail_quote"><div><br></div><div>Fro=
m PDF/X-4 (ISo 15930-7:2010, 6.4.2.1):</div></div><blockquote class=3D"webk=
it-indent-blockquote" style=3D"margin: 0 0 0 40px; border: none; padding: 0=
px;">
<div class=3D"gmail_quote"><div>The profile that is the value of the DestOu=
tputProfile key shall be an Output Device Profile (Device Class =3D =93prtr=
=94) as defined in ICC.1:1998-09, ICC.1:2001-12, ICC.1:2003-09 or ISO 15076=
-1:2005 and shall be interpreted as representing the intended printing cond=
ition.</div>
</div></blockquote><div class=3D"gmail_quote"><div><br></div><div>ICC spec =
(7.2.5) identifies &#39;prtr&#39; as an &quot;Output Device&quot; profile. =
=A0So if you really do an RGB-based output device, then you could have a &#=
39;prtr&#39; profile for it - but I am not aware of any in actual use.</div=
>
<div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style=3D"=
word-wrap:break-word"><div><div></div><div>I ask this because somewhere I w=
as given the distinct impression that PDF/X-3 does allow RGB OutputIntents,=
 in which case objects could be /DeviceRGB.=A0</div>
</div></div></blockquote><div><br></div><div>IF you had an actual RGB-based=
 OutputIntent, that is true - but not in actual practice.</div><div><br></d=
iv><div>Leonard=A0</div></div>

--00032557474ebfb058049a3e8fe2--