Pass clean html parameter, fix a couple old references that should be <warning>

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

diff --git a/doc/Makefile.in b/doc/Makefile.in
index 31fd778efc1bd342c2498dd2ba32244fa0033004..ddb882cdf299b3d495851f18566768688cfd244f 100644 (file)
--- a/doc/Makefile.in
+++ b/doc/Makefile.in
@@ -58,6 +58,7 @@ XSLTPROC_COMMONOPTS= \
        --param funcsynopsis.style kr \
        --param admon.graphics 1 \
        --param admon.textlabel 0 \
+       --param make.clean.html 1 \
        --param simplesect.in.toc 0 \
        --param use.id.as.filename 1 \
        --param chunk.quietly 1 \

diff --git a/doc/reference_output.xml b/doc/reference_output.xml
index 09120e22356bf9a6d4bf82adfc186ce0a68f8134..948cf23e39a6c7019300e5dc8bc43ff70a865e3f 100644 (file)
--- a/doc/reference_output.xml
+++ b/doc/reference_output.xml
@@ -272,9 +272,9 @@
                        <note>
                          <para>The WKT spec does not include the SRID.  To get the OGC WKT format use ST_AsText.</para>
                        </note>
-                       <para><inlinegraphic fileref="images/warning.png" />
-                               WKT format does not maintain precision so to prevent floating truncation, use ST_AsBinary or ST_AsEWKB format for transport.
-                       </para>
+                       <warning>
+        <para>WKT format does not maintain precision so to prevent floating truncation, use ST_AsBinary or ST_AsEWKB format for transport.</para>
+                       </warning>
                        <note>
                          <para>ST_AsEWKT is the reverse of <xref linkend="ST_GeomFromEWKT" />.  Use <xref linkend="ST_GeomFromEWKT" /> to convert to a postgis geometry from ST_AsEWKT representation.</para>
                        </note>
@@ -954,9 +954,9 @@ SELECT (ST_AsLatLonText('POINT (-302.2342342 -792.32498)'));
                          <para>The WKT spec does not include the SRID.  To get the SRID as part of the data, use the non-standard
                                PostGIS <xref linkend="ST_AsEWKT" /></para>
                        </note>
-                       <para><inlinegraphic fileref="images/warning.png" />
-                               WKT format does not maintain precision so to prevent floating truncation, use ST_AsBinary or ST_AsEWKB format for transport.
-                       </para>
+      <warning>
+                       <para>WKT format does not maintain precision so to prevent floating truncation, use ST_AsBinary or ST_AsEWKB format for transport.</para>
+      </warning>
                        <note>
                          <para>ST_AsText is the reverse of <xref linkend="ST_GeomFromText" />.  Use <xref linkend="ST_GeomFromText" /> to convert to a postgis geometry from ST_AsText representation.</para>
                        </note>

diff --git a/doc/reference_processing.xml b/doc/reference_processing.xml
index e48e7d8e9cb554fa930ccb21467126dc2f483b86..795c6928f35bba364d9df84cc2ae28bd5b8a50ac 100644 (file)
--- a/doc/reference_processing.xml
+++ b/doc/reference_processing.xml
@@ -68,8 +68,8 @@ from the input geometry.
                        <note><para>Negative radii: For polygons, a negative radius can be used, which will shrink the polygon rather than expanding it.</para></note>
                                <note><para>Geography: For geography this is really a thin wrapper around the geometry implementation. It first determines the best SRID that
                                        fits the bounding box of the geography object (favoring UTM, Lambert Azimuthal Equal Area (LAEA) north/south pole, and falling back on mercator in worst case scenario) and then buffers in that planar spatial ref and retransforms back to WGS84 geography.</para></note>
-                       <para><inlinegraphic fileref="images/warning.png" />
-                       For geography this may not behave as expected if object is sufficiently large that it falls between two UTM zones or crosses the dateline</para>
+                       <warning><para>
+                       For geography this may not behave as expected if object is sufficiently large that it falls between two UTM zones or crosses the dateline</para></warning>
                                <para>Enhanced: 2.5.0 - ST_Buffer geometry support was enhanced to allow for side buffering specification <code>side=both|left|right</code>.</para>
                                <para>Availability: 1.5 - ST_Buffer was enhanced to support different endcaps and join types. These are useful for example to convert road linestrings
                                        into polygon roads with flat or square edges instead of rounded edges. Thin wrapper for geography was added. - requires GEOS &gt;= 3.2 to take advantage of advanced geometry functionality.
@@ -2880,9 +2880,9 @@ MULTILINESTRING((76 175,90 161),(90 161,101 150),(126 125,126 156.25)))
                        plotted in a 180 centric map</para>
                <note><para>This is only useful for data in long lat e.g. 4326 (WGS 84 long lat)</para></note>
 
-               <para><inlinegraphic fileref="images/warning.png" />
-                       Pre-1.3.4 bug prevented this from working for MULTIPOINT. 1.3.4+ works with MULTIPOINT as well.
-               </para>
+               <warning>
+                       <para>Pre-1.3.4 bug prevented this from working for MULTIPOINT. 1.3.4+ works with MULTIPOINT as well.</para>
+    </warning>
 
                <para>&Z_support;</para>
                <para>Enhanced: 2.0.0 support for Polyhedral surfaces and TIN was introduced.</para>