Austin Ziegler has been planning to eventually rewrite PDF::Writer and
get it up to date with the newest Ruby hotness. Of course, that's an
ambitious project and for the time being, it doesn't seem like we'll
see that happen in the near future.
Ruport is habitually fixing PDF::Writer issues, some of them are
stylistic, which probably deserve to stay in Ruport, some are
convenience, which the mileage may vary on.
However, there are some bonifide bug fixes in Ruport's PDF
implementation, that ultimately belong in PDF::Writer.
Austin seems to be all tied up, but he expressed interest in having
someone act as maintainer for the 1.1 branch, applying some of the
defect patches and cleaning things up a bit. Even though I'd be a
good fit for this role, I don't have the cycles to do it.
If anyone out on this list is interested in possibly volunteering to
work on this(ruport commiters included), we want to hear from you.
I'd be happy to help you along insofar as I'll point you at all the
tricks Ruport does to fix stuff, and then put you in touch with Austin
so we can maybe solidify PDF::Writer a bit.
While this will without a doubt benefit Ruport, it'll also benefit the
PDF::Writer audience in general, so it's a good shot to do that, if
you're interested. The ideal candidate will have some deal of disdain
for the library's implementation and will be willing to solve annoying
and painful problems.
-greg
