CanSplitImage

Use this section level rule to identify the segments of sections (images) that can be dynamically split.

CanSplitImage (Debug)

Parameter	Description
Debug	Optional. Include this parameter to tell the system to include debug information about when and how the section is split in the LOG.DAT file.

Keep in mind:

You must include the PaginateAndPropagate rule in the AFGJOB.JDT file. The PaginateAndPropagate rule looks for the CanSplitImage indicator. Without this rule, sections are paginated normally.
If the print driver produces output for a non-edge printer, such as PCL, you must have a header and footer that are copied on overflow. Otherwise, the data that falls into the non-print area is lost.
Text area objects must be flagged as Can span pages or the section is not split.
Text area sections that are greater 26,400 FAP units must be defined as Custom in the Paper Type field on the Page Properties tab. To add information to one of these sections, increase the paper height on the Page Properties tab to accommodate the increased size before you add the new information. Otherwise, the system may create a multipage section, which is not supported.
Text areas that are multipage sections are not supported.
This rule cannot split a section that includes a text area with an inserted file object.
This rule is not supported when you are using a group rule. The group pagination logic does not check for split sections, nor does it call the section split logic.

This table shows how each type of object is handled within a text area:

Object
Different fonts	Yes
Borders	Yes.
Background shading	Yes
Bullets or numbers	No
Columns	Yes
Boxes	Yes *
Fields	Yes
Files	No
Graphics (LOG, BMP, TIF, and PNG files)	Yes *
Charts	Yes *
Vectors	Yes *
Shaded areas	Yes
Bar codes	Yes *
Lines	Yes *
Boxes	Yes *
* If the object falls on the page to be split, the system moves it to the next page.

Here is how the system splits the section:

The system loads the section and flags it as inline.
The system duplicates the section. The new section follows the original section.
The system moves up the bottom of the original section to just above the footer.
The system moves the objects from the original section to the new section if the bottom of the object extends beyond the bottom of the original section.
If the object is a text area and is defined as Can Span, the system splits the text area, as described here:

The system makes sure the original section is not set to Can Grow.
The system creates the new text area in the new section and copies the object from the original text area into the new text area.
The system creates a list of the text areas to divide and repositions all objects moved to the new section. All objects are moved up as much as possible but maintain their relative positions.
The system then moves the section down as far as the objects are moved up. This preserves the relative position of the objects.
The system turns on the Can grow and shrink attribute and turns off the Can span pages attributes in the text areas earlier saved in the list. It then resizes the new section to its minimum size and turns the Can Span attribute back on. Pagination continues as usual with two sections, instead of one.

Here are some examples that show what happens when a text area with a border is split:

Split image

Shaded areas are split in a similar manner:

Split image