2020.1

You only need to call merge.section.paginate() in a Post Pagination Script if the script has
added or removed content to such an extent that the page boundaries need to be renewed.
For an example see: "Creating a Table Of Contents" on page429.
Pagination
The Pagination object that is accessed via the section object (see "section" on page915)
contains the total page count, sheet count and start/end page numbers for a single section.
These properties are read-only and are only available in Post Pagination Scripts (see "Post
Pagination Scripts" on page427).
For the total page and sheet count of all Print sections together use the merge object's
"Pagination" on page926 (see also: "merge" below).
For information about where an element is located and the counts of pages and sheets in a
page bundle - a group of sections in which the page numbering continues - use "info()" on
page913.
Field Type Description
pageCount Number The total number of pages in this section.
pageEnd Number
The index (1-based) of the last page in this section.
pageStart Number The index (1-based) of the first page in this section.
sheetCount Number The total number of sheets in this section.
sheetEnd Number
The index (1-based) of the last sheet in this section.
sheetStart Number
The index (1-based) of the first sheet in this section.
merge
In Control Scripts, the root level instance of the object merge is the entry point from where you
can query and change the way contexts are merged. It gives access to the template with all its
contexts and sections.
For more information about Control Scripts, see "Control Scripts" on page412 and "Control
Page 924