qpdf-announce — announcements of qpdf releases and news

[Qpdf-announce] qpdf cmake prerelease (10.6.3.0cmake1)

[Jay B. <ej...@ql...>]

I have made a *prerelease* version of qpdf with cmake. When built, this version is identical to 10.6.3. If you are just a "user" of qpdf, you can ignore this release unless you want to try out the new Windows installers which are now available in addition to zip files. This release is for packagers, developers, and other people who care about building or packaging qpdf. If you use the qpdf DLL from Windows at runtime, you might want to test this out as well. The new DLL should be binary compatible, but cmake may use more updated compiler flags or do other things that will improve compatibility compared to the old build. Also, cmake handles "rpath" differently, so hopefully this puts an end to issues on rpm-based platforms with rpath containing build paths.

You can find the pre-release here: https://github.com/qpdf/qpdf/releases/tag/release-qpdf-10.6.3.0cmake1

If you are a packager, I would be interested to know if you are successful switching over to cmake. You can email me or mention it in https://github.com/qpdf/qpdf/discussions/676.

If you package qpdf for a distribution, this version is not intended for distribution, but you can use it to work out changes to your packaging and, if you have an experimental channel or something like that, you could release it there. I have uploaded debian package to "experimental" to ensure that the new packages go through the build cycle properly on all platforms. For the debian package, I have also enabled "autopkgtest", which are runtime tests on the installed package. I have included the test scripts in the source tree. You can find details in the pkg-test directory in the source distribution.

If you find problems with this release, such as errors in the documentation or problems building on your platform, please create an issue: https://github.com/qpdf/qpdf/issues

If you just want to let me know that you have successfully updated the packaging for your distribution (which I would appreciate knowing) or you have an opinion about how I did something or a suggestion for doing it differently, feel free to contribute to the release discussion here: https://github.com/qpdf/qpdf/discussions/676

Rather than repeating the details here, I would refer you to the release page where I have described the changes. Release notes specific to this prerelease can be found at https://qpdf.readthedocs.io/en/release-qpdf-10.6.3.0cmake1/release-notes.html.

The TODO file in the source distribution has some notes about additional changes I intend to make before qpdf 11. I couldn't make those changes yet because the change the ABI. I will make those changes very early in the qpdf 11 release cycle.

I have not made a release on sourceforge for this version, so you have to get it from github.

I don't expect to release qpdf 11 for several weeks.

--Jay

[Qpdf-announce] qpdf 10.6.3

[Jay B. <ej...@ql...>]

I have released qpdf 10.6.3. This is a small, bug-fix only release that corrects one additional character encoding issue (native UTF8 as specified in the PDF 2.0 spec) and one case with appearance stream generation.

** NOTE ** -- qpdf 11 will be built with cmake. I will send out a later email with a reference to a github discussion ticket about the cmake migration. I will be particularly interested in feedback from Windows developers and people who package qpdf for distributions and will provide a way for people to do early testing. The cmake conversion will happen early in the qpdf 11 release cycle so there will ample time for people to test and update their environments.

Releases: https://github.com/qpdf/qpdf/releases
Release notes: https://qpdf.readthedocs.io/en/stable/release-notes.html

--Jay

[Qpdf-announce] qpdf 10.6.2

[Jay B. <ej...@ql...>]

10.6.2 is out -- hopefully the last in the flurry. This fixes a few more character encoding issues. Distributions: if you are blocked on qpdf 10.6 because of pikepdf "regressions", be aware that a new pikepdf is also being released. We have worked together to ensure that we are back in sync. The pikepdf tests are very thorough and were able to uncover a few subtle cases in the way qpdf was handling encoding.

As always, releases are at https://github.com/qpdf/qpdf/releases, and release notes are at https://qpdf.readthedocs.io/en/stable/release-notes.html.

--Jay

[Qpdf-announce] qpdf 10.6.1

[Jay B. <ej...@ql...>]

I have released qpdf 10.6.1. The only significant change is correction of an error in test_driver.cc that was causing compilation failure on some platforms.

Usual boilerplate:
* Releases are at https://github.com/qpdf/qpdf/releases
* Relase notes are at https://qpdf.readthedocs.io/en/stable/release-notes.html

--Jay

[Qpdf-announce] 10.6.1 coming

[Jay B. <ej...@ql...>]

