Nice posts! I wish you had written them back when I was experimenting. I don't remember all the details of the problems I ran into. Prawn has a different language (not HTML) and has terrible diagnostic messages and documentation, so you can change a small thing and suddenly have no output and just have to experiment until you figure out what it's doing.
I don't remember exactly why I decided to bypass the wkhtmltopdf-based gems, but I remember that some code that didn't output what I expected in the gem worked fine when I just called wkhtmltopdf directly. I completely agree with the pain of installing. I'd say the first thing to do is write a really simple webpage and pass it to wkhtmltopdf on your development machine and your server. Use a couple different fonts and more than one page's worth, and perhaps some unusual css. > directly)... anyhow, I did write a couple blog posts on the subject which > maybe would be helpful: > > http://blog.structuralartistry.com/post/2316402105/using-wkhtmltopdf-with-ruby-and-rails > http://blog.structuralartistry.com/post/2327213260/installing-wkhtmltopdf-on-ubuntu-server -- 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.
