Looseleaf methods

TopLeaf supports two forms of looseleaf:

  • full looseleaf, which is designed to minimize the size of each update pack;

  • change pages looseleaf, which is designed to minimize the size of the whole updated publication.

Which method you choose is governed by a number of factors.

The full looseleaf method:

  • Produces smaller update packs for print publications.

  • Supports two page or single page leaves. A two page leaf consists of a front and a back page. Both pages are included in the numbering sequence. In single page looseleaf, each leaf consists of a single page which always has an unnumbered back in the printed version.

  • Uses a sequential page numbering scheme. If the replacement material for an existing leaf cannot be rendered on that leaf, the excess material overflows onto one or more point pages.

  • Supports gapping and link lines to allow for growth without point pages.

  • Declares all content as a single flattened document file — with the exception of external images, no content may be referenced from an external file. This is because the content of the partition document is allocated to one or more leaves, and the document leaf boundaries correspond to a portion of that file.

  • Creates updates based primarily on changes to the document content. Each time the content is modified TopLeaf identifies all leaves where the content has changed. Leaves that do not contain changed content can also be manually, conditionally, or automatically included in a release.

  • Allows editorial intervention and checking. For example, if a change in one part of the document causes a change to a cross reference in another location, then you may manually include those other leaves in the release. When non-adjacent leaves within a section of the publication change frequently, you may consolidate those changes to avoid the creation of an unwieldy collection of point pages that run to several levels.

  • Provides limited support for on-the-fly transformations of the input document stream.

  • Places some restrictions on data and mappings.

whereas the change pages method:

  • Produces larger update packs, since a change early in a section may require the whole remainder of the section to be included in the release. However the size of the whole updated publication is optimized.

  • Uses a section based page numbering scheme. Point pages and link lines are not required.

  • Assigns a unique identifier to each page and then identifies changes within the rendered pages to determine the set of pages in a release.

  • Issues leaves in the update pack.

  • Places no restrictions on data or mappings.

  • Requires minimal editorial intervention and checking and is ideal for full automation.