Although I posted this same comment on a blog entry that discussed your lack of public API for rendering, I read somewhere on the site that I should post my comment in the forums so that it could get tagged as a feature request. So, here it is again for that purpose.
Thank you in advance for considering implementing this functionality. It may be a show stopper for us if we are not able to find a work around to this limitation.
We are wanting to use Aspose to create final documents on the fly from an RTF template. One of the issues that we have is that the final document cannot contain the electronic signature block orphaned on the last page by itself. We have tried using the widow/orphan and keep w/next settings in Word, but this does not always render the document in an acceptable format as it can possibly pull a large paragraph from the previous page to the last page and thus create too much white space on the second to the last page.
The only acceptable format is to evaluate whether or not the signature block is orphaned on the last page and if it is to put a section break two lines from the bottom of the last paragraph on the previous page, thus forcing the last two lines of the previous page to flow to the last page with the signature block.
Not having the ability to determine which page a given paragraph is on prohibits us from being able to do this in Aspose. Please consider exposing your rendering API publicly as soon as possible as the lack of this functionaly may prevent us from utilize Aspose as our document rendering solution.