qpdf-announce — announcements of qpdf releases and news

[Qpdf-announce] qpdf 2.2.2

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

Just two days after releasing qpdf 2.2.1, I'm release qpdf 2.2.2.  There
is only one change: the addition of the qpdf_read_memory method to the
"C" API.  I had neglected to add this to the C API when adding the
QPDF::processMemoryFile() method to the C++ API.  You can visit the qpdf
project page at the usual location:

https://sourceforge.net/projects/qpdf/

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] qpdf 2.2.1

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

I have released qpdf 2.2.1.  Jian Ma's VC6 port has also been updated.
qpdf 2.2.1 features the following changes:

 * New method for allowing processing of PDF files loaded into memory as
   well as those on disk

 * Ability to redirect standard output and error messages to alternative
   std::ostream objects so that they can be redirected; this could be
   useful for GUI authors.  (Note that qpdf doesn't generate any such
   messages if you call suppressWarnings(true) and don't call any of the
   debugging methods, so existing GUI authors are safe -- details in
   QPDF.hh.)

 * Enhancements to accept certain types of errors in pdf files that
   previous versions of qpdf would have rejected

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] port of qpdf to vc6 now in contrib

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

I have uploaded a port of qpdf to Microsoft VC6 to the contrib area.
Thanks to Jian Ma for generously providing this port.

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] QPDF 2.2.0 is out

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

I have released QPDF 2.2.0.  The big change from 2.1.5 is the addition
of some new methods in QPDFObjectHandle to support adding new streams
and replacing the data of existing streams.  This opens up a number of
new possibilities for things that can be done that couldn't be done
before.  Additionally, there is one memory leak that was fixed.  If you
tested qpdf 2.2.rc1, the only code change from that release is the
addition of a QPDFObjectHandle::getRawStreamData method to make a little
easier to get the uncompressed data from a stream.

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] qpdf 2.2.rc1

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

To all qpdf users:

I've uploaded a release candidate for what will soon be version 2.2.0 of
qpdf.  The major change from 2.1.5 is the addition of new methods that
allow addition of new streams and replacing stream data.  This makes new
applications possible, such as replacing images in PDF files, scaling
pages, or numerous other possibilities.  True to the spirit of qpdf,
there is still no *knowledge* of the contents of streams, but now you can
write your own programs that can work with contents of streams in a PDF
file before writing out a new file with qpdf-writer.  The following
methods have been added to QPDFObjectHandle:

  newStream: allows a completely new stream, with data provided, to be
  added to a PDF file

  replaceStreamData: allows replacing a stream's original data with new
  data

  addPageContents: allows a new content stream to be added to the
  beginning or end of a page's list of content streams.  Automatically
  converts /Contents from a stream to an array of streams if needed

  replaceOrRemoveKey: a convenience routine that replaces a dictionary
  key with the given value unless the value is a null object, in which
  case it removes the key

In addition, there are two new example programs: pdf-double-page-size
and pdf-invert-images.  These two programs illustrate how to use the new
methods.  Both examples are inspired by specific things various qpdf
users have wanted to do.

Additionally, this version includes a fix to a small memory leak.  The
final 2.2.0 version will also include information about how to build
qpdf with Microsoft Visual C++ version 6.  I hope to do the final
release in a week or two.

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] qpdf 2.1.5

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

I have released qpdf 2.1.5.  This version includes one change: a fix to
support encryption and decryption of PDF files whose file identifier
strings (/ID in the trailer) are other than 16 bytes long.  I had never
encountered such a file before someone brought one to my attention, but
they're out there, and qpdf now handles them properly.

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] qpdf 2.1.4

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

I have released qpdf 2.1.4.  There are two changes from version 2.1.3:

 * Version 2.1.2 included a fix for calculating padding during
   linearization of files with object streams, but the fix was applied
   to only one of two places where it was needed.  This fix is now been
   applied in the other place.  If you use qpdf to linearize files, you
   should definitely upgrade to version 2.1.4.  The bug would have
   caused an assertion failure, so you would definitely know if you'd
   seen it.  The bug did not result in creation of incorrect linearized
   files.

 * The output of qpdf --check is a little more clear with respect to the
   fact that qpdf doesn't check for every possible error.

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] qpdf 2.1.3

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

I have released qpdf version 2.1.3.  There are two small bug fixes in
this version.  In earlier versions, qpdf would fail with an error if you
tried to rewrite a file that contained object streams with unreferenced
objects that in turn referenced indirect scalars.  (Huh?)  Anyway, this
is a rare situation, but it is fixed in 2.1.3.  Also, if a PDF file is
encrypted using AES encryption and one of the inputs to AES has a length
that is not a multiple of 16, qpdf 2.1.3 will be able to decrypt the
data anyway.  There's a chance that there may be some trailing garbage
at the end of the input, but this is usually harmless.

If anyone subscribed here is inclined to write a review on the
sourceforge project page for qpdf, that would be great.  At this point,
there's one anonymous thumbs up vote and one anonymous thumbs down vote,
both made without any comments.

https://sourceforge.net/projects/qpdf/

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] qpdf 2.1.2 has been released

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

I have released qpdf version 2.1.2.  This version fixes a bug in the
linearization code.  In older versions, qpdf could sometimes crash with
an assertion failure when linearizing files with compressed object
streams.  The effect of this bug is that certain files with object
streams (PDF >= 1.5 "compressed objects"), particularly those with
graphics or other large objects on the first page, might have crashed
qpdf during the linearization.  The problem is fixed in version 2.1.2.
No changes have been made to public interfaces, so the new libraries are
binary compatible with those of 2.1.1 and 2.1.

Visit the qpdf web site: http://qpdf.sourceforge.net.

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] qpdf version 2.1 is released

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

I have released version 2.1 of qpdf.  There are no significant changes
from the release candidate: just a minor code change to make qpdf more
flexible in recovering certain types of damaged files and a few
improvements to the RPM .spec file.  As with the release candidate, you
can download the sources (for UNIX, Linux, or Windows) or you can also
download prebuilt Windows binaries.  qpdf 2.1 has also been uploaded to
debian's "unstable" release and should be available shortly to debian
users.

In addition to qpdf 2.1, you can also download Zarko Gajic's
[http://delphi.about.com] Delphi wrapper and sources to a demo
application.  Zarko has generously contributed this code and allowed it
to be released under Artistic License version 2.0, which are the same
terms as qpdf itself.  This wrapper class provides a good example of how
to access QPDF in Windows by directly calling into the DLL.

-- 
Jay Berkenbilt <ej...@ql...>

[Qpdf-announce] qpdf 2.1.rc1 is available for download

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

QPDF version 2.1.rc1 (release candidate) is available for download.
Notable changes in this release are support for AES encryption as well
as some of the new encryption formats introduced in PDF 1.5 and 1.6 as
well as support for Windows.  In addition to the source download, there
are Windows executables with a DLL.  Versions are available for download
built with gcc 4.4 from mingw and also with VC9 (Visual C++ .NET 2008).
I plan on releasing a final 2.1 next weekend.  If there are no problems
found in this version, the only change will be removal of the "rc1" from
the version number.

-- 
Jay Berkenbilt <ej...@ql...>