-
Lazily load MD5 and RC4 once in the life of the program. Only load the legacy provider if RC4 is actually being used.
-
* Define it even though previous experiments have shown it to be unnecessary since it seems like it may be necessary after all * Add QPDF_DLL_CLASS to QPDFObjectHelper and QPDFDocumentHelper in case there's some future unknown reason why someone may want to have them and/or in case it helps with the weird QPDFNameTreeObjectHelper problem.
-
It has disappeared from the DLL on Windows a few times.
-
That way we can always ensure that the right compiler flags are being used if there is an issue.
-
Verify runpath for all executables, check to make sure the AppImage works in various intended ways.
-
* Use correct cmake flag to not build static libraries * Force correct relative RPATH in installed executables
-
* Don't "shift" when $ARGV0 is a qpdf executable * Base -- to basename to avoid stuff like `qpdf --version` calling `basename --version`
-
Avoid representing as PDF Doc encoding any string whose PDF Doc encoding representation starts with a UTF-16 or UTF-8 marker.
-
Make sure that our attempt to test both signed and unsigned char is actually right.
-
Base implementation of the buffer on std::basic_string<unsigned char>.
-
For greater visibility and community participation, track ABI change ideas that aren't in the source in a github discussion item rather than in TODO.
-
This reverts commit 416d9668ee97c54a692d9280364746ce8aeeed43. This commit causes numerous failures in the pikepdf test suite and also causes a symbol to disappear from the public API. More investigation will be required.
-
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.