An incorrect use of abs() in test_driver.cc is causing compilation failures on some platforms. I plan to release 10.6.1 later today. If you are a packager and are running into this failure, feel free to sit tight for 10.6.1.

[Qpdf-announce] qpdf 10.6.0

[Jay B. <ej...@ql...>]

qpdf 10.6.0 is out. This release includes the largest refactoring of qpdf's code to date with moving all of the qpdf CLI's functionality into the library and exposing it through a new QPDFJob object. This includes a fluent interface as well as a way for library users to pass in an argv array or a JSON format that is equivalent to the command-line syntax.

If you are writing code that uses qpdf, you may want to start preparing for qpdf 11, which will replace PointerHolder with std::shared_ptr wherever it appears in qpdf's API. A backward-compatible PointerHolder that is interchangeable with std::shared_ptr will be provided. This may be adequate for most applications, but certain cases such as containers of PointerHolders, will most likely need to be changed. For detailed information on what to expect and how to prepare, see Smart Pointers <https://qpdf.readthedocs.io/en/10.6/design.html#smart-pointers>. See also comments in PointerHolder.hh <https://github.com/qpdf/qpdf/blob/235c89e037d6d9925cf201cadfa9e0df1771212c/include/qpdf/PointerHolder.hh#L25>. No changes are required for 10.6, but you will have to perform some steps before qpdf 11 in order to avoid compiler warnings. I am not expecting to release qpdf 11 for a few months.

Other release features:
* Several new interfaces in QPDFObjectHandle, also exposed to the C API, for an alternative and more type-safe way of retrieving values from QPDFObjectHandle
* Completely revamped qpdf --help and rewrite of the Running qpdf <https://qpdf.readthedocs.io/en/10.6/cli.html> section of the manual.

As always, you can download from https://github.com/qpdf/qpdf/releases and view release notes at https://qpdf.readthedocs.io/en/stable/release-notes.html.

[Qpdf-announce] qpdf 10.5

[Jay B. <ej...@ql...>]

QPDF 10.5.0 is out.

**NOTE TO PACKAGERS** -- packaging of the qpdf documentation has changed -- please see release notes and below.

New location for release notes: https://qpdf.readthedocs.io/en/stable/release-notes.html

This release features significant enhancements to the C API, exposing more functionality as well as closing some previous omissions around error handling. Notable enhancements include some functions for working with streams, pages, and foreign objects as well as some smaller fixes like being able to work with strings that have embedded null  characters.

QPDF 10.5.0 also features new documentation, now hosted at https://qpdf.readthedocs.io. At this time, the content is mostly the same, but I'm hoping to do a significant rework and improvement of the documentation in an upcoming release.

For packagers, note that pre-built documentation is no longer included in the source distribution. You can download pre-built docs from the release area or from the Read the Docs site. The release notes reference material in the manual that talks about your options for packaging. For my Windows and AppImage distributions, I'm still embedding offline docs. The debian package does not embed offline docs. I won't repeat the information already in the docs about it.

I'm planning some significant changes to the doc as well as a new high-level interface for bringing qpdf CLI functionality into the library and making it easier to access from other languages than C and C++. If you're interested in the details and/or helping to shape the direction of this, please see https://github.com/qpdf/qpdf/discussions/593.

--Jay

[Qpdf-announce] qpdf 10.4.0

[Jay B. <ej...@ql...>]

I have released version 10.4.0. This is primarily a bug-fix release. Notable changes: OpenSSL 3.0 is now supported. When using the openssl crypto engine, the openssl version is detected at compile-time. The distributed Windows releases are now built with openssl 3. 

This version of issues warnings from the qpdf CLI in some cases when weak cryptographic algorithms are used. These warnings can be turned off by passing --allow-weak-crypto. I am considering for qpdf 11 to make a small API change to force developers of applications that use qpdf to explicitly opt in to using weak crypto. Any feedback on this would be appreciated. See https://github.com/qpdf/qpdf/issues/576 for a discussion.

For a full list of changes from previous releases, please see the release notes <http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes>. The releases can be downloaded from https://github.com/qpdf/qpdf/releases as usual.

--Jay

[Qpdf-announce] rebuild of msvc 32-bit qpdf binary distribution for 10.3.2

[Jay B. <ej...@ql...>]

