From f3c1ad2abe0d5f61d4306537631c47174a037a0d Mon Sep 17 00:00:00 2001
From: William Victor Mote <vmote@apache.org>
Date: Tue, 22 Apr 2003 02:35:38 +0000
Subject: [PATCH] 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
---
 .../content/xdocs/design/areas.xml            | 33 -------------------
 .../content/xdocs/design/renderers.xml        | 17 ++++++++++
 2 files changed, 17 insertions(+), 33 deletions(-)

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.</p>
 </section>
-
-<section>
-  <title>Rendering Area Tree</title>
-<p>
-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.
-  </p>
-  <p>
-The relevent structures that will need to be rendered are:
-Page
-Viewport
-Region
-Span
-Block
-Line
-Inline
-  </p>
-  <p>
-A renderer implementation does the following:
-  </p>
-       <ul>
-       <li>render each individual page</li>
-       <li>clip and align child areas to a viewport</li>
-       <li>handle all types of inline area, text, image etc.</li>
-       <li>draw various lines and rectangles</li>
-       </ul>
-  <p>
-An abstract renderer will be able to handle the generic positioning
-of child areas, iterating through areas that have child areas.
-  </p>
-  </section>
-
   </body>
 </document>
 
diff --git a/src/documentation/content/xdocs/design/renderers.xml b/src/documentation/content/xdocs/design/renderers.xml
index de8b461ec..6de480243 100644
--- a/src/documentation/content/xdocs/design/renderers.xml
+++ b/src/documentation/content/xdocs/design/renderers.xml
@@ -159,6 +159,23 @@ rendering is used to draw the pages onto the printjob.</td>
 However, the AbstractRenderer does most of what is needed, including iterating through the tree parts, so it is probably better to extend this.
 This means that you only need to implement the basic functionality such as text, images, and lines.
 AbstractRenderer's methods can easily be overridden to handle things in a different way or do some extra processing.</p>
+      <p>The relevent AreaTree structures that will need to be rendered are:</p>
+      <ul>
+        <li>Page</li>
+        <li>Viewport</li>
+        <li>Region</li>
+        <li>Span</li>
+        <li>Block</li>
+        <li>Line</li>
+        <li>Inline</li>
+      </ul>
+      <p>A renderer implementation does the following:</p>
+      <ul>
+        <li>render each individual page</li>
+        <li>clip and align child areas to a viewport</li>
+        <li>handle all types of inline area, text, image etc.</li>
+        <li>draw various lines and rectangles</li>
+      </ul>
     </section>
     <section id="multiple">
       <title>Multiple Renderers</title>
-- 
2.39.5