summaryrefslogtreecommitdiff
path: root/source/pdf/pdf-run.c
diff options
context:
space:
mode:
authorMichael Vrhel <michael.vrhel@artifex.com>2017-07-12 17:16:08 -0700
committerRobin Watts <robin.watts@artifex.com>2017-07-17 19:32:06 +0100
commita072383d980fda364df6cd123383e9d1327430b7 (patch)
tree048ec67cb0b8fa1348f3c1d5d9e67051519e4c5e /source/pdf/pdf-run.c
parent63713f22ae830142dfe0d3896948ec53c4705ace (diff)
downloadmupdf-a072383d980fda364df6cd123383e9d1327430b7.tar.xz
If page has no group then use output intent color space
If the document has an output intent but no page group was defined then we should not let the target device color space define what our base group is. Instead we should push a group that uses the target output intent color space. This problem occurs on page 3 of the Altona test file (TextKnockout page).
Diffstat (limited to 'source/pdf/pdf-run.c')
-rw-r--r--source/pdf/pdf-run.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/source/pdf/pdf-run.c b/source/pdf/pdf-run.c
index 1d823277..7bff750b 100644
--- a/source/pdf/pdf-run.c
+++ b/source/pdf/pdf-run.c
@@ -70,6 +70,10 @@ pdf_run_page_contents_with_usage(fz_context *ctx, pdf_document *doc, pdf_page *p
}
}
}
+ else
+ {
+ colorspace = fz_default_output_intent(ctx, default_cs);
+ }
fz_begin_group(ctx, dev, fz_transform_rect(&mediabox, &local_ctm), colorspace, 1, 0, 0, 1);
}