PDF import: a DeviceCMYK image in a PDF/X file opens with the output intent's profile

A file whose catalog has a CMYK /GTS_PDFX output intent describes its
DeviceCMYK colors with that intent's profile. A DeviceCMYK image in
such a file now opens tagged with that profile, so a CMYK image that a
PDF/X export writes as DeviceCMYK opens with its profile again.

An image drawn where a /DefaultCMYK is in scope keeps no profile, since
the default replaces DeviceCMYK there. The scope is read per image from
the resources it is drawn with, and the image cache keeps the tagged and
untagged reads apart.
This commit is contained in:
dotCooCoo
2026-11-17 10:44:47 -08:00
parent c7c14be61b
commit 76078f1991
8 changed files with 160 additions and 14 deletions
+3 -2
View File
@@ -1450,8 +1450,9 @@ Imported colours keep their model:
DeviceCMYK and CMYK ICC colours stay CMYK (a file painted mostly in CMYK opens as a CMYK document), DeviceGray is Gray,
and Separation and DeviceN inks become spot swatches the art links to at its tint (gradient stops too). CMYK images
(DeviceCMYK, or ICC-based with four components) keep their ink amounts: a CMYK JPEG as it is, any other as a CMYK TIFF
(masked CMYK images, and ones with 1, 2 or 4 bits per sample, open in RGB with a warning). Placing a CMYK TIFF keeps it
CMYK too.
(masked CMYK images, and ones with 1, 2 or 4 bits per sample, open in RGB with a warning). In a file with a CMYK
`/GTS_PDFX` output intent, a DeviceCMYK image carries the output intent's profile, except where it is drawn with a
`/DefaultCMYK` in the resources in scope. Placing a CMYK TIFF keeps it CMYK too.
`colorMode: "rgb" | "cmyk"` opens any file in that mode instead, its colours converted as `file.documentColorMode` does
(`grays` too):