From: William Victor Mote
Date: Tue, 22 Apr 2003 02:35:38 +0000 (+0000)
Subject: Move some content from areas.xml to renderers.xml.
X-Git-Tag: Root_Temp_KnuthStylePageBreaking~1579
X-Git-Url: https://source.dussan.org/?a=commitdiff_plain;h=f3c1ad2abe0d5f61d4306537631c47174a037a0d;p=xmlgraphics-fop.git
Move some content from areas.xml to renderers.xml.
git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196303 13f79535-47bb-0310-9956-ffa450edef68
---
diff --git a/src/documentation/content/xdocs/design/areas.xml b/src/documentation/content/xdocs/design/areas.xml
index e923eb770..2a6b26c3b 100644
--- a/src/documentation/content/xdocs/design/areas.xml
+++ b/src/documentation/content/xdocs/design/areas.xml
@@ -221,39 +221,6 @@ area tree in the spec) so that this information can be passed to the
renderer. This is useful for setting the title and organising the groups
of page sequences.
-
-
- Rendering Area Tree
-
-The rendering of an area tree is done by rendering each page
-to a suitable output. The regions are rendered in order and each
-region is contained by a viewport.
-
-
-The relevent structures that will need to be rendered are:
-Page
-Viewport
-Region
-Span
-Block
-Line
-Inline
-
-
-A renderer implementation does the following:
-
-
- - render each individual page
- - clip and align child areas to a viewport
- - handle all types of inline area, text, image etc.
- - draw various lines and rectangles
-
-
-An abstract renderer will be able to handle the generic positioning
-of child areas, iterating through areas that have child areas.
-
-
-