From 79bc9c182e74bcd58c6de33be8dfeb384a07199b Mon Sep 17 00:00:00 2001 From: Robin Watts Date: Mon, 25 Sep 2017 19:22:49 +0100 Subject: Fix separations object handling when cloning for spots. The 'producing spots' case is poorly tested, but I believe we should be keeping the spot information internally, rather than NULLing it out. --- include/mupdf/fitz/separation.h | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'include') diff --git a/include/mupdf/fitz/separation.h b/include/mupdf/fitz/separation.h index 9bbb1845..aa66b3ba 100644 --- a/include/mupdf/fitz/separation.h +++ b/include/mupdf/fitz/separation.h @@ -67,8 +67,11 @@ int fz_separations_controllable(fz_context *ctx, const fz_separations *seps); /* Return the number of active separations. */ int fz_count_active_separations(fz_context *ctx, const fz_separations *seps); -/* If the separations selection is unsuitable for overprint, - * clone it to produce one that is, otherwise return NULL. */ +/* Return a separations object with all the spots in the input + * separations object that are set to composite, reset to be + * enabled. If there ARE no spots in the object, this returns + * NULL. If the object already has all its spots enabled, then + * just returns another handle on the same object. */ fz_separations *fz_clone_separations_for_overprint(fz_context *ctx, fz_separations *seps); /* Convert a color given in terms of one colorspace, -- cgit v1.2.3