try to force paragraph at top using sectinfo abstract. Make note about deprecation...

git-svn-id: http://svn.osgeo.org/postgis/trunk@4926 b70326c6-7e19-0410-871a-916f4a2858ee

diff --git a/doc/reference.xml b/doc/reference.xml
index 9c94dbf331f980164783e1289e058133f327209d..72cccd2ea12dd4ed8fcd796a5d5b60cea293aac2 100644 (file)
--- a/doc/reference.xml
+++ b/doc/reference.xml
@@ -12,8 +12,8 @@
        to an SQL-MM-centric convention. As a result, most of the functions that
        you know and love have been renamed using the standard spatial type (ST)
        prefix. Previous functions are still available, though are not listed in
-       this document where updated functions are equivalent. These will be
-       deprecated in a future release.</para>
+       this document where updated functions are equivalent. The non ST_ functions not listed in this documentation are
+       deprecated and will be removed in a future release so STOP USING THEM.</para>
   </note>
 
   &reference_type;

diff --git a/doc/reference_type.xml b/doc/reference_type.xml
index 57be6f17172f4e9364283c858de0bc60c8809bc0..387318cbbac42f0fafe8fc5ab28a2e25342bd189 100644 (file)
--- a/doc/reference_type.xml
+++ b/doc/reference_type.xml
@@ -1,6 +1,8 @@
 <?xml version="1.0" encoding="UTF-8"?>
   <sect1 id="PostGIS_Types">
     <title>PostgreSQL PostGIS Types</title>
+    <sect1info>
+    <abstract>
     <para>This section lists the PostgreSQL data types installed by PostGIS.  Note we describe the casting behavior of these which is very 
        important especially when designing your own functions.  
     </para>
@@ -13,8 +15,9 @@
        but no geometry.  What happens is that both functions are equally good to use with geometry since geometry has an autocast for both 
        -- so you end up with an ambiguous function error. To force PostgreSQL to choose, you do a CAST(mygeom As box3d)  or mygeom::box3d.</para>
        
-    <para><note>At least asof PostgreSQL 8.3 - Everything can be CAST to text (presumably because of the magical unknown type), so no defined CASTS for that need to be present for you to CAST an object to text.</note></para>
-    
+    <para><note>At least as of PostgreSQL 8.3 - Everything can be CAST to text (presumably because of the magical unknown type), so no defined CASTS for that need to be present for you to CAST an object to text.</note></para>
+    </abstract>
+    </sect1info>
        <refentry id="box2d">
       <refnamediv>
         <refname>box2d</refname>