svn: /pear/peardoc/trunk/en/ chapters/constitution.xml chapters/faq/devs.xml chapters/faq/documentation.xml chapters/faq/users.xml chapters/group.xml chapters/installation/cli.xml chapters/installation/svn.xml chapters/intro.xml chapters/rfcs/estrict-compatibility.xml chapters/rfcs/header-comments.xml chapters/rfcs/orphan-packages.xml chapters/rfcs/qa-team.xml chapters/standards.xml chapters/support.xml guide/developers/contributing.xml guide/developers/documentation.xml guide/migrating/customroles.xml guide/newmaint/takingover.xml guide/users/commandline/commands.xml guide/users/installation/cli.xml guide/users/installation/svn.xml livedocs.ent package/html/html-treemenu.xml package/php/php-codesniffer/coding-standard-tutorial.xml package/qa/qa-pear-packagestatus.xml package/qa/qa-peardoc-coverage/intro.xml package/structures/structures-datagrid/structures-datagrid-renderer/checkablehtmltable.xml package/structures/structures-datagrid/structures-datagrid-

Modified: pear/peardoc/trunk/en/chapters/constitution.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/constitution.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/constitution.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -63,7 +63,7 @@
    <listitem>
    <para>
     The PEAR Group only has power over issues that affect all of PEAR such as
-    coding standards, CVS karma, and all major decisions made about PEAR as
+    coding standards, SVN karma, and all major decisions made about PEAR as
     a whole.  For example, licenses allowed and what defines a collective are
     two issues that only the PEAR Group can resolve.
    </para>
@@ -133,7 +133,7 @@
       <listitem>
        <simpara>
         Extra-governmental technical gurus - these people have shell access
-        on the pear.php.net website, CVS karma for everything, and generally
+        on the pear.php.net website, SVN karma for everything, and generally
         can do things that others cannot do.
        </simpara>
       </listitem>
@@ -270,7 +270,7 @@
       </listitem>
       <listitem>
        <simpara>
-        Grant CVS karma requests
+        Grant SVN karma requests
        </simpara>
       </listitem>
       <listitem>

Modified: pear/peardoc/trunk/en/chapters/faq/devs.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/faq/devs.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/faq/devs.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -4,7 +4,7 @@


  <section xml:id="faq.contributor"><info><title>
-    How do I become a PEAR contributor and/or how do I get CVS access to
+    How do I become a PEAR contributor and/or how do I get SVN access to
     PEAR?
    </title><titleabbrev>
     Becoming contributor
@@ -83,18 +83,18 @@


   <simpara>
-    In CVS, PEAR code is organized by package instead of hierarchical
+    In SVN, PEAR code is organized by package instead of hierarchical
     like it would finally be installed.  For example, if you want to
     use the XML_RPC class, you include "XML/RPC.php".  It's easy to
-    think that in CVS, this file should be in pear/XML/RPC.php, but
+    think that in SVN, this file should be in pear/XML/RPC.php, but
     that's not the case.  XML_RPC is an independent package with its
-    own directory in CVS, in this case the RPC.php file is actually
+    own directory in SVN, in this case the RPC.php file is actually
     located at pear/XML_RPC/RPC.php.  The package description file
     (package.xml) is used to say where the files should finally be
     installed.
    </simpara>
   <simpara>
-    The reason CVS is organized this way is that it makes package
+    The reason SVN is organized this way is that it makes package
     administration much easier.
    </simpara>
  </section>
@@ -155,7 +155,7 @@
      <term>snapshot</term>
      <listitem>
       <simpara>
-        a CVS snapshot from a certain date
+        a SVN snapshot from a certain date
        </simpara>
      </listitem>
     </varlistentry>

Modified: pear/peardoc/trunk/en/chapters/faq/documentation.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/faq/documentation.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/faq/documentation.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -68,7 +68,7 @@
    the English files. To follow the modifications in the English tree,
    you should <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="mailto:&email.pear.doc-subscribe;">subscribe to the PEAR
    documentation mailing list</link>