It was brought to my attention <https://github.com/qpdf/qpdf/issues/533> that the msvc 32-bit distribution of qpdf 10.3.2 contains a fix-qdf.exe that is, for some reason, being detected as malicious by Windows Defender and some other antivirus engines <https://www.virustotal.com/gui/file/3f153e9b183d4e75111c0adb78c3590afa006ed14f39a525b1a344dc36c99bc4/detection>. I am assuming this is a false positive. In any case, I have rebuilt that particular binary distribution and put it up on github and sourceforge in place of the original zip file. I have also submitted the allegedly malicious fix-qdf.exe to Microsoft for analysis.

None of the other binary distributions and none of the other executables in that distribution were suspected to be malicious, and of course building from source is just fine.

--Jay

[Qpdf-announce] qpdf 10.3.2

[Jay B. <ej...@ql...>]

I released qpdf 10.3.2 with minor fixes and enhancements including fixing an 11-year-old (known) bug that was leaving unreferenced objects in object streams with --object-stream=preserve. This release also includes portability fixes for handling timezones, which fixes a problem with the build in FreeBSD. For a full list of changes from previous releases, please see the release notes <http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes>. Download the release from the usual place: https://github.com/qpdf/qpdf/releases

--Jay

[Qpdf-announce] qpdf 10.3.1

[Jay B. <ej...@ql...>]

I just released qpdf 10.3.1 with a fix to a small but serious bug that would cause page splitting to fail with an exception for certain valid files with interactive forms. I also added a small defensive fix to the CLI to make it less serious if there are any other mistakes lurking in the new code. Hopefully this one will last a little longer than its two predecessors.

As usual, download from https://github.com/qpdf/qpdf/releases and check out the release notes at http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes.

--Jay

[Qpdf-announce] qpdf 10.3.0

[Jay B. <ej...@ql...>]

I have released qpdf 10.3.0. This is basically a bug fix release -- the form field handling code in 10.2.0 was not quite right as it didn't properly deal with inheriting form field attributes from the document level or adequately resolve conflicts when merging files. I have tested 10.3.0's results in a wider range of files and cases and on a wider range of viewers, as well as having reread the sections of the spec that deal with form fields.

Download location (usual place): https://github.com/qpdf/qpdf/releases, release notes: http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes

The API for dealing with form fields and annotations is really complex and hard to use. As I move forward with adding support for more document-level features, I'm planning on building a higher level interface for doing stuff with pages that will handle things properly at the document level. My goal is for the qpdf CLI's --pages, --split-pages, and --overlay/--underlay as well as some possible enhancements for other page rearrangement operations to be mostly a thin layer around calls to some kind of page copier class. For now, your best bet at figuring out how to use form field handling methods is to look at the pages code in qpdf/qpdf.cc. If you maintain some kind of wrapper around qpdf and are not in a rush to support form fields, you might want to consider waiting for the higher level interface, though I don't know when I will have a chance to build them. If you are working with the new interfaces and running into trouble, please feel free to create an issue or discussion item on github. Perhaps whatever we discuss will help improve the future interface for handling this and other document-level constructs.

--Jay

[Qpdf-announce] qpdf 10.2.0

[Jay B. <ej...@ql...>]

I have released qpdf 10.2.0, which you can get from https://github.com/qpdf/qpdf/releases/. This release includes a number of enhancements including a very often requested feature/fix, which is that page splitting and merging operations now preserve interactive form field functionality. This release includes several enhancements to the API and CLI also including support for file attachments, an added way to read a password from stdin, several enhancements to form field and annotation helpers, and rewritten support for name and number trees. This release also requires a C++-14 compiler. I have no plans to require anything newer than C++-14 in the foreseeable future. There are also a few bug fixes. For a full list of changes from previous releases, please see the release notes at http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes.

--Jay

[Qpdf-announce] preview of coming attractions + C++14 survey

[Jay B. <ej...@ql...>]

Hello all --

I'm busily working on a 10.2 release with a number of enhancements. This message has two purposes: to let people know of some things that are coming in case anyone wants to check them out, and to seek feedback on requiring C++14. If you aren't interested in these topics, no need to read further. Stay tuned for a 10.2 announcement in the next few weeks.

Short version:
 * I'm planning on requiring a C++14 compiler, but I have no plans to go beyond that in the foreseeable future.
 * I have added new APIs for attachments a few other things that will be frozen when 10.2 is out but can still be tweaked in the meantime.
More details here.

