Regarding the questions about our Pro-IV -> XML + XSL -> PDF solution.
We only use this method for form type reports, not for lists. With list reports, the layout (e.g. lines, fonts, etc)
aren't so important for our users, and regular Pro-IV printing is quicker.
When you already have a report function in Pro-IV, changing it to output to XML isn't difficult. We use a few
global logics to initialise the XML file and add records to it, all within the existing report characteristics.
We don't use the native XML report, because we made this solution before Pro-IV could ouput XML. And still
there are a couple of limitations with the Pro-IV XML report that makes it unusable for us.
Overall, not much extra work to be with the report function, once you have the framework ready.
The XSL stylesheet is where most work will be needed, depending on how complex the report is. If it is only
a list, you only have to list the tag names and adjust the sizes.
As I said, we only use the solution for form reports, e.g. invoices. Many of these need some of the information
accurately placed on the paper, for OCR scanning, and will require some fine tuning.
We also have a couple reports that produce graphs that is made with SVG in the stylesheet. It works very
well, but requires some effort to program.
Joseph: Page breaks are not an issue with XSL FO. From what you write, I guess your reference is HTML. With
XSL FO (and PDF) you work with pages and and you can specify static headers and such.
Check it out at "http://xml.apache.org/fop".
I've attached a sample. Warning: Norwegian language is used.
And I'll attach one more sample to show how graphs are included.