-   to get CVS commit messages, or read the archives. If you never update your
+   to get SVN commit messages, or read the archives. If you never update your
    files, the translations can get useless.
   </para>
   <para>
@@ -105,9 +105,9 @@
    </para>
    <para>
     Currently, all three fields (English revision, Maintainer, Status)
-    are needed. Maintainer is intended to be a CVS user name, or some
+    are needed. Maintainer is intended to be a SVN user name, or some
     nickname without a space, status can be anything without a space.
-    Note, that this header is not updated by CVS (in contrast with
+    Note, that this header is not updated by SVN (in contrast with
     <literal>$Revision</literal>, which is updated automatically).
     This is only updated when you edit the contents of the comment
     yourself.
@@ -169,7 +169,7 @@

 </translation>
 ]]></programlisting>
-    In this file, you can add users without a CVS account, and can
+    In this file, you can add users without a SVN account, and can
     assign ready documents or work-in-progress files to them.
     The biggest advantage of using this addon is that all this information
     is used to generate dynamic tables of translators and files in

Modified: pear/peardoc/trunk/en/chapters/faq/users.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/faq/users.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/faq/users.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -255,7 +255,7 @@

   <para>
    Unlike other aspects of PEAR development, the windows build of PHP 4.3.x is not tracked
-   in CVS.  Instead, it is located on the machine that builds windows snapshots.  Often,
+   in SVN.  Instead, it is located on the machine that builds windows snapshots.  Often,
    this will not be updated when the rest of PEAR is updated.  Note that PHP 5.x releases
    use a different build system and are automatically updated to the latest versions of
    PEAR.

Modified: pear/peardoc/trunk/en/chapters/group.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/group.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/group.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -16,7 +16,7 @@
        <para>
          This document was issued on 4th November 2003 and describes
          which directory structure must be used in PEAR packages.  The
-         goal of this document is to unify the directory naming in CVS
+         goal of this document is to unify the directory naming in SVN
          and after installations.
        </para>

@@ -268,13 +268,13 @@
            <simpara>
              A package with bugs open for longer than 2 months and the
              developers have not commented on the bug or made any
-             commits to CVS during that time frame.
+             commits to SVN during that time frame.
            </simpara>
          </listitem>
          <listitem>
            <simpara>
              A package that has no open bugs and has bug fixes committed
-             to CVS but does not have a release within 6 months of the
+             to SVN but does not have a release within 6 months of the
              bugs being fixed.
            </simpara>
          </listitem>

Modified: pear/peardoc/trunk/en/chapters/installation/cli.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/installation/cli.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/installation/cli.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -200,8 +200,8 @@
          </entry>
         </row>
         <row>
-         <entry>cvstag</entry>
-         <entry>Set a CVS release tag</entry>
+         <entry>svntag</entry>
+         <entry>Set a SVN release tag</entry>
         </row>
         <row>
          <entry>download</entry>

Modified: pear/peardoc/trunk/en/chapters/installation/svn.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/installation/svn.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/installation/svn.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="installation.cvs"><info><title>CVS installer</title></info>
+<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="installation.cvs"><info><title>SVN installer</title></info>


    <para>
@@ -8,7 +8,7 @@
    </para>
    <para>
     It is NOT recommended to run a package from SVN in working environments!
-    Because CVS versions are not regular releases, this means:
+    Because SVN versions are not regular releases, this means:
     <itemizedlist>
      <listitem>
       <simpara>You could get no kind of help from the maintainer or anybody other.</simpara>
@@ -79,7 +79,7 @@
    </orderedlist>
    <para>
     You should upgrade to an official release of the package as early as possible.
-    Before you install the official release, uninstall the CVS version to avoid
+    Before you install the official release, uninstall the SVN version to avoid
     version conflicts.
    </para>
   </section>

Modified: pear/peardoc/trunk/en/chapters/intro.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/intro.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/intro.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -138,7 +138,7 @@
      Other functions the pear.php.net site provides are:
      <itemizedlist>
       <listitem>
