New muPDF compiler warnings - 2017-10-25-11:30:02 - c40b136f4ecb78a481326a544b56eb7be251445c

Previous Revision: fbdd9c7c1bda2081e49b82a3a0d9ca5cf7abe492
 Current Revision: c40b136f4ecb78a481326a544b56eb7be251445c

commit c40b136f4ecb78a481326a544b56eb7be251445c
Author:     Robin Watts <[email protected]>
AuthorDate: Thu Sep 14 15:52:47 2017 +0100
CommitDate: Tue Oct 24 15:16:36 2017 +0100

    Fix overprinting simulation in RGB output with no spots.
    
    Running Ghent_V5.0/GWG010_CMYK_OP_x3.pdf to PNG produces
    'X' marks, where Acrobat does not. This is expected if
    overprint similation is turned off, but not if it is
    enabled.
    
    The file does not define a colorspace for the initial page,
    uses no transparency, and has no spots defined. Accordingly,
    when we clone the page fz_separation object, we end up with
    no object at all. The draw device therefore doesn't even
    attempt to do overprint simulation.
    
    We fix this by ensuring that we always have a non-NULL
    separation object. Possibly we should make fz_page_separations
    return a non-NULL, but empty object?
    
    Even with this change, running to PNG still does not give the
    required rendering. This is because PNGs use RGB, rather than
    CMYK, and overprint is disabled for non-subtractive spaces.
    
    We therefore adjust the code in push_group_for_separations
    that decides whether it can avoid pushing an extra group.
    If the basic pixmap is RGB, then we never skip the extra
    group.

source/fitz/draw-device.c
source/tools/mudraw.c



muPDF:

new cppcheck warnings (Cppcheck 1.72): 

source/tools/mudraw.c:1243: error: Memory leak: p

http://miles.ghostscript.com:8080/artifex/mupdf/c40b136f4ecb78a481326a544b56eb7be251445c/mupdf-cppcheck.txt