aboutsummaryrefslogtreecommitdiffstats
path: root/manual/release-notes.rst
AgeCommit message (Collapse)Author
2022-10-01Prepare 11.1.1 releasev11.1.111.1Jay Berkenbilt
2022-09-1411.1: Fix typo in release notesv11.1.0Jay Berkenbilt
2022-09-14Prepare 11.1.0 releaseJay Berkenbilt
2022-09-14Force project includes before system includes (fixes #763)Jay Berkenbilt
From time to time, someone has a problem because their build is grabbing an old version of qpdf header files that are installed somewhere on their system. I am hoping this will put an end to that.
2022-09-13Mention change of tagging convention (fixes #772)Jay Berkenbilt
2022-09-12Bump version to 11.1.0Jay Berkenbilt
Some new symbols were exported.
2022-09-12Add some missing QPDF_DLL markersJay Berkenbilt
These markers are being added for nested classes that are already marked with QPDF_DLL_CLASS. They don't make any different on Linux, but they matter on Windows.
2022-09-12Remove obsolete LL_FMT check from build (fixes #768)Jay Berkenbilt
This was broken for cross-compilation and has probably been unnecessary for several years now. Also fix extraneous whitespace in related some tests.
2022-09-10Prepare 11.0.0 releaseJay Berkenbilt
2022-09-10Change QPDFObjectHandle == to isSameObjectAsJay Berkenbilt
Replace operator== and operator!=, which were testing for the same underlying object, with isSameObjectAs. This change was motivated by the fact that pikepdf internally had its own operator== method for QPDFObjectHandle that did structural comparison. I backed out qpdf's operator== as a courtesy to pikepdf (in my own testing) but also because I think people might naturally assume that operator== does a structural comparison, and isSameObjectAs is clearer in its intent.
2022-09-09Clean up release notes for qpdf 11Jay Berkenbilt
2022-09-09Add JSON v2 support to C APIJay Berkenbilt
2022-09-08Create a special "destroyed" type rather than using nullJay Berkenbilt
When a QPDF is destroyed, changing indirect objects to direct nulls makes them effectively disappear silently when they sneak into other places. Instead, we should treat this as an error. Adding a destroyed object type makes this possible.
2022-09-07Revert getOwningQPDF, and add getQPDF that returns a referenceJay Berkenbilt
2022-09-07Clarify and improve QPDFPageObjectHelper::get*Box methodsJay Berkenbilt
Add copy_if_fallback and explain how it differs from copy_if_shared.
2022-09-07Implement QPDFObjectHandle equalityJay Berkenbilt
2022-09-06Support --show-encryption without a valid password (fixes #598)Jay Berkenbilt
2022-09-06Re-introduce QPDFObject.hh as deprecatedJay Berkenbilt
* Just removing a header file would cause build errors with no hint as to what happened. This way, people get a warning rather than error for the life of qpdf 11, and the warning tells them what to do. * This avoids build surprises resulting from having two versions of QPDF headers installed at once. If you were building code out of a checkout of qpdf but had an older version installed on your system, if your code included <qpdf/QPDFObject.hh>, everything would work, but then your code would break without QPDFObject.hh later.
2022-09-06Update formatting a documentation from last PRJay Berkenbilt
2022-09-02Disable copying/assigning to QPDF objects, add QPDF::create()Jay Berkenbilt
2022-09-02Remove QPDFObject::object_type_e as alias for qpdf_object_type_eJay Berkenbilt
2022-09-01Include memory usage in performance test outputJay Berkenbilt
2022-09-01Update ChangeLog and Release Notes from previous pull requestsJay Berkenbilt
2022-08-27Add ChangeLog/release-notes (with credit) for last pull requestJay Berkenbilt
2022-08-07Disable QTC inside the library by default (fixes #714)Jay Berkenbilt
This results in measurable performance improvements to packaged binary libqpdf distributions. QTC remains available for library users and is still selectively enabled in CI.
2022-07-24Tweak "AndGet" mutator functions againJay Berkenbilt
Remove any ambiguity around whether old or new value is being returned.
2022-07-24Add ChangeLog and release notes for previous contributionJay Berkenbilt
2022-06-19Add qpdfjob_register_progress_reporterJay Berkenbilt
2022-06-19Add examples for output capture (fixes #691)Jay Berkenbilt
2022-06-19Add C API to QPDFLoggerJay Berkenbilt
2022-06-19Add more flexible funtions to qpdfjob C APIJay Berkenbilt
2022-06-18Expose exit code values to C API via Constants.hJay Berkenbilt
2022-06-18Spell checkJay Berkenbilt
2022-06-18Use the default logger for other writes to stdout/stderrJay Berkenbilt
When there is no context for writing output or error messages, use the default logger.
2022-06-18Use "save" logger when saving data to standard outputJay Berkenbilt
This includes the output PDF, streams from --show-object and attachments from --save-attachment. This also enables --verbose and --progress to work with saving to stdout.
2022-06-18QPDF, QPDFJob: use QPDFLogger instead of custom output streamsJay Berkenbilt
2022-06-18Add integer types to Pipeline::operator<<Jay Berkenbilt
2022-05-31ChangeLog, release notes for json v2Jay Berkenbilt
2022-05-31Update documentation for qpdf JSON v2Jay Berkenbilt
2022-05-31In json mode, reveal recovered user password when otherwise unavailableJay Berkenbilt
2022-05-31Add additional information when listing attachmentsJay Berkenbilt
2022-05-20Back out fluent QPDFObjectHandle methods. Keep the andGet methods.Jay Berkenbilt
I decided these were confusing and inconsistent with how JSON works. They muddle the API rather than improving it.
2022-05-04JSON: add write methods and implement unparse() in terms of thoseJay Berkenbilt
2022-05-04Make "objects" and "pages" consistent in JSON outputJay Berkenbilt
2022-05-04Add new Pl_String PipelineJay Berkenbilt
2022-05-04Add new Pl_OStream PipelineJay Berkenbilt
2022-05-04Add new Pipeline convenience methodsJay Berkenbilt
2022-05-04Make Pipeline::write take an unsigned char const* (API change)Jay Berkenbilt
2022-04-30Mark weak encryption with API changes (fixes #576)Jay Berkenbilt
2022-04-30Revert "Remove QPDFObjectHandle::replaceOrRemoveKey"Jay Berkenbilt
This reverts commit dc059560e73e0b373a6e54e71b07e3af4b692cb4. I changed my mind. There's no harm in leaving it deprecated for a release cycle.
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-06-26 21:05:56 +0200