-       <simpara>user account management (independent of the CVS server)</simpara>
+       <simpara>user account management (independent of the SVN server)</simpara>
       </listitem>
       <listitem>
        <simpara>package management</simpara>

Modified: pear/peardoc/trunk/en/chapters/rfcs/estrict-compatibility.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/rfcs/estrict-compatibility.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/rfcs/estrict-compatibility.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -139,7 +139,7 @@

       <para>If a new major version of an existing package was registered on
       PEAR website before the deadline is reached or the code of this new
-      major version was present in PEAR CVS then this version is considered an
+      major version was present in PEAR SVN then this version is considered an
       "existing package" for the purpose of this RFC.</para>

       <para>Nevertheless, developers of existing packages are strongly

Modified: pear/peardoc/trunk/en/chapters/rfcs/header-comments.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/rfcs/header-comments.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/rfcs/header-comments.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -61,7 +61,7 @@
  * @author     Another Author &lt;[email protected]&gt;
  * @copyright  1997-2005 The PHP Group
  * @license    http://www.php.net/license/3_0.txt  PHP License 3.0
- * @version    CVS: $Id: header-comments.xml,v 1.4 2009-05-04 20:16:19 cweiske Exp $
+ * @version    SVN: $Id: header-comments.xml,v 1.4 2009-05-04 20:16:19 cweiske Exp $
  * @link       http://pear.php.net/package/PackageName
  * @see        NetOther, Net_Sample::Net_Sample()
  * @since      File available since Release 1.2.0
@@ -257,7 +257,7 @@
       <title>@version</title>

       <para>There were several comments about what to put in the @version
-      tags. This proposal uses the CVS "<literal>Id</literal>" tag for the
+      tags. This proposal uses the SVN "<literal>Id</literal>" tag for the
       "page-level" docblock which covers the file, while the class-level
       docblocks will use <literal>@package_version@</literal>, which gets
       replaced with the release's version number by the PEAR installer.</para>

Modified: pear/peardoc/trunk/en/chapters/rfcs/orphan-packages.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/rfcs/orphan-packages.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/rfcs/orphan-packages.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -31,12 +31,12 @@
       <listitem>
         <para>A package with bugs open for longer than <emphasis>2
         months</emphasis> and the developers have not commented on the bug or
-        made any commits to CVS during that time frame.</para>
+        made any commits to SVN during that time frame.</para>
       </listitem>

       <listitem>
         <para>A package that has no open bugs and has bug fixes committed to
-        CVS but does not have a release within <emphasis>6 months</emphasis>
+        SVN but does not have a release within <emphasis>6 months</emphasis>
         of the bugs being fixed.</para>
       </listitem>


Modified: pear/peardoc/trunk/en/chapters/rfcs/qa-team.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/rfcs/qa-team.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/rfcs/qa-team.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -161,7 +161,7 @@

       <para>The same time frames apply when the QA team want to make a release
       because of unreleased fixes/improvements which are only available via
-      CVS, or when the QA team wants to determine if a package has been
+      SVN, or when the QA team wants to determine if a package has been
       orphaned (using the time frames specified for non major issues).</para>

       <para>The QA team can decide what are major issues after discussion on
@@ -312,7 +312,7 @@
       </listitem>

       <listitem>
-        <para>Giving the core dudes full CVS karma on the pear CVS module, as
+        <para>Giving the core dudes full SVN karma on the pear SVN module, as
         well as full access rights to package management part of pear
         web</para>
       </listitem>

Modified: pear/peardoc/trunk/en/chapters/standards.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/standards.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/standards.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -69,7 +69,7 @@

    <para>
     Use an indent of 4 spaces, with no tabs. This helps to avoid problems
-    with diffs, patches, CVS history and annotations.
+    with diffs, patches, SVN history and annotations.
    </para>
    <para>
     For Emacs you should set indent-tabs-mode to nil. Here is an example
@@ -587,7 +587,7 @@
  * @author     Another Author <[email protected]>
  * @copyright  1997-2005 The PHP Group
  * @license    http://www.php.net/license/3_01.txt  PHP License 3.01
