OpenSystemsDevelopment / qpdf

Make explicit that copyForeignObject can be used on page objects and
will copy them properly but not update the pages tree.

When linearizing a file or getting the list of all pages in a file,
detect if the pages tree contains a duplicated page object and, if so,
shallow copy it. This makes it possible to have a one to one mapping
of page positions to page objects.

Support conversion of pages to form XObjects and placement of form
XObjects on pages.

Add getAttribute for handling inheritable page attributes, and fix
getPageImages and annotation flattening code to use it.

mingw doesn't like it when you don't inline empty virtual destructors.

Setting encryption permissions for R >= 3 set permission bits in
groups corresponding to menu options in Acrobat 5. The new API allows
the bits to be set individually.

The original QPDF is only required now when the source
QPDFObjectHandle is a stream that gets its stream data from a
QPDFObjectHandle::StreamDataProvider.

This is in preparation of being able to pipe a stream's data without
keeping a copy of its containing qpdf object.

Use this instead of QPDF* as a map key for object_copiers.

Instead of calling assert for problems found during checking
linearization data, throw an exception which is later caught and
issued as an error. Ideally we would handle errors more robustly, but
this is still a significant improvement.

On certain operations, such as iterating through all objects and
adding new indirect objects, walk through the entire object structure
and explicitly resolve any indirect references to non-existent
objects. That prevents new objects from springing into existence and
causing the previously dangling references to point to them.

Also add some additional methods for detecting form field types to
assist in the json creation and for later use.

Instead of directly putting the contents of the annotation appearance
streams into the page's content stream, add commands to render the
form xobjects directly. This is a more robust way to do it than the
original solution as it works properly with patterns and avoids
problems with resource name clashes between the pages and the form
xobjects.

Flatten annotations by integrating their appearance streams into the
content stream of the containing page. In the case of form fields,
only flatten if /NeedAppearance is false (or equivalently absent). If
flattening form fields, also remove /AcroForm from the document
catalog.

Generate page content fragment for rendering appearance streams
including all matrix calculation.

Unparse is admittedly strange, but I'd rather be strange and
consistent, and everything else in the qpdf library uses unparse to
serialize. (If you're reading this, the convention of using "unparse"
comes from the "clu" programming language.)

Also move tests to libtests.