Rearrange to reflect download availability from either SourceForge FTP or main boost.org web site.

[SVN r9978]

more/download.html

@@ -19,19 +19,39 @@
 
 <h1>Boost Download and Installation</h1>
 
-The boost libraries are intended for easy download and installation.
+The boost libraries are intended for easy download and <a href="#Installation">installation</a>.
 However, unlike other packages, there is no global setup and
 configuration tool.
 
 <h2>Download</h2>
-The boost libraries are available in various formats.  Most of the
-files are available through links from the individual library's
-documentation. Since many boost headers include other boost headers,
-installing one at a time is painful.&nbsp; Downloading all of Boost as a single archive
-file (.zip or .tar.gz)&nbsp; is a lot easier.&nbsp; CVS access is also
-available.
+The boost libraries are available in various formats:
+<ul>
+  <li><a href="ftp://boost.sourceforge.net/pub/boost/release/">FTP download</a> all of Boost as a single archive
+file (<a href="#.zip">.zip</a> or <a href="#.tar.gz">.tar.gz</a>) file from our
+    SourceForge FTP site. Older versions also available. (FTP download is
+    suggested first since it doesn't count against our web site host's monthly
+    fee.&nbsp; But some users behind firewalls can't use FTP, and the
+    SourceForge FTP site is sometimes down or very busy.)</li>
+</ul>
+<ul>
+  <li><a href="../boost_all.zip">ZIP download</a> all of Boost as a single archive
+file from our web site.</li>
+</ul>
+<ul>
+  <li><a href="../boost_all.tar.gz">TAR.GZ download</a> all of Boost as a single archive
+file from our web site.</li>
+</ul>
+<ul>
+  <li><a href="#CVS">Command line</a> or <a href="#Browser">browser</a> access
+    to Boost's CVS repository.</li>
+</ul>
+<ul>
+  <li>Download individual files from links in the documentation on the web
+    site.&nbsp; Because of the number of files involved, and <a href="../libs/hdr_depend.html">header
+    dependencies</a>, this option usually isn't very useful.</li>
+</ul>
 
-<h3>.zip file</h3>
+<h3><a name=".zip">.zip</a> file</h3>
 
 The .zip format is widely supported by both free decoders and
 commercial compress/archive utilities.  If you don't already have a
@@ -43,12 +63,8 @@ Text file line endings in the .zip file are as supplied by each library
 developer.&nbsp; This works fine for Windows, but not for Unix/Linux.&nbsp; The
 .tar.gz file supplies Unix/Linux friendly line endings.
 
-<ul>
-<li><a href="ftp://boost.sourceforge.net/pub/boost/release/">Latest version</a>
-</ul>
-
 
-<h3>.tar.gz file</h3>
+<h3><a name=".tar.gz">.tar.gz</a> file</h3>
 
 The .tar.gz format is widely supported on Unix/Linux platforms.  Some
 Windows compress/archive utilities can read the format as well.&nbsp; Because
@@ -57,11 +73,7 @@ each file individually, the .tar.gz file is smaller that the .zip file.
 <p>Text file line endings in the .tar.gz file have been converted to newlines
 for ease of use on Unix/Linux platforms.</p>
 
-<ul>
-<li><a href="ftp://boost.sourceforge.net/pub/boost/release/">Latest version</a>
-</ul>
-
-<h3>CVS archive</h3>
+<h3><a name="CVS">CVS</a> command line access</h3>
 
 For those who have CVS installed, the libraries are also available
 from the public CVS repository.  The general procedure for
@@ -87,14 +99,14 @@ CVS write access, please contact one of the
 <a href="mailto:boost-owner@yahoogroups.com">moderators</a>.
  
 
-<h3>WWW access to the CVS archive</h3>
+<h3>CVS <a name="Browser">Browser</a> access via WebCVS</h3>
 
 For access to individual files in the CVS archive, you can also use its
 <a href="http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/boost/?cvsroot=boost">WWW interface</a>.
 
 
 
-<h2>Installation</h2>
+<h2><a name="Installation">Installation</a></h2>
 
 Many boost libraries are implemented entirely within their header
 files.  The only preparation for their use is to add the path for the
@@ -114,12 +126,12 @@ A few boost libraries are implemented by separate source files, and
 thus require compilation on your system to link properly.  Boost does
 not currently have an overall "build" or "make" mechanism in place.
 Some of the individual libraries do include make and/or project files
-for various compilers, though.
+for various compilers.
 <p>
 
 <hr>
 
-Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->14 March, 2001<!--webbot bot="Timestamp" endspan i-checksum="28773" -->
+Revised <!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->24 April, 2001<!--webbot bot="Timestamp" endspan i-checksum="29814" -->
 <p>Written by&nbsp; <a href="../people/jens_maurer.htm">Jens Maurer</a>
 2001-02-11</p>