preparing 2.4.7 switched to the latest xmllint manual page from John

* configure.in: preparing 2.4.7
* Makefile.am doc/Makefile.am: switched to the latest xmllint
  manual page from John
* doc/*: updated the doc and rebuilt the generated pages
Daniel
diff --git a/doc/xml.html b/doc/xml.html
index d4befa9..a8c0d10 100644
--- a/doc/xml.html
+++ b/doc/xml.html
@@ -559,9 +559,25 @@
     SGML docs</li>
 </ul>
 
+<h3>2.4.7: Oct 30 2001</h3>
+<ul>
+  <li>exported some debugging interfaces</li>
+  <li>serious rewrite of the catalog code</li>
+  <li>integrated Gary Pennington thread safety patch, added configure option
+    and regression tests</li>
+  <li>removed an HTML parser bug</li>
+  <li>fixed a couple of potentially serious validation bugs</li>
+  <li>integrated the SGML DocBook support in xmllint</li>
+  <li>changed the nanoftp anonymous login passwd</li>
+  <li>some I/O cleanup and a couple of interfaces for Perl wrapper</li>
+  <li>general bug fixes</li>
+  <li>updated xmllint man page by John Fleck</li>
+  <li>some VMS and Windows updates</li>
+</ul>
+
 <h3>2.4.6: Oct 10 2001</h3>
 <ul>
-  <li>added and updated man pages by John Fleck</li>
+  <li>added an updated man pages by John Fleck</li>
   <li>portability and configure fixes</li>
   <li>an infinite loop on the HTML parser was removed (William)</li>
   <li>Windows makefile patches from Igor</li>
@@ -2124,6 +2140,7 @@
 
 
 
+
 } </pre>
   </li>
   <li>And then use it to save the document:
@@ -2994,6 +3011,35 @@
 has been drastically improved too. Don't take those changes as an excuse to
 not upgrade, it may cost a lot on the long term ...</p>
 
+<h2><a name="Thread">Thread safety</a></h2>
+
+<p>Starting with 2.4.7, libxml makes provisions to ensure that concurent
+threads can safely work in parallel parsing different documents. There is
+however a couple of things to do to ensure it:</p>
+<ul>
+  <li>configure the library accordingly using the --with-threads options</li>
+  <li>call xmlInitParser() in the "main" thread before using any of the
+    libxml API (except possibly selecting a different memory allocator)</li>
+</ul>
+
+<p>Note that the thread safety cannot be ensured for multiple threads sharing
+the same document, the locking must be done at the application level, libxml
+exports a basic mutex and reentrant mutexes API in &lt;libxml/threads.h&gt;.
+The parts of the library checked for thread safety are:</p>
+<ul>
+  <li>concurrent loading</li>
+  <li>file access resolution</li>
+  <li>catalog access</li>
+  <li>catalog building</li>
+  <li>entities lookup/accesses</li>
+  <li>validation</li>
+  <li>global variables per-thread override</li>
+  <li>memory handling</li>
+</ul>
+
+<p>XPath is supposed to be thread safe now, but this wasn't tested
+seriously.</p>
+
 <h2><a name="DOM"></a><a name="Principles">DOM Principles</a></h2>
 
 <p><a href="http://www.w3.org/DOM/">DOM</a> stands for the <em>Document