Replaced "CVS" in the top-lvel files by "Subversion".

git-svn-id: https://svn.apache.org/repos/asf/jakarta/poi/trunk@376062 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/src/documentation/content/xdocs/book.xml b/src/documentation/content/xdocs/book.xml
index 13538d3e9cc240f6534973a119f31eb6c4dab195..7da92a66512bcf79379e1b71be08125c1f92c794 100644 (file)
--- a/src/documentation/content/xdocs/book.xml
+++ b/src/documentation/content/xdocs/book.xml
@@ -58,13 +58,10 @@
     </menu>
 
     <menu label="Code">
-        <!--    <menu-item label="Source Code" href="http://jakarta.apache.org/poi/javadocs/javasrc/"/>       -->
-        <menu-item label="CVS" href="http://jakarta.apache.org/site/cvsindex.html"/>
-        <!-- <menu-item label="CVS Changelog" href="changelog.html"/> -->
+        <menu-item label="Subversion (current source code)" href="http://jakarta.apache.org/site/cvsindex.html"/>
         <menu-item label="Top Voted Bugs" href="http://issues.apache.org/bugzilla/buglist.cgi?votes=1&amp;product=POI&amp;order=bugs.votes"/>
         <menu-item label="Bug Database" href="http://issues.apache.org/bugzilla/buglist.cgi?product=POI"/>
         <menu-item label="Patches" href="http://issues.apache.org/bugzilla/buglist.cgi?product=POI&amp;short_desc=%5BPATCH%5D&amp;short_desc_type=allwordssubstr"/>
-
         <menu-item label="Junit Test Results" href="ext:junit"/>
         <menu-item label="Dependency Metrics" href="ext:jdepend"/>
         <!--    <menu-item label="Checkstyle Metrics" href="http://jakarta.apache.org/poi/metrics/checkstyle/"/> -->

diff --git a/src/documentation/content/xdocs/casestudies.xml b/src/documentation/content/xdocs/casestudies.xml
index 6f578cf0cdb9f15477c6d8950ffb7959d220c4b1..ae1b52545b1e6f82807cff544fcd7842b1792d09 100644 (file)
--- a/src/documentation/content/xdocs/casestudies.xml
+++ b/src/documentation/content/xdocs/casestudies.xml
@@ -138,7 +138,7 @@ format,
                     Managament and Maintenance System for the Telecommunications industry
                     based
                     on Turbine and Velocity. Originally the invoicing was done with a simple
-                    CVS
+                    CSV
                     sheet which was then marked up by accounts and customized for each client.
                     As growth has been consistent with the application, the requirement for
                     invoices that need not be touched by hand increased. POI provided the

diff --git a/src/documentation/content/xdocs/hpsf/how-to.xml b/src/documentation/content/xdocs/hpsf/how-to.xml
index 1098a6710f775a8cd5055783f279758b89858b29..b993685140741567e79f139439c1a4c9c2699fe6 100644 (file)
--- a/src/documentation/content/xdocs/hpsf/how-to.xml
+++ b/src/documentation/content/xdocs/hpsf/how-to.xml
@@ -48,7 +48,7 @@
      details!  <strong>Please note:</strong> HPSF's writing functionality is
      <strong>not</strong> present in POI releases up to and including 2.5. In
      order to write properties you have to download a later POI release (when
-     available) or retrieve the POI development version from the CVS
+     available) or retrieve the POI development version from the Subversion
      repository.
     </li>
    </ol>

diff --git a/src/documentation/content/xdocs/index.xml b/src/documentation/content/xdocs/index.xml
index cd0b32928e1634273347a0cb906d49f34c2ef63f..642689970e5ebae6efe79e2d5b5d69e919e11bdc 100644 (file)
--- a/src/documentation/content/xdocs/index.xml
+++ b/src/documentation/content/xdocs/index.xml
@@ -92,8 +92,8 @@
        <p>HPSF supports reading and writing of properties. However, with the
          current POI release only reading is possible. In order to write
          properties, you'll have to fetch the latest POI version <link
-           href="http://jakarta.apache.org/site/cvsindex.html">from the CVS
-           repository</link>.</p>
+           href="http://jakarta.apache.org/site/cvsindex.html">from the
+           Subversion repository</link>.</p>
 
        <p>Please see <link href="./hpsf/index.html">the HPSF project
            page</link> for more information.</p>
@@ -124,3 +124,21 @@
     </legal>
   </footer>
 </document>
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: xml
+sgml-omittag:nil
+sgml-shorttag:nil
+sgml-namecase-general:nil
+sgml-general-insert-case:lower
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:2
+sgml-indent-data:t
+sgml-parent-document:nil
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+-->

diff --git a/src/documentation/content/xdocs/patches.xml b/src/documentation/content/xdocs/patches.xml
index d81c3380e7d8f2b2ea28122f4d06704c39312af2..0079aa3c8afe0433e78f3030c82db9766b16b663 100644 (file)
--- a/src/documentation/content/xdocs/patches.xml
+++ b/src/documentation/content/xdocs/patches.xml
@@ -35,16 +35,17 @@
                 <link href="contrib.xml">Third-Party
                     Contributions</link>. The preferred submission method for patches is:
             </p>
-            <ul>
-                <li>Post to POI developers list</li>
-                <li>Describe the patch, the reason for it and (if necessary) why this is important.</li>
-                <li>Generate the patch in
-                    <code>diff -u</code> format from CVS
-                </li>
-                <li>Also generate a documentation patch or new file, if this is something that should be documented.
-                </li>
-                <li>Post as an attachment rather than inline (unless it is trivially small).</li>
-            </ul>
+      <ul>
+        <li>Post to POI developers list</li>
+        <li>Describe the patch, the reason for it and (if necessary) why this
+          is important.</li>
+        <li>Generate the patch in the unified diff format. This format is
+          created by the typical Subversion client when you execute the
+          <code>svn diff</code> command or the equivalent of it in a GUI environment.</li>
+        <li>Also generate a documentation patch or new file, if this is
+          something that should be documented.</li>
+        <li>Post as an attachment rather than inline (unless it is trivially small).</li>
+      </ul>
             <p>Following the above guidelines will facilitate your patch being reviewed
                 and applied efficiently.</p>
         </section>

diff --git a/src/documentation/content/xdocs/poi-ruby.xml b/src/documentation/content/xdocs/poi-ruby.xml
index 4b7d00e9ea6abb7a56d569ef4182973db872b70f..11a96b5913e94f9886e6b3016cf593a9e2655884 100644 (file)
--- a/src/documentation/content/xdocs/poi-ruby.xml
+++ b/src/documentation/content/xdocs/poi-ruby.xml
@@ -32,9 +32,9 @@
        <em>libgcj </em>, presumably from the same version of GCC with which you compiled.  
         </p> 
        </section>
-       <section><title>CVS</title>
+       <section><title>Subversion</title>
        <p>
-       The POI-Ruby module sits under the POI <link href="http://jakarta.apache.org/site/cvsindex.html">CVS</link> in the <em>src/contrib/poi-ruby</em> directory. Running <em>make</em>
+       The POI-Ruby module sits under the POI <link href="http://jakarta.apache.org/site/cvsindex.html">Subversion</link> in the <em>src/contrib/poi-ruby</em> directory. Running <em>make</em>
        inside that directory will create a loadable ruby extention <em>poi4r.so</em> in the release subdirectory. Tests 
        are in the <em>tests/</em> subdirectory, and should be run from the <em>poi-ruby</em> directory. Please read the tests to figure out the usage.
        </p>