aboutsummaryrefslogtreecommitdiffstats
path: root/src/documentation/content/xdocs/design/breakpos.xml
diff options
context:
space:
mode:
authorWilliam Victor Mote <vmote@apache.org>2002-11-29 22:00:32 +0000
committerWilliam Victor Mote <vmote@apache.org>2002-11-29 22:00:32 +0000
commitdbd6d2d0a69d1cab2b30efc4680177c350efc473 (patch)
treec260f1b8453fff5d13e4cd2fe6eff58462a258c5 /src/documentation/content/xdocs/design/breakpos.xml
parent728652fb0a5c1c1feba55af0c0231978c6d5a171 (diff)
downloadxmlgraphics-fop-dbd6d2d0a69d1cab2b30efc4680177c350efc473.tar.gz
xmlgraphics-fop-dbd6d2d0a69d1cab2b30efc4680177c350efc473.zip
white-space and line-ending fixes
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@195676 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'src/documentation/content/xdocs/design/breakpos.xml')
-rw-r--r--src/documentation/content/xdocs/design/breakpos.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/documentation/content/xdocs/design/breakpos.xml b/src/documentation/content/xdocs/design/breakpos.xml
index c2eaa1aed..80bf40155 100644
--- a/src/documentation/content/xdocs/design/breakpos.xml
+++ b/src/documentation/content/xdocs/design/breakpos.xml
@@ -35,11 +35,11 @@ non-stacking direction (at least for inline areas, it must have both). Flags
indicating various conditions (ISFIRST, ISLAST, CAN_BREAK_AFTER,
FORCE_BREAK_AFTER, ANCHORS etc). A BreakPoss contains a reference to
the top-level LayoutManager which generated it.
-</p>
+</p>
<p>A BreakPoss contains an object implementing
the BreakPoss.Position interface. This object is specific to the layout
manager which created the BreakPoss. It should indicate where the
-break occurs and allow the LM to
+break occurs and allow the LM to
create an area corresponding to the BP. A higher level LM Position
must somehow reference or wrap the Position returned by its child LM in its
BreakPoss object. The layout manager modifies the flags and dimension
@@ -59,7 +59,7 @@ create the corresponding areas.</p>
</section>
<section>
<title>A walk-through</title>
-<p>Layout Managers are created from the top down. First the
+<p>Layout Managers are created from the top down. First the
page sequence creates a PageLM and a FlowLM. The PageLM will manage
finding the right page model (with help from the PageSequenceMaster)
and managing the balancing act between before-floats, footnotes and