On Tue, 8 Mar 2005 14:02:47 -0500 (EST), Chris Devers <[EMAIL PROTECTED]> wrote:
[...]
> Similarly -- and this way lies madness, I admit up front -- just run the
> script on a system that can use AppleScript or COM (or WSH or whatever
> it is, I'm not a Windows programmer) to just automate interacting with a
> regular browser like Firefox or Safari, and save the result that way. If
> you run it on OSX, you can go straight from this to a PDF file for free.

I've done this on Windows for web pages that were IE only.  It was a
small PITA to get running (you have to install a driver to print to PDF
files and there were some magic parameters that had to be set by
hand in IE so that it would print to a file), but not that hard.  What was
hard was that it was unreliable, and every so often needed to be
kicked.  Which was OK since it was a batch process that produced a
bunch of them that were stored as files.  (I would NOT do this for an
interactive web page!)

I was very happy when those web pages got cleaned up so that we
could switch to html2pdf instead.

Cheers,
Ben
 
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm

Reply via email to