The <leaf-settings/> command

This command allows you to override the default looseleaf settings when processing a full looseleaf partition.

Where allowed

The $document mapping.

Range of effect

The entire document.

Attributes

group-start

Specifies the folio assigned to the first leaf group in the partition. If not specified, then the value of the partition First Folio is assumed.

group-gap

When using a partition based numbering scheme, leaves may be organised into one or more leaf groups. The group-gap specifies the size of the folio numbering gap between each leaf group. The default is 100.

foliosep

Declares the folio separator string inserted between the partition identifier and the page folio, or the partition link identifier and the page link folio. The folio separator string will not appear if the content of the partition identifier or link identifier is defined as a null (empty) string. The default folio separator is an &mdash;.

levelsep

Specifies the point page level separator TopLeaf uses when rendering a full looseleaf page folio that declares one or more point page levels.

The point page level separator identifies either a single punctuation character inserted before each point page level or a bracket character pair that encloses each point page level. The exception is the 999(ab) page folio format, which supports a primary folio index and one additional point page, with the level separator specifying the bracket character pair enclosing a single point page level.

The following table explains how to render some common stroke page formats:

To produce this page folio output ... Select this page folio format ... And define this point page level separator ...
999/9/9 999/9/9 /
999.1.1 999/9/9 .
999,1,1 999/9/9 &#44; (or &x#2c;)
999(1) 999/9/9 (
999(a) 999(a) (
999[a] 999(a) [
999{a} 999(a) &lcub; (or &x#7b;)
999<a> 999(a) &lt;(or &#60;)
999a 999(a) "" (a null string)
XII XII/9/9 /
xii.9.9 xii/9/9 .
[Note] Note
  1. With the exception of a limited number of reserved characters you cannot use character references or entity references to specify a point page level separator character.

  2. The point page level separator is always defined as a single character.

  3. The default point page level separator character is a /

  4. For more information about looseleaf typesetting, see the User Guide.

leaf-split

When a leaf boundary is positioned within the scope of scanned document content, TopLeaf composes the leaves sharing that boundary as a single unit, irrespective of whether the content of either leaf is changed or the leaves are manually included. In the case where a leaf is changed or manually included, and a leaf boundary is positioned within the scope of scanned document content, TopLeaf applies an automatic leaf inclusion to the adjacent leaf. If you need to disable automatic leaf inclusion for scanned content, set this value to legacy.

max-pointlevels

The maximum number of leaf point page levels permitted. If a leaf within a leaf group or leaf section defines a folio with more than the specified number of point page levels, TopLeaf will automatically recompose the content of the leaf group or leaf section as a single unit. The default is 4.

max-spread

The maximum amount of interword space permitted within the last line of a leaf, expressed as a percentage of the column width. Where a published leaf boundary is positioned within a justified paragraph, subsequently adding or removing content before that boundary may cause the last line to be rendered with excessive interword spacing. The last line of a leaf will be set ragged right if the percentage of interword spacing in that line exceeds the specified value. The default is 33 percent.

warn-leafoverflow

When you compose the first release after a manual leaf split, unexpected overflow leaves are listed as a messages in the typesetting log file. If you want TopLeaf to generate a warning when unexpected overflow leaves are created, set this value to yes.

implied-break

When changing to a new page type, TopLeaf automatically generates an implied content break if the orientation of the selected and current page types differ, and where an explicit content break has not been declared.

If leaf, then the selection of a page type with a different orientation will force a leaf break, and subsequent content begins at the start of the next leaf. This is the default for a full looseleaf partition.

If page, then the selection of a page type with a different orientation will force a page break, and subsequent content begins at the start of the next page. This is the default for a partition that does not use a full looseleaf page management model.

[Note] Note

When the implied break mode is leaf, TopLeaf may need to insert a blank page to ensure that any following content begins on an odd numbered page. Set the implied break mode to page if you do not want TopLeaf to insert a blank page each time the page orientation changes.

check-legacyboundaries

In a full looseleaf update, a leaf boundary may be of type inline (located within a paragraph), or coincide with a paragraph block boundary. TopLeaf refers to the leaf boundary type when initialising the paragraph style at the beginning of a run of changed or included leaves. By default, the leaf boundary type is tracked as each leaf is created, but this information was not recorded for leaves created using TopLeaf legacy stylesheets.

To force TopLeaf to dynamically check if a legacy leaf boundary is of type block or inline, declare the command:

<leaf-settings check-legacyboundaries="yes" />
leaf-pagetypes

By default, when the leaves of a full looseleaf partition are typeset, a set of initial page types may be assigned from values defined within the first leaf of a run of changed or included leaves, or from values defined within each unchanged leaf. You can overrule this behaviour by declaring the command:

<leaf-settings leaf-pagetypes="ignore" />

Applying this state means that any page types declared within each leaf are always ignored, and that the page types assigned at the start of each leaf are determined entirely by the stylesheet mappings.

internal-leafgroups

When using a partition based numbering scheme, leaves can be organised into one or more leaf groups. By default, each leaf group creates a numbering boundary across which a run of changed or included leaves may not extend. You can overrule this behaviour by declaring the command:

<leaf-settings internal-leafgroups="ignore" />

Applying this state means that the leaf group status for all internal leaf groups is ignored when typesetting a partition update, and TopLeaf is permitted to extend a run of changed or included leaves across those leaf group boundaries. When the partition is published, the leaf group status for all internal leaf groups will be removed.