+++ /dev/null
-<refentry xmlns="http://docbook.org/ns/docbook"\r
- xmlns:xlink="http://www.w3.org/1999/xlink"\r
- xmlns:xi="http://www.w3.org/2001/XInclude"\r
- xmlns:src="http://nwalsh.com/xmlns/litprog/fragment"\r
- xmlns:xsl="http://www.w3.org/1999/XSL/Transform"\r
- version="5.0" xml:id="refentry.pagebreak">\r
-<refmeta>\r
-<refentrytitle>refentry.pagebreak</refentrytitle>\r
-<refmiscinfo class="other" otherclass="datatype">boolean</refmiscinfo>\r
-</refmeta>\r
-<refnamediv>\r
-<refname>refentry.pagebreak</refname>\r
-<refpurpose>Start each refentry on a new page</refpurpose>\r
-</refnamediv>\r
-\r
-<refsynopsisdiv>\r
-<src:fragment xml:id="refentry.pagebreak.frag"><xsl:param name="refentry.pagebreak" select="1"/></src:fragment>\r
-</refsynopsisdiv>\r
-\r
-<refsection><info><title>Description</title></info>\r
-\r
-<para>If non-zero (the default), each <tag>refentry</tag>\r
-element will start on a new page. If zero, a page\r
-break will not be generated between <tag>refentry</tag> elements.\r
-The exception is when the <tag>refentry</tag> elements are children of\r
-a <tag>part</tag> element, in which case the page breaks are always\r
-retained. That is because a <tag>part</tag> element does not generate\r
-a page-sequence for its children, so each <tag>refentry</tag> must\r
-start its own page-sequence.\r
-</para>\r
-\r
-</refsection>\r
-</refentry>\r