-
... to QPDFObjectHandle_private.hh
-
Fix object stream error/warning messages reporting wrong object id
-
This was due to the use of last_object_description, which is not set for the object stream itself. Also, modify the messages introduced #1391 and #1392 to report the supposed offset of the objects.
-
Refactor writing of object streams
-
Cache output of pass 1.
-
Fix #1394
-
Move methods responsible for loading or keeping track of objects to QPDF_objects.cc. The split was part of the reverted #1297. Reintroducing it now makes it easier/safer to keep the work to refactor the xref and object tables in sync with main.
-
Also, add reverted #194 to .git-blame-ignore-revs.
-
This reverts commit bb045907a043b5c6de9fb804ff11087333747329.
-
Split QPDF.cc into QPDF.cc and QPDF_objects.cc
-
Move methods responsible for loading or keeping track of objects to QPDF_objects.cc. The split was part of the reverted #1297. Reintroducing it now makes it easier/safer to keep the work to refactor the xref and object tables in sync with main.
-
Refine recovery from missing startxref (fixes #1335)
-
Refactor xref table reconstruction (Fixes #1362)
-
Refactor InputSource
-
linearization parameter dictionary. Spec states that that linearization parameter dictionary must be the first object.
-
Improve support for reading into std::string objects.
-
Move qpdf private inline methods to private header file.
-
Minor code tidy and update .git-blame-ignore-revs
-
Ignore reverted #1272, #1289, #1297 and #1301. Ignore last two commits.
-
If startxref cannot be found in the last 1024 try finding it in the whole file and check whether it is valid.
-
Split reconstruction into three passes - scanning of input for objects and trailer, insertion of objects into the xref table, and loading the trailer. This allows insertion to take place in the usual reverse order and removes the need for a separate insertReconstructedXrefEntry method. It also allows trailer to be tried from most recent to oldest. Ignore any found trailers without /Root entry.
-
I always think of doing this after I have already tagged the release.
-
There simply is no chance Members will be required during the life of qpdf 12.