CTS logo
hazy blue Catskill Mountains in distance

News: PDF::Builder v3.012 Released, 26 October 2018

Please see the Free Software section, as well as the PDF::Builder section of the forum.


A Thought…

When the facts change, I change my mind, sir. What do you do?

   — John Maynard Keynes

Perl library for creating and updating PDF documents

Links to files and information…

The Current Version is v3.003

The PDF::API library, and its current version, PDF::API2 (version 2) has been available on the CPAN library for many years. Unfortunately, its maintenance record has been less than consistent. It was originally written by Alfred Reibenschuh, et al., and is currently maintained by Steve Simms. I started participating in the maintenance of the package, but butted heads with Steve too many times for my liking. He only wants to fix bugs (at least, for now) and refuses to consider any enhancements, or cleanup of code or POD documentation. If I submit a bug report that is too large for his liking, he simply ignores it. Steve is doing good and necessary work in fixing bugs, but I feel that his scope is too narrow for the good of the product. Thus, I have reluctantly decided that I need to fork the project in order to get necessary improvements into the code. My plan is to include bug fixes he provides for the official (version 2) PDF::API2, as well as my own bug fixes and enhancements. I hope that some day all my work can be folded back into the official release.

Why not PDF::API3?

It took some consideration as to what this forked version should be called. There was already an official PDF::API3 project on CPAN, but it appears to be stillborn (created in early 2009 by Otto Hirr, and never updated). I also didn't want to call it PDF::API4, as most people are familiar with PDF::API2 as the name of the library, not as PDF::API version 2. So, I settled on calling it version 3 (starting with 3.001) of PDF::API2. Don't like that? Fork your own!

I plan to keep changes as upwardly compatible as humanly possible, but it is possible that some fixes and enhancements might break existing code. If known, I will attempt to note that in the documentation, and provide a workaround or alternate library. Worst case, new calls or methods will be provided, and the old ones left in for now (and deprecated).

Why is it not on GitHub?

I may yet place the code on GitHub (or some other public repository, such as CPAN). I have not yet done so, as I want to see how it's received and how much participation I get from the public and other developers. It certainly would be nice to be able to use either CPAN's or GitHub's bug tracking facility, rather than bending a forum to do it. If bug tracking becomes painful, or the work of consolidating bug fixes and generating a release becomes overwhelming, I'll consider putting it on GitHub so that others can more easily participate. In the meantime, I will accept bug reports via my site forum, and bug fixes and enhancements via patch files (preferably diff -ur olddir/ newdir/ or WinMerge: Tools > Generate Patch) via bug report (forum) attachments, or email attachments.

 

All content © copyright 2005 – 2018 by Catskill Technology Services, LLC.
All rights reserved.
Note that Third Party software (whether Open Source or proprietary) on this site remains under the copyright and license of its owners. Catskill Technology Services, LLC does not claim copyright over such software.

 

This page is https://www.catskilltech.com/FreeSW/product/PDF-API2/title/PDF%3A%3AAPI2/freeSW_full

Like a quotation you saw earlier, and wish you could see it again? Want to see if there are more quotes from a certain person? Enter the address https://www.catskilltech.com/?quote=term to find a quotation containing that term. Looking for a term of multiple words separated by spaces? Separate the words by +'s: Mark+Twain.

Last updated Wed, 19 Jul 2017 at 2:16 PM

Valid HTML 5

Wed, 12 Dec 2018 at 8:42 AM EST

Valid CSS