Have you thought about taking a look at what the Sql-Ledger people are using? It seems to me that they are using perl to fill in and "compile" LaT_EX templates to postscript and then passing the result off to Ghostscript to make the PDF.

Of course some will say that LaT_EX is nasty to use / learn, but it's really quite straight forward, stable, excessively documented, has many friendly/helpful users, and portable ( I think the only thing you can't find a binary for is EPOC/WinCE/PalmOS etc and even that may be untrue!).

Ghostscript is much the same.

The only real downside is needing to have access to both in addition to Perl, especially since LaT_EX does come with "the kitchen sink" (you can get a set of CTAN (comprehensive TeX archive network) disks with everything for cheap.) and is a large install.

I'm kind of thinking that maybe PDF::Template could be a front for such a system to, I don't know, maybe help abstract out the *icky* details? Who knows maybe the Sql-Ledger people (sic) would drool all over for something like that. I know I would, I looked at PDF::Template quite a while ago and decided that, as it stood at that time, reading perlop.c was better for my mental health ;).

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.