- * @version    CVS: ]]>&dollar;<![CDATA[Id:$
+ * @version    SVN: ]]>&dollar;<![CDATA[Id:$
  * @link       http://pear.php.net/package/PackageName
  * @see        NetOther, Net_Sample::Net_Sample()
  * @since      File available since Release 1.2.0
@@ -922,7 +922,7 @@
        <simpara>
         (required) Used for tagging a release.  If you don't use it,
         there's no way to go back and retrieve your package from the
-        CVS server in the state it was in at the time of the release.
+        SVN server in the state it was in at the time of the release.
        </simpara>
       </listitem>
      </varlistentry>
@@ -1866,7 +1866,7 @@
  * @author     Another Author <[email protected]>
  * @copyright  1997-2005 The PHP Group
  * @license    http://www.php.net/license/3_01.txt  PHP License 3.01
- * @version    CVS: ]]>&dollar;<![CDATA[Id:$
+ * @version    SVN: ]]>&dollar;<![CDATA[Id:$
  * @link       http://pear.php.net/package/PackageName
  * @see        NetOther, Net_Sample::Net_Sample()
  * @since      File available since Release 1.2.0
@@ -2103,7 +2103,7 @@
     For one there is
     <link linkend="package.php.php-codesniffer">PHP_CodeSniffer</link>
     which can be used to detect coding standard errors in your scripts.
-    Further, whole PEAR CVS repository is checked each night for violations
+    Further, whole PEAR SVN repository is checked each night for violations
     - the results can be found at
     <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.qa.cweiske.overview;">PEAR QA results overview page</link>
     as well as on the linked subpages which explain the errors in detail.

Modified: pear/peardoc/trunk/en/chapters/support.xml
===================================================================
--- pear/peardoc/trunk/en/chapters/support.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/chapters/support.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -38,7 +38,7 @@
       </listitem>
       <listitem>
        <para>
-        CVS commit list
+        SVN commit list
        </para>
       </listitem>
       <listitem>
@@ -56,9 +56,9 @@
     <para>
      The first four lists are intended to help you, if you have
      questions. Please read below to get to know, what list
-     fits to your needs. The CVS commit list is intended for people
+     fits to your needs. The SVN commit list is intended for people
      that are contributing to PEAR: All commits to our revision
-     control system (CVS) are sent to this list. The core and QA lists
+     control system (SVN) are sent to this list. The core and QA lists
      are intended for people that want to take part in the development
      of PEAR.
     </para>

Modified: pear/peardoc/trunk/en/guide/developers/contributing.xml
===================================================================
--- pear/peardoc/trunk/en/guide/developers/contributing.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/guide/developers/contributing.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -168,7 +168,7 @@
        tests should be included with every stable release, so that users can
        run them if a bug occurs to help you debug the package.  Examples of
        .phpt regression tests can be found as part of the
-       <link linkend="core.pear.pear">PEAR</link> package in CVS.  For examples of
+       <link linkend="core.pear.pear">PEAR</link> package in SVN.  For examples of
        PHPUnit tests, see the <link linkend="package.authentication.auth">Auth</link>
        package.
       </para>
@@ -340,17 +340,17 @@
         </listitem>

         <listitem>
-         <simpara>PHP CVS account</simpara>
+         <simpara>PHP SVN account</simpara>

          <para>
           If you want to administrate your code via
-          <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.cvs;">CVS</link> , you can also
+          <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.cvs;">SVN</link> , you can also
           apply for a SVN account to have access to the pear
           <abbrev>SVN</abbrev> module on <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.cvs;">
           svn.php.net</link>. This makes it easier for other users
           to contribute to your code. The PHP Group ([email protected]) manage
-          the PHP CVS server, which is used for maintaining PEAR packages.
-          If you already have a PHP CVS account you will ask the
+          the PHP SVN server, which is used for maintaining PEAR packages.
+          If you already have a PHP SVN account you will ask the
           PEAR Group for Karma for a given package or set of packages.
           Please send an email to <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="mailto:&email.pear.group;">
           &email.pear.group;</link> specifying what packages you need
@@ -360,10 +360,10 @@
          </para>

          <para>
-          If you already have a CVS repository somewhere else (e.g. on
+          If you already have a SVN repository somewhere else (e.g. on
           <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.sourceforge;">SourceForge</link>),
-          or if you don't want to maintain your code via CVS, you don't
-          need the PHP CVS account.  It is highly recommended to use some kind
+          or if you don't want to maintain your code via SVN, you don't
+          need the PHP SVN account.  It is highly recommended to use some kind
           of public repository, so that users can try out any
           bug fixes you apply to the code, before a new release is
           rolled.
@@ -381,9 +381,9 @@
        packages from there.
       </para>
       <para>
-       To get a PHP CVS account, go
+       To get a PHP SVN account, go
        <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.cvs.new;">here</link> to sign
-       up for it. The PHP CVS account has to be approved by the PHP
+       up for it. The PHP SVN account has to be approved by the PHP
        Group.
       </para>
      </listitem>

Modified: pear/peardoc/trunk/en/guide/developers/documentation.xml
===================================================================
--- pear/peardoc/trunk/en/guide/developers/documentation.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/guide/developers/documentation.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -81,7 +81,7 @@
     </note>

     <para>Besides that, one only needs a <link
-    linkend="developers.documentation.sources">CVS checkout of the peardoc
+    linkend="developers.documentation.sources">SVN checkout of the peardoc
     module</link>.</para>

     <section xml:id="developers.documentation.building.preparing">
@@ -380,9 +380,9 @@
     </section>

     <section xml:id="developers.documentation.writing.committing">
-      <title>Committing changes into CVS</title>
+      <title>Committing changes into SVN</title>

-      <para>Before committing your changes into peardoc CVS, test and build
+      <para>Before committing your changes into peardoc SVN, test and build
       it! This is absolutely necessary - it makes sure that other people
       writing documentation can build the manual without problems, and that
       the official pear.php.net build works.</para>

Modified: pear/peardoc/trunk/en/guide/migrating/customroles.xml
===================================================================
--- pear/peardoc/trunk/en/guide/migrating/customroles.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/guide/migrating/customroles.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -163,7 +163,7 @@
  * @author     Greg Beaver <[email protected]>
  * @copyright  2005 Greg Beaver
  * @license    http://www.php.net/license/3_0.txt  PHP License 3.0
- * @version    CVS: $Id: customroles.xml,v 1.6 2008-10-09 15:16:18 cweiske Exp $
+ * @version    SVN: $Id: customroles.xml,v 1.6 2008-10-09 15:16:18 cweiske Exp $
  * @link       http://pear.chiaraquartet.net/index.php?package=Chiarafoo
  * @since      File available since Release 0.1.0
  */

Modified: pear/peardoc/trunk/en/guide/newmaint/takingover.xml
===================================================================
--- pear/peardoc/trunk/en/guide/newmaint/takingover.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/guide/newmaint/takingover.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -37,12 +37,12 @@

     <listitem>
       <simpara>
-        If the sources of the package are kept in the PHP CVS
+        If the sources of the package are kept in the PHP SVN
         repository, you will also need an account for this.  You can
         sign up for it on the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.cvs.new;">PHP
         website</link>.  Please mention in the purpose field of the
         request form that the PEAR QA team has told you to get an
-        account, so that your request can be processed faster.  CVS
+        account, so that your request can be processed faster.  SVN
         accounts are managed by the PHP Group, so PEAR unfortunately has
         only limited influence on this process.
       </simpara>

Modified: pear/peardoc/trunk/en/guide/users/commandline/commands.xml
===================================================================
--- pear/peardoc/trunk/en/guide/users/commandline/commands.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/guide/users/commandline/commands.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -126,9 +126,9 @@
             </row>

             <row>
-              <entry>cvstag</entry>
+              <entry>svntag</entry>

-              <entry>Set a CVS release tag</entry>
+              <entry>Set a SVN release tag</entry>
             </row>

             <row>

Modified: pear/peardoc/trunk/en/guide/users/installation/cli.xml
===================================================================
--- pear/peardoc/trunk/en/guide/users/installation/cli.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/guide/users/installation/cli.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -200,8 +200,8 @@
          </entry>
         </row>
         <row>
-         <entry>cvstag</entry>
-         <entry>Set a CVS release tag</entry>
+         <entry>svntag</entry>
+         <entry>Set a SVN release tag</entry>
         </row>
         <row>
          <entry>download</entry>

Modified: pear/peardoc/trunk/en/guide/users/installation/svn.xml
===================================================================
--- pear/peardoc/trunk/en/guide/users/installation/svn.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/guide/users/installation/svn.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="installation.cvs"><info><title>CVS installer</title></info>
+<section xmlns="http://docbook.org/ns/docbook" version="lillet" xml:id="installation.cvs"><info><title>SVN installer</title></info>


    <para>

Modified: pear/peardoc/trunk/en/livedocs.ent
===================================================================
--- pear/peardoc/trunk/en/livedocs.ent	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/livedocs.ent	2009-09-02 22:19:03 UTC (rev 287974)
@@ -4,5 +4,5 @@
 <!ENTITY livedocs.editors 'Edited by:<br />'>
 <!ENTITY livedocs.copyright 'Copyright &copy; %s by %s'>
 <!ENTITY livedocs.published 'Published on: %s'>
-<!ENTITY livedocs.noversion 'no version information, might be only in CVS'>
+<!ENTITY livedocs.noversion 'no version information, might be only in SVN'>
 <!ENTITY livedocs.new-in-vers-5 'New in PHP 5'>

Modified: pear/peardoc/trunk/en/package/html/html-treemenu.xml
===================================================================
--- pear/peardoc/trunk/en/package/html/html-treemenu.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/package/html/html-treemenu.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -28,7 +28,7 @@
    You can get on your harddrive in
    <filename>$pear_data_dir/HTML_TreeMenu</filename>
    or online at the
-   <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.cvs.pear;HTML_TreeMenu/">PEAR CVS-Web</link>.
+   <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.cvs.pear;HTML_TreeMenu/">PEAR SVN-Web</link>.
   </para>
  </chapter>


Modified: pear/peardoc/trunk/en/package/php/php-codesniffer/coding-standard-tutorial.xml
===================================================================
--- pear/peardoc/trunk/en/package/php/php-codesniffer/coding-standard-tutorial.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/package/php/php-codesniffer/coding-standard-tutorial.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -75,7 +75,7 @@
  * @package   PHP_CodeSniffer
  * @author    Your Name <[email protected]>
  * @license   http://matrix.squiz.net/developer/tools/php_cs/licence BSD Licence
- * @version   CVS: $Id: coding-standard-tutorial.xml,v 1.9 2008-10-09 15:16:47 cweiske Exp $
+ * @version   SVN: $Id: coding-standard-tutorial.xml,v 1.9 2008-10-09 15:16:47 cweiske Exp $
  * @link      http://pear.php.net/package/PHP_CodeSniffer
  */

@@ -181,7 +181,7 @@
  * @package   PHP_CodeSniffer
  * @author    Your Name <[email protected]>
  * @license   http://matrix.squiz.net/developer/tools/php_cs/licence BSD Licence
- * @version   CVS: $Id: coding-standard-tutorial.xml,v 1.9 2008-10-09 15:16:47 cweiske Exp $
+ * @version   SVN: $Id: coding-standard-tutorial.xml,v 1.9 2008-10-09 15:16:47 cweiske Exp $
  * @link      http://pear.php.net/package/PHP_CodeSniffer
  */


Modified: pear/peardoc/trunk/en/package/qa/qa-pear-packagestatus.xml
===================================================================
--- pear/peardoc/trunk/en/package/qa/qa-pear-packagestatus.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/package/qa/qa-pear-packagestatus.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -7,7 +7,7 @@
  <chapter>
  <para>
   Simple little tool that walks over a checkout of
-  PEAR's CVS directory (<literal>pear</literal>)
+  PEAR's SVN directory (<literal>pear</literal>)
   and reports the following issues:
  </para>


Modified: pear/peardoc/trunk/en/package/qa/qa-peardoc-coverage/intro.xml
===================================================================
--- pear/peardoc/trunk/en/package/qa/qa-peardoc-coverage/intro.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/package/qa/qa-peardoc-coverage/intro.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -22,7 +22,7 @@
    <classname>QA_Peardoc_Coverage</classname> is its incarnation.
   </para>
   <para>
-   <classname>QA_Peardoc_Coverage</classname> uses a CVS checkout of
+   <classname>QA_Peardoc_Coverage</classname> uses a SVN checkout of
    PEAR and PEARDOC to find out which packages are documented, which
    classes and method are mentioned in the docs, and which developers
    do a good job in documenting their code.

Modified: pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/checkablehtmltable.xml
===================================================================
--- pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/checkablehtmltable.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/checkablehtmltable.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -9,7 +9,7 @@
   <para>
   This driver is <emphasis>experimental</emphasis>
   and has not been officially released yet.
-  It is <emphasis>only available from CVS</emphasis>.
+  It is <emphasis>only available from SVN</emphasis>.
   </para>
  </refsection>
  <refsection xml:id="package.structures.structures-datagrid.structures-datagrid-renderer.checkablehtmltable.desc"><info><title>Description</title></info>

Modified: pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/flexy.xml
===================================================================
--- pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/flexy.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/flexy.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -9,7 +9,7 @@
   <para>
   This driver is <emphasis>experimental</emphasis>
   and has not been officially released yet.
-  It is <emphasis>only available from CVS</emphasis>.
+  It is <emphasis>only available from SVN</emphasis>.
   </para>
  </refsection>
  <refsection xml:id="package.structures.structures-datagrid.structures-datagrid-renderer.flexy.modes"><info><title>Supported operations modes</title></info>

Modified: pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/htmleditform.xml
===================================================================
--- pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/htmleditform.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/package/structures/structures-datagrid/structures-datagrid-renderer/htmleditform.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -9,7 +9,7 @@
   <para>
   This driver is <emphasis>experimental</emphasis>
   and has not been officially released yet.
-  It is <emphasis>only available from CVS</emphasis>.
+  It is <emphasis>only available from SVN</emphasis>.
   </para>
  </refsection>
  <refsection xml:id="package.structures.structures-datagrid.structures-datagrid-renderer.htmleditform.modes"><info><title>Supported operations modes</title></info>

Modified: pear/peardoc/trunk/en/package/webservices/services-yahoo/design.xml
===================================================================
--- pear/peardoc/trunk/en/package/webservices/services-yahoo/design.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/package/webservices/services-yahoo/design.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -41,7 +41,7 @@
    If you would like to study the code of the package, you can do so by
    either downloading a release from the <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.pear.package;Services_Yahoo">package homepage</link> or
    by <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="&url.php.cvs.pear;Services_Yahoo">browsing the
-    code in CVS</link>.
+    code in SVN</link>.
   </para>

   <para>

Modified: pear/peardoc/trunk/en/pyrus/commands/pickle.xml
===================================================================
--- pear/peardoc/trunk/en/pyrus/commands/pickle.xml	2009-09-02 20:02:17 UTC (rev 287973)
+++ pear/peardoc/trunk/en/pyrus/commands/pickle.xml	2009-09-02 22:19:03 UTC (rev 287974)
@@ -6,7 +6,7 @@
   <info><title>Introduction</title></info>
   <para>
    The pickle command is designed to make the creation of an extension for
-   <acronym>PECL</acronym> developers very easy.  It scans a CVS checkout
+   <acronym>PECL</acronym> developers very easy.  It scans a SVN checkout
    of a PECL package directory, generates package.xml, and packages a
    release in one step.
   </para>