commit fc8dc355dac40605e66a7e8722db5077f03076f3
author Daniel Veillard <veillard@src.gnome.org> Sat Oct 18 09:07:46 2003 +0000
committer Daniel Veillard <veillard@src.gnome.org> Sat Oct 18 09:07:46 2003 +0000
tree ec7bbb04816b0198c6584774dbbd4f2890510404
parent 871611bb0325095b30559ff1edc1fdaa2ad5fd2f

added new APIs for creating reader from sources or reusing a reader with a

* xmlreader.c include/libxml/xmlreader.h: added new APIs
  for creating reader from sources or reusing a reader with
  a new source, like the xmlReadxx and xmlCtxtReadxxx
* win32/libxml2.def.src doc/libxml2-api.xml doc/apibuild.py
  doc/Makefile.am: regenerated the APIs
* doc/xml.html: applied a patch from Stefan Kost for namesapce docs
Daniel

doc/xml.html

diff --git a/doc/xml.html b/doc/xml.html
index d72d4b9..f7fcdaa 100644
--- a/doc/xml.html
+++ b/doc/xml.html
@@ -3758,7 +3758,14 @@
 
 <p>@@Interfaces@@</p>
 
-<p>@@Examples@@</p>
+<pre>
+xmlNodePtr node;
+if(!strncmp(node-&gt;name,"mytag",5)
+  &amp;&amp; node-&gt;ns
+  &amp;&amp; !strcmp(node-&gt;ns-&gt;href,"http://www.mysite.com/myns/1.0")) {
+  ...
+}
+</pre>
 
 <p>Usually people object to using namespaces together with validity checking.
 I will try to make sure that using namespaces won't break validity checking,
@@ -3766,9 +3773,11 @@
 suggest adding namespaces to your document. A default namespace scheme
 <code>xmlns="http://...."</code> should not break validity even on less
 flexible parsers. Using namespaces to mix and differentiate content coming
-from multiple DTDs will certainly break current validation schemes. I will
-try to provide ways to do this, but this may not be portable or
-standardized.</p>
+from multiple DTDs will certainly break current validation schemes.
+To check such documents one needs to use schema-validation, which is supported
+in libxml2 as well. See <a href="http://www.relaxng.org/">relagx-ng</a> and
+<a href="http://www.w3c.org/XML/Schema">w3c-schema</a>.
+</p>
 
 <h2><a name="Upgrading">Upgrading 1.x code</a></h2>
 
@@ -3796,7 +3805,7 @@
 <p>So client code of libxml designed to run with version 1.x may have to be
 changed to compile against version 2.x of libxml. Here is a list of changes
 that I have collected, they may not be sufficient, so in case you find other
-change which are required, <a href="mailto:Daniel.Ïeillardw3.org">drop me a
+change which are required, <a href="mailto:Daniel.Veillard@w3.org">drop me a
 mail</a>:</p>
 <ol>
   <li>The package name have changed from libxml to libxml2, the library name