Colin,
Tried using page breaks today and they are not doing quite what I expected or is described.
PAGE BREAK BEHAVIOR
If I publish with the "Add a page breaks" (sic) checkbox checked my page looks different when viewed on-screen as well as when printed (which is contrary to what the rollover help tip says). Two differences:
1 -- Any text put in the "Notes" tab under "Publish" will display on-screen (and print) after the series/summary table for EVERY fleet. Without the checkbox it just displays (and prints) after the series/summary table for the last fleet. [As mentioned elsewhere, I strongly favor before rather than after but the same comment about repetition would apply.]
2 -- The white space between the end of a table (series/summary or race) [or the series note for a series/summary table] and the next text is increased. This is due to the pagebreaks being put into a <br> tag rather than some other kind of tag. Those <br> elements don't have a class so they cannot be set separately without setting all other <br> tags in the document (setting "display: none;" for the <br> tag fixes the problem as the "new line" characteristic of the tag is then ignored).
I would solve this by making two changes. First, the current tag is:
"<br style="page-break-after:always" />." That puts the tag as the last thing on a printed page. I would use a style of "page-break-before:always" instead and put it in a <div> tag with a class. That would put the tag as the first thing on a new page. The difference is that with it being the first page one can set the top printed margin for all pages except the first.
I would suggest "<div class="pagebreak" style="page-break-before:always"></div>" or leave the style out and include it in a class definition. The reason for always having a class (even if the style is hard-coded) would be to allow setting the top margin of a printed page (I tried this with latest Firefox and it works just fine). I think the preferred solution would be the class only.
GLITCH/ ANOMALY
I discovered a slight glitch which might need documentation or fixing. If in the "footer.txt" file you put your footer as <footer>text</footer> then there is no page-break before the last fleet. The "</footer> tag must be on its own line for there to correctly be a page-break before the last fleet. Either way, there is no page-break between the table for the last fleet and the footer, which is as it should be.
Art