This commit was manufactured by cvs2svn to create tag

'Version_1_32_0'.

[SVN r26264]

doc/conversion_traits.html

@@ -94,7 +94,7 @@ enum sign_mixture_enum
 } } // namespace boost::numeric
 </PRE>
 <p>Classifying <code>S</code> and <code>T</code> as either <code>integral</code>
-or <code>float</code>, this <a href="../../../mpl/doc/ref/Integral_Constant.html">MPL's Integral Constant</a>
+or <code>float</code>, this <a href="../../../mpl/doc/refmanual/integral-constant.html">MPL's Integral Constant</a>
 indicates the combination of these attributes. <br>
 Its <code>::value</code> is of enumeration type <A HREF="#ncm"><CODE>boost::numeric::int_float_mixture_enum</CODE></A>
 </p>
@@ -111,7 +111,7 @@ Its <code>::value</code> is of enumeration type <A HREF="#ncm"><CODE>boost::nume
 } } // namespace boost::numeric
 </PRE>
 <p>Classifying <code>S</code> and <code>T</code> as either <code>signed</code>
-or <code>unsigned</code>, this <a href="../../../mpl/doc/ref/Integral_Constant.html">MPL's Integral Constant</a>
+or <code>unsigned</code>, this <a href="../../../mpl/doc/refmanual/integral-constant.html">MPL's Integral Constant</a>
 indicates the combination of these attributes. <br>
 Its <code>::value</code> is of enumeration type <A HREF="#ncm"><CODE>boost::numeric::sign_mixture_enum</CODE></A>
 </p>
@@ -128,7 +128,7 @@ Its <code>::value</code> is of enumeration type <A HREF="#ncm"><CODE>boost::nume
 } } // namespace boost::numeric
 </PRE>
 <p>Classifying <code>S</code> and <code>T</code> as either <code>user-defined</code>
-or <code>builtin</code>, this <a href="../../../mpl/doc/ref/Integral_Constant.html">MPL's Integral Constant</a>
+or <code>builtin</code>, this <a href="../../../mpl/doc/refmanual/integral-constant.html">MPL's Integral Constant</a>
 indicates the combination of these attributes. <br>
 Its <code>::value</code> is of enumeration type <A HREF="#ncm"><CODE>boost::numeric::udt_builtin_mixture_enum</CODE></A>
 </p>
@@ -146,7 +146,7 @@ Its <code>::value</code> is of enumeration type <A HREF="#ncm"><CODE>boost::nume
 </PRE>
 <p>Indicates if the range of the target type T is a subset of the range of the source type S.
 That is: if there are some source values which fall out of the Target type's range.<br>
-It is a boolean <a href="../../../mpl/doc/ref/Integral_Constant.html">MPL's Integral Constant</a>..<br>
+It is a boolean <a href="../../../mpl/doc/refmanual/integral-constant.html">MPL's Integral Constant</a>..<br>
 It does not indicate if
 a <i>particular</i> conversion is effectively out of range; it indicates that
 some conversion <i>might be</i> out of range because not all the source values
@@ -188,7 +188,7 @@ are representable as Target type.</p>
   </P>
 
   <P>The traits class provides the following
-     <a href="../../../mpl/doc/ref/Integral_Constant.html">MPL's Integral Constants</a>
+     <a href="../../../mpl/doc/refmanual/integral-constant.html">MPL's Integral Constants</a>
      of enumeration type. They express the <i>combination</i> of certain attributes of the Source and
     Target types (thus they are call <i>mixture</i>):</P>
 		<TABLE BORDER="1">
@@ -216,7 +216,7 @@ are representable as Target type.</p>
 		</TABLE>
 
   <P>The traits class provides the following
-     <a href="../../../mpl/doc/ref/Integral_Constant.html">MPL's Integral Constants</a>
+     <a href="../../../mpl/doc/refmanual/integral-constant.html">MPL's Integral Constants</a>
     of boolean type which indicates indirectly the relation between the Source and Target
     <i>ranges</i>
     (see <A href="definitions.html#range">Definitions</A> for details).</P>

doc/converter.html

@@ -23,7 +23,7 @@ HREF="../../../../boost/numeric/conversion/converter.hpp">boost/numeric/conversi
 <HR>
 <H2>Contents</H2>
 <DT><A HREF="#synposis">Synopsis</A></DT>
-<DT><A HREF="udt_support.html">User Defined Types support</A></DT>
+<DT><A HREF="requirements.html">User Defined Types support</A></DT>
 <DT><A HREF="#rchklogic">Range Checking Logic</A></DT>
 <DT><A HREF="#examples">Examples</A></DT>
 

doc/converter_policies.html

@@ -223,7 +223,7 @@ overflow handler</P>
   for instance, use a fully qualified call.<br>
   This technique allows the default rounder policies to be used directly with
   user defined types. The user only requires that suitable overloads of floor()
-  and ceil() be visible. See also <a HREF="udt_support.html">User Defined Numeric Types support</a><br>
+  and ceil() be visible. See also <a HREF="requirements.html">User Defined Numeric Types support</a><br>
 </P>
 <HR>
 <H2><A NAME="rawc">Policy <CODE>RawConverter</CODE></A></H2>