Add <section> ids.

git-svn-id: https://svn.apache.org/repos/asf/xmlgraphics/fop/trunk@196311 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/src/documentation/content/xdocs/design/properties.xml b/src/documentation/content/xdocs/design/properties.xml
index d0c50a66fcd039a2b34449b7d65aab12017d7ec3..426cbd4dd0dea990c3f2823f6cf52f611d17cb3a 100644 (file)
--- a/src/documentation/content/xdocs/design/properties.xml
+++ b/src/documentation/content/xdocs/design/properties.xml
@@ -19,7 +19,7 @@ basic idea of the PLB is to handle each attribute in the list in turn,
 find an appropriate "Maker" for it, call the Maker to convert the
 attribute value into a Property object of the correct type, and store
 that Property in the PropertyList.</p>
-    <section>
+    <section id="datatypes">
       <title>Property datatypes</title>
       <p>The property datatypes are defined in the
 org.apache.fop.datatypes package, except Number and String which are java
@@ -55,7 +55,7 @@ such as Length or ColorType. A subclass may also choose to return a
 reasonable value for other accessor types. For example, a
 SpaceProperty will return the optimum value if asked for a Length.</p>
     </section>
-    <section>
+    <section id="makers">
       <title>Property Makers</title>
       <p>The Property class contains a nested class called
 <em>Maker</em>. This is the base class for all other property Makers. It
@@ -83,7 +83,7 @@ Maker. The attribute name to Maker mappings are automatically created
 during the code generation phase by processing the XML property
 description files.</p>
     </section>
-    <section>
+    <section id="attribute-list">
       <title>Processing the attribute list</title>
       <p>The PLB first looks to see if the font-size property is specified, since
 it sets up relative units which can be used in other property
@@ -92,7 +92,7 @@ specifies part of a compound property such as space-before.optimum, the
 PLB looks to see if the attribute list also contains the "base" property
 (space-before in this case) and processes that first.</p>
     </section>
-    <section>
+    <section id="maker-design">
       <title>How the Property Maker works</title>
       <p>There is a family of Maker objects for each of the property datatypes,
 such as Length, Number, Enumerated, Space, etc. But since each Property
@@ -126,7 +126,7 @@ These are stored as special kinds of Length objects which are evaluated
 during layout. Expressions involving "em" units which are relative to
 font-size _are_ resolved during the FO tree building however.</p>
     </section>
-    <section>
+    <section id="property-list-struct">
       <title>Structure of the PropertyList</title>
       <p>The PropertyList extends HashMap and its basic function is to associate
 Property value objects with Property names. The Property objects are all
@@ -147,9 +147,9 @@ the PropertyList of the nearest ancestor FO.) If the property isn't
 inherited or no value is found at any level, the initial value is
 returned.</p>
     </section>
-    <section>
+    <section id="property-spec">
       <title>XML property specification format</title>
-      <section>
+      <section id="generic">
         <title>Generic properties</title>
         <p>In the properties xml files, one can define generic property
 definitions which can serve as a basis for individual property
@@ -196,7 +196,7 @@ svgproperties.xml, no specific classes are generated.  Classes are only
 generated for those SVG properties which are not based on generic
 classes defined in svg.</p>
       </section>
-      <section>
+      <section id="element-specific">
         <title>Element-specific properties</title>
         <p>Properties may be defined for all flow objects or only for
 particular flow objects. A PropertyListBuilder object will always look
@@ -213,7 +213,7 @@ properties will hide the earlier ones! Use the <em>ref</em>
 functionality if the same property is to be used in different sets of
 element-specific mappings.</p>
       </section>
-      <section>
+      <section id="reference">
         <title>Reference properties</title>
         <p>A property element may have a type attribute with the value
   <code>ref</code>. The
@@ -229,7 +229,7 @@ element-specific mappings.</p>
   reference the defined FO properties. The generating mapping for the
   SVG properties will use the FO Maker classes.</p>
       </section>
-      <section>
+      <section id="corresponding">
         <title>Corresponding properties</title>
         <p>Some properties have both <em>absolute</em> and
 <em>writing-mode-relative</em> forms. In general, the absolute forms
@@ -253,7 +253,7 @@ attributes. However it does use start-indent and end-indent, rather
 than the "absolute" margin properties.</p>
       </section>
     </section>
-    <section>
+    <section id="mapping">
       <title>Mapping</title>
       <p>The XSL script <code>propmap.xsl</code> is used to generate
 property mappings based on
@@ -270,7 +270,7 @@ class, which returns an instance of its nested Maker class.</p>
       <p>The property generation also handles element-specific property
 mappings as specified in the properties XML files.</p>
     </section>
-    <section>
+    <section id="enumerated">
       <title>Enumerated values</title>
       <p>For any property whose datatype is <code>Enum</code> or which
 contains possible enumerated values, FOP code may need to access
@@ -294,7 +294,7 @@ three nested interfaces, one for each component, and each defines
 these two constants. An example of a reference in code to the constant
 is <code>KeepTogether.WithinPage.AUTO</code>.</p>
     </section>
-    <section>
+    <section id="compound">
       <title>Compound property types</title>
       <p>Some XSL FO properties are specified by compound datatypes. In the FO file,
 these are defined by a group of attributes, each having a name of the