In recent years, we've generated PDFs in the following ways:* Simple HTML generation within Interchange, then passed through HTMLDoc (http://htmldoc.org) for conversion to PDF. * Use Postscript::BasicTypeSetter to generate Postscript, then pass that through Ghostscript to generate PDF as needed.
* Use PDF::API2 within custom Perl modules/routinesThe reliance on HTMLDoc for HTML-to-PDF conversion has the benefit of simplicity, but it's not particularly rich and effectively only offers the level of sophistication of a version-3 browser. The Postscript-based approach provides complete control over fonts, positioning, etc., but was done some years before PDF::API2 was available; it was a successful approach but doesn't seem likely to be the most logical approach now. PDF::API2 is pretty comprehensive and completely met our needs for the uses to which it was put; however, it's relatively low level compared to the level most of us are accustomed to working at when dealing with presentation/content, so it would hard to offer a generic usertag that exposed the full richness of the PDF::API2 interface.
So, our collective suggestion on this topic: use PDF::API2, but perhaps plan on making custom usertags per use case or something like that. It may be possible to make a usertag that can handle a number of simple tasks for PDF generation, but we'll always need to drop directly to Perl in order to get particularly fancy.
Thanks. - Ethan -- Ethan Rowe End Point Corporation suppressed _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.