Actually our RPG2PDF API is meant to replace O specs in an existing RPG
program and write directly to a PDF instead of a print file.
It does work with relatively exact positioning, but we have a framework
sample which allows an RPG programmer to simulate what they would be
doing in a plain old report output.
In the background we map to the lower level iText calls to do the
physical PDF generation, so here's another vote for iText :-)
Regards,
Richard Schoen
RJS Software Systems Inc.
"Get the information you need. Now!"
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 7
date: Thu, 25 Feb 2010 17:16:14 -0800 (PST)
from: Nathan Andelin <nandelin@xxxxxxxxx>
subject: Re: [WEB400] RPGCGI - Convert HTML page to PDF
From: Simon Coulter
Umm ... maybe it's just me but why would you do it this way? Surely
the correct approach is to build the PDF from the original data not
try to convert HTML to PDF.
It may help if someone were to speak up about generating PDF files
directly. If I recall correctly the API offered by RJS seems rather
complex when it came to absolute positioning and & GUI formatting.
I really like externally defined CSS and Dreamweaver for HTML
formatting, and transforming HTML templates to stream files, using
variable substitution with RPG. So much easier. CSS, in particular can
be applied to all types of reports - simply by reference.
-Nathan.
midrange.com
