Changed all references to CVS to be SVN; changed corresponding links.

* doc/xslt.html: Changed all
  references to CVS to be SVN; changed corresponding links.
* doc/*html: regenerated the documentation for above

svn path=/trunk/; revision=1421

1 files changed, 24 insertions, 24 deletions

diff --git a/doc/xslt.html b/doc/xslt.html
index 6189e7b3..8fe9b55c 100644
--- a/doc/xslt.html
+++ b/doc/xslt.html
@@ -110,7 +110,7 @@ sure to specify that the bug is for the package libxslt.</p>
 
 <p>For small problems you can try to get help on IRC, the #xml channel on
 irc.gnome.org (port 6667) usually have a few person subscribed which may help
-(but there is no garantee and if a real issue is raised it should go on the
+(but there is no guarantee and if a real issue is raised it should go on the
 mailing-list for archival).</p>
 
 <p>There is also a mailing-list <a
@@ -134,18 +134,18 @@ bounces* (in the order of a thousand a day !) I cannot approve them manually
 anymore. If your mail to the list bounced waiting for administrator approval,
 it is LOST ! Repost it and fix the problem triggering the error. Also please
 note that <span style="color: #FF0000; background-color: #FFFFFF">emails with
-a legal warning asking to not copy or redistribute freely the informations
+a legal warning asking to not copy or redistribute freely the information
 they contain</span> are <strong>NOT</strong> acceptable for the mailing-list,
 such mail will as much as possible be discarded automatically, and are less
 likely to be answered if they made it to the list, <strong>DO NOT</strong>
 post to the list from an email address where such legal requirements are
 automatically added, get private paying support if you can't share
-informations.</p>
+information.</p>
 
 <p>Check the following too <span style="color: #E50000">before
 posting</span>:</p>
 <ul>
-  <li><a href="search.php">use the search engine</a> to get informations
+  <li><a href="search.php">use the search engine</a> to get information
     related to your problem.</li>
   <li>make sure you are <a href="ftp://xmlsoft.org/libxslt/">using a recent
     version</a>, and that the problem still shows up in those</li>
@@ -162,7 +162,7 @@ posting</span>:</p>
     stylesheet (as an attachment)</li>
 </ul>
 
-<p>Then send the bug with associated informations to reproduce it to the <a
+<p>Then send the bug with associated information to reproduce it to the <a
 href="mailto:xslt@gnome.org">xslt@gnome.org</a> list; if it's really libxslt
 related I will approve it. Please do not send mail to me directly, it makes
 things really hard to track and in some cases I am not the best person to
@@ -177,10 +177,10 @@ answer a given question, ask on the list.</p>
     others" and is not welcome. I will automatically Carbon-Copy the
     xslt@gnome.org mailing list for any technical reply made about libxml2 or
     libxslt.</li>
-  <li>There is <span style="color: #E50000">no garantee for support</span>,
+  <li>There is <span style="color: #E50000">no guarantee for support</span>,
     if your question remains unanswered after a week, repost it, making sure
-    you gave all the detail needed and the informations requested.</li>
-  <li>Failing to provide informations as requested or double checking first
+    you gave all the detail needed and the information requested.</li>
+  <li>Failing to provide information as requested or double checking first
     for prior feedback also carries the implicit message "the time of the
     library maintainers is less valuable than my time" and might not be
     welcome.</li>
@@ -248,15 +248,15 @@ binaries</a>.</p>
 platform, get in touch with me to upload the package. I will keep them in the
 <a href="ftp://xmlsoft.org/libxml2/contribs/">contrib directory</a></p>
 
-<p>Libxslt is also available from CVS:</p>
+<p>Libxslt is also available from SVN:</p>
 <ul>
-  <li><p>The <a href="http://cvs.gnome.org/viewcvs/libxslt/">GNOME CVS
+  <li><p>The <a href="http://svn.gnome.org/viewcvs/libxslt/trunk/">GNOME SVN
     base</a>. Check the <a
-    href="http://developer.gnome.org/tools/cvs.html">GNOME CVS Tools</a>
-    page; the CVS module is <b>libxslt</b>.</p>
+    href="http://developer.gnome.org/tools/svn.html">GNOME SVN Tools</a>
+    page; the SVN module is <b>libxslt</b>.</p>
   </li>
   <li><a href="ftp://xmlsoft.org/libxml2/libxslt-cvs-snapshot.tar.gz">snapshots from
-    CVS</a> updated every hour are also provided</li>
+    SVN</a> updated every hour are also provided</li>
 </ul>
 
 <h2><a name="FAQ">FAQ</a></h2>
@@ -300,7 +300,7 @@ platform, get in touch with me to upload the package. I will keep them in the
 <h2><a name="News">News</a></h2>
 
 <p>The <a href="ChangeLog.html">change log</a> describes the recents commits
-to the <a href="http://cvs.gnome.org/viewcvs/libxslt/">CVS</a> code base.</p>
+to the <a href="http://svn.gnome.org/viewcvs/libxslt/trunk/">SVN</a> code base.</p>
 
 <p>Those are the public releases made:</p>
 
@@ -857,7 +857,7 @@ to the <a href="http://cvs.gnome.org/viewcvs/libxslt/">CVS</a> code base.</p>
   <li>patches for Windows and update of Windows Makefiles by Igor</li>
   <li>OpenVMS port instructions from John A Fotheringham</li>
   <li>fixed some Makefiles annoyance and libraries prelinking
-  informations</li>
+  information</li>
 </ul>
 
 <h3>1.0.7: Nov 10 2001</h3>
@@ -1134,7 +1134,7 @@ Usage: xsltproc [options] stylesheet file [file ...]
       --warnnet warn against fetching over the network
       --catalogs : use the catalogs from $SGML_CATALOG_FILES
       --xinclude : do XInclude processing on document input
-      --profile or --norman : dump profiling informations 
+      --profile or --norman : dump profiling information 
 orchis:~ -&gt;</pre>
 
 <h2><a name="DocBook">DocBook</a></h2>
@@ -1147,7 +1147,7 @@ computer hardware and software.</p>
 
 <p>xsltproc and libxslt are not specifically dependant on DocBook, but since
 a lot of people use xsltproc and libxml2 for DocBook formatting, here are a
-few pointers and informations which may be helpful:</p>
+few pointers and information which may be helpful:</p>
 <ul>
   <li>The <a href="http://www.oasis-open.org/committees/docbook/">DocBook
     homepage at Oasis</a> you should find pointers there on all the lastest
@@ -1156,7 +1156,7 @@ few pointers and informations which may be helpful:</p>
     the official reference documentation for DocBook.</li>
   <li><a
     href="https://sourceforge.net/docman/index.php?group_id=21935">DocBook
-    Open Repository</a> contains a lot of informations about DocBook</li>
+    Open Repository</a> contains a lot of information about DocBook</li>
   <li>Bob Stayton provides a <a href="http://www.sagehill.net/">lot of
     resources</a> and consulting services around DocBook.</li>
   <li>Here is a <a href="/buildDocBookCatalog">shell script</a> to generate
@@ -1215,7 +1215,7 @@ again:</p>
 
 <p>Okay this section is clearly incomplete. But integrating libxslt into your
 application should be relatively easy. First check the few steps described
-below, then for more detailed informations, look at the<a
+below, then for more detailed information, look at the<a
 href="html/libxslt-lib.html"> generated pages</a> for the API and the source
 of libxslt/xsltproc.c  and the  <a
 href="tutorial/libxslttutorial.html">tutorial</a>.</p>
@@ -1288,7 +1288,7 @@ or libxslt wrappers or bindings:</p>
 <p>The libxslt Python module depends on the <a
 href="http://xmlsoft.org/python.html">libxml2 Python</a> module.</p>
 
-<p>The distribution includes a set of Python bindings, which are garanteed to
+<p>The distribution includes a set of Python bindings, which are guaranteed to
 be maintained as part of the library in the future, though the Python
 interface have not yet reached the completeness of the C API.</p>
 
@@ -1351,7 +1351,7 @@ in that example and how is the processing done:</p>
     HTML tree are suitable for XSLT processing in libxslt. This is actually
     how this page is generated !</li>
   <li><code>result</code> : this is a document generated by applying the
-    stylesheet to the document. Note that some of the stylesheet informations
+    stylesheet to the document. Note that some of the stylesheet information
     may be related to the serialization of that document and as in this
     example a specific saveResultToFilename() method of the stylesheet should
     be used to save it to a file (in that case to "foo").</li>
@@ -1399,7 +1399,7 @@ looks for the current insertion node in the resulting output (either the
 resulting document or the Result Value Tree being generated), and saves it to
 a global variable for checking that the access actually worked.</p>
 
-<p>For more informations on the xpathParserContext and transformContext
+<p>For more information on the xpathParserContext and transformContext
 objects check the <a href="internals.html">libray internals description</a>.
 The pctxt is actually an object from a class derived from the
 libxml2.xpathParserContext() with just a couple more properties including the
@@ -1570,7 +1570,7 @@ indicates the kind of node it represents, the most common ones are:</p>
 
 <p>For the XSLT processing, entity nodes should not be generated (i.e. they
 should be replaced by their content). Most nodes also contains the following
-"navigation" informations:</p>
+"navigation" information:</p>
 <ul>
   <li>the containing <strong>doc</strong>ument</li>
   <li>the <strong>parent</strong> node</li>
@@ -2300,7 +2300,7 @@ libxslt:test element, it will output a comment in the result tree:</p>
  * @ctxt:  an XSLT processing context
  * @node:  The current node
  * @inst:  the instruction in the stylesheet
- * @comp:  precomputed informations
+ * @comp:  precomputed information
  *
  * Process a libxslt:test node
  */