All resources, except RunList, are allowed to be partitioned with RunIndex.
The RunList uses a zero-based page numbering. For example, 0 is the first page of the document and 9 is the tenth page of the document.
Negative numbers reference pages from the back of a file. For example, -1 is the last page of the document, and -2 is the before-last page of the document.
Syntax
XPath: //<Element>[@PartIDKeys="RunIndex"]/<Element>/@RunIndex
Type
Range list
Supported values
|
@RunIndex |
Description |
|---|---|
|
Range list |
Selects a set of logical pages from the RunList. A range list is an array of pages ranges and individual pages separated by whitespace. A range consists of two integers connected with a tilde (~). |
For ranges with negative values, only one range of the kind [n ~ -m] is supported, where n>0 and m>0.
All page rages with positive values are supported.
Individual pages: "0", "2 5", "50 100 -1"
Ranges: "0 ~2", "5 ~ 22 50 ~ 100", "0 ~ 1 2 ~ -3 -2 ~ -1"
Mixed: "0 1 ~ 3 5 22 100 ~ -1"
If partitioned, GatheringParams, StitchingParams, and FoldingParams must have the same RunIndex partition values.
When different resources are used, GatheringParams, StitchingParams, and FoldingParams are allowed to have different RunIndex partition values.
Within the same resource, the values for RunIndex are not allowed to overlap or be repeated. So the following is not correct:
<DigitalPrintingParams PartIDKeys="RunIndex">
<DigitalPrintingParams RunIndex="0 ~ 3" …/>
<DigitalPrintingParams RunIndex="3 ~ 4" …/> => WRONG
<DigitalPrintingParams RunIndex="5 ~ -1" …/>
<DigitalPrintingParams>