C++14 rationale: I'd like to start using [[deprecated]] on future non-compatible API changes. C++14 seems to be about as widely supported as C++11 and mostly contains minor fixes and enhancements to the C++11 standard. C++14 is the default for recent versions of clang, gcc, and MSVC going back a few years. I doubt that requiring C++14 rather than C++11 will remove many, if any, compilers from the list that can build qpdf. It remains my intention to support older and more obscure compilers when possible, so it will likely be years before I would consider C++17, C++20, or other versions.

API enhancements: As I work toward adding more helpers for document-level structures with an eventual goal of making page splitting and merging handle them more fully, I have added very much improved name and number tree support and some helper classes for file attachments. I am about to add some additional improvements to form fields and annotations as well with the aim of making it easier to create form fields and annotations. I have also added some C++-style iterators to the interface. This includes iterator support for name and number trees as well as wrappers around QPDFObjectHandle that allow iteration over dictionaries and arrays. I have maintained full backward-compatibility at this point, though I will remove the legacy constructors for name and number tree helpers in qpdf 11. As always, moving to the new API will be trivial.

The name/number tree support, iterators, and file attachment helpers are already in master. Unless I hear very strongly compelling reasons not to proceed with C++14, I will probably push that in the next day or so.

--Jay

[Qpdf-announce] qpdf 10.1.0

[Jay B. <ej...@ql...>]

I have released qpdf 10.1.0. This release includes several enhancements to the API including increased support for form XObjects and addition of user-providable stream filter decoders. There are also several enhancements to the C API including functions to work with objects. There are also a few bug fixes and performance enhancements. For a full list of changes from previous releases, please see the release notes: http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes.

qpdf 10.1.0 can be downloaded from https://github.com/qpdf/qpdf/releases as usual. Debian packages have been uploaded, and the Ubuntu ppa has also been updated.

For those of you who are using your own build system, note the addition of two new source files in libqpdf: QPDFStreamFilter.cc and SF_FlateLzwDecode.cc as well as the new example pdf-custom-filter.cc.

--Jay

[Qpdf-announce] qpdf 10.0.4

[Jay B. <ej...@ql...>]

I have released qpdf 10.0.4. This just includes a few fixes to some integer overflow conditions. This includes a bug in which qpdf was failing to ignore some unused bits in the xref stream, which under unusual conditions, could cause an integer overflow. But it turns out that some PDFs generated by DocuSign triggered the unusual circumstances. There are no functional changes in qpdf 10.0.4 other than these fixes.

Download as usual from https://github.com/qpdf/qpdf/releases
Release notes: http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes

--Jay

[Qpdf-announce] qpdf 10.0.3

[Jay B. <ej...@ql...>]

Well, turns out qpdf 10.0.2 wasn't a very long-lived release. I have released 10.0.3, which fixes a bug that I introduced with one of the fixes in 10.0.2. After introducing a bug, I dug deeper and found the actual root cause of the issue, which I fixed properly, thus solving the original problem and also fixing the new one. Download from https://github.com/qpdf/qpdf/releases; see release notes at http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes as usual.

I guess I can remove the brown paper bag from my head just in time for Halloween.

--Jay

[Qpdf-announce] qpdf 10.0.2 is out

[Jay B. <ej...@ql...>]

I have released qpdf 10.0.2. This release includes several fixes and performance improvements over 10.0.1. This release includes prebuilt Linux binaries in a zip file for use in docker containers or AWS Lambda. Also, the Windows releases are built with the latest versions of dependent libraries and now use the OpenSSL crypto provider by default. This is also the first release of qpdf to be built with GitHub Actions. For a full list of changes from previous releases, please see the release notes <http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes>. Here are some additional highlights:
 * Addition of the --disable-rpath flag to ./configure, intended to help packagers, especially on rpm-based distributions
 * Bug fix in content stream concatenation to prevent merging of the last token in the previous stream with the first token in the next stream in some cases
 * All outstanding fuzz errors found by Google's OSS-Fuzz project have been resolve including a memory leak and some integer overflows
 * Fixed internal error copying foreign streams with replaced stream data under certain specific conditions
If you use your own build system rather than qpdf's build system, please take a look at the release notes as there is one change that might affect your build.

Packages can be downloaded from the usual place: https://github.com/qpdf/qpdf/releases

Debian packages and packages for the Ubuntu PPA have been uploaded and should be available soon.

