prawn

If you're using Ruby, prawn is a nice solution also, but my favorite is going via LaTeX.

It's just unfamiliarity - you would have the same reaction to a prawn if you hadn't grown up with it.

I got my Prawn setup into a reasonable state pretty early, and it's be Mostly Fine, Just Fine.

I'm rather less worried about annoying them, because i eat enough prawn toast that i'm already on their shitlist.

Thai Man: Menu boy no be coward, like shrimp; menu boy be brave, like prawn.

When a prawn tail has been shelled (but tail left on for presentation) and in tempura, I will eat the tail also.

Thank you so much for the thoughtful response, prawn.

Easy to get on a roll as @prawn mentioned.

Bit of a prawn salad in your view, then?

(Saying that, if I hadn't seen a prawn until now, I think the appearance would put me off).

I'd probably prefer something allowing everything to be defined from the Ruby side (other than the images themselves, of course, or at least other than the raster ones), similar to how Prawn works.

I'm responding to you and at no point do I feel like I am marketing "prawn" or anything I do online.

I'm Prawn's maintainer and I think the "fine control over rendering at the cost of having to finely control your renderer" is spot-on.

Hi prawn, rightly or wrongly, we live by the "launch fast" maxim.

If you don't know the real name of the gem, you Google for functionality or common name ([ruby prawn gem]), find a blog post, copy/paste the line that starts with "gem install" (gem install prawn), and then go back to whatever you were doing.

Prawn provides very fine control over the rendering, at the expense of having to finely control your render.

Another vote for Prawn, which I use for on-the-fly PDFs at cycle.travel (Ruby but not Rails).

Stick with Prawn, as it is sanity saving for this task.