[Accessibility conventions are described at the bottom of the page]
*** This is a free preview excerpt of a commercial publication. ***

10. Breaks, keeps, spacing, borders and backgrounds
[> 11.][< 9.0][^^^]
10.0 Spacing and arrangement constraint definition
[> 11.][< 10.][^^][^^^]
An area's placement is governed by XSL-FO stacking rules and the area's traits refined from object properties
[[1] - at the block level in a page
[[2] - before-float-reference-area
 [2] - normal-flow-reference-areas (page columns)
 [2] - footnote-reference-area
][1] - at the line level in a block
[[2] - lines are generated by the formatter, not the stylesheet
 [2] - different line-stacking strategies are available to be specified
][1] - at an inline-level in a line
[[2] - characters, graphics, etc.
]]
Areas that are stacked normally are stacked in the pertinent progression direction
[[1] - page-level reference areas stack in the block-progression direction
 [1] - lines and table rows stack in the block-progression direction
 [1] - page column, table column and inline areas stack in the inline-progression direction
]
The "natural" stacking of areas may produce typographically unpleasant results
[[1] - initial values implement common-sense formatting control for consistent presentation
 [1] - many traditional conventions break the behavior of the initial values
[[2] - e.g. needing to keep a heading in the body on the same page as the first paragraph to which the heading applies when the naturally occurring page break would otherwise come between the two items
 [2] - necessary sometimes to override the physical arrangement of information implied by the initial values for area properties
]]
Conditionality and precedence can eliminate areas from being rendered
[[1] - can prevent the unnecessary use of inter-block spacing when pagination renders a block without an adjacent sibling
[[2] - e.g. a block forced to the top of a new page doesn't always need the space defined for between blocks to be rendered
][1] - formatting special cases can be accommodated with simple specifications of intent
[[2] - the formatter determine the applicability of spaces based on object properties
 [2] - the transformation process can ascribe properties easier than determining space behaviors
]]
Numerous properties are available to specify these nuances of layout
[[1] - arbitrarily breaking the flow of content to a new column or page
 [1] - maintaining a minimum number of widow and orphan lines of a block on a page
 [1] - keeping information together in the same reference area
 [1] - drawing borders around information
 [1] - painting backgrounds behind information
]

*** This is a free preview excerpt of a commercial publication. ***

This is an accessible version of Crane's commercial training material. The content has been specifically designed to assist screen reader software in viewing the entire textual content. Figures are replaced with text narratives.

Navigation hints are in square brackets:
[Tx.x] and [Fx.x] are textual representations of the applicability icons;
[digit] indicates list depth for nested lists;
[link [URL]] indicates the URL of a hyperlink if different than link;
[EXAMPLE] indicates an example listing of code;
[FIGURE] indicates the presence of a figure replaced by its description;
[>] jumps forward;
[<] jumps backward;
[^] jumps to start of the section;
[^^] jumps to the start of the chapter;
[^^^] jumps to the table of contents.
Suggestions for improvement are welcome: [info@CraneSoftwrights.com]
Book sales: [http://www.CraneSoftwrights.com/links/trn-acc.htm]
Information: [http://www.CraneSoftwrights.com/links/info-acc.htm]
This content is protected by copyright and, as there are no means to protect this accessible version from plagiarism, please do not make any commercial edition available to others.

+//ISBN 978-1-894049::CSL::Courses::PFUX//DOCUMENT Practical Formatting Using XSL-FO 2008-01-27 17:30UTC//EN
Practical Formatting Using XSL-FO
Seventh Edition - 2008-01-27
ISBN 978-1-894049-19-1
Copyright © Crane Softwrights Ltd.