summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichael Vrhel <michael.vrhel@artifex.com>2019-09-03 12:34:55 -0700
committerMichael Vrhel <michael.vrhel@artifex.com>2019-09-03 12:34:55 -0700
commitb7d32c453538bee41c34f8a77a3feb1dcc0ce759 (patch)
tree66322cb25a5ae13b60165e14e1b87f711d791e21
parent40934a68930a1d6a41a26df694e1e50fe3c60202 (diff)
downloadghostpdl-b7d32c453538bee41c34f8a77a3feb1dcc0ce759.tar.gz
Undo commit 95f7befcec1b30fd5014c8ad616485d32901ce33 for release
Proper handling of the page group color space is going to require a more complex solution whereby we ensure that we do the final alpha blending in the page group color space and not the target device color space.
-rw-r--r--base/gstrans.c7
1 files changed, 2 insertions, 5 deletions
diff --git a/base/gstrans.c b/base/gstrans.c
index 44ed3a7d3..8c4fca30d 100644
--- a/base/gstrans.c
+++ b/base/gstrans.c
@@ -264,12 +264,9 @@ gs_begin_transparency_group(gs_gstate *pgs,
target device (process color model). Here we just want
to set it as a unknown type for clist writing, as we will take care
of using the parent group color space later during clist reading.
- Also, if the group was not isolated we MUST use the parent group
- color space regardless of what the group color space is specified to be.
- Note that the page group should always be isolated */
+ */
+
- if (group_type == PDF14_BEGIN_TRANS_PAGE_GROUP)
- params.Isolated = true;
if (ptgp->ColorSpace == NULL || params.Isolated != true) {
params.group_color = UNKNOWN;
params.group_color_numcomps = 0;