fix invalid bookmarks

[SVN r16823]

libs/utility

@@ -1 +1 @@
-Subproject commit 119c64be0be476f416ef8a8585e1948a2d65b26d
+Subproject commit 683701cd07a222d72d95a94209b49c04f6360a5f

more/lib_guide.htm

@@ -27,19 +27,19 @@
 &nbsp;&nbsp;&nbsp; <a href="#Portability">Portability requirements</a><br>
 &nbsp;&nbsp;&nbsp; <a href="#Ownership">Ownership</a><br>
 <a href="#Guidelines">Guidelines</a><br>
-&nbsp;&nbsp;&nbsp; <a href="#Design and Programming">Design and programming</a><br>
-&nbsp;&nbsp;&nbsp; <a href="#Directory structure">Directory structure and 
+&nbsp;&nbsp;&nbsp; <a href="#Design_and_Programming">Design and programming</a><br>
+&nbsp;&nbsp;&nbsp; <a href="#Directory_structure">Directory structure and 
 filenames</a><br>
-&nbsp;&nbsp;&nbsp; <a href="#Naming consistency">Naming consistency</a><br>
+&nbsp;&nbsp;&nbsp; <a href="#Naming­_consistency">Naming consistency</a><br>
 &nbsp;&nbsp;&nbsp; <a href="#Documentation">Documentation</a><br>
 <a href="#Rationale">Rationale</a><br>
 &nbsp;&nbsp;&nbsp; <a href="#Exception-specification">Exception-specification 
 rationale</a><br>
 &nbsp;&nbsp;&nbsp; <a href="#Naming">Naming conventions rationale</a><br>
-&nbsp;&nbsp;&nbsp; <a href="#code fonts">Source code fonts rationale</a><br>
+&nbsp;&nbsp;&nbsp; <a href="#code_fonts">Source code fonts rationale</a><br>
 &nbsp;&nbsp;&nbsp; <a href="#Tabs">Tabs rationale</a><br>
 &nbsp;&nbsp;&nbsp; <a href="#JavaScript">ECMAScript/JavaScript rationale</a><br>
-&nbsp;&nbsp;&nbsp; <a href="#Rationale rationale">Rationale rationale</a><br>
+&nbsp;&nbsp;&nbsp; <a href="#Rationale_rationale">Rationale rationale</a><br>
 &nbsp;&nbsp;&nbsp; <a href="#Acknowledgements">Acknowledgements rationale</a></p>
 <h2 align="left"><a name="Introduction">Introduction</a></h2>
 <p align="left">This page describes requirements and guidelines for the content
@@ -65,8 +65,8 @@ rejected, it must meets these requirements:</p>
   <li>The library must come reasonably close to meeting the <a href="#Guidelines">Guidelines</a>
     below.
     <ul>
-    <li><a href="#Design and Programming">Design and Programming</a></li>
-    <li><a href="#Directory structure">Directory Structure</a></li>
+    <li><a href="#Design_and_Programming">Design and Programming</a></li>
+    <li><a href="#Directory_structure">Directory Structure</a></li>
     <li><a href="#Documentation">Documentation</a></li>
     </ul>
   </li>
@@ -142,7 +142,7 @@ Boost won't accept libraries without clear copyright information.</p>
 <p align="left">Please use these guidelines as a checklist for preparing the
 content a library submission.&nbsp; Not every guideline applies to every
 library, but a reasonable effort to comply is expected.</p>
-<h3><a name="Design and Programming">Design and Programming</a></h3>
+<h3><a name="Design_and_Programming">Design and Programming</a></h3>
 <ul>
   <li>Aim first for clarity and correctness; optimization should be only a
     secondary concern in most Boost libraries.</li>
@@ -154,7 +154,7 @@ library, but a reasonable effort to comply is expected.</p>
 </ul>
 <ul>
   <li>Headers should be good neighbors. See the <a href="header.htm">header
-    policy</a>. See <a href="#Naming consistency">Naming consistency</a>.</li>
+    policy</a>. See <a href="#Naming­_consistency">Naming consistency</a>.</li>
 </ul>
 <ul>
   <li>Follow quality programming practices. See, for example, &quot;Effective
@@ -203,7 +203,7 @@ library, but a reasonable effort to comply is expected.</p>
     line lengths in their own code, boost's widely distributed source code
     should follow more conservative guidelines:
     <ul>
-      <li>Use fixed-width fonts.&nbsp; See <a href="#code fonts">fonts rationale</a>.</li>
+      <li>Use fixed-width fonts.&nbsp; See <a href="#code_fonts">fonts rationale</a>.</li>
       <li>Use spaces rather than tabs. See <a href="#Tabs">tabs rationale</a>.</li>
       <li>Limit line lengths to 80 characters.</li>
     </ul>
@@ -225,14 +225,14 @@ library, but a reasonable effort to comply is expected.</p>
     </ul>
   </li>
 </ul>
-<h3><a name="Directory structure">Directory Structure</a> and Filenames</h3>
+<h3><a name="Directory_structure">Directory Structure</a> and Filenames</h3>
 <ul>
   <li>File and directory names must contain only lowercase ASCII letters ,
     numbers, underscores, and a period.&nbsp; Leading character must be
     alphabetic. Maximum length 31. Only a single period is permitted.&nbsp;
     These requirements ensure file and directory names are relatively portable.</li>
   <li>All libraries have at their highest level a primary directory named for
-    the particular library. See <a href="#Naming consistency">Naming consistency</a>. The primary directory may have sub-directories.</li>
+    the particular library. See <a href="#Naming­_consistency">Naming consistency</a>. The primary directory may have sub-directories.</li>
   <li>For very simple libraries implemented entirely within the library header,
     all files go in the primary directory (except headers, which go in the boost
     header directory).</li>
