You must change the page size before newPage(). There's always a degree of uncertainty about when a paragraph goes to the next page and that can cause problems even in well written programs. Layout rules are a complex subject and even TEX gets it wrong sometimes.
All the apps I have in production use PdfPTable and ColumnText placed at absolute positions using my (simple) layout rules. The extra effort is not that much and the results are always as expected.
The reports in question need to be rendered both as PDF for printing, and as HTML for import into a spreadsheet package, so using PdfTable is not an option.
I still don't understand why the switch from landscape to portrait should only "half take effect". I am seeing this behaviour after a document.newPage(), which isn't taken into account in the example code you posted, which shows a problem when page orientations half way through a table render.
Would it be a possible solution to create a method document.newPage(Rectange.A4), meaning "I want a new page, and that new page must be portrait"?
Regards, Graham --
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ iText-questions mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/itext-questions
