It would be useful to know where actual page breaks were created by original XHTML line number.

Uses:
1. End-users usually refer to errors on page x in a PDF and it would be handy to locate at least the line number of the offending source markup

2. It would be nice to feed the eventual page break information back to the markup (and to the end user) so that users can make informed decisions about whether to force a page break or remove extra space etc. in the original markup.

I could envision a quick Prince function that didn't actually generate a PDF but rather inserted <forcedpagebreak> and <nonforcedpagebreak> tokens in the original markup (or an output file).

-John

John Clarke
Cornerstone Systems Northwest Inc.

Thanks John, good suggestions!

It's a bit tricky for us to do this now, as by the time we get to page-breaking we've lost track of exactly where in the input documents and style sheets the content came from. However, once we start work on producing tagged PDFs it will be more feasible to do this, as we will be keeping closer track of the relationship between input and output documents.

Thanks Mike,
Yes, this was just a suggestion that would empower the end-user to make some of the page break decisions without using trial and error. We can live without it, but it sure would be nice. (and not nearly as cool as vector image inserts )
-John

John Clarke
Cornerstone Systems Northwest Inc.

Would you be interested in an interactive way of adjusting the paragraph tracking in order to do page fitting?
Google "Princess xml 2010".

Jim Albright
Wycliffe Bible Translators