On 14 May 2010, at 19:23, Jonathan Steel wrote:
prince: /Users/jonathan/tmp/97.html: error: could not load input
it. Being so expensive, Prince pretty much had to work without a
hitch
if I was going to spend any time trying to make it work.
So what I really meant by this was that with several other options
available, things had to work almost immediately if I was going to
spend
any time considering them. Although it is definitely our site that is
causing the problem with Prince, finding the problem in the site could
be just as much work as creating the pdf from scratch using something
like prawn. If I did fix the site, then I still had no guarantee
that it
would work with Prince when I was done, so I might as well just make
the
PDF from scratch.
Invalid pages in the browser are just as evil, aren't they ;-) I
sometimes wish browsers were a lot less forgiving on that part, it
would avoid a lot of seemingly unrelated issues, especially when you
start using Javascript DOM manipulations.
When we tried Prawn, the size of the PDF it produces was about twice
of what a similar Prince document spits out. I'm assuming the output
it far from optimized. That said, it's a very valid option in some
simple PDF cases and certainly less pricey :-)
Best regards
Peter De Berdt
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en.
