Rebuild optional docs.

[SVN r57812]

doc/html/boost_optional/acknowledgments.html

@@ -3,7 +3,7 @@
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>Acknowledgments</title>
 <link rel="stylesheet" href="../boostbook.css" type="text/css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.74.0">
+<meta name="generator" content="DocBook XSL Stylesheets V1.75.2">
 <link rel="home" href="../index.html" title="Chapter<65>1.<2E>Boost.Optional">
 <link rel="up" href="../index.html" title="Chapter<65>1.<2E>Boost.Optional">
 <link rel="prev" href="dependencies_and_portability.html" title="Dependencies and Portability">
@@ -21,89 +21,89 @@
 <div class="spirit-nav">
 <a accesskey="p" href="dependencies_and_portability.html"><img src="../../../../../doc/html/images/prev.png" alt="Prev"></a><a accesskey="u" href="../index.html"><img src="../../../../../doc/html/images/up.png" alt="Up"></a><a accesskey="h" href="../index.html"><img src="../../../../../doc/html/images/home.png" alt="Home"></a>
 </div>
-<div class="section" lang="en">
+<div class="section" title="Acknowledgments">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="boost_optional.acknowledgments"></a><a class="link" href="acknowledgments.html" title="Acknowledgments">Acknowledgments</a>
 </h2></div></div></div>
 <a name="boost_optional.acknowledgments.pre_formal_review"></a><h4>
-<a name="id704954"></a>
+<a name="id583998"></a>
       <a class="link" href="acknowledgments.html#boost_optional.acknowledgments.pre_formal_review">Pre-formal
       review</a>
     </h4>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
         Peter Dimov suggested the name 'optional', and was the first to point out
         the need for aligned storage.
       </li>
-<li>
+<li class="listitem">
         Douglas Gregor developed 'type_with_alignment', and later Eric Friedman coded
         'aligned_storage', which are the core of the optional class implementation.
       </li>
-<li>
+<li class="listitem">
         Andrei Alexandrescu and Brian Parker also worked with aligned storage techniques
         and their work influenced the current implementation.
       </li>
-<li>
+<li class="listitem">
         Gennadiy Rozental made extensive and important comments which shaped the
         design.
       </li>
-<li>
+<li class="listitem">
         Vesa Karvonen and Douglas Gregor made quite useful comparisons between optional,
         variant and any; and made other relevant comments.
       </li>
-<li>
+<li class="listitem">
         Douglas Gregor and Peter Dimov commented on comparisons and evaluation in
         boolean contexts.
       </li>
-<li>
+<li class="listitem">
         Eric Friedman helped understand the issues involved with aligned storage,
         move/copy operations and exception safety.
       </li>
-<li>
+<li class="listitem">
         Many others have participated with useful comments: Aleksey Gurotov, Kevlin
         Henney, David Abrahams, and others I can't recall.
       </li>
 </ul></div>
 <a name="boost_optional.acknowledgments.post_formal_review"></a><h4>
-<a name="id705000"></a>
+<a name="id584068"></a>
       <a class="link" href="acknowledgments.html#boost_optional.acknowledgments.post_formal_review">Post-formal
       review</a>
     </h4>
-<div class="itemizedlist"><ul type="disc">
-<li>
+<div class="itemizedlist"><ul class="itemizedlist" type="disc">
+<li class="listitem">
         William Kempf carefully considered the originally proposed interface and
         suggested the new interface which is currently used. He also started and
         fueled the discussion about the analogy optional&lt;&gt;/smart pointer and
         about relational operators.
       </li>
-<li>
+<li class="listitem">
         Peter Dimov, Joel de Guzman, David Abrahams, Tanton Gibbs and Ian Hanson
         focused on the relational semantics of optional (originally undefined); concluding
         with the fact that the pointer-like interface doesn't make it a pointer so
         it shall have deep relational operators.
       </li>
-<li>
+<li class="listitem">
         Augustus Saunders also explored the different relational semantics between
         optional&lt;&gt; and a pointer and developed the OptionalPointee concept
         as an aid against potential conflicts on generic code.
       </li>
-<li>
+<li class="listitem">
         Joel de Guzman noticed that optional&lt;&gt; can be seen as an API on top
         of variant&lt;T,nil_t&gt;.
       </li>
-<li>
+<li class="listitem">
         Dave Gomboc explained the meaning and usage of the Haskell analog to optional&lt;&gt;:
         the Maybe type constructor (analogy originally pointed out by David Sankel).
       </li>
-<li>
+<li class="listitem">
         Other comments were posted by Vincent Finn, Anthony Williams, Ed Brey, Rob
         Stewart, and others.
       </li>
-<li>
+<li class="listitem">
         Joel de Guzman made the case for the support of references and helped with
         the proper semantics.
       </li>
-<li>
+<li class="listitem">
         Mat Marcus shown the virtues of a value-oriented interface, influencing the
         current design, and contributed the idea of "none".
       </li>