summaryrefslogtreecommitdiffstats
path: root/libqpdf
AgeCommit message (Collapse)Author
2013-01-23Cosmetic changes to be closer to Adobe terminologyJay Berkenbilt
Change object type Keyword to Operator, and place the order of the object types in object_type_e in the same order as they are mentioned in the PDF specification. Note that this change only breaks backward compatibility with code that has not yet been released.
2013-01-22Add getTypeCode() and getTypeName()Jay Berkenbilt
Add virtual methods to QPDFObject, wrappers to QPDFObjectHandle, and implementations to all the QPDF_Object types.
2013-01-20Add QPDFObjectHandle::parseContentStream methodJay Berkenbilt
This method allows parsing of the PDF objects in a content stream or array of content streams.
2013-01-20Added new QPDFObjectHandle types Keyword and InlineImageJay Berkenbilt
These object types are to facilitate content stream parsing.
2013-01-20Set version to 4.1.a0Jay Berkenbilt
Next released version will be 4.1.0 since new APIs are being added.
2013-01-17Prepare 4.0.1 releaserelease-qpdf-4.0.1Jay Berkenbilt
2013-01-03Set version number to 4.0.0+Jay Berkenbilt
2012-12-31Update versions for 4.0.0 releaserelease-qpdf-4.0.0Jay Berkenbilt
2012-12-31Fix spelling errorsJay Berkenbilt
Fixed spelling errors in previously published commits and update spelling dictionary
2012-12-31Update "C" API with functions for new featuresJay Berkenbilt
2012-12-31Avoid modifying trailer when writingJay Berkenbilt
When preparing the trailer for writing to the new file, trim a copy of the trailer instead of the original file's trailer.
2012-12-31Update shared library major version to 10Jay Berkenbilt
The upcoming 3.1 release contains non-compatible API changes, though they only affect parts of the interface that are extremely unlikely to have been used outside of qpdf itself. The methods and data types affected were used for communication between QPDFWriter and QPDF and would have had no real use in end user code.
2012-12-31Remove /Crypt from stream filters unconditionallyJay Berkenbilt
When writing a new stream, always remove /Crypt even if we are not otherwise able to filter the stream.
2012-12-31Refactor Dictionary writing codeJay Berkenbilt
Original code was written before we could shallow copy objects, so all the filtering was done by suppressing the output of certain keys and replacing them with other keys. Now we can simplify the code greatly by modifying shallow copies of dictionaries in place.
2012-12-31Support for encryption with /V=5 and /R=5 and /R=6Jay Berkenbilt
Read and write support is implemented for /V=5 with /R=5 as well as /R=6. /R=5 is the deprecated encryption method used by Acrobat IX. /R=6 is the encryption method used by PDF 2.0 from ISO 32000-2.
2012-12-31Support files with only attachments encryptedJay Berkenbilt
Test cases added in a future commit since they depend on /R=6 support.
2012-12-31Add random number functions to QUtilJay Berkenbilt
2012-12-31Fix infinite loop trimming passwords with ( in themJay Berkenbilt
2012-12-31SHA2 pipeline with support for 256, 384, and 512 bitsJay Berkenbilt
Implemented pipeline around sph sha calls using standard test vectors for full-byte values. Did not test or support partial byte values.
2012-12-31Incorporate sha2 code from sphlib 3.0Jay Berkenbilt
Changes from upstream are limited to change #include paths so that I can place header files and included "c" files in a subdirectory. I didn't keep the unit tests from sphlib but instead verified them by running them manually. I will implement the same tests using the Pl_SHA2 pipeline except that sphlib's sha2 implementation supports partial bytes, which I will not exercise in qpdf or our tests.
2012-12-31Allow specification of AES initialization vectorJay Berkenbilt
2012-12-31Update AES classes to work with 256-bit keysJay Berkenbilt
2012-12-31Add ExtensionLevel support to version handlingJay Berkenbilt
All version operations are now fully aware of extension levels.
2012-12-31Add V5 parameters to EncryptionDataJay Berkenbilt
2012-12-31change EncryptionDataJay Berkenbilt
2012-12-31Eliminate flattenScalarReferencesJay Berkenbilt
2012-12-25Improve memory safety of finding PDF headerJay Berkenbilt
2012-12-25Find PDF header anywhere in the first 1024 bytesJay Berkenbilt
2012-11-20Ignore objects with offset 0Jay Berkenbilt
2012-09-23Allow reading from InputSource and writing to PipelineJay Berkenbilt
Allowing users to subclass InputSource and Pipeline to read and write from/to arbitrary sources provides the maximum flexibility for users who want to read and write from other than files or memory.
2012-09-23Indicate pre-release versionJay Berkenbilt
2012-09-06Prepare 3.0.2 releaserelease-qpdf-3.0.2Jay Berkenbilt
2012-09-06Update libtool data for API changesJay Berkenbilt
2012-09-06Add QPDFWriter::setExtraHeaderTextJay Berkenbilt
2012-09-06Reset state in QPDF::calculateLinearizationDataJay Berkenbilt
This makes it possible to use two different writers to write linearized files from the same QPDF object.
2012-09-06Fix segmentation fault with use of QPDFWriter::setOutputMemoryJay Berkenbilt
2012-08-11Prepare 3.0.1 releaserelease-qpdf-3.0.1Jay Berkenbilt
2012-08-11Bug fix: let EOF resolve literal tokenJay Berkenbilt
Previously only whitespace and comments did it. This fix is needed for object streams whose last object is a literal (name, integer, real, string) not terminated by space or newline.
2012-08-11Refactor: move resolution of literal to its own methodJay Berkenbilt
2012-08-02Update version to 3.0.0release-qpdf-3.0.0Jay Berkenbilt
2012-07-29Fix spelling errorsJay Berkenbilt
2012-07-29Update documentation and version numbersJay Berkenbilt
3.0.rc1
2012-07-25added QPDFObjectHandle::replaceStreamData(std::string data).Tobias Hoffmann
2012-07-22Windows compilation fixesJay Berkenbilt
2012-07-21Implement QPDFObjectHandle::parseJay Berkenbilt
Move object parsing code from QPDF to QPDFObjectHandle and parameterize the parts of it that are specific to a QPDF object. Provide a version that can't handle indirect objects and that can be called on an arbitrary string. A side effect of this change is that the offset used when reporting invalid stream length has changed, but since the new value seems like a better value than the old one, the test suite has been updated rather than making the code backward compatible. This only effects the offset reported for invalid streams that lack /Length or have an invalid /Length key. Updated some test code and exmaples to use QPDFObjectHandle::parse. Supporting changes include adding a BufferInputSource constructor that takes a string.
2012-07-21Move readToken from QPDF to QPDFTokenizerJay Berkenbilt
2012-07-21Refactor: pull *InputSource out of QPDFJay Berkenbilt
InputSource, FileInputSource, and BufferInputSource are now top-level classes instead of privately nested inside QPDF.
2012-07-18Prevent seeking before beginning of BufferInputSourceJay Berkenbilt
2012-07-16Add command line option to copy encryption from other fileJay Berkenbilt
Add --copy-encryption and --encryption-file-password options to qpdf. Also strengthen test suite for copying encryption. The strengthened test suite would have caught the failure to preserve AES and the failure to update the file version, which was invalidating the encrypted data.
2012-07-16Minor fixes to copyEncryptionParametersJay Berkenbilt
This fixes were to code added yesterday; the problems would not have impacted any previously released code. These are all changes related to the possibility that copyEncryptionParameters may be called on behalf a different QPDF than the one being written.
generated by cgit v1.2.3-54-g00ecf (git 2.45.2) at 2024-07-03 14:11:05 +0200