A more robust system for coping with badly malformed files

[johnwhitington]

For example, badly-malformed file from customer cannot be read, but both qpdf and gs can:

$ qpdf Burling2005.pdf out.pdf
WARNING: Burling2005.pdf (object 5391 0, offset 1531352): unknown token while reading object; treating as string
WARNING: Burling2005.pdf (object 5391 0, offset 1531604): unknown token while reading object; treating as string
WARNING: Burling2005.pdf (object 5391 0, offset 1531286): expected dictionary key but found non-name object; inserting key /QPDFFake1
WARNING: Burling2005.pdf (object 5391 0, offset 1531286): expected dictionary key but found non-name object; inserting key /QPDFFake2
qpdf: operation succeeded with warnings; resulting file may have some problems

Should we introduce such a system?

[johnwhitington]

Fixed in v2.6