all devices regression report - 2017-10-07-07:41:06 - 83ef35dce760f68019afd1b07bac8118cd9837a2

Differences in all devices errors using gs/examples files

Previous Revision: 45a826638bfc6309a829b38ecf14ff9c21f438ca
 Current Revision: 83ef35dce760f68019afd1b07bac8118cd9837a2

commit 83ef35dce760f68019afd1b07bac8118cd9837a2
Author:     Ken Sharp <[email protected]>
AuthorDate: Fri Oct 6 17:23:59 2017 +0100
CommitDate: Fri Oct 6 17:24:16 2017 +0100

    PDF and PS Interprters and ps2write - fix type 6 halftones & transfers
    
    Bug698621 "PDF 2.0 tests not applying transfer function from halftone"
    
    The halftones in question are defined (by the PDF interpreter) as type
    6 halftones, ie file-based threshold arrays.
    
    Rather to my surprise, the reason this didn't work turns out to be
    because the PostScript interpreter has never supported transfer functions
    with type 6 halftones.
    
    So; add support for transfer functions in type 6 halftones. This exposed
    a problem with ps2write (and potentially pdfwrite) when emitting these
    transfer functions, instead of simply specifying the object number of
    the function, we were writing it out decorated with "/TransferFunction"
    which caused ps2write output to fail. So fix that here too.
    
    Remove the 'OBSELETE' comment from the halftone structure, I don't know
    who thought this was obselete, but it really does not seem to be.

base/gsht1.c
base/gxht.h
devices/vector/gdevpdfg.c
psi/zht2.c

new errors:

errors that went away:

errors that are not whitelisted:
=== ghostpdl/examples/transparency_example.ps === cp50 ===
=== ghostpdl/examples/transparency_example.ps === psdrgb ===