@@ -292,7 +292,7 @@ Automatic redirection failed, please go to
 &lt;/body&gt;
 &lt;/html&gt;</pre>
 </blockquote>
-<h3><a name="Naming consistency">Naming consistency</a></h3>
+<h3><a name="Naming­_consistency">Naming consistency</a></h3>
 <p>As library developers and users have gained experience with Boost, the 
 following consistent naming approach has come to be viewed as very helpful, 
 particularly for larger libraries which need their own header subdirectories and 
@@ -390,7 +390,7 @@ early boost postings. A short summary:</p>
   </li>
 </ul>
 <hr>
-<h3>Source <a name="code fonts">code fonts</a> rationale</h3>
+<h3>Source <a name="code_fonts">code fonts</a> rationale</h3>
 <p>Dave Abrahams comments: An important purpose (I daresay the primary purpose)
 of source code is communication: the documentation of intent. This is a doubly
 important goal for boost, I think. Using a fixed-width font allows us to
@@ -425,7 +425,7 @@ ECMAScript/JavaScript. Reasons given for banning included:</p>
   difficult.</li>
 </ul>
 <hr>
-<h3><a name="Rationale rationale">Rationale rationale</a></h3>
+<h3><a name="Rationale_rationale">Rationale rationale</a></h3>
 <p>Rationale is defined as &quot;The fundamental reasons for something;
 basis&quot; by the American Heritage Dictionary.</p>
 <p>Beman Dawes comments:&nbsp; Failure to supply contemporaneous rationale for
@@ -444,7 +444,7 @@ suggestion.&nbsp; Major contributions are usually acknowledged in the
 documentation, while minor fixes are often mentioned in comments within the code
 itself.</p>
 <hr>
-<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->22 December, 2002<!--webbot bot="Timestamp" endspan i-checksum="38508" --></p>
+<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->09 January, 2003<!--webbot bot="Timestamp" endspan i-checksum="38582" --></p>
 
 </body>
 

more/submission_process.htm

@@ -37,7 +37,7 @@ page for issues of content.</p>
   <li><a href="#Lifecycle">Lifecycle</a>.</li>
 </ul>
 <h2><a name="Learn">Learn</a> about Boost</h2>
-<p>Subscribe to the <a href="../index.htm#Mailing List">mailing list</a> for a
+<p>Subscribe to the <a href="mailing_lists.htm#main">main developers mailing list</a> for a
 while, or look through the <a href="mailing_lists.htm#archive">archives</a>.&nbsp;
 Click around the <a href="../index.htm">web site</a>.&nbsp; Understand the <a href="lib_guide.htm">Requirements</a>.&nbsp;
 Read the rest of this page to learn about the process.&nbsp; Otherwise, you will
@@ -79,7 +79,8 @@ at the <a href="http://www.info-zip.org/pub/infozip/">Info-ZIP</a> web site, whi
 includes a FAQ and much other useful information about the .zip format. Many
 commercial compressor-archiver utilities also support this format.</p>
 <p>The submission file should contain material as if on the
-boost.org web site.&nbsp; The closer the submission file mirrors the final <a href="lib_guide.htm#Directory structure">directory
+boost.org web site.&nbsp; The closer the submission file mirrors the final
+<a href="lib_guide.htm#Directory_structure">directory
 structure</a> and format of the web site, the better.
 <p>Like a preliminary submission, post the final submission .zip file in the <a href="http://www.yahoogroups.com/files/boost/">files section</a> of
 the Boost YahooGroups web site
@@ -119,7 +120,7 @@ you no longer can or wish to maintain your library, please post a message on the
 Boost developers mailing list and help someone else take over as the library 
 maintainer.</p>
 <hr>
-<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->13 May, 2002<!--webbot bot="Timestamp" endspan i-checksum="13969" --></p>
+<p>Revised <!--webbot bot="Timestamp" s-type="EDITED" s-format="%d %B, %Y" startspan -->09 January, 2003<!--webbot bot="Timestamp" endspan i-checksum="38582" --></p>
 
 </body>
 

more/test_policy.htm

@@ -2,7 +2,7 @@
 
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
-<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
+<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
 <meta name="ProgId" content="FrontPage.Editor.Document">
 <title>Boost Test Policies and Protocols</title>
 </head>
@@ -29,7 +29,8 @@ of the key answers to <a href="http://oldwww.comlab.ox.ac.uk/oucl/people/tony.ho
 Hoare's</a> question <a href="http://oldwww.comlab.ox.ac.uk/oucl/users/tony.hoare/icse18.html">&quot;How
 did software get so reliable without proof.&quot;</a></p>
 <h2>Regression test</h2>
-<p>Boost uses an automatic <a href="regression.html"> regression test suite</a> which generates HTML <a href="../status/compiler_status.html#Compiler Status Tables">compiler
+<p>Boost uses an automatic <a href="regression.html"> regression test suite</a> which generates HTML
+<a href="../status/compiler_status.html">compiler
 status tables</a>.</p>
 <h2>Test Policy</h2>
 <h3>Required</h3>
@@ -83,11 +84,11 @@ generation of HTML compiler status tables, was developed by Beman Dawes in June,
 <h2>Acknowledgements</h2>
 <p>Written by Beman Dawes. Jens Maurer, Paul Moore, Gary Powell and Jeremy Siek contributed helpful suggestions.</p>
 <hr>
-<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->19 August, 2001<!--webbot bot="Timestamp" endspan i-checksum="34359" -->
+<p>Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->09 January, 2003<!--webbot bot="Timestamp" endspan i-checksum="38582" -->
 </p>
 <p>&nbsp;</p>
 <p>&nbsp;</p>
 
 </body>
 
-</html>
+</html>