On Wed, January 18, 2012 9:12 am, James Simmons wrote:
I'm still kind of puzzled about how we're going to deal with page breaks (and numbers) in the final output.
Am I correct in assuming that the final output will be HTML? If so, I see two options: 1. Place an anchor at each page break, e.g.: <a id="pg0027" title="27"></a> (I don't like self-closing anchor tags because many user agents don't understand them). This will provide a mark inside the file that will be invisible to the user, but can be used for navigational purposes, as well as automated refactoring. 2. Use a page-break <span>, e.g.: <span id="pg0027" class="page-break">27</span> This case is a little more intrusive, but on a CSS-enabled user agent the page numbers can still be suppressed by adding a CSS rule to hide page numbers, e.g.: span.page-break { display:none } It also allows fancy CSS to move page numbers into the margin. I'm less happy with this solution because I have a rule of thumb that says that everyone should author HTML in such a way that the rendering should be acceptable (not necessarily ideal) on a user agent that doesn't understand CSS. HTH Lee