--Jay

[Qpdf-announce] qpdf 10.0.1

[Jay B. <ej...@ql...>]

Right on the heels of 10.0.0, I've released 10.0.1. There was one regression in 10.0.0 in QPDFObjectHandle::getStreamData that was causing it to return unfiltered data when the stream couldn't be filtered instead of throwing an exception. I decided this was bad enough to warrant pushing out a 10.0.1 release. You can see the release notes in the usual place <http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes>.

In addition to being able to download qpdf from https://github.com/qpdf/qpdf/releases/tag/release-qpdf-10.0.1, there is also now a PPA for Ubuntu: ppa:qpdf/qpdf, which you can find at https://launchpad.net/~qpdf/+archive/ubuntu/qpdf. For Ubuntu users, that means you can install the latest qpdf from the ppa within several minutes after release. This PPA contains backports of the official debian packages, which I also upload at the time of release.

Hopefully 10.0.1 will be around a little longer than 10.0.0!

--Jay

[Qpdf-announce] qpdf 10.0.0

[Jay B. <ej...@ql...>]

I have released qpdf 10.0.0. This release includes several notable improvements: substantially improved performance over the 8.x and 9.x releases, an openssl crypto provider, delegation of random number generation to the crypto provider, fast and automatic determination of whether to run slow unreferenced resource removal when splitting pages (though you can force the behavior to be on or off as well), and a few others. For a full list of changes from previous releases, please see the release notes <http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes>.

For package builders, please note that you will have to decide whether to build qpdf with gnutls, openssl, both, or neither. There is additional information about this in the manual and release notes.

At this time, the official Windows builds of qpdf are still using the native crypto provider and static versions of the dependent libraries, but I am hoping to include either gnutls or openssl crypto soon. This should be better from a security standpoint and should also hopefully eliminate the occasional but elusive problem on Windows of failing to get a new crypt context.

qpdf 10.0.0 can be downloaded from the usual place: https://github.com/qpdf/qpdf/releases/tag/release-qpdf-10.0.0

--Jay

[Qpdf-announce] qpdf 9.1.1

[Jay B. <ej...@ql...>]

I have released qpdf 9.1.1. In spite of what you may think based on the
version number, this is not an emergency release. As always, you can
consult the release notes
<http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes> to
see the latest changes, and you can download from the github release area
<https://github.com/qpdf/qpdf/releases/tag/release-qpdf-9.1.1>.

*Note to packagers:* I have rewritten fix-qdf in C++, so it is now a proper
executable. That means that qpdf no longer has a runtime dependency on perl
(yay). Perl is still required to build qpdf if you run its test suite.

Otherwise, qpdf 9.1.1 contains a small number of minor enhancements and bug
fixes, including CLI flags for determining whether a file is encrypted or
needs a password as well as addition of encryption information to the json
output.

In the absence of any major issues, I hope that this will be the version to
make it into Ubuntu 20.04 LTS. The debian packages have already been
uploaded.

--Jay

[Qpdf-announce] qpdf 9.1.0

[Jay B. <ej...@ql...>]

I have released qpdf version 9.1.0. Other than a few doc fixes, there were
no changes from the release candidate. For a full list of changes, please
see the release notes
<http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes>. The
rest of this email contains no new information from the 9.1.rc1 release
announcement.

*If you package qpdf for an OS distribution, there are changes that matter
to you. Please read this carefully.*

This version of qpdf requires a C++-11 compiler. Additionally, the crypto
provider can be selected at build time and run time, and a gnutls-based
crypto provider is included. If possible, you should have gnutls available
when build qpdf so that you can use the gnutls provider. However, if gnutls
is not an option in your environment, qpdf will work as it always has using
the native crypto provider. Some source files have been added or renamed,
which only matters if you are doing your own build with qpdf's Makefiles.
The manual has details on these changes.

My recommendation for packagers is that, if you have gnutls available, you
add the configure options "--enable-crypto-gnutls
--disable-implicit-crypto" to your configure invocation. This will build
qpdf with only the gnutls crypto provider and omit the native provider
entirely. I am building the packages in this way for Debian, and
RedHat/Fedora are also going to do this. For the foreseeable future, I have
no intention of removing qpdf's native crypto, but this could change for
either of two reasons: I need to add some additional crypto beyond what is
already there (e.g. to support digital signature), or a problem is
discovered in the native crypto. If gnutls is not to your liking, I believe
it would be reasonably straightforward to create crypto providers using
openssl, gcrypt, or nettle, and I would consider adding one or more of
these if necessary.

In addition to the configurable crypto providers, qpdf 9.1 adds some new
methods to facilitate manipulation of the PDF file by file offset, useful
for tools that may want to manipulate the file in ways that go beyond the
basic semantics of PDF objects. These changes were contributed by a user
who has created a digital signature tool for PDF files.

--Jay

[Qpdf-announce] qpdf 9.1 release candidate 1

[Jay B. <ej...@ql...>]

I have released qpdf version 9.1.rc1, a release candidate for 9.1.0. For a
full list of changes, please see the release notes
<http://qpdf.sourceforge.net/files/qpdf-manual.html#ref.release-notes>.

*If you package qpdf for an OS distribution, there are changes that matter
to you. Please read this carefully.*

This version of qpdf requires a C++-11 compiler. Additionally, the crypto
provider can be selected at build time and run time, and a gnutls-based
crypto provider is included. If possible, you should have gnutls available
when build qpdf so that you can use the gnutls provider. However, if gnutls
is not an option in your environment, qpdf will work as it always has using
the native crypto provider. Some source files have been added or renamed,
which only matters if you are doing your own build with qpdf's Makefiles.
The manual has details on these changes.

My recommendation for packagers is that, if you have gnutls available, you
add the configure options "--enable-crypto-gnutls
--disable-implicit-crypto" to your configure invocation. This will build
qpdf with only the gnutls crypto provider and omit the native provider
entirely. I am building the packages in this way for Debian, and
RedHat/Fedora are also going to do this. For the foreseeable future, I have
no intention of removing qpdf's native crypto, but this could change for
either of two reasons: I need to add some additional crypto beyond what is
already there (e.g. to support digital signature), or a problem is
discovered in the native crypto. If gnutls is not to your liking, I believe
it would be reasonably straightforward to create crypto providers using
openssl, gcrypt, or nettle, and I would consider adding one or more of
these if necessary.

In addition to the configurable crypto providers, qpdf 9.1 adds some new
methods to facilitate manipulation of the PDF file by file offset, useful
for tools that may want to manipulate the file in ways that go beyond the
basic semantics of PDF objects. These changes were contributed by a user
who has created a digital signature tool for PDF files.

This release candidate is provided primarily for people who want to test
their build or packaging of qpdf with the new crypto providers. A 9.1.0
release will follow in about a week if all goes well. I have already
noticed that I neglected to update the manual to describe the new third
party dependencies and C++-11 requirement, though these changes are noted
in the README.

I'll plan on giving this RC about a week to bake in and will plan on
releasing rc2 or 9.1.0 next week, depending on what happens this week.

--Jay

[Qpdf-announce] qpdf 9.1.0 will require a C++-11 compiler

[Jay B. <ej...@ql...>]

I am working toward getting qpdf 9.1.0 out soon. One major new enhancement
is the ability to provider alternative crypto providers, a feature
requested by RedHat/Fedora. My choice of implementation for this feature
uses C++-11 in non-trivial ways. In particular, pluggable crypto relies on
guaranteed thread safety of block-scoped static initializers and
`std::function` for registration and activation of crypto providers. It
also makes use of C++-11 smart pointers in favor of PointerHolder in new
interfaces. However, all of this is invisible unless you are going to
implement your own crypto provider.

I had originally anticipated that I would save C++-11 for qpdf 10, but I
was able to use it for this feature without breaking ABI compatibility.
Although current versions of clang, g++, and MSVC all support C++-14 by
default, I have constrained myself to only C++-11 features for now. When I
develop locally, I use --std=c++11 to prevent myself from accidentally
using C++-14 features. It's possible that I will expose additional C++-11
functionality in the public API for qpdf 10.

[Qpdf-announce] qpdf 9.0.2

[Jay B. <ej...@ql...>]

I have released 9.0.2 with one fix: the recently added --replace-input
option didn't work when the input file contained a slash in the path. I
wouldn't ordinarily do a release for a single fix, but this was such a
goofy bug that I just wanted to get it out there. There are a few changes
in the works that will add additional interfaces, so the next release will
most likely be 9.1.0. You can download qpdf from
https://github.com/qpdf/qpdf/releases.