vmote       2003/04/06 20:37:19

  Modified:    src/documentation/content/xdocs download.xml
  Log:
  Rearrange for clarity.
  
  Revision  Changes    Path
  1.6       +31 -31    xml-fop/src/documentation/content/xdocs/download.xml
  
  Index: download.xml
  ===================================================================
  RCS file: /home/cvs/xml-fop/src/documentation/content/xdocs/download.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- download.xml      1 Apr 2003 20:11:26 -0000       1.5
  +++ download.xml      7 Apr 2003 03:37:18 -0000       1.6
  @@ -3,38 +3,38 @@
       
"http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-forrest/src/resources/schema/dtd/document-v11.dtd";>
   
   <document>
  -    <header>
  -        <title>Download</title>
  -    </header>
  -
  -    <body>
  -<section>
  -  <title>Downloading FOP</title>
  -    <p>You can download the latest release version from the <link
  -       href="http://xml.apache.org/dist/fop/";>distribution directory</link>. </p>
  -    <p>Each version exists as binary (bin) and source (src) distribution. The 
binary distribution contains the
  -      compiled package along with the documentation (including some example XSL-FO 
files). The source distribution
  -      additionally contains the whole source code.</p>
  -    <p>If you want to work with the latest and nicest code, you can download it 
from CVS. See the section
  -       on AnonCVS in the <link href="http://xml.apache.org/cvs.html";>xml.apache.org 
documentation</link> for details.</p>
  -    <p>Sometimes people have difficulties to access the CVS server; in this case 
you can download
  -       a snapshot from the CVS files <link 
href="http://xml.apache.org/from-cvs/xml-fop/";>here</link>.
  -       Please be aware that the snapshots currently mirrors the development code 
for the upcoming FOP 1.0 and not the
  -       code from the current releases. You need to download from CVS in this case. 
(See the note below)</p>
  -    <p>If you don't download a binary distribution you have to build FOP yourself - 
  -      see <link href="compiling.html">Compiling FOP</link> for details.
  -    </p>
  -    <note>
  -      Important: Currently, releases of FOP are coming out of the
  -      "fop-0_20_2-maintain" branch. The "MAIN" branch is currently
  -      under development. See <link href="dev/index.html">Development Docs</link>
  -      for more information.
  -    </note>
  -    <p>To run FOP from the command line, see <link href="running.html">Running 
FOP</link>.</p>
  -    <p>If you are interested in embedding FOP in a Java application of your own, see
  -       <link href="embedding.html">Embedding FOP</link>.
  -    </p>
  +  <header>
  +    <title>Downloading FOP</title>
  +  </header>
  +  <body>
  +  <section>
  +    <title>Binary or Source?</title>
  +    <p>Most FOP users will want to download the latest binary distribution, which 
is ready to run "out of the box."
  +However, a source distribution will be preferable if you fall into one of the 
following categories:</p>
  +    <ul>
  +      <li>You wish to modify FOP.</li>
  +      <li>You wish to use a version more recent than the latest release. For 
example, if you have read on the user mailing list that a bug has been fixed or a 
feature added that you are eager to try, you might download a source distribution from 
the CVS repository so that you don't have to wait for the next release.</li>
  +    </ul>
  +  </section>
  +  <section>
  +    <title>Binary Download</title>
  +    <p>Binary distributions include "-bin" in their names, and can be downloaded 
from the <link href="http://xml.apache.org/dist/fop/";>FOP Distribution</link> 
directory.
  +</p>
  +  </section>
  +  <section>
  +    <title>Source Download</title>
  +    <p>You must first determine which of the two main development branches you wish 
to download, "maintenance" or "redesign".
  +See <link href="dev/index.html">Development Introduction</link> for more details on 
the choices, and for the CVS tags to use when downloading the "maintenance" branch.</p>
  +    <p>There are three ways to obtain a source distribution. Please note that they 
are listed from least current to most current:</p>
  +    <ul>
  +      <li>Download a released version from the <link 
href="http://xml.apache.org/dist/fop/";>FOP Distribution</link> directory. Source 
distributions include "-src" in their names. Please note that official releases 
currently are <em>only</em> made from the "maintenance" branch.</li>
  +      <li>Download a CVS snapshot from the cvs files <link 
href="http://xml.apache.org/from-cvs/xml-fop/";>here</link>. These snapshots are built 
approximately every six hours, and have the GMT of their creation time embedded in 
their names. Please note that CVS snapshots are made only for the "redesign" 
branch.</li>
  +      <li>Download directly from the CVS repository.
  +Anyone can do this using the <link 
href="http://xml.apache.org/cvs.html#AnonCVS";>Anonymous CVS Server</link>. By default, 
the CVS code is up-to-the-minute, the same code that the developers are modifying. See 
the <link href="dev/tools.html#cvs">CVS section of Developer Tools</link> for more 
information on using CVS.</li>
  +    </ul>
  +    <p>With any source distribution, you will need to <link 
href="compiling.html">Build FOP</link> from the source files.</p>
   </section>
       </body>
   </document>
   
  +<!-- Last Line of $RCSFile$ -->
  \ No newline at end of file
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to