I have a simple HTML layout using two columns. Example markup can be reviewed at http://jsfiddle.net/MJzZE/

This layout is going to represent a 5 - 7 page report, so there must be page breaks.

The content of the columns is user-provided markup, so it is varies at runtime, is not easily split up, and I don't know how large it will end up being on the page -- so I don't know where I would put manual page breaks.

Intuitively, the user expects the content to fill both columns on page 1 first, then both columns on page 2, etc. So column 1 on page 2 should begin with the overflow from column 2 on page 1.

But EO PDF appears to just make two very tall columns (as the browser does) then slice them at page boundaries. The effect is that the content of column 1 extends to page 2 and onward before wrapping back to column 2 on page 1.

EO PDF also slices images in half if they happen to span a page boundary.

Both effects can be seen at http://screencast.com/t/ojIPeamht

It seems like these issues make a multi-column layout across pages infeasible. Is there a way to get this done?

Thank you for the information. I am trying those settings and getting good results, with one exception: images are still cut off at page boundaries. I need for the images to be pushed to the next column if they do not fit in the remainder of the current column. Example shot:

http://screencast.com/t/jJsq2mLdDItQ

The grey box is an img tag with display: inline-block. Is there a way to keep it from being cut off?

Another concern I have is that HtmlToPdf.Options is a static property. This is a routine on a web server that may be running several times at once. Won't the options set bleed between worker threads? Or are they somehow threadsafe?