I'd use MS write as a pre-installed application reading RTF and printing to a PDF printer. Your perl just needs to control the process, maybe by using a "print to PDF" dll. I'm working in software validation for the pharmaceutical industry, so I know that customers would highly prefer use of standard software. The development and validation effort for a perl script is much higher. Getting into touch with the final customer might be difficult in your position, but would be worth it. | [reply] |
| [reply] |
MidLifeXis,
Thank you for your input! This application needs to be entirely self-contained, however, and there is no way that I can demand that users install something as huge as OO.o -- or include it as part of my installation. There are actually smaller third-party tools (see, e.g., pdfforge.org) available out there for doing this, but I need to accomplish this within my own application. Do you have any ideas for doing this entirely within Perl?
-Brian
| [reply] |
Aaah, this is for on a customer machine. That makes a difference. I took the OP as doing a batch conversion or a document server of some sort.
In the described case, I would agree, OO with a perl driver may not be the easiest sell.
--MidLifeXis
The tomes, scrolls etc are dusty because they reside in a dusty old house, not because they're unused. --hangon in this post
| [reply] |