possible mem leak patch from Jason Adams integrated xf:escape-uri() from
* xpath.c: possible mem leak patch from Jason Adams
* xpath.c: integrated xf:escape-uri() from Wesley Terpstra
in the XQuery namespace
* configure.in: preparing 2.4.24
* doc/*.html: updated the web pages
* python/generator.py: closing bug #85258 by generating conditional
compile check to avoid linking to routines not configured in.
Daniel
diff --git a/doc/FAQ.html b/doc/FAQ.html
index 1213039..f235429 100644
--- a/doc/FAQ.html
+++ b/doc/FAQ.html
@@ -105,9 +105,9 @@
</li>
<li>
<em>Can I embed libxml in a proprietary application ?</em>
- <p>Yes. The MIT License allows you to keep proprietary the changes
- you made to libxml, but it would be graceful to send-back bug fixes
- and improvements as patches for possible incorporation in the main
+ <p>Yes. The MIT License allows you to keep proprietary the changes you
+ made to libxml, but it would be graceful to send-back bug fixes and
+ improvements as patches for possible incorporation in the main
development tree.</p>
</li>
</ol>
@@ -128,8 +128,8 @@
<li>
<em>I see libxml and libxml2 releases, which one should I install ?</em>
<ul>
-<li>If you are not constrained by backward compatibility issues
- with existing applications, install libxml2 only</li>
+<li>If you are not constrained by backward compatibility issues with
+ existing applications, install libxml2 only</li>
<li>If you are not doing development, you can safely install both.
Usually the packages <a href="http://rpmfind.net/linux/RPM/libxml.html">libxml</a> and <a href="http://rpmfind.net/linux/RPM/libxml2.html">libxml2</a> are
compatible (this is not the case for development packages).</li>
@@ -145,8 +145,8 @@
<li>
<em>I can't install the libxml package, it conflicts with libxml0</em>
<p>You probably have an old libxml0 package used to provide the shared
- library for libxml.so.0, you can probably safely remove it. The
- libxml packages provided on <a href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> provide
+ library for libxml.so.0, you can probably safely remove it. The libxml
+ packages provided on <a href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> provide
libxml.so.0</p>
</li>
<li>
@@ -156,9 +156,9 @@
rebuild it locally with</p>
<p>
<code>rpm --rebuild libxml(2)-xxx.src.rpm</code>.</p>
- <p>If everything goes well it will generate two binary rpm packages (one providing
- the shared libs and xmllint, and the other one, the -devel package,
- providing includes, static libraries and scripts needed to build
+ <p>If everything goes well it will generate two binary rpm packages (one
+ providing the shared libs and xmllint, and the other one, the -devel
+ package, providing includes, static libraries and scripts needed to build
applications with libxml(2)) that you can install locally.</p>
</li>
</ol>
@@ -197,17 +197,18 @@
</li>
<li>
<em>Make check fails on some platforms</em>
- <p>Sometimes the regression tests' results don't completely match the value
- produced by the parser, and the makefile uses diff to print the delta. On
- some platforms the diff return breaks the compilation process; if the
- diff is small this is probably not a serious problem.</p>
+ <p>Sometimes the regression tests' results don't completely match the
+ value produced by the parser, and the makefile uses diff to print the
+ delta. On some platforms the diff return breaks the compilation process;
+ if the diff is small this is probably not a serious problem.</p>
<p>Sometimes (especially on Solaris) make checks fail due to limitations
in make. Try using GNU-make instead.</p>
</li>
<li>
<em>I use the CVS version and there is no configure script</em>
- <p>The configure script (and other Makefiles) are generated. Use the autogen.sh
- script to regenerate the configure script and Makefiles, like:</p>
+ <p>The configure script (and other Makefiles) are generated. Use the
+ autogen.sh script to regenerate the configure script and Makefiles,
+ like:</p>
<p><code>./autogen.sh --prefix=/usr --disable-shared</code></p>
</li>
<li>
@@ -293,8 +294,8 @@
patches.</p>
</li>
<li>
-<em>Where can I get more examples and information than privoded on the web
- page?</em>
+<em>Where can I get more examples and information than privoded on the
+ web page?</em>
<p>Ideally a libxml book would be nice. I have no such plan ... But you
can:</p>
<ul>
@@ -311,9 +312,9 @@
<li>
<a href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&dir=gnome-xml">Browse
the libxml source</a> , I try to write code as clean and documented
- as possible, so looking at it may be helpful. In particular the code of
- xmllint.c and of the various testXXX.c test programs should provide
- good examples of how to do things with the library.</li>
+ as possible, so looking at it may be helpful. In particular the code
+ of xmllint.c and of the various testXXX.c test programs should
+ provide good examples of how to do things with the library.</li>
</ul>
</li>
<li>What about C++ ?
@@ -336,8 +337,8 @@
</li>
<li>How to validate a document a posteriori ?
<p>It is possible to validate documents which had not been validated at
- initial parsing time or documents which have been built from scratch using
- the API. Use the <a href="http://xmlsoft.org/html/libxml-valid.html#XMLVALIDATEDTD">xmlValidateDtd()</a>
+ initial parsing time or documents which have been built from scratch
+ using the API. Use the <a href="http://xmlsoft.org/html/libxml-valid.html#XMLVALIDATEDTD">xmlValidateDtd()</a>
function. It is also possible to simply add a DTD to an existing
document:</p>
<pre>xmlDocPtr doc; /* your existing document */