all devices regression report - 2017-11-23-10:06:59 - 3ad236df1e509d0326a1fa31c98e068b5712fd75

Differences in all devices errors using gs/examples files

Previous Revision: f32c03a2daad2d2e0e859bd6fc7547b68bd8bed9
 Current Revision: 3ad236df1e509d0326a1fa31c98e068b5712fd75

commit 3ad236df1e509d0326a1fa31c98e068b5712fd75
Author:     Chris Liddell <[email protected]>
AuthorDate: Thu Nov 23 09:40:36 2017 +0000
CommitDate: Thu Nov 23 16:45:21 2017 +0000

    Bug 698773: Cope with "charstring" of invalid type
    
    This file has a font whose CharStrings dictionary contains:
    /space 3 def
    
    Ideally, when we hit such a case, we should fallback to the .notdef glyph,
    unfortunately, it also has:
    /.notdef 0 def
    
    We *should* throw an error since this is clearly totally invalid, but other
    interpreters *appear* to simply ignore the problem. So, we opt to return an
    empty charstring.

psi/zfapi.c

new errors:

errors that went away:

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