This is an old revision of the document!
Policy requirements:
Technical requirements:
The paginated .txt publication format must
The unpaginated .txt publication format must
Current requirements re: page breaking for xml2rfc v2
#172: page-breaking enhancements Improve the PI autobreaks="yes". Currently, it seems to be "yes" by default but has no effect. It should prevent a page break from appearing in - the middle of a figure (see Figure 1 in the attached file) - in the middle of a reference (see Section 10.2 in the attached file) - between a section title and the first sentence (see Section 5 in the attached file). This is the same as #72, which is marked fixed, but doesn't seem to be for this case. If there is an Appendix A, insert a page break before it. (This could be tied to rfcedstyle="yes", as it's RFC Editor style.) Or, improve the ability to insert a page break -- vspace blankLines="100"
doesn't always work.
Ticket URL: <http://trac.tools.ietf.org/tools/xml2rfc/trac/ticket/172>]
Current internal guidance to the RPC:
"3+ lines held together" i.e., at the bottom of a page, there is not a single line or 2 lines (unless they are their own paragraph). Keep a section title with the first 3 lines of the section. Keep a figure on one page. This includes its title (if any). - if figure does not fit on one page, break between discrete items in the figure. Keep a table on one page. This includes its title (if any). - if table does not fit on one page, break between rows. Keep a term with its definition. - if definition is long (over 5 lines), keep at least the first 3 lines of the definition with the term. Keep a given reference on one page. Start Appendix A on a new page.
More subjective: Keep intro text with what it's introducing. (Example: text that introduces a list, an equation, or a piece of pseudocode) Break pseudocode nicely.