Hallski complained it could not be included by itself. Daniel
* include/libxml/xmlIO.h: Hallski complained it could not be
included by itself.
Daniel
diff --git a/doc/example.html b/doc/example.html
index 21f2249..e98bc9b 100644
--- a/doc/example.html
+++ b/doc/example.html
@@ -147,7 +147,7 @@
</gjob:Jobs>
</gjob:Helping></pre>
<p>While loading the XML file into an internal DOM tree is a matter of
-calling only a couple of functions, browsing the tree to gather the data and
+calling only a couple of functions, browsing the tree to gather the ata and
generate the internal structures is harder, and more error prone.</p>
<p>The suggested principle is to be tolerant with respect to the input
structure. For example, the ordering of the attributes is not significant,
diff --git a/doc/python.html b/doc/python.html
index d0b9fa7..2bfe080 100644
--- a/doc/python.html
+++ b/doc/python.html
@@ -112,7 +112,7 @@
<li>Petr Kozelka provides <a href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
libxml2</a> with Kylix, Delphi and other Pascal compilers</li>
<li>Uwe Fechner also provides <a href="http://sourceforge.net/projects/idom2-pas/">idom2</a>, a DOM2
- implementation for Kylix2/D5/D6 from Borland </li>
+ implementation for Kylix2/D5/D6 from Borland</li>
<li>Wai-Sun "Squidster" Chia provides <a href="http://www.rubycolor.org/arc/redist/">bindings for Ruby</a> and
libxml2 bindings are also available in Ruby through the <a href="http://libgdome-ruby.berlios.de/">libgdome-ruby</a> module
maintained by Tobias Peters.</li>
diff --git a/doc/xmlio.html b/doc/xmlio.html
index e16b783..6151f2d 100644
--- a/doc/xmlio.html
+++ b/doc/xmlio.html
@@ -226,6 +226,7 @@
+
} </pre>
</li>
<li>And then use it to save the document:
diff --git a/doc/xmlmem.html b/doc/xmlmem.html
index 498972e..2ba3993 100644
--- a/doc/xmlmem.html
+++ b/doc/xmlmem.html
@@ -168,7 +168,11 @@
possible to find more easilly:</p>
<ol>
<li>write down the block number xxxx not allocated</li>
-<li>export the environement variable XML_MEM_BREAKPOINT=xxxx</li>
+<li>export the environement variable XML_MEM_BREAKPOINT=xxxx , the easiest
+ when using GDB is to simply give the command
+ <p><code>set environment XML_MEM_BREAKPOINT xxxx</code></p>
+<p>before running the program.</p>
+</li>
<li>run the program under a debugger and set a breakpoint on
xmlMallocBreakpoint() a specific function called when this precise block
is allocated</li>
@@ -178,7 +182,10 @@
</ol>
<p>I used to use a commercial tool to debug libxml memory problems but after
noticing that it was not detecting memory leaks that simple mechanism was
-used and proved extremely efficient until now.</p>
+used and proved extremely efficient until now. Lately I have also used <a href="http://developer.kde.org/~sewardj/">valgrind</a> with quite some
+success, it is tied to the i386 architecture since it works by emulating the
+processor and instruction set, it is slow but extremely efficient, i.e. it
+spot memory usage errors in a very precise way.</p>
<h3><a name="General4">General memory requirements</a></h3>
<p>How much libxml memory require ? It's hard to tell in average it depends
of a number of things:</p>