fixed links broken due to the reorg of xmlsoft.org, daniel.

doc/xml.html

@@ -78,7 +78,7 @@ building tag-based structured documents/data.</p>
 <p>There are some on-line resources about using libxml:</p>
 <ol>
   <li>Check the <a href="FAQ.html">FAQ</a></li>
-  <li>Check the <a href="http://xmlsoft.org/libxml.html">extensive
+  <li>Check the <a href="http://xmlsoft.org/html/libxml-lib.html">extensive
     documentation</a> automatically extracted from code comments.</li>
   <li>This page provides a global overview and <a href="#real">some
     examples</a> on how to use libxml.</li>
@@ -141,10 +141,10 @@ about Docbook), but it's a good starting point.</p>
 href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> or on the <a
 href="ftp://ftp.gnome.org/pub/GNOME/MIRRORS.html">Gnome FTP server</a> either
 as a <a href="ftp://ftp.gnome.org/pub/GNOME/stable/sources/libxml/">source
-archive</a> or <a href="ftp://ftp.gnome.org/pub/GNOME/contrib/rpms/">RPM
+archive</a> or <a href="ftp://ftp.gnome.org/pub/GNOME/contrib/redhat/SRPMS/">RPM
 packages</a>. (NOTE that you need both the <a
-href="http://rpmfind.net/linux/RPM/libxml.html">libxml</a> and <a
-href="http://rpmfind.net/linux/RPM/libxml-devel.html">libxml-devel</a>
+href="http://rpmfind.net/linux/RPM/libxml2.html">libxml(2)</a> and <a
+href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml(2)-devel</a>
 packages installed to compile applications using libxml.)</p>
 
 <p><a name="Snapshot">Snapshot:</a></p>
@@ -388,12 +388,12 @@ for really accurate description</h3>
 <h3>1.7.0: sep 23 1999</h3>
 <ul>
   <li>Added the ability to fetch remote DTD or parsed entities, see the <a
-    href="gnome-xml-nanohttp.html">nanohttp</a> module.</li>
+    href="html/gnome-xml-nanohttp.html">nanohttp</a> module.</li>
   <li>Added an errno to report errors by another mean than a simple printf
     like callback</li>
   <li>Finished ID/IDREF support and checking when validation</li>
   <li>Serious memory leaks fixed (there is now a <a
-    href="gnome-xml-xmlmemory.html">memory wrapper</a> module)</li>
+    href="html/gnome-xml-xmlmemory.html">memory wrapper</a> module)</li>
   <li>Improvement of <a href="http://www.w3.org/TR/xpath">XPath</a>
     implementation</li>
   <li>Added an HTML parser front-end</li>
@@ -557,8 +557,8 @@ required, but as a separate set of documents. The interfaces of the XML
 library are by principle low level, there is nearly zero abstraction. Those
 interested in a higher level API should <a href="#DOM">look at DOM</a>.</p>
 
-<p>The <a href="gnome-xml-parser.html">parser interfaces for XML</a> are
-separated from the <a href="gnome-xml-htmlparser.html">HTML parser
+<p>The <a href="html/gnome-xml-parser.html">parser interfaces for XML</a> are
+separated from the <a href="html/gnome-xml-htmlparser.html">HTML parser
 interfaces</a>.  Let's have a look at how the XML parser can be called:</p>
 
 <h3><a name="Invoking">Invoking the parser : the pull method</a></h3>
@@ -658,7 +658,7 @@ that produces the XML document used in the previous examples:</p>
 
 <h3><a name="Traversing">Traversing the tree</a></h3>
 
-<p>Basically by <a href="gnome-xml-tree.html">including "tree.h"</a> your code
+<p>Basically by <a href="html/gnome-xml-tree.html">including "tree.h"</a> your code
 has access to the internal structure of all the elements of the tree. The
 names should be somewhat simple like <strong>parent</strong>,
 <strong>childs</strong>, <strong>next</strong>, <strong>prev</strong>,
@@ -680,7 +680,7 @@ element which is not the document Root Element, a function
 <h3><a name="Modifying">Modifying the tree</a></h3>
 
 <p>Functions are provided for reading and writing the document content. Here
-is an excerpt from the <a href="gnome-xml-tree.html">tree API</a>:</p>
+is an excerpt from the <a href="html/gnome-xml-tree.html">tree API</a>:</p>
 <dl>
   <dt><code>xmlAttrPtr xmlSetProp(xmlNodePtr node, const xmlChar *name, const
   xmlChar *value);</code></dt>
@@ -800,7 +800,7 @@ content to be able to save the document back without losing this usually
 precious information (if the user went through the pain of explicitly defining
 entities, he may have a a rather negative attitude if you blindly susbtitute
 them as saving time). The <a
-href="gnome-xml-parser.html#XMLSUBSTITUTEENTITIESDEFAULT">xmlSubstituteEntitiesDefault()</a>
+href="html/gnome-xml-parser.html#XMLSUBSTITUTEENTITIESDEFAULT">xmlSubstituteEntitiesDefault()</a>
 function allows you to check and change the behaviour, which is to not
 substitute entities by default.</p>
 
@@ -1182,6 +1182,6 @@ Gnome CVS base under gnome-xml/example</p>
 
 <p><a href="mailto:Daniel.Veillard@w3.org">Daniel Veillard</a></p>
 
-<p>$Id: xml.html,v 1.36 2000/07/02 07:56:37 veillard Exp $</p>
+<p>$Id: xml.html,v 1.37 2000/07/03 11:41:26 veillard Exp $</p>
 </body>
 </html>