blob: 6ecd81cf0790abd854b1d43c6261d94c03d016cf [file] [log] [blame]
Daniel Veillard09ab7e12001-07-10 15:49:44 +00001<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
Daniel Veillardccb09631998-10-27 06:21:04 +00003<html>
4<head>
Daniel Veillard598bec32003-07-06 10:02:03 +00005 <title>The XML C parser and toolkit of Gnome</title>
Daniel Veillard67952602006-01-05 15:29:44 +00006 <meta name="GENERATOR" content="amaya 8.5, see http://www.w3.org/Amaya/">
Daniel Veillardb24054a1999-12-18 15:32:46 +00007 <meta http-equiv="Content-Type" content="text/html">
Daniel Veillardccb09631998-10-27 06:21:04 +00008</head>
Daniel Veillardccb09631998-10-27 06:21:04 +00009
Daniel Veillardb05deb71999-08-10 19:04:08 +000010<body bgcolor="#ffffff">
Daniel Veillard598bec32003-07-06 10:02:03 +000011<h1 align="center">The XML C parser and toolkit of Gnome</h1>
Daniel Veillardb05deb71999-08-10 19:04:08 +000012
Daniel Veillard67952602006-01-05 15:29:44 +000013<h1>Note: this is the flat content of the <a href="index.html">web
14site</a></h1>
Daniel Veillard9c466822001-10-25 12:03:39 +000015
Daniel Veillardc9484202001-10-24 12:35:52 +000016<h1 style="text-align: center">libxml, a.k.a. gnome-xml</h1>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +000017
18<p></p>
Daniel Veillard9c466822001-10-25 12:03:39 +000019
Daniel Veillard7ebac022004-02-25 22:36:35 +000020<p
21style="text-align: right; font-style: italic; font-size: 10pt">"Programming
22with libxml2 is like the thrilling embrace of an exotic stranger." <a
23href="http://diveintomark.org/archives/2004/02/18/libxml2">Mark
24Pilgrim</a></p>
25
Daniel Veillard598bec32003-07-06 10:02:03 +000026<p>Libxml2 is the XML C parser and toolkit developed for the Gnome project
Daniel Veillard23a52c52003-08-18 10:01:18 +000027(but usable outside of the Gnome platform), it is free software available
Daniel Veillardeec1ae92003-09-09 13:11:01 +000028under the <a href="http://www.opensource.org/licenses/mit-license.html">MIT
29License</a>. XML itself is a metalanguage to design markup languages, i.e.
30text language where semantic and structure are added to the content using
31extra "markup" information enclosed between angle brackets. HTML is the most
32well-known markup language. Though the library is written in C <a
33href="python.html">a variety of language bindings</a> make it available in
34other environments.</p>
Daniel Veillard9c466822001-10-25 12:03:39 +000035
Daniel Veillard710823b2003-03-04 10:05:52 +000036<p>Libxml2 is known to be very portable, the library should build and work
37without serious troubles on a variety of systems (Linux, Unix, Windows,
38CygWin, MacOS, MacOS X, RISC Os, OS/2, VMS, QNX, MVS, ...)</p>
39
Daniel Veillard9c466822001-10-25 12:03:39 +000040<p>Libxml2 implements a number of existing standards related to markup
41languages:</p>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +000042<ul>
Daniel Veillard9c466822001-10-25 12:03:39 +000043 <li>the XML standard: <a
44 href="http://www.w3.org/TR/REC-xml">http://www.w3.org/TR/REC-xml</a></li>
45 <li>Namespaces in XML: <a
46 href="http://www.w3.org/TR/REC-xml-names/">http://www.w3.org/TR/REC-xml-names/</a></li>
47 <li>XML Base: <a
48 href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a></li>
Daniel Veillardaf43f632002-03-08 15:05:20 +000049 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc2396.txt">RFC 2396</a> :
50 Uniform Resource Identifiers <a
Daniel Veillard9c466822001-10-25 12:03:39 +000051 href="http://www.ietf.org/rfc/rfc2396.txt">http://www.ietf.org/rfc/rfc2396.txt</a></li>
52 <li>XML Path Language (XPath) 1.0: <a
53 href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a></li>
54 <li>HTML4 parser: <a
55 href="http://www.w3.org/TR/html401/">http://www.w3.org/TR/html401/</a></li>
Daniel Veillard23a52c52003-08-18 10:01:18 +000056 <li>XML Pointer Language (XPointer) Version 1.0: <a
Daniel Veillard9c466822001-10-25 12:03:39 +000057 href="http://www.w3.org/TR/xptr">http://www.w3.org/TR/xptr</a></li>
58 <li>XML Inclusions (XInclude) Version 1.0: <a
59 href="http://www.w3.org/TR/xinclude/">http://www.w3.org/TR/xinclude/</a></li>
Daniel Veillard23a52c52003-08-18 10:01:18 +000060 <li>ISO-8859-x encodings, as well as <a
Daniel Veillard9c466822001-10-25 12:03:39 +000061 href="http://www.cis.ohio-state.edu/rfc/rfc2044.txt">rfc2044</a> [UTF-8]
62 and <a href="http://www.cis.ohio-state.edu/rfc/rfc2781.txt">rfc2781</a>
Daniel Veillard23a52c52003-08-18 10:01:18 +000063 [UTF-16] Unicode encodings, and more if using iconv support</li>
Daniel Veillard9c466822001-10-25 12:03:39 +000064 <li>part of SGML Open Technical Resolution TR9401:1997</li>
65 <li>XML Catalogs Working Draft 06 August 2001: <a
66 href="http://www.oasis-open.org/committees/entity/spec-2001-08-06.html">http://www.oasis-open.org/committees/entity/spec-2001-08-06.html</a></li>
Daniel Veillard5c396542002-03-15 07:57:50 +000067 <li>Canonical XML Version 1.0: <a
68 href="http://www.w3.org/TR/xml-c14n">http://www.w3.org/TR/xml-c14n</a>
Daniel Veillard2d347fa2002-03-17 10:34:11 +000069 and the Exclusive XML Canonicalization CR draft <a
70 href="http://www.w3.org/TR/xml-exc-c14n">http://www.w3.org/TR/xml-exc-c14n</a></li>
Daniel Veillard758c5312003-12-15 11:51:25 +000071 <li>Relax NG, ISO/IEC 19757-2:2003, <a
Daniel Veillard17bed982003-02-24 20:11:43 +000072 href="http://www.oasis-open.org/committees/relax-ng/spec-20011203.html">http://www.oasis-open.org/committees/relax-ng/spec-20011203.html</a></li>
Daniel Veillardf83a2c72003-04-08 13:48:40 +000073 <li>W3C XML Schemas Part 2: Datatypes <a
74 href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">REC 02 May
Daniel Veillard7ecced52003-12-18 14:22:09 +000075 2001</a></li>
Daniel Veillardeca726d2004-04-18 21:47:34 +000076 <li>W3C <a href="http://www.w3.org/TR/xml-id/">xml:id</a> Working Draft 7
77 April 2004</li>
Daniel Veillard96984452000-08-31 13:50:12 +000078</ul>
79
Daniel Veillard560c2a42003-07-06 21:13:49 +000080<p>In most cases libxml2 tries to implement the specifications in a
Daniel Veillard7c4eb632004-04-19 21:29:12 +000081relatively strictly compliant way. As of release 2.4.16, libxml2 passed all
Daniel Veillard560c2a42003-07-06 21:13:49 +0000821800+ tests from the <a
Daniel Veillarda5393562002-02-20 11:40:49 +000083href="http://www.oasis-open.org/committees/xml-conformance/">OASIS XML Tests
84Suite</a>.</p>
Daniel Veillard5b16f582002-02-20 11:38:46 +000085
Daniel Veillard0b28e882002-07-24 23:47:05 +000086<p>To some extent libxml2 provides support for the following additional
87specifications but doesn't claim to implement them completely:</p>
Daniel Veillard9c466822001-10-25 12:03:39 +000088<ul>
89 <li>Document Object Model (DOM) <a
90 href="http://www.w3.org/TR/DOM-Level-2-Core/">http://www.w3.org/TR/DOM-Level-2-Core/</a>
Daniel Veillardd4cfcef2004-05-06 18:55:27 +000091 the document model, but it doesn't implement the API itself, gdome2 does
92 this on top of libxml2</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +000093 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc959.txt">RFC 959</a> :
Daniel Veillard8a469172003-06-12 16:05:07 +000094 libxml2 implements a basic FTP client code</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +000095 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc1945.txt">RFC 1945</a> :
96 HTTP/1.0, again a basic HTTP client code</li>
Daniel Veillard7c4eb632004-04-19 21:29:12 +000097 <li>SAX: a SAX2 like interface and a minimal SAX1 implementation compatible
98 with early expat versions</li>
Daniel Veillard9c466822001-10-25 12:03:39 +000099</ul>
100
Daniel Veillardf83a2c72003-04-08 13:48:40 +0000101<p>A partial implementation of <a
102href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">XML Schemas Part
1031: Structure</a> is being worked on but it would be far too early to make any
104conformance statement about it at the moment.</p>
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000105
Daniel Veillard96984452000-08-31 13:50:12 +0000106<p>Separate documents:</p>
107<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000108 <li><a href="http://xmlsoft.org/XSLT/">the libxslt page</a> providing an
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000109 implementation of XSLT 1.0 and common extensions like EXSLT for
110 libxml2</li>
Daniel Veillardc6271d22001-10-27 07:50:58 +0000111 <li><a href="http://www.cs.unibo.it/~casarini/gdome2/">the gdome2 page</a>
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000112 : a standard DOM2 implementation for libxml2</li>
113 <li><a href="http://www.aleksey.com/xmlsec/">the XMLSec page</a>: an
114 implementation of <a href="http://www.w3.org/TR/xmldsig-core/">W3C XML
115 Digital Signature</a> for libxml2</li>
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000116 <li>also check the related links section below for more related and active
117 projects.</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000118</ul>
Daniel Veillard252004d2004-03-23 12:32:32 +0000119<!----------------<p>Results of the <a
Daniel Veillard806cada2003-03-19 21:58:59 +0000120href="http://xmlbench.sourceforge.net/results/benchmark/index.html">xmlbench
Daniel Veillard31ae4622004-02-16 07:45:44 +0000121benchmark</a> on sourceforge February 2004 (smaller is better):</p>
Daniel Veillardd8da01c2003-03-24 15:58:23 +0000122
Daniel Veillard31ae4622004-02-16 07:45:44 +0000123<p align="center"><img src="benchmark.png"
Daniel Veillardd8da01c2003-03-24 15:58:23 +0000124alt="benchmark results for Expat Xerces libxml2 Oracle and Sun toolkits"></p>
Daniel Veillardcf80b782004-03-07 19:32:19 +0000125-------------->
Daniel Veillard806cada2003-03-19 21:58:59 +0000126
Daniel Veillarde1662542002-08-28 11:50:59 +0000127<p>Logo designed by <a href="mailto:liyanage@access.ch">Marc Liyanage</a>.</p>
128
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000129<h2><a name="Introducti">Introduction</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000130
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000131<p>This document describes libxml, the <a
Daniel Veillard560c2a42003-07-06 21:13:49 +0000132href="http://www.w3.org/XML/">XML</a> C parser and toolkit developed for the
133<a href="http://www.gnome.org/">Gnome</a> project. <a
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000134href="http://www.w3.org/XML/">XML is a standard</a> for building tag-based
135structured documents/data.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000136
Daniel Veillard0142b842000-01-14 14:45:24 +0000137<p>Here are some key points about libxml:</p>
138<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +0000139 <li>Libxml2 exports Push (progressive) and Pull (blocking) type parser
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000140 interfaces for both XML and HTML.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000141 <li>Libxml2 can do DTD validation at parse time, using a parsed document
Daniel Veillard91e9d582001-02-26 07:31:12 +0000142 instance, or with an arbitrary DTD.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000143 <li>Libxml2 includes complete <a
Daniel Veillard8c2ecaf2001-07-10 17:53:07 +0000144 href="http://www.w3.org/TR/xpath">XPath</a>, <a
145 href="http://www.w3.org/TR/xptr">XPointer</a> and <a
146 href="http://www.w3.org/TR/xinclude">XInclude</a> implementations.</li>
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000147 <li>It is written in plain C, making as few assumptions as possible, and
Daniel Veillard189446d2000-10-13 10:23:06 +0000148 sticking closely to ANSI C/POSIX for easy embedding. Works on
Daniel Veillardab8500d2000-10-15 21:06:19 +0000149 Linux/Unix/Windows, ported to a number of other platforms.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000150 <li>Basic support for HTTP and FTP client allowing applications to fetch
Daniel Veillard0b28e882002-07-24 23:47:05 +0000151 remote resources.</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000152 <li>The design is modular, most of the extensions can be compiled out.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000153 <li>The internal document representation is as close as possible to the <a
Daniel Veillard0142b842000-01-14 14:45:24 +0000154 href="http://www.w3.org/DOM/">DOM</a> interfaces.</li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000155 <li>Libxml2 also has a <a
156 href="http://www.megginson.com/SAX/index.html">SAX like interface</a>;
157 the interface is designed to be compatible with <a
Daniel Veillard402e8c82000-02-29 22:57:47 +0000158 href="http://www.jclark.com/xml/expat.html">Expat</a>.</li>
Daniel Veillardc575b992002-02-08 13:28:40 +0000159 <li>This library is released under the <a
160 href="http://www.opensource.org/licenses/mit-license.html">MIT
Daniel Veillard0b28e882002-07-24 23:47:05 +0000161 License</a>. See the Copyright file in the distribution for the precise
Daniel Veillardc575b992002-02-08 13:28:40 +0000162 wording.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000163</ul>
Daniel Veillardccb09631998-10-27 06:21:04 +0000164
Daniel Veillarde0c1d722001-03-21 10:28:36 +0000165<p>Warning: unless you are forced to because your application links with a
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000166Gnome-1.X library requiring it, <strong><span
Daniel Veillarde0c1d722001-03-21 10:28:36 +0000167style="background-color: #FF0000">Do Not Use libxml1</span></strong>, use
168libxml2</p>
169
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000170<h2><a name="FAQ">FAQ</a></h2>
171
Daniel Veillard0b28e882002-07-24 23:47:05 +0000172<p>Table of Contents:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000173<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +0000174 <li><a href="FAQ.html#License">License(s)</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000175 <li><a href="FAQ.html#Installati">Installation</a></li>
176 <li><a href="FAQ.html#Compilatio">Compilation</a></li>
177 <li><a href="FAQ.html#Developer">Developer corner</a></li>
178</ul>
179
Daniel Veillard63d83142002-05-20 06:51:05 +0000180<h3><a name="License">License</a>(s)</h3>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000181<ol>
182 <li><em>Licensing Terms for libxml</em>
Daniel Veillard8a469172003-06-12 16:05:07 +0000183 <p>libxml2 is released under the <a
Daniel Veillardc575b992002-02-08 13:28:40 +0000184 href="http://www.opensource.org/licenses/mit-license.html">MIT
Daniel Veillard0b28e882002-07-24 23:47:05 +0000185 License</a>; see the file Copyright in the distribution for the precise
Daniel Veillardc575b992002-02-08 13:28:40 +0000186 wording</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000187 </li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000188 <li><em>Can I embed libxml2 in a proprietary application ?</em>
Daniel Veillard42766c02002-08-22 20:52:17 +0000189 <p>Yes. The MIT License allows you to keep proprietary the changes you
190 made to libxml, but it would be graceful to send-back bug fixes and
191 improvements as patches for possible incorporation in the main
Daniel Veillard0b28e882002-07-24 23:47:05 +0000192 development tree.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000193 </li>
194</ol>
195
196<h3><a name="Installati">Installation</a></h3>
197<ol>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000198 <li><strong><span style="background-color: #FF0000">Do Not Use
199 libxml1</span></strong>, use libxml2</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000200 <li><em>Where can I get libxml</em> ?
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000201 <p>The original distribution comes from <a
202 href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> or <a
Daniel Veillard024f1992003-12-10 16:43:49 +0000203 href="ftp://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/">gnome.org</a></p>
Daniel Veillard63d83142002-05-20 06:51:05 +0000204 <p>Most Linux and BSD distributions include libxml, this is probably the
Daniel Veillard0b28e882002-07-24 23:47:05 +0000205 safer way for end-users to use libxml.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000206 <p>David Doolin provides precompiled Windows versions at <a
207 href="http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/ ">http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/</a></p>
208 </li>
209 <li><em>I see libxml and libxml2 releases, which one should I install ?</em>
210 <ul>
Daniel Veillard42766c02002-08-22 20:52:17 +0000211 <li>If you are not constrained by backward compatibility issues with
212 existing applications, install libxml2 only</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000213 <li>If you are not doing development, you can safely install both.
Daniel Veillard0b28e882002-07-24 23:47:05 +0000214 Usually the packages <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000215 href="http://rpmfind.net/linux/RPM/libxml.html">libxml</a> and <a
216 href="http://rpmfind.net/linux/RPM/libxml2.html">libxml2</a> are
Daniel Veillard0b28e882002-07-24 23:47:05 +0000217 compatible (this is not the case for development packages).</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000218 <li>If you are a developer and your system provides separate packaging
219 for shared libraries and the development components, it is possible
220 to install libxml and libxml2, and also <a
221 href="http://rpmfind.net/linux/RPM/libxml-devel.html">libxml-devel</a>
222 and <a
223 href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml2-devel</a>
224 too for libxml2 &gt;= 2.3.0</li>
225 <li>If you are developing a new application, please develop against
226 libxml2(-devel)</li>
227 </ul>
228 </li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000229 <li><em>I can't install the libxml package, it conflicts with libxml0</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000230 <p>You probably have an old libxml0 package used to provide the shared
Daniel Veillard42766c02002-08-22 20:52:17 +0000231 library for libxml.so.0, you can probably safely remove it. The libxml
232 packages provided on <a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000233 href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> provide
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000234 libxml.so.0</p>
235 </li>
236 <li><em>I can't install the libxml(2) RPM package due to failed
Daniel Veillard63d83142002-05-20 06:51:05 +0000237 dependencies</em>
238 <p>The most generic solution is to re-fetch the latest src.rpm , and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000239 rebuild it locally with</p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000240 <p><code>rpm --rebuild libxml(2)-xxx.src.rpm</code>.</p>
Daniel Veillard42766c02002-08-22 20:52:17 +0000241 <p>If everything goes well it will generate two binary rpm packages (one
242 providing the shared libs and xmllint, and the other one, the -devel
243 package, providing includes, static libraries and scripts needed to build
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000244 applications with libxml(2)) that you can install locally.</p>
245 </li>
246</ol>
247
248<h3><a name="Compilatio">Compilation</a></h3>
249<ol>
Daniel Veillard8a469172003-06-12 16:05:07 +0000250 <li><em>What is the process to compile libxml2 ?</em>
251 <p>As most UNIX libraries libxml2 follows the "standard":</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000252 <p><code>gunzip -c xxx.tar.gz | tar xvf -</code></p>
253 <p><code>cd libxml-xxxx</code></p>
254 <p><code>./configure --help</code></p>
255 <p>to see the options, then the compilation/installation proper</p>
256 <p><code>./configure [possible options]</code></p>
257 <p><code>make</code></p>
258 <p><code>make install</code></p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000259 <p>At that point you may have to rerun ldconfig or a similar utility to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000260 update your list of installed shared libs.</p>
261 </li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000262 <li><em>What other libraries are needed to compile/install libxml2 ?</em>
263 <p>Libxml2 does not require any other library, the normal C ANSI API
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000264 should be sufficient (please report any violation to this rule you may
265 find).</p>
Daniel Veillard8a469172003-06-12 16:05:07 +0000266 <p>However if found at configuration time libxml2 will detect and use the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000267 following libs:</p>
268 <ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000269 <li><a href="http://www.info-zip.org/pub/infozip/zlib/">libz</a> : a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000270 highly portable and available widely compression library.</li>
271 <li>iconv: a powerful character encoding conversion library. It is
272 included by default in recent glibc libraries, so it doesn't need to
273 be installed specifically on Linux. It now seems a <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000274 href="http://www.opennc.org/onlinepubs/7908799/xsh/iconv.html">part
275 of the official UNIX</a> specification. Here is one <a
Daniel Veillarddad3f682002-11-17 16:47:27 +0000276 href="http://www.gnu.org/software/libiconv/">implementation of the
277 library</a> which source can be found <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000278 href="ftp://ftp.ilog.fr/pub/Users/haible/gnu/">here</a>.</li>
279 </ul>
280 </li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000281 <li><em>Make check fails on some platforms</em>
Daniel Veillard42766c02002-08-22 20:52:17 +0000282 <p>Sometimes the regression tests' results don't completely match the
283 value produced by the parser, and the makefile uses diff to print the
284 delta. On some platforms the diff return breaks the compilation process;
285 if the diff is small this is probably not a serious problem.</p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000286 <p>Sometimes (especially on Solaris) make checks fail due to limitations
Daniel Veillarde46182c2002-02-12 14:29:11 +0000287 in make. Try using GNU-make instead.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000288 </li>
289 <li><em>I use the CVS version and there is no configure script</em>
Daniel Veillard42766c02002-08-22 20:52:17 +0000290 <p>The configure script (and other Makefiles) are generated. Use the
291 autogen.sh script to regenerate the configure script and Makefiles,
292 like:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000293 <p><code>./autogen.sh --prefix=/usr --disable-shared</code></p>
294 </li>
295 <li><em>I have troubles when running make tests with gcc-3.0</em>
296 <p>It seems the initial release of gcc-3.0 has a problem with the
297 optimizer which miscompiles the URI module. Please use another
Daniel Veillard0b28e882002-07-24 23:47:05 +0000298 compiler.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000299 </li>
300</ol>
301
302<h3><a name="Developer">Developer</a> corner</h3>
303<ol>
Daniel Veillard93d95252003-04-29 20:25:40 +0000304 <li><em>Troubles compiling or linking programs using libxml2</em>
305 <p>Usually the problem comes from the fact that the compiler doesn't get
306 the right compilation or linking flags. There is a small shell script
307 <code>xml2-config</code> which is installed as part of libxml2 usual
Daniel Veillard560c2a42003-07-06 21:13:49 +0000308 install process which provides those flags. Use</p>
Daniel Veillard93d95252003-04-29 20:25:40 +0000309 <p><code>xml2-config --cflags</code></p>
310 <p>to get the compilation flags and</p>
311 <p><code>xml2-config --libs</code></p>
312 <p>to get the linker flags. Usually this is done directly from the
313 Makefile as:</p>
314 <p><code>CFLAGS=`xml2-config --cflags`</code></p>
315 <p><code>LIBS=`xml2-config --libs`</code></p>
316 </li>
Daniel Veillard67952602006-01-05 15:29:44 +0000317 <li><em>I want to install my own copy of libxml2 in my home directory and
318 link my programs against it, but it doesn't work</em>
William M. Brack99906ad2005-01-09 17:02:42 +0000319 <p>There are many different ways to accomplish this. Here is one way to
Daniel Veillard67952602006-01-05 15:29:44 +0000320 do this under Linux. Suppose your home directory is <code>/home/user.
321 </code>Then:</p>
322 <ul>
323 <li>Create a subdirectory, let's call it <code>myxml</code></li>
William M. Brack99906ad2005-01-09 17:02:42 +0000324 <li>unpack the libxml2 distribution into that subdirectory</li>
Daniel Veillard67952602006-01-05 15:29:44 +0000325 <li>chdir into the unpacked distribution
326 (<code>/home/user/myxml/libxml2 </code>)</li>
William M. Brack99906ad2005-01-09 17:02:42 +0000327 <li>configure the library using the "<code>--prefix</code>" switch,
Daniel Veillard67952602006-01-05 15:29:44 +0000328 specifying an installation subdirectory in
329 <code>/home/user/myxml</code>, e.g.
330 <p><code>./configure --prefix /home/user/myxml/xmlinst</code> {other
331 configuration options}</p>
332 </li>
William M. Brack99906ad2005-01-09 17:02:42 +0000333 <li>now run <code>make</code> followed by <code>make install</code></li>
334 <li>At this point, the installation subdirectory contains the complete
Daniel Veillard67952602006-01-05 15:29:44 +0000335 "private" include files, library files and binary program files (e.g.
336 xmllint), located in
337 <p><code>/home/user/myxml/xmlinst/lib,
338 /home/user/myxml/xmlinst/include </code> and <code>
339 /home/user/myxml/xmlinst/bin</code></p>
340 respectively.</li>
341 <li>In order to use this "private" library, you should first add it to
342 the beginning of your default PATH (so that your own private program
343 files such as xmllint will be used instead of the normal system
344 ones). To do this, the Bash command would be
345 <p><code>export PATH=/home/user/myxml/xmlinst/bin:$PATH</code></p>
346 </li>
William M. Brack99906ad2005-01-09 17:02:42 +0000347 <li>Now suppose you have a program <code>test1.c</code> that you would
Daniel Veillard67952602006-01-05 15:29:44 +0000348 like to compile with your "private" library. Simply compile it using
349 the command
350 <p><code>gcc `xml2-config --cflags --libs` -o test test.c</code></p>
351 Note that, because your PATH has been set with <code>
352 /home/user/myxml/xmlinst/bin</code> at the beginning, the xml2-config
353 program which you just installed will be used instead of the system
354 default one, and this will <em>automatically</em> get the correct
355 libraries linked with your program.</li>
356 </ul>
357 </li>
358
359 <p></p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000360 <li><em>xmlDocDump() generates output on one line.</em>
Daniel Veillard8a469172003-06-12 16:05:07 +0000361 <p>Libxml2 will not <strong>invent</strong> spaces in the content of a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000362 document since <strong>all spaces in the content of a document are
363 significant</strong>. If you build a tree from the API and want
364 indentation:</p>
365 <ol>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000366 <li>the correct way is to generate those yourself too.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000367 <li>the dangerous way is to ask libxml2 to add those blanks to your
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000368 content <strong>modifying the content of your document in the
369 process</strong>. The result may not be what you expect. There is
370 <strong>NO</strong> way to guarantee that such a modification won't
Daniel Veillard0b28e882002-07-24 23:47:05 +0000371 affect other parts of the content of your document. See <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000372 href="http://xmlsoft.org/html/libxml-parser.html#xmlKeepBlanksDefault">xmlKeepBlanksDefault
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000373 ()</a> and <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000374 href="http://xmlsoft.org/html/libxml-tree.html#xmlSaveFormatFile">xmlSaveFormatFile
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000375 ()</a></li>
376 </ol>
377 </li>
378 <li>Extra nodes in the document:
379 <p><em>For a XML file as below:</em></p>
380 <pre>&lt;?xml version="1.0"?&gt;
381&lt;PLAN xmlns="http://www.argus.ca/autotest/1.0/"&gt;
382&lt;NODE CommFlag="0"/&gt;
383&lt;NODE CommFlag="1"/&gt;
384&lt;/PLAN&gt;</pre>
385 <p><em>after parsing it with the function
386 pxmlDoc=xmlParseFile(...);</em></p>
387 <p><em>I want to the get the content of the first node (node with the
388 CommFlag="0")</em></p>
389 <p><em>so I did it as following;</em></p>
Daniel Veillard63d83142002-05-20 06:51:05 +0000390 <pre>xmlNodePtr pnode;
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000391pnode=pxmlDoc-&gt;children-&gt;children;</pre>
392 <p><em>but it does not work. If I change it to</em></p>
393 <pre>pnode=pxmlDoc-&gt;children-&gt;children-&gt;next;</pre>
394 <p><em>then it works. Can someone explain it to me.</em></p>
395 <p></p>
396 <p>In XML all characters in the content of the document are significant
397 <strong>including blanks and formatting line breaks</strong>.</p>
398 <p>The extra nodes you are wondering about are just that, text nodes with
Daniel Veillard63d83142002-05-20 06:51:05 +0000399 the formatting spaces which are part of the document but that people tend
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000400 to forget. There is a function <a
401 href="http://xmlsoft.org/html/libxml-parser.html">xmlKeepBlanksDefault
402 ()</a> to remove those at parse time, but that's an heuristic, and its
Daniel Veillard0b28e882002-07-24 23:47:05 +0000403 use should be limited to cases where you are certain there is no
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000404 mixed-content in the document.</p>
405 </li>
406 <li><em>I get compilation errors of existing code like when accessing
Daniel Veillard0b28e882002-07-24 23:47:05 +0000407 <strong>root</strong> or <strong>child fields</strong> of nodes.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000408 <p>You are compiling code developed for libxml version 1 and using a
409 libxml2 development environment. Either switch back to libxml v1 devel or
410 even better fix the code to compile with libxml2 (or both) by <a
411 href="upgrade.html">following the instructions</a>.</p>
412 </li>
413 <li><em>I get compilation errors about non existing
414 <strong>xmlRootNode</strong> or <strong>xmlChildrenNode</strong>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000415 fields.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000416 <p>The source code you are using has been <a
417 href="upgrade.html">upgraded</a> to be able to compile with both libxml
418 and libxml2, but you need to install a more recent version:
419 libxml(-devel) &gt;= 1.8.8 or libxml2(-devel) &gt;= 2.1.0</p>
420 </li>
421 <li><em>XPath implementation looks seriously broken</em>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000422 <p>XPath implementation prior to 2.3.0 was really incomplete. Upgrade to
423 a recent version, there are no known bugs in the current version.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000424 </li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000425 <li><em>The example provided in the web page does not compile.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000426 <p>It's hard to maintain the documentation in sync with the code
427 &lt;grin/&gt; ...</p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000428 <p>Check the previous points 1/ and 2/ raised before, and please send
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000429 patches.</p>
430 </li>
Daniel Veillard8d7b5c72003-11-15 18:24:36 +0000431 <li><em>Where can I get more examples and information than provided on the
Daniel Veillard42766c02002-08-22 20:52:17 +0000432 web page?</em>
Daniel Veillard8a469172003-06-12 16:05:07 +0000433 <p>Ideally a libxml2 book would be nice. I have no such plan ... But you
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000434 can:</p>
435 <ul>
436 <li>check more deeply the <a href="html/libxml-lib.html">existing
437 generated doc</a></li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000438 <li>have a look at <a href="examples/index.html">the set of
439 examples</a>.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000440 <li>look for examples of use for libxml2 function using the Gnome code.
Daniel Veillard0b28e882002-07-24 23:47:05 +0000441 For example the following will query the full Gnome CVS base for the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000442 use of the <strong>xmlAddChild()</strong> function:
443 <p><a
444 href="http://cvs.gnome.org/lxr/search?string=xmlAddChild">http://cvs.gnome.org/lxr/search?string=xmlAddChild</a></p>
445 <p>This may be slow, a large hardware donation to the gnome project
446 could cure this :-)</p>
447 </li>
448 <li><a
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000449 href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gnome-xml">Browse
450 the libxml2 source</a> , I try to write code as clean and documented
Daniel Veillard42766c02002-08-22 20:52:17 +0000451 as possible, so looking at it may be helpful. In particular the code
452 of xmllint.c and of the various testXXX.c test programs should
453 provide good examples of how to do things with the library.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000454 </ul>
455 </li>
456 <li>What about C++ ?
Daniel Veillard8a469172003-06-12 16:05:07 +0000457 <p>libxml2 is written in pure C in order to allow easy reuse on a number
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000458 of platforms, including embedded systems. I don't intend to convert to
459 C++.</p>
Daniel Veillard91e69c52003-08-04 01:43:07 +0000460 <p>There is however a C++ wrapper which may fulfill your needs:</p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000461 <ul>
462 <li>by Ari Johnson &lt;ari@btigate.com&gt;:
463 <p>Website: <a
Daniel Veillard91e69c52003-08-04 01:43:07 +0000464 href="http://libxmlplusplus.sourceforge.net/">http://libxmlplusplus.sourceforge.net/</a></p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000465 <p>Download: <a
Daniel Veillard91e69c52003-08-04 01:43:07 +0000466 href="http://sourceforge.net/project/showfiles.php?group_id=12999">http://sourceforge.net/project/showfiles.php?group_id=12999</a></p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000467 </li>
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000468 <!-- Website is currently unavailable as of 2003-08-02
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000469 <li>by Peter Jones &lt;pjones@pmade.org&gt;
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000470 <p>Website: <a
471 href="http://pmade.org/pjones/software/xmlwrapp/">http://pmade.org/pjones/software/xmlwrapp/</a></p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000472 </li>
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000473 -->
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000474 </ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000475 </li>
476 <li>How to validate a document a posteriori ?
477 <p>It is possible to validate documents which had not been validated at
Daniel Veillard42766c02002-08-22 20:52:17 +0000478 initial parsing time or documents which have been built from scratch
479 using the API. Use the <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000480 href="http://xmlsoft.org/html/libxml-valid.html#xmlValidateDtd">xmlValidateDtd()</a>
Daniel Veillard63d83142002-05-20 06:51:05 +0000481 function. It is also possible to simply add a DTD to an existing
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000482 document:</p>
483 <pre>xmlDocPtr doc; /* your existing document */
Daniel Veillard0b28e882002-07-24 23:47:05 +0000484xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
485
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000486 dtd-&gt;name = xmlStrDup((xmlChar*)"root_name"); /* use the given root */
487
488 doc-&gt;intSubset = dtd;
489 if (doc-&gt;children == NULL) xmlAddChild((xmlNodePtr)doc, (xmlNodePtr)dtd);
490 else xmlAddPrevSibling(doc-&gt;children, (xmlNodePtr)dtd);
491 </pre>
492 </li>
Daniel Veillarddad3f682002-11-17 16:47:27 +0000493 <li>So what is this funky "xmlChar" used all the time?
494 <p>It is a null terminated sequence of utf-8 characters. And only utf-8!
495 You need to convert strings encoded in different ways to utf-8 before
496 passing them to the API. This can be accomplished with the iconv library
497 for instance.</p>
John Fleck61f6fb62002-10-31 15:23:29 +0000498 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000499 <li>etc ...</li>
500</ol>
501
502<p></p>
503
Daniel Veillard66f68e72003-08-18 16:39:51 +0000504<h2><a name="Documentat">Developer Menu</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000505
Daniel Veillard0b28e882002-07-24 23:47:05 +0000506<p>There are several on-line resources related to using libxml:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000507<ol>
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000508 <li>Use the <a href="search.php">search engine</a> to look up
509 information.</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000510 <li>Check the <a href="FAQ.html">FAQ.</a></li>
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000511 <li>Check the <a href="http://xmlsoft.org/html/libxml-lib.html">extensive
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000512 documentation</a> automatically extracted from code comments.</li>
Daniel Veillard8d869642000-07-14 12:12:59 +0000513 <li>Look at the documentation about <a href="encoding.html">libxml
Daniel Veillard0b28e882002-07-24 23:47:05 +0000514 internationalization support</a>.</li>
Daniel Veillardbc66f852002-01-14 09:49:20 +0000515 <li>This page provides a global overview and <a href="example.html">some
Daniel Veillard402e8c82000-02-29 22:57:47 +0000516 examples</a> on how to use libxml.</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000517 <li><a href="examples/index.html">Code examples</a></li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000518 <li>John Fleck's libxml2 tutorial: <a href="tutorial/index.html">html</a>
519 or <a href="tutorial/xmltutorial.pdf">pdf</a>.</li>
Daniel Veillard1177ca42003-04-26 22:29:54 +0000520 <li>If you need to parse large files, check the <a
521 href="xmlreader.html">xmlReader</a> API tutorial</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000522 <li><a href="mailto:james@daa.com.au">James Henstridge</a> wrote <a
Daniel Veillard402e8c82000-02-29 22:57:47 +0000523 href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">some nice
524 documentation</a> explaining how to use the libxml SAX interface.</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000525 <li>George Lebl wrote <a
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000526 href="http://www-106.ibm.com/developerworks/library/l-gnome3/">an article
Daniel Veillard402e8c82000-02-29 22:57:47 +0000527 for IBM developerWorks</a> about using libxml.</li>
Daniel Veillardec303412000-03-24 13:41:54 +0000528 <li>Check <a href="http://cvs.gnome.org/lxr/source/gnome-xml/TODO">the TODO
Daniel Veillard0b28e882002-07-24 23:47:05 +0000529 file</a>.</li>
Daniel Veillard42766c02002-08-22 20:52:17 +0000530 <li>Read the <a href="upgrade.html">1.x to 2.x upgrade path</a>
531 description. If you are starting a new project using libxml you should
532 really use the 2.x version.</li>
Daniel Veillard845cce42002-01-09 11:51:37 +0000533 <li>And don't forget to look at the <a
534 href="http://mail.gnome.org/archives/xml/">mailing-list archive</a>.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000535</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000536
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000537<h2><a name="Reporting">Reporting bugs and getting help</a></h2>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000538
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000539<p>Well, bugs or missing features are always possible, and I will make a
540point of fixing them in a timely fashion. The best way to report a bug is to
Daniel Veillardccf996f2003-08-14 10:48:38 +0000541use the <a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome
Daniel Veillard42766c02002-08-22 20:52:17 +0000542bug tracking database</a> (make sure to use the "libxml2" module name). I
543look at reports there regularly and it's good to have a reminder when a bug
544is still open. Be sure to specify that the bug is for the package libxml2.</p>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000545
Daniel Veillard4ac494b2003-09-18 15:08:00 +0000546<p>For small problems you can try to get help on IRC, the #xml channel on
547irc.gnome.org (port 6667) usually have a few person subscribed which may help
548(but there is no garantee and if a real issue is raised it should go on the
549mailing-list for archival).</p>
Daniel Veillard9582d6c2003-09-16 11:40:04 +0000550
Daniel Veillard0142b842000-01-14 14:45:24 +0000551<p>There is also a mailing-list <a
Daniel Veillard3197f162001-04-04 00:40:08 +0000552href="mailto:xml@gnome.org">xml@gnome.org</a> for libxml, with an <a
553href="http://mail.gnome.org/archives/xml/">on-line archive</a> (<a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000554href="http://xmlsoft.org/messages">old</a>). To subscribe to this list,
555please visit the <a
556href="http://mail.gnome.org/mailman/listinfo/xml">associated Web</a> page and
557follow the instructions. <strong>Do not send code, I won't debug it</strong>
558(but patches are really appreciated!).</p>
Daniel Veillardd99224d2004-04-06 10:04:16 +0000559
560<p>Please note that with the current amount of virus and SPAM, sending mail
561to the list without being subscribed won't work. There is *far too many
562bounces* (in the order of a thousand a day !) I cannot approve them manually
563anymore. If your mail to the list bounced waiting for administrator approval,
564it is LOST ! Repost it and fix the problem triggering the error.</p>
Daniel Veillard234547b2001-07-05 09:46:10 +0000565
Daniel Veillard008186f2001-09-13 14:24:44 +0000566<p>Check the following <strong><span style="color: #FF0000">before
567posting</span></strong>:</p>
Daniel Veillard234547b2001-07-05 09:46:10 +0000568<ul>
Daniel Veillard321be0c2002-10-08 21:26:42 +0000569 <li>Read the <a href="FAQ.html">FAQ</a> and <a href="search.php">use the
Daniel Veillarda37aab82003-06-09 09:10:36 +0000570 search engine</a> to get information related to your problem.</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000571 <li>Make sure you are <a href="ftp://xmlsoft.org/">using a recent
572 version</a>, and that the problem still shows up in a recent version.</li>
573 <li>Check the <a href="http://mail.gnome.org/archives/xml/">list
574 archives</a> to see if the problem was reported already. In this case
Daniel Veillard63d83142002-05-20 06:51:05 +0000575 there is probably a fix available, similarly check the <a
Daniel Veillardccf996f2003-08-14 10:48:38 +0000576 href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">registered
Daniel Veillard0b28e882002-07-24 23:47:05 +0000577 open bugs</a>.</li>
578 <li>Make sure you can reproduce the bug with xmllint or one of the test
579 programs found in source in the distribution.</li>
Daniel Veillard234547b2001-07-05 09:46:10 +0000580 <li>Please send the command showing the error as well as the input (as an
Daniel Veillard63d83142002-05-20 06:51:05 +0000581 attachment)</li>
Daniel Veillard234547b2001-07-05 09:46:10 +0000582</ul>
Daniel Veillard0142b842000-01-14 14:45:24 +0000583
Daniel Veillarda37aab82003-06-09 09:10:36 +0000584<p>Then send the bug with associated information to reproduce it to the <a
Daniel Veillard33a67802001-03-07 09:44:02 +0000585href="mailto:xml@gnome.org">xml@gnome.org</a> list; if it's really libxml
Daniel Veillard98d071d2003-01-10 09:22:44 +0000586related I will approve it. Please do not send mail to me directly, it makes
Daniel Veillard0b28e882002-07-24 23:47:05 +0000587things really hard to track and in some cases I am not the best person to
Daniel Veillard98d071d2003-01-10 09:22:44 +0000588answer a given question, ask on the list.</p>
589
590<p>To <span style="color: #E50000">be really clear about support</span>:</p>
591<ul>
Daniel Veillarda37aab82003-06-09 09:10:36 +0000592 <li>Support or help <span style="color: #E50000">requests MUST be sent to
Daniel Veillard98d071d2003-01-10 09:22:44 +0000593 the list or on bugzilla</span> in case of problems, so that the Question
594 and Answers can be shared publicly. Failing to do so carries the implicit
595 message "I want free support but I don't want to share the benefits with
Daniel Veillard831e8fd2003-01-25 11:45:34 +0000596 others" and is not welcome. I will automatically Carbon-Copy the
597 xml@gnome.org mailing list for any technical reply made about libxml2 or
598 libxslt.</li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000599 <li>There is <span style="color: #E50000">no garantee of support</span>, if
600 your question remains unanswered after a week, repost it, making sure you
601 gave all the detail needed and the information requested.</li>
Daniel Veillarda37aab82003-06-09 09:10:36 +0000602 <li>Failing to provide information as requested or double checking first
Daniel Veillard98d071d2003-01-10 09:22:44 +0000603 for prior feedback also carries the implicit message "the time of the
604 library maintainers is less valuable than my time" and might not be
605 welcome.</li>
606</ul>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000607
Daniel Veillard91e9d582001-02-26 07:31:12 +0000608<p>Of course, bugs reported with a suggested patch for fixing them will
Daniel Veillard0b28e882002-07-24 23:47:05 +0000609probably be processed faster than those without.</p>
Daniel Veillardec303412000-03-24 13:41:54 +0000610
611<p>If you're looking for help, a quick look at <a
Daniel Veillardf7ed3362001-08-17 12:01:21 +0000612href="http://mail.gnome.org/archives/xml/">the list archive</a> may actually
Daniel Veillard560c2a42003-07-06 21:13:49 +0000613provide the answer. I usually send source samples when answering libxml2
614usage questions. The <a
615href="http://xmlsoft.org/html/book1.html">auto-generated documentation</a> is
616not as polished as I would like (i need to learn more about DocBook), but
617it's a good starting point.</p>
Daniel Veillardec303412000-03-24 13:41:54 +0000618
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000619<h2><a name="help">How to help</a></h2>
620
621<p>You can help the project in various ways, the best thing to do first is to
622subscribe to the mailing-list as explained before, check the <a
Daniel Veillardf7ed3362001-08-17 12:01:21 +0000623href="http://mail.gnome.org/archives/xml/">archives </a>and the <a
Daniel Veillardccf996f2003-08-14 10:48:38 +0000624href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome bug
Daniel Veillard0b28e882002-07-24 23:47:05 +0000625database</a>:</p>
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000626<ol>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000627 <li>Provide patches when you find problems.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000628 <li>Provide the diffs when you port libxml2 to a new platform. They may not
Daniel Veillardab8500d2000-10-15 21:06:19 +0000629 be integrated in all cases but help pinpointing portability problems
630 and</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000631 <li>Provide documentation fixes (either as patches to the code comments or
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000632 as HTML diffs).</li>
Daniel Veillard42766c02002-08-22 20:52:17 +0000633 <li>Provide new documentations pieces (translations, examples, etc
634 ...).</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000635 <li>Check the TODO file and try to close one of the items.</li>
636 <li>Take one of the points raised in the archive or the bug database and
Daniel Veillarde7ead2d2001-08-22 23:44:09 +0000637 provide a fix. <a href="mailto:daniel@veillard.com">Get in touch with me
638 </a>before to avoid synchronization problems and check that the suggested
639 fix will fit in nicely :-)</li>
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000640</ol>
641
Daniel Veillard10a2c651999-12-12 13:03:50 +0000642<h2><a name="Downloads">Downloads</a></h2>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000643
Daniel Veillard688f6692004-03-26 10:57:38 +0000644<p>The latest versions of libxml2 can be found on the <a
Daniel Veillardeca726d2004-04-18 21:47:34 +0000645href="ftp://xmlsoft.org/">xmlsoft.org</a> server ( <a
646href="http://xmlsoft.org/sources/">HTTP</a>, <a
647href="ftp://xmlsoft.org/">FTP</a> and rsync are available), there is also
Daniel Veillard210818b2004-09-29 15:50:37 +0000648mirrors (<a href="ftp://ftp.planetmirror.com/pub/xmlsoft/">Australia</a>( <a
649href="http://xmlsoft.planetmirror.com/">Web</a>), <a
Daniel Veillard20c8cf22001-06-26 22:47:36 +0000650href="ftp://fr.rpmfind.net/pub/libxml/">France</a>) or on the <a
Daniel Veillardd99224d2004-04-06 10:04:16 +0000651href="ftp://ftp.gnome.org/pub/GNOME/MIRRORS.html">Gnome FTP server</a> as <a
652href="ftp://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/">source archive</a>
Daniel Veillard688f6692004-03-26 10:57:38 +0000653, Antonin Sprinzl also provide <a href="ftp://gd.tuwien.ac.at/pub/libxml/">a
Daniel Veillarde16b5742002-09-26 17:50:03 +0000654mirror in Austria</a>. (NOTE that you need both the <a
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000655href="http://rpmfind.net/linux/RPM/libxml2.html">libxml(2)</a> and <a
656href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml(2)-devel</a>
Daniel Veillardb46a5732003-04-08 13:35:48 +0000657packages installed to compile applications using libxml.)</p>
Daniel Veillardeca726d2004-04-18 21:47:34 +0000658
659<p>You can find all the history of libxml(2) and libxslt releases in the <a
Daniel Veillardd4cfcef2004-05-06 18:55:27 +0000660href="http://xmlsoft.org/sources/old/">old</a> directory. The precompiled
Daniel Veillardf81a8e82004-08-03 21:58:41 +0000661Windows binaries made by Igor Zlatovic are available in the <a
662href="http://xmlsoft.org/sources/win32/">win32</a> directory.</p>
Daniel Veillardb46a5732003-04-08 13:35:48 +0000663
664<p>Binary ports:</p>
665<ul>
666 <li>Red Hat RPMs for i386 are available directly on <a
667 href="ftp://xmlsoft.org/">xmlsoft.org</a>, the source RPM will compile on
668 any architecture supported by Red Hat.</li>
Daniel Veillardb331fff2004-08-22 14:21:57 +0000669 <li><a href="mailto:igor@zlatkovic.com">Igor Zlatkovic</a> is now the
670 maintainer of the Windows port, <a
Daniel Veillardb46a5732003-04-08 13:35:48 +0000671 href="http://www.zlatkovic.com/projects/libxml/index.html">he provides
Daniel Veillardb11f5b92004-08-03 22:09:36 +0000672 binaries</a>.</li>
Daniel Veillard67952602006-01-05 15:29:44 +0000673 <li>Blastwave provides <a
674 href="http://www.blastwave.org/packages.php/libxml2">Solaris
675 binaries</a>.</li>
Daniel Veillardd49370e2005-04-11 23:28:16 +0000676 <li><a href="mailto:Steve.Ball@explain.com.au">Steve Ball</a> provides <a
677 href="http://www.explain.com.au/oss/libxml2xslt.html">Mac Os X
Daniel Veillardb46a5732003-04-08 13:35:48 +0000678 binaries</a>.</li>
679 <li>The HP-UX porting center provides <a
680 href="http://hpux.connect.org.uk/hppd/hpux/Gnome/">HP-UX binaries</a></li>
Daniel Veillard67952602006-01-05 15:29:44 +0000681 <li>Bull provides precompiled <a
682 href="http://gnome.bullfreeware.com/new_index.html">RPMs for AIX</a> as
683 patr of their GNOME packages</li>
Daniel Veillardb46a5732003-04-08 13:35:48 +0000684</ul>
685
686<p>If you know other supported binary ports, please <a
687href="http://veillard.com/">contact me</a>.</p>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000688
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000689<p><a name="Snapshot">Snapshot:</a></p>
690<ul>
Daniel Veillard3cef1192004-08-18 09:30:31 +0000691 <li>Code from the W3C cvs base libxml2 module, updated hourly <a
Daniel Veillardfc263f12004-08-31 07:02:04 +0000692 href="ftp://xmlsoft.org/libxml2-cvs-snapshot.tar.gz">libxml2-cvs-snapshot.tar.gz</a>.</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000693 <li>Docs, content of the web site, the list archive included <a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000694 href="ftp://xmlsoft.org/libxml-docs.tar.gz">libxml-docs.tar.gz</a>.</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000695</ul>
696
Daniel Veillardc6271d22001-10-27 07:50:58 +0000697<p><a name="Contribs">Contributions:</a></p>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000698
699<p>I do accept external contributions, especially if compiling on another
Daniel Veillardd99224d2004-04-06 10:04:16 +0000700platform, get in touch with the list to upload the package, wrappers for
701various languages have been provided, and can be found in the <a
702href="python.html">bindings section</a></p>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000703
Daniel Veillard8a469172003-06-12 16:05:07 +0000704<p>Libxml2 is also available from CVS:</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000705<ul>
Daniel Veillardb331fff2004-08-22 14:21:57 +0000706 <li><p>The <a href="http://cvs.gnome.org/viewcvs/libxml2/">Gnome CVS
707 base</a>. Check the <a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000708 href="http://developer.gnome.org/tools/cvs.html">Gnome CVS Tools</a>
Daniel Veillardd99224d2004-04-06 10:04:16 +0000709 page; the CVS module is <b>libxml2</b>.</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000710 </li>
Daniel Veillard82687162001-01-22 15:32:01 +0000711 <li>The <strong>libxslt</strong> module is also present there</li>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000712</ul>
713
Daniel Veillard78fed532004-10-09 19:44:48 +0000714<h2><a name="News">Releases</a></h2>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000715
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000716<p>Items not finished and worked on, get in touch with the list if you want
Daniel Veillard688f6692004-03-26 10:57:38 +0000717to help those</p>
Daniel Veillardab8500d2000-10-15 21:06:19 +0000718<ul>
Daniel Veillard72fef162003-02-05 14:31:19 +0000719 <li>More testing on RelaxNG</li>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +0000720 <li>Finishing up <a href="http://www.w3.org/TR/xmlschema-1/">XML
Daniel Veillard72fef162003-02-05 14:31:19 +0000721 Schemas</a></li>
722</ul>
723
Daniel Veillard2d908032004-08-10 10:16:36 +0000724<p>The <a href="ChangeLog.html">change log</a> describes the recents commits
725to the <a href="http://cvs.gnome.org/viewcvs/libxml2/">CVS</a> code base.</p>
726
Daniel Veillardd99224d2004-04-06 10:04:16 +0000727<p>There is the list of public releases:</p>
728
Daniel Veillard67952602006-01-05 15:29:44 +0000729<h3>2.6.23: Jan 5 2006</h3>
730<ul>
731 <li>portability fixes: Windows (Rob Richards), getaddrinfo on Windows
732 (Kolja Nowak, Rob Richards), icc warnings (Kjartan Maraas),
733 --with-minimum compilation fixes (William Brack), error case handling fix
734 on Solaris (Albert Chin), don't use 'list' as parameter name reported by
735 Samuel Diaz Garcia, more old Unices portability fixes (Albert Chin),
736 MinGW compilation (Mark Junker), HP-UX compiler warnings (Rick Jones),
737 </li>
738 <li>code cleanup: xmlReportError (Adrian Mouat), remove xmlBufferClose
739 (Geert Jansen), unreachable code (Oleksandr Kononenko), refactoring
740 parsing code (Bjorn Reese)</li>
741 <li>bug fixes: xmlBuildRelativeURI and empty path (William Brack),
742 combinatory explosion and performances in regexp code, leak in
743 xmlTextReaderReadString(), xmlStringLenDecodeEntities problem (Massimo
744 Morara), Identity Constraints bugs and a segfault (Kasimier Buchcik),
745 XPath pattern based evaluation bugs (DV &amp; Kasimier),
746 xmlSchemaContentModelDump() memory leak (Kasimier), potential leak in
747 xmlSchemaCheckCSelectorXPath(), xmlTextWriterVSprintf() misuse of
748 vsnprintf (William Brack), XHTML serialization fix (Rob Richards), CRLF
749 split problem (William), issues with non-namespaced attributes in
750 xmlAddChild() xmlAddNextSibling() and xmlAddPrevSibling() (Rob Richards),
751 HTML parsing of script, Python must not output to stdout (Nic Ferrier),
752 exclusive C14N namespace visibility (Aleksey Sanin), XSD dataype
753 totalDigits bug (Kasimier Buchcik), error handling when writing to an
754 xmlBuffer (Rob Richards), runtest schemas error not reported (Hisashi
755 Fujinaka), signed/unsigned problem in date/time code (Albert Chin), fix
756 XSI driven XSD validation (Kasimier), parsing of xs:decimal (Kasimier),
757 fix DTD writer output (Rob Richards), leak in xmlTextReaderReadInnerXml
758 (Gary Coady), regexp bug affecting schemas (Kasimier), configuration of
759 runtime debugging (Kasimier), xmlNodeBufGetContent bug on entity refs
760 (Oleksandr Kononenko), xmlRegExecPushString2 bug (Sreeni Nair),
761 compilation and build fixes (Michael Day), removed dependancies on
762 xmlSchemaValidError (Kasimier), bug with &lt;xml:foo/&gt;, more XPath
763 pattern based evaluation fixes (Kasimier)</li>
764 <li>improvements: XSD Schemas redefinitions/restrictions (Kasimier
765 Buchcik), node copy checks and fix for attribute (Rob Richards), counted
766 transition bug in regexps, ctxt-&gt;standalone = -2 to indicate no
767 standalone attribute was found, add xmlSchemaSetParserStructuredErrors()
768 (Kasimier Buchcik), add xmlTextReaderSchemaValidateCtxt() to API
769 (Kasimier), handle gzipped HTTP resources (Gary Coady), add
770 htmlDocDumpMemoryFormat. (Rob Richards), </li>
771 <li>documentation: typo (Michael Day), libxml man page (Albert Chin), save
772 function to XML buffer (Geert Jansen), small doc fix (Aron Stansvik),
773 </li>
774</ul>
775
Daniel Veillard33b20b72005-09-12 21:43:20 +0000776<h3>2.6.22: Sep 12 2005</h3>
777<ul>
778 <li>build fixes: compile without schematron (Stéphane Bidoul)</li>
779 <li>bug fixes: xmlDebugDumpNode on namespace node (Oleg Paraschenko)i,
Daniel Veillard67952602006-01-05 15:29:44 +0000780 CDATA push parser bug, xmlElemDump problem with XHTML1 doc,
781 XML_FEATURE_xxx clash with expat headers renamed XML_WITH_xxx, fix some
782 output formatting for meta element (Rob Richards), script and style
783 XHTML1 serialization (David Madore), Attribute derivation fixups in XSD
784 (Kasimier Buchcik), better IDC error reports (Kasimier Buchcik)</li>
785 <li>improvements: add XML_SAVE_NO_EMPTY xmlSaveOption (Rob Richards), add
786 XML_SAVE_NO_XHTML xmlSaveOption, XML Schemas improvements preparing for
787 derive (Kasimier Buchcik).</li>
Daniel Veillard33b20b72005-09-12 21:43:20 +0000788 <li>documentation: generation of gtk-doc like docs, integration with
Daniel Veillard67952602006-01-05 15:29:44 +0000789 devhelp.</li>
Daniel Veillard33b20b72005-09-12 21:43:20 +0000790</ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000791
Daniel Veillardb3d14912005-09-04 20:47:39 +0000792<h3>2.6.21: Sep 4 2005</h3>
793<ul>
794 <li>build fixes: Cygwin portability fixes (Gerrit P. Haase), calling
Daniel Veillard67952602006-01-05 15:29:44 +0000795 convention problems on Windows (Marcus Boerger), cleanups based on Linus'
796 sparse tool, update of win32/configure.js (Rob Richards), remove warnings
797 on Windows(Marcus Boerger), compilation without SAX1, detection of the
798 Python binary, use $GCC inestad of $CC = 'gcc' (Andrew W. Nosenko),
799 compilation/link with threads and old gcc, compile problem by C370 on
800 Z/OS,</li>
Daniel Veillardb3d14912005-09-04 20:47:39 +0000801 <li>bug fixes: http_proxy environments (Peter Breitenlohner), HTML UTF-8
Daniel Veillard67952602006-01-05 15:29:44 +0000802 bug (Jiri Netolicky), XPath NaN compare bug (William Brack),
803 htmlParseScript potential bug, Schemas regexp handling of spaces, Base64
804 Schemas comparisons NIST passes, automata build error xsd:all,
805 xmlGetNodePath for namespaced attributes (Alexander Pohoyda), xmlSchemas
806 foreign namespaces handling, XML Schemas facet comparison (Kupriyanov
807 Anatolij), xmlSchemaPSimpleTypeErr error report (Kasimier Buchcik), xml:
808 namespace ahndling in Schemas (Kasimier), empty model group in Schemas
809 (Kasimier), wilcard in Schemas (Kasimier), URI composition (William),
810 xs:anyType in Schemas (Kasimier), Python resolver emmitting error
811 messages directly, Python xmlAttr.parent (Jakub Piotr Clapa), trying to
812 fix the file path/URI conversion, xmlTextReaderGetAttribute fix (Rob
813 Richards), xmlSchemaFreeAnnot memleak (Kasimier), HTML UTF-8
814 serialization, streaming XPath, Schemas determinism detection problem,
815 XInclude bug, Schemas context type (Dean Hill), validation fix (Derek
816 Poon), xmlTextReaderGetAttribute[Ns] namespaces (Rob Richards), Schemas
817 type fix (Kuba Nowakowski), UTF-8 parser bug, error in encoding handling,
818 xmlGetLineNo fixes, bug on entities handling, entity name extraction in
819 error handling with XInclude, text nodes in HTML body tags (Gary Coady),
820 xml:id and IDness at the treee level fixes, XPath streaming patterns
821 bugs.</li>
Daniel Veillardb3d14912005-09-04 20:47:39 +0000822 <li>improvements: structured interfaces for schemas and RNG error reports
Daniel Veillard67952602006-01-05 15:29:44 +0000823 (Marcus Boerger), optimization of the char data inner loop parsing
824 (thanks to Behdad Esfahbod for the idea), schematron validation though
825 not finished yet, xmlSaveOption to omit XML declaration, keyref match
826 error reports (Kasimier), formal expression handling code not plugged
827 yet, more lax mode for the HTML parser, parser XML_PARSE_COMPACT option
828 for text nodes allocation.</li>
Daniel Veillardb3d14912005-09-04 20:47:39 +0000829 <li>documentation: xmllint man page had --nonet duplicated</li>
830</ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000831
Daniel Veillard78dfc9f2005-07-10 22:30:30 +0000832<h3>2.6.20: Jul 10 2005</h3>
833<ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000834 <li>build fixes: Windows build (Rob Richards), Mingw compilation (Igor
835 Zlatkovic), Windows Makefile (Igor), gcc warnings (Kasimier and
836 andriy@google.com), use gcc weak references to pthread to avoid the
837 pthread dependancy on Linux, compilation problem (Steve Nairn), compiling
838 of subset (Morten Welinder), IPv6/ss_family compilation (William Brack),
839 compilation when disabling parts of the library, standalone test
840 distribution.</li>
841 <li>bug fixes: bug in lang(), memory cleanup on errors (William Brack),
842 HTTP query strings (Aron Stansvik), memory leak in DTD (William), integer
843 overflow in XPath (William), nanoftp buffer size, pattern "." apth fixup
844 (Kasimier), leak in tree reported by Malcolm Rowe, replaceNode patch
845 (Brent Hendricks), CDATA with NULL content (Mark Vakoc), xml:base fixup
846 on XInclude (William), pattern fixes (William), attribute bug in
847 exclusive c14n (Aleksey Sanin), xml:space and xml:lang with SAX2 (Rob
848 Richards), namespace trouble in complex parsing (Malcolm Rowe), XSD type
849 QNames fixes (Kasimier), XPath streaming fixups (William), RelaxNG bug
850 (Rob Richards), Schemas for Schemas fixes (Kasimier), removal of ID (Rob
851 Richards), a small RelaxNG leak, HTML parsing in push mode bug (James
852 Bursa), failure to detect UTF-8 parsing bugs in CDATA sections,
853 areBlanks() heuristic failure, duplicate attributes in DTD bug
854 (William).</li>
855 <li>improvements: lot of work on Schemas by Kasimier Buchcik both on
856 conformance and streaming, Schemas validation messages (Kasimier Buchcik,
857 Matthew Burgess), namespace removal at the python level (Brent
858 Hendricks), Update to new Schemas regression tests from W3C/Nist
859 (Kasimier), xmlSchemaValidateFile() (Kasimier), implementation of
860 xmlTextReaderReadInnerXml and xmlTextReaderReadOuterXml (James Wert),
861 standalone test framework and programs, new DOM import APIs
862 xmlDOMWrapReconcileNamespaces() xmlDOMWrapAdoptNode() and
863 xmlDOMWrapRemoveNode(), extension of xmllint capabilities for SAX and
864 Schemas regression tests, xmlStopParser() available in pull mode too,
865 ienhancement to xmllint --shell namespaces support, Windows port of the
866 standalone testing tools (Kasimier and William),
867 xmlSchemaValidateStream() xmlSchemaSAXPlug() and xmlSchemaSAXUnplug() SAX
868 Schemas APIs, Schemas xmlReader support.</li>
Daniel Veillard78dfc9f2005-07-10 22:30:30 +0000869</ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000870
Daniel Veillard771971f2005-04-02 10:49:51 +0000871<h3>2.6.19: Apr 02 2005</h3>
872<ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000873 <li>build fixes: drop .la from RPMs, --with-minimum build fix (William
874 Brack), use XML_SOCKLEN_T instead of SOCKLEN_T because it breaks with AIX
875 5.3 compiler, fixed elfgcchack.h generation and PLT reduction code on
876 Linux/ELF/gcc4</li>
877 <li>bug fixes: schemas type decimal fixups (William Brack), xmmlint return
878 code (Gerry Murphy), small schemas fixes (Matthew Burgess and GUY
879 Fabrice), workaround "DAV:" namespace brokeness in c14n (Aleksey Sanin),
880 segfault in Schemas (Kasimier Buchcik), Schemas attribute validation
881 (Kasimier), Prop related functions and xmlNewNodeEatName (Rob Richards),
882 HTML serialization of name attribute on a elements, Python error handlers
883 leaks and improvement (Brent Hendricks), uninitialized variable in
884 encoding code, Relax-NG validation bug, potential crash if
885 gnorableWhitespace is NULL, xmlSAXParseDoc and xmlParseDoc signatures,
886 switched back to assuming UTF-8 in case no encoding is given at
887 serialization time</li>
888 <li>improvements: lot of work on Schemas by Kasimier Buchcik on facets
889 checking and also mixed handling.</li>
Daniel Veillard771971f2005-04-02 10:49:51 +0000890 <li></li>
891</ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000892
Daniel Veillard57c000e2005-03-13 18:34:29 +0000893<h3>2.6.18: Mar 13 2005</h3>
894<ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000895 <li>build fixes: warnings (Peter Breitenlohner), testapi.c generation,
896 Bakefile support (Francesco Montorsi), Windows compilation (Joel Reed),
897 some gcc4 fixes, HP-UX portability fixes (Rick Jones).</li>
898 <li>bug fixes: xmlSchemaElementDump namespace (Kasimier Buchcik), push and
899 xmlreader stopping on non-fatal errors, thread support for dictionnaries
900 reference counting (Gary Coady), internal subset and push problem, URL
901 saved in xmlCopyDoc, various schemas bug fixes (Kasimier), Python paths
902 fixup (Stephane Bidoul), xmlGetNodePath and namespaces, xmlSetNsProp fix
903 (Mike Hommey), warning should not count as error (William Brack),
904 xmlCreatePushParser empty chunk, XInclude parser flags (William), cleanup
905 FTP and HTTP code to reuse the uri parsing and IPv6 (William),
906 xmlTextWriterStartAttributeNS fix (Rob Richards), XMLLINT_INDENT being
907 empty (William), xmlWriter bugs (Rob Richards), multithreading on Windows
908 (Rich Salz), xmlSearchNsByHref fix (Kasimier), Python binding leak (Brent
909 Hendricks), aliasing bug exposed by gcc4 on s390, xmlTextReaderNext bug
910 (Rob Richards), Schemas decimal type fixes (William Brack),
911 xmlByteConsumed static buffer (Ben Maurer).</li>
912 <li>improvement: speedup parsing comments and DTDs, dictionnary support for
913 hash tables, Schemas Identity constraints (Kasimier), streaming XPath
914 subset, xmlTextReaderReadString added (Bjorn Reese), Schemas canonical
915 values handling (Kasimier), add xmlTextReaderByteConsumed (Aron
916 Stansvik),</li>
917 <li>Documentation: Wiki support (Joel Reed)</li>
Daniel Veillard57c000e2005-03-13 18:34:29 +0000918</ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000919
Daniel Veillard298d9642005-01-16 20:01:55 +0000920<h3>2.6.17: Jan 16 2005</h3>
921<ul>
Daniel Veillard67952602006-01-05 15:29:44 +0000922 <li>build fixes: Windows, warnings removal (William Brack),
923 maintainer-clean dependency(William), build in a different directory
924 (William), fixing --with-minimum configure build (William), BeOS build
925 (Marcin Konicki), Python-2.4 detection (William), compilation on AIX (Dan
926 McNichol)</li>
Daniel Veillard298d9642005-01-16 20:01:55 +0000927 <li>bug fixes: xmlTextReaderHasAttributes (Rob Richards), xmlCtxtReadFile()
Daniel Veillard67952602006-01-05 15:29:44 +0000928 to use the catalog(s), loop on output (William Brack), XPath memory leak,
929 ID deallocation problem (Steve Shepard), debugDumpNode crash (William),
930 warning not using error callback (William), xmlStopParser bug (William),
931 UTF-16 with BOM on DTDs (William), namespace bug on empty elements in
932 push mode (Rob Richards), line and col computations fixups (Aleksey
933 Sanin), xmlURIEscape fix (William), xmlXPathErr on bad range (William),
934 patterns with too many steps, bug in RNG choice optimization, line number
935 sometimes missing.</li>
936 <li>improvements: XSD Schemas (Kasimier Buchcik), python generator
937 (William), xmlUTF8Strpos speedup (William), unicode Python strings
938 (William), XSD error reports (Kasimier Buchcik), Python __str__ call
939 serialize().</li>
940 <li>new APIs: added xmlDictExists(), GetLineNumber and GetColumnNumber for
941 the xmlReader (Aleksey Sanin), Dynamic Shared Libraries APIs (mostly Joel
942 Reed), error extraction API from regexps, new XMLSave option for format
943 (Phil Shafer)</li>
944 <li>documentation: site improvement (John Fleck), FAQ entries
945 (William).</li>
Daniel Veillard298d9642005-01-16 20:01:55 +0000946</ul>
947
Daniel Veillardc3d7cb42004-11-10 14:34:45 +0000948<h3>2.6.16: Nov 10 2004</h3>
949<ul>
950 <li>general hardening and bug fixing crossing all the API based on new
951 automated regression testing</li>
952 <li>build fix: IPv6 build and test on AIX (Dodji Seketeli)</li>
953 <li>bug fixes: problem with XML::Libxml reported by Petr Pajas, encoding
954 conversion functions return values, UTF-8 bug affecting XPath reported by
955 Markus Bertheau, catalog problem with NULL entries (William Brack)</li>
956 <li>documentation: fix to xmllint man page, some API function descritpion
957 were updated.</li>
958 <li>improvements: DTD validation APIs provided at the Python level (Brent
Daniel Veillard67952602006-01-05 15:29:44 +0000959 Hendricks)</li>
Daniel Veillardc3d7cb42004-11-10 14:34:45 +0000960</ul>
961
Daniel Veillardc2f83d12004-10-27 22:59:21 +0000962<h3>2.6.15: Oct 27 2004</h3>
Daniel Veillard6927b102004-10-27 17:29:04 +0000963<ul>
964 <li>security fixes on the nanoftp and nanohttp modules</li>
965 <li>build fixes: xmllint detection bug in configure, building outside the
966 source tree (Thomas Fitzsimmons)</li>
967 <li>bug fixes: HTML parser on broken ASCII chars in names (William), Python
968 paths (Malcolm Tredinnick), xmlHasNsProp and default namespace (William),
969 saving to python file objects (Malcolm Tredinnick), DTD lookup fix
970 (Malcolm), save back &lt;group&gt; in catalogs (William), tree build
971 fixes (DV and Rob Richards), Schemas memory bug, structured error handler
972 on Python 64bits, thread local memory deallocation, memory leak reported
973 by Volker Roth, xmlValidateDtd in the presence of an internal subset,
974 entities and _private problem (William), xmlBuildRelativeURI error
975 (William).</li>
976 <li>improvements: better XInclude error reports (William), tree debugging
977 module and tests, convenience functions at the Reader API (Graham
978 Bennett), add support for PI in the HTML parser.</li>
979</ul>
980
Daniel Veillard210818b2004-09-29 15:50:37 +0000981<h3>2.6.14: Sep 29 2004</h3>
982<ul>
983 <li>build fixes: configure paths for xmllint and xsltproc, compilation
984 without HTML parser, compilation warning cleanups (William Brack &amp;
Daniel Veillard6927b102004-10-27 17:29:04 +0000985 Malcolm Tredinnick), VMS makefile update (Craig Berry),</li>
Daniel Veillard210818b2004-09-29 15:50:37 +0000986 <li>bug fixes: xmlGetUTF8Char (William Brack), QName properties (Kasimier
987 Buchcik), XInclude testing, Notation serialization, UTF8ToISO8859x
988 transcoding (Mark Itzcovitz), lots of XML Schemas cleanup and fixes
989 (Kasimier), ChangeLog cleanup (Stepan Kasal), memory fixes (Mark Vakoc),
990 handling of failed realloc(), out of bound array adressing in Schemas
991 date handling, Python space/tabs cleanups (Malcolm Tredinnick), NMTOKENS
Daniel Veillard6927b102004-10-27 17:29:04 +0000992 E20 validation fix (Malcolm),</li>
Daniel Veillard210818b2004-09-29 15:50:37 +0000993 <li>improvements: added W3C XML Schemas testsuite (Kasimier Buchcik), add
994 xmlSchemaValidateOneElement (Kasimier), Python exception hierearchy
995 (Malcolm Tredinnick), Python libxml2 driver improvement (Malcolm
996 Tredinnick), Schemas support for xsi:schemaLocation,
997 xsi:noNamespaceSchemaLocation, xsi:type (Kasimier Buchcik)</li>
998</ul>
999
Daniel Veillardd1de4a32004-08-31 13:43:07 +00001000<h3>2.6.13: Aug 31 2004</h3>
1001<ul>
1002 <li>build fixes: Windows and zlib (Igor Zlatkovic), -O flag with gcc,
Daniel Veillard210818b2004-09-29 15:50:37 +00001003 Solaris compiler warning, fixing RPM BuildRequires,</li>
Daniel Veillardd1de4a32004-08-31 13:43:07 +00001004 <li>fixes: DTD loading on Windows (Igor), Schemas error reports APIs
1005 (Kasimier Buchcik), Schemas validation crash, xmlCheckUTF8 (William Brack
1006 and Julius Mittenzwei), Schemas facet check (Kasimier), default namespace
1007 problem (William), Schemas hexbinary empty values, encoding error could
1008 genrate a serialization loop.</li>
1009 <li>Improvements: Schemas validity improvements (Kasimier), added --path
1010 and --load-trace options to xmllint</li>
1011 <li>documentation: tutorial update (John Fleck)</li>
1012</ul>
1013
Daniel Veillardb331fff2004-08-22 14:21:57 +00001014<h3>2.6.12: Aug 22 2004</h3>
1015<ul>
1016 <li>build fixes: fix --with-minimum, elfgcchack.h fixes (Peter
1017 Breitenlohner), perl path lookup (William), diff on Solaris (Albert
1018 Chin), some 64bits cleanups.</li>
1019 <li>Python: avoid a warning with 2.3 (William Brack), tab and space mixes
1020 (William), wrapper generator fixes (William), Cygwin support (Gerrit P.
1021 Haase), node wrapper fix (Marc-Antoine Parent), XML Schemas support
1022 (Torkel Lyng)</li>
1023 <li>Schemas: a lot of bug fixes and improvements from Kasimier Buchcik</li>
1024 <li>fixes: RVT fixes (William), XPath context resets bug (William), memory
1025 debug (Steve Hay), catalog white space handling (Peter Breitenlohner),
1026 xmlReader state after attribute reading (William), structured error
1027 handler (William), XInclude generated xml:base fixup (William), Windows
1028 memory reallocation problem (Steve Hay), Out of Memory conditions
1029 handling (William and Olivier Andrieu), htmlNewDoc() charset bug,
1030 htmlReadMemory init (William), a posteriori validation DTD base
1031 (William), notations serialization missing, xmlGetNodePath (Dodji),
1032 xmlCheckUTF8 (Diego Tartara), missing line numbers on entity
1033 (William)</li>
1034 <li>improvements: DocBook catalog build scrip (William), xmlcatalog tool
1035 (Albert Chin), xmllint --c14n option, no_proxy environment (Mike Hommey),
1036 xmlParseInNodeContext() addition, extend xmllint --shell, allow XInclude
1037 to not generate start/end nodes, extend xmllint --version to include CVS
1038 tag (William)</li>
1039 <li>documentation: web pages fixes, validity API docs fixes (William)
1040 schemas API fix (Eric Haszlakiewicz), xmllint man page (John Fleck)</li>
1041</ul>
1042
Daniel Veillard45cb0f42004-07-05 17:45:35 +00001043<h3>2.6.11: July 5 2004</h3>
1044<ul>
1045 <li>Schemas: a lot of changes and improvements by Kasimier Buchcik for
1046 attributes, namespaces and simple types.</li>
1047 <li>build fixes: --with-minimum (William Brack), some gcc cleanup
1048 (William), --with-thread-alloc (William)</li>
1049 <li>portability: Windows binary package change (Igor Zlatkovic), Catalog
1050 path on Windows</li>
1051 <li>documentation: update to the tutorial (John Fleck), xmllint return code
Daniel Veillardb331fff2004-08-22 14:21:57 +00001052 (John Fleck), man pages (Ville Skytta),</li>
Daniel Veillard45cb0f42004-07-05 17:45:35 +00001053 <li>bug fixes: C14N bug serializing namespaces (Aleksey Sanin), testSAX
1054 properly initialize the library (William), empty node set in XPath
1055 (William), xmlSchemas errors (William), invalid charref problem pointed
1056 by Morus Walter, XInclude xml:base generation (William), Relax-NG bug
Daniel Veillardb331fff2004-08-22 14:21:57 +00001057 with div processing (William), XPointer and xml:base problem(William),
Daniel Veillard45cb0f42004-07-05 17:45:35 +00001058 Reader and entities, xmllint return code for schemas (William), reader
1059 streaming problem (Steve Ball), DTD serialization problem (William),
1060 libxml.m4 fixes (Mike Hommey), do not provide destructors as methods on
1061 Python classes, xmlReader buffer bug, Python bindings memory interfaces
1062 improvement (with Stéphane Bidoul), Fixed the push parser to be back to
1063 synchronous behaviour.</li>
1064 <li>improvement: custom per-thread I/O enhancement (Rob Richards), register
1065 namespace in debug shell (Stefano Debenedetti), Python based regression
1066 test for non-Unix users (William), dynamically increase the number of
1067 XPath extension functions in Python and fix a memory leak (Marc-Antoine
1068 Parent and William)</li>
1069 <li>performance: hack done with Arjan van de Ven to reduce ELF footprint
1070 and generated code on Linux, plus use gcc runtime profiling to optimize
1071 the code generated in the RPM packages.</li>
1072</ul>
1073
Daniel Veillard81205012004-05-18 03:06:41 +00001074<h3>2.6.10: May 17 2004</h3>
1075<ul>
1076 <li>Web page generated for ChangeLog</li>
1077 <li>build fixes: --without-html problems, make check without make all</li>
1078 <li>portability: problem with xpath.c on Windows (MSC and Borland), memcmp
1079 vs. strncmp on Solaris, XPath tests on Windows (Mark Vakoc), C++ do not
1080 use "list" as parameter name, make tests work with Python 1.5 (Ed
1081 Davis),</li>
1082 <li>improvements: made xmlTextReaderMode public, small buffers resizing
1083 (Morten Welinder), add --maxmem option to xmllint, add
1084 xmlPopInputCallback() for Matt Sergeant, refactoring of serialization
Daniel Veillard45cb0f42004-07-05 17:45:35 +00001085 escaping, added escaping customization</li>
Daniel Veillard81205012004-05-18 03:06:41 +00001086 <li>bugfixes: xsd:extension (Taihei Goi), assorted regexp bugs (William
1087 Brack), xmlReader end of stream problem, node deregistration with reader,
1088 URI escaping and filemanes, XHTML1 formatting (Nick Wellnhofer), regexp
1089 transition reduction (William), various XSD Schemas fixes (Kasimier
1090 Buchcik), XInclude fallback problem (William), weird problems with DTD
1091 (William), structured error handler callback context (William), reverse
1092 xmlEncodeSpecialChars() behaviour back to escaping '"'</li>
1093</ul>
1094
Daniel Veillardeca726d2004-04-18 21:47:34 +00001095<h3>2.6.9: Apr 18 2004</h3>
1096<ul>
1097 <li>implement xml:id Working Draft, relaxed XPath id() checking</li>
1098 <li>bugfixes: xmlCtxtReset (Brent Hendricks), line number and CDATA (Dave
1099 Beckett), Relax-NG compilation (William Brack), Regexp patches (with
1100 William), xmlUriEscape (Mark Vakoc), a Relax-NG notAllowed problem (with
1101 William), Relax-NG name classes compares (William), XInclude duplicate
1102 fallback (William), external DTD encoding detection (William), a DTD
1103 validation bug (William), xmlReader Close() fix, recusive extention
1104 schemas</li>
1105 <li>improvements: use xmlRead* APIs in test tools (Mark Vakoc), indenting
1106 save optimization, better handle IIS broken HTTP redirect behaviour (Ian
1107 Hummel), HTML parser frameset (James Bursa), libxml2-python RPM
1108 dependancy, XML Schemas union support (Kasimier Buchcik), warning removal
1109 clanup (William), keep ChangeLog compressed when installing from RPMs</li>
1110 <li>documentation: examples and xmlDocDumpMemory docs (John Fleck), new
Daniel Veillardd4cfcef2004-05-06 18:55:27 +00001111 example (load, xpath, modify, save), xmlCatalogDump() comments,</li>
Daniel Veillardeca726d2004-04-18 21:47:34 +00001112 <li>Windows: Borland C++ builder (Eric Zurcher), work around Microsoft
1113 compiler NaN handling bug (Mark Vakoc)</li>
1114</ul>
1115
Daniel Veillard252004d2004-03-23 12:32:32 +00001116<h3>2.6.8: Mar 23 2004</h3>
1117<ul>
1118 <li>First step of the cleanup of the serialization code and APIs</li>
1119 <li>XML Schemas: mixed content (Adam Dickmeiss), QName handling fixes (Adam
1120 Dickmeiss), anyURI for "" (John Belmonte)</li>
1121 <li>Python: Canonicalization C14N support added (Anthony Carrico)</li>
1122 <li>xmlDocCopyNode() extension (William)</li>
1123 <li>Relax-NG: fix when processing XInclude results (William), external
1124 reference in interleave (William), missing error on &lt;choice&gt;
1125 failure (William), memory leak in schemas datatype facets.</li>
1126 <li>xmlWriter: patch for better DTD support (Alfred Mickautsch)</li>
1127 <li>bug fixes: xmlXPathLangFunction memory leak (Mike Hommey and William
1128 Brack), no ID errors if using HTML_PARSE_NOERROR, xmlcatalog fallbacks to
1129 URI on SYSTEM lookup failure, XInclude parse flags inheritance (William),
1130 XInclude and XPointer fixes for entities (William), XML parser bug
1131 reported by Holger Rauch, nanohttp fd leak (William), regexps char
1132 groups '-' handling (William), dictionnary reference counting problems,
Daniel Veillardd99224d2004-04-06 10:04:16 +00001133 do not close stderr.</li>
Daniel Veillard252004d2004-03-23 12:32:32 +00001134 <li>performance patches from Petr Pajas</li>
1135 <li>Documentation fixes: XML_CATALOG_FILES in man pages (Mike Hommey)</li>
1136 <li>compilation and portability fixes: --without-valid, catalog cleanups
1137 (Peter Breitenlohner), MingW patch (Roland Schwingel), cross-compilation
1138 to Windows (Christophe de Vienne), --with-html-dir fixup (Julio Merino
1139 Vidal), Windows build (Eric Zurcher)</li>
1140</ul>
1141
Daniel Veillard92914492004-02-23 16:33:21 +00001142<h3>2.6.7: Feb 23 2004</h3>
1143<ul>
1144 <li>documentation: tutorial updates (John Fleck), benchmark results</li>
1145 <li>xmlWriter: updates and fixes (Alfred Mickautsch, Lucas Brasilino)</li>
1146 <li>XPath optimization (Petr Pajas)</li>
1147 <li>DTD ID handling optimization</li>
1148 <li>bugfixes: xpath number with &gt; 19 fractional (William Brack), push
1149 mode with unescaped '&gt;' characters, fix xmllint --stream --timing, fix
1150 xmllint --memory --stream memory usage, xmlAttrSerializeTxtContent
1151 handling NULL, trying to fix Relax-NG/Perl interface.</li>
1152 <li>python: 2.3 compatibility, whitespace fixes (Malcolm Tredinnick)</li>
1153 <li>Added relaxng option to xmllint --shell</li>
1154</ul>
1155
Daniel Veillard5c9547e2004-02-12 15:31:49 +00001156<h3>2.6.6: Feb 12 2004</h3>
1157<ul>
1158 <li>nanohttp and nanoftp: buffer overflow error on URI parsing (Igor and
1159 William) reported by Yuuichi Teranishi</li>
1160 <li>bugfixes: make test and path issues, xmlWriter attribute serialization
1161 (William Brack), xmlWriter indentation (William), schemas validation
1162 (Eric Haszlakiewicz), XInclude dictionnaries issues (William and Oleg
1163 Paraschenko), XInclude empty fallback (William), HTML warnings (William),
1164 XPointer in XInclude (William), Python namespace serialization,
1165 isolat1ToUTF8 bound error (Alfred Mickautsch), output of parameter
1166 entities in internal subset (William), internal subset bug in push mode,
1167 &lt;xs:all&gt; fix (Alexey Sarytchev)</li>
1168 <li>Build: fix for automake-1.8 (Alexander Winston), warnings removal
1169 (Philip Ludlam), SOCKLEN_T detection fixes (Daniel Richard), fix
1170 --with-minimum configuration.</li>
1171 <li>XInclude: allow the 2001 namespace without warning.</li>
1172 <li>Documentation: missing example/index.html (John Fleck), version
1173 dependancies (John Fleck)</li>
1174 <li>reader API: structured error reporting (Steve Ball)</li>
1175 <li>Windows compilation: mingw, msys (Mikhail Grushinskiy), function
1176 prototype (Cameron Johnson), MSVC6 compiler warnings, _WINSOCKAPI_
1177 patch</li>
1178 <li>Parsers: added xmlByteConsumed(ctxt) API to get the byte offest in
1179 input.</li>
1180</ul>
1181
Daniel Veillard189f46b2004-01-25 21:03:04 +00001182<h3>2.6.5: Jan 25 2004</h3>
1183<ul>
1184 <li>Bugfixes: dictionnaries for schemas (William Brack), regexp segfault
1185 (William), xs:all problem (William), a number of XPointer bugfixes
1186 (William), xmllint error go to stderr, DTD validation problem with
1187 namespace, memory leak (William), SAX1 cleanup and minimal options fixes
1188 (Mark Vadoc), parser context reset on error (Shaun McCance), XPath union
1189 evaluation problem (William) , xmlReallocLoc with NULL (Aleksey Sanin),
1190 XML Schemas double free (Steve Ball), XInclude with no href, argument
1191 callbacks order for XPath callbacks (Frederic Peters)</li>
1192 <li>Documentation: python scripts (William Brack), xslt stylesheets (John
1193 Fleck), doc (Sven Zimmerman), I/O example.</li>
1194 <li>Python bindings: fixes (William), enum support (Stéphane Bidoul),
1195 structured error reporting (Stéphane Bidoul)</li>
1196 <li>XInclude: various fixes for conformance, problem related to dictionnary
1197 references (William &amp; me), recursion (William)</li>
1198 <li>xmlWriter: indentation (Lucas Brasilino), memory leaks (Alfred
Daniel Veillard5c9547e2004-02-12 15:31:49 +00001199 Mickautsch),</li>
Daniel Veillard189f46b2004-01-25 21:03:04 +00001200 <li>xmlSchemas: normalizedString datatype (John Belmonte)</li>
1201 <li>code cleanup for strings functions (William)</li>
1202 <li>Windows: compiler patches (Mark Vakoc)</li>
1203 <li>Parser optimizations, a few new XPath and dictionnary APIs for future
1204 XSLT optimizations.</li>
1205</ul>
1206
Daniel Veillarde6e59cd2003-12-24 11:56:44 +00001207<h3>2.6.4: Dec 24 2003</h3>
1208<ul>
1209 <li>Windows build fixes (Igor Zlatkovic)</li>
Daniel Veillard189f46b2004-01-25 21:03:04 +00001210 <li>Some serious XInclude problems reported by Oleg Paraschenko and</li>
1211 <li>Unix and Makefile packaging fixes (me, William Brack,</li>
Daniel Veillarde6e59cd2003-12-24 11:56:44 +00001212 <li>Documentation improvements (John Fleck, William Brack), example fix
1213 (Lucas Brasilino)</li>
1214 <li>bugfixes: xmlTextReaderExpand() with xmlReaderWalker, XPath handling of
1215 NULL strings (William Brack) , API building reader or parser from
1216 filedescriptor should not close it, changed XPath sorting to be stable
1217 again (William Brack), xmlGetNodePath() generating '(null)' (William
1218 Brack), DTD validation and namespace bug (William Brack), XML Schemas
1219 double inclusion behaviour</li>
1220</ul>
1221
Daniel Veillardc480c4e2003-12-10 13:24:38 +00001222<h3>2.6.3: Dec 10 2003</h3>
1223<ul>
1224 <li>documentation updates and cleanup (DV, William Brack, John Fleck)</li>
1225 <li>added a repository of examples, examples from Aleksey Sanin, Dodji
Daniel Veillarde6e59cd2003-12-24 11:56:44 +00001226 Seketeli, Alfred Mickautsch</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +00001227 <li>Windows updates: Mark Vakoc, Igor Zlatkovic, Eric Zurcher, Mingw
1228 (Kenneth Haley)</li>
1229 <li>Unicode range checking (William Brack)</li>
1230 <li>code cleanup (William Brack)</li>
1231 <li>Python bindings: doc (John Fleck), bug fixes</li>
1232 <li>UTF-16 cleanup and BOM issues (William Brack)</li>
1233 <li>bug fixes: ID and xmlReader validation, XPath (William Brack),
1234 xmlWriter (Alfred Mickautsch), hash.h inclusion problem, HTML parser
1235 (James Bursa), attribute defaulting and validation, some serialization
1236 cleanups, XML_GET_LINE macro, memory debug when using threads (William
1237 Brack), serialization of attributes and entities content, xmlWriter
1238 (Daniel Schulman)</li>
1239 <li>XInclude bugfix, new APIs and update to the last version including the
1240 namespace change.</li>
1241 <li>XML Schemas improvements: include (Robert Stepanek), import and
1242 namespace handling, fixed the regression tests troubles, added examples
Daniel Veillarde6e59cd2003-12-24 11:56:44 +00001243 based on Eric van der Vlist book, regexp fixes</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +00001244 <li>preliminary pattern support for streaming (needed for schemas
1245 constraints), added xmlTextReaderPreservePattern() to collect subdocument
1246 when streaming.</li>
1247 <li>various fixes in the structured error handling</li>
1248</ul>
1249
Daniel Veillard6d373a22003-11-04 10:26:43 +00001250<h3>2.6.2: Nov 4 2003</h3>
1251<ul>
1252 <li>XPath context unregistration fixes</li>
1253 <li>text node coalescing fixes (Mark Lilback)</li>
1254 <li>API to screate a W3C Schemas from an existing document (Steve Ball)</li>
1255 <li>BeOS patches (Marcin 'Shard' Konicki)</li>
1256 <li>xmlStrVPrintf function added (Aleksey Sanin)</li>
1257 <li>compilation fixes (Mark Vakoc)</li>
1258 <li>stdin parsing fix (William Brack)</li>
1259 <li>a posteriori DTD validation fixes</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +00001260 <li>xmlReader bug fixes: Walker fixes, python bindings</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +00001261 <li>fixed xmlStopParser() to really stop the parser and errors</li>
1262 <li>always generate line numbers when using the new xmlReadxxx
1263 functions</li>
1264 <li>added XInclude support to the xmlReader interface</li>
1265 <li>implemented XML_PARSE_NONET parser option</li>
1266 <li>DocBook XSLT processing bug fixed</li>
1267 <li>HTML serialization for &lt;p&gt; elements (William Brack and me)</li>
1268 <li>XPointer failure in XInclude are now handled as resource errors</li>
1269 <li>fixed xmllint --html to use the HTML serializer on output (added
1270 --xmlout to implement the previous behaviour of saving it using the XML
1271 serializer)</li>
1272</ul>
1273
Daniel Veillarde4e3f5d2003-10-28 23:06:32 +00001274<h3>2.6.1: Oct 28 2003</h3>
1275<ul>
1276 <li>Mostly bugfixes after the big 2.6.0 changes</li>
1277 <li>Unix compilation patches: libxml.m4 (Patrick Welche), warnings cleanup
1278 (William Brack)</li>
1279 <li>Windows compilation patches (Joachim Bauch, Stephane Bidoul, Igor
1280 Zlatkovic)</li>
1281 <li>xmlWriter bugfix (Alfred Mickautsch)</li>
1282 <li>chvalid.[ch]: couple of fixes from Stephane Bidoul</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +00001283 <li>context reset: error state reset, push parser reset (Graham
1284 Bennett)</li>
Daniel Veillarde4e3f5d2003-10-28 23:06:32 +00001285 <li>context reuse: generate errors if file is not readable</li>
1286 <li>defaulted attributes for element coming from internal entities
1287 (Stephane Bidoul)</li>
1288 <li>Python: tab and spaces mix (William Brack)</li>
1289 <li>Error handler could crash in DTD validation in 2.6.0</li>
1290 <li>xmlReader: do not use the document or element _private field</li>
1291 <li>testSAX.c: avoid a problem with some PIs (Massimo Morara)</li>
1292 <li>general bug fixes: mandatory encoding in text decl, serializing
1293 Document Fragment nodes, xmlSearchNs 2.6.0 problem (Kasimier Buchcik),
1294 XPath errors not reported, slow HTML parsing of large documents.</li>
1295</ul>
1296
Daniel Veillard3e35f8e2003-10-21 00:05:38 +00001297<h3>2.6.0: Oct 20 2003</h3>
1298<ul>
1299 <li>Major revision release: should be API and ABI compatible but got a lot
1300 of change</li>
1301 <li>Increased the library modularity, far more options can be stripped out,
1302 a --with-minimum configuration will weight around 160KBytes</li>
1303 <li>Use per parser and per document dictionnary, allocate names and small
1304 text nodes from the dictionnary</li>
1305 <li>Switch to a SAX2 like parser rewrote most of the XML parser core,
1306 provides namespace resolution and defaulted attributes, minimize memory
1307 allocations and copies, namespace checking and specific error handling,
1308 immutable buffers, make predefined entities static structures, etc...</li>
1309 <li>rewrote all the error handling in the library, all errors can be
1310 intercepted at a structured level, with precise information
1311 available.</li>
1312 <li>New simpler and more generic XML and HTML parser APIs, allowing to
1313 easilly modify the parsing options and reuse parser context for multiple
1314 consecutive documents.</li>
1315 <li>Similar new APIs for the xmlReader, for options and reuse, provided new
1316 functions to access content as const strings, use them for Python
1317 bindings</li>
1318 <li>a lot of other smaller API improvements: xmlStrPrintf (Aleksey Sanin),
1319 Walker i.e. reader on a document tree based on Alfred Mickautsch code,
1320 make room in nodes for line numbers, reference counting and future PSVI
1321 extensions, generation of character ranges to be checked with faster
1322 algorithm (William), xmlParserMaxDepth (Crutcher Dunnavant), buffer
1323 access</li>
1324 <li>New xmlWriter API provided by Alfred Mickautsch</li>
1325 <li>Schemas: base64 support by Anthony Carrico</li>
1326 <li>Parser&lt;-&gt;HTTP integration fix, proper processing of the Mime-Type
1327 and charset informations if available.</li>
1328 <li>Relax-NG: bug fixes including the one reported by Martijn Faassen and
1329 zeroOrMore, better error reporting.</li>
1330 <li>Python bindings (Stéphane Bidoul), never use stdout for errors
1331 output</li>
1332 <li>Portability: all the headers have macros for export and calling
1333 convention definitions (Igor Zlatkovic), VMS update (Craig A. Berry),
1334 Windows: threads (Jesse Pelton), Borland compiler (Eric Zurcher, Igor),
1335 Mingw (Igor), typos (Mark Vakoc), beta version (Stephane Bidoul),
1336 warning cleanups on AIX and MIPS compilers (William Brack), BeOS (Marcin
1337 'Shard' Konicki)</li>
1338 <li>Documentation fixes and README (William Brack), search fix (William),
1339 tutorial updates (John Fleck), namespace docs (Stefan Kost)</li>
1340 <li>Bug fixes: xmlCleanupParser (Dave Beckett), threading uninitialized
1341 mutexes, HTML doctype lowercase, SAX/IO (William), compression detection
1342 and restore (William), attribute declaration in DTDs (William), namespace
1343 on attribute in HTML output (William), input filename (Rob Richards),
1344 namespace DTD validation, xmlReplaceNode (Chris Ryland), I/O callbacks
1345 (Markus Keim), CDATA serialization (Shaun McCance), xmlReader (Peter
1346 Derr), high codepoint charref like &amp;#x10FFFF;, buffer access in push
1347 mode (Justin Fletcher), TLS threads on Windows (Jesse Pelton), XPath bug
1348 (William), xmlCleanupParser (Marc Liyanage), CDATA output (William), HTTP
1349 error handling.</li>
1350 <li>xmllint options: --dtdvalidfpi for Tobias Reif, --sax1 for compat
1351 testing, --nodict for building without tree dictionnary, --nocdata to
1352 replace CDATA by text, --nsclean to remove surperfluous namespace
1353 declarations</li>
1354 <li>added xml2-config --libtool-libs option from Kevin P. Fleming</li>
1355 <li>a lot of profiling and tuning of the code, speedup patch for
1356 xmlSearchNs() by Luca Padovani. The xmlReader should do far less
1357 allocation and it speed should get closer to SAX. Chris Anderson worked
1358 on speeding and cleaning up repetitive checking code.</li>
1359 <li>cleanup of "make tests"</li>
1360 <li>libxml-2.0-uninstalled.pc from Malcolm Tredinnick</li>
1361 <li>deactivated the broken docBook SGML parser code and plugged the XML
1362 parser instead.</li>
1363</ul>
1364
Daniel Veillardeec1ae92003-09-09 13:11:01 +00001365<h3>2.5.11: Sep 9 2003</h3>
1366
1367<p>A bugfix only release:</p>
1368<ul>
1369 <li>risk of crash in Relax-NG</li>
1370 <li>risk of crash when using multithreaded programs</li>
1371</ul>
1372
Daniel Veillardcfba2fe2003-08-15 00:33:43 +00001373<h3>2.5.10: Aug 15 2003</h3>
1374
1375<p>A bugfixes only release</p>
1376<ul>
1377 <li>Windows Makefiles (William Brack)</li>
1378 <li>UTF-16 support fixes (Mark Itzcovitz)</li>
1379 <li>Makefile and portability (William Brack) automake, Linux alpha, Mingw
Daniel Veillardeec1ae92003-09-09 13:11:01 +00001380 on Windows (Mikhail Grushinskiy)</li>
Daniel Veillardcfba2fe2003-08-15 00:33:43 +00001381 <li>HTML parser (Oliver Stoeneberg)</li>
1382 <li>XInclude performance problem reported by Kevin Ruscoe</li>
1383 <li>XML parser performance problem reported by Grant Goodale</li>
1384 <li>xmlSAXParseDTD() bug fix from Malcolm Tredinnick</li>
Daniel Veillardeec1ae92003-09-09 13:11:01 +00001385 <li>and a couple other cleanup</li>
Daniel Veillardcfba2fe2003-08-15 00:33:43 +00001386</ul>
1387
Daniel Veillard83ee40d2003-08-09 22:24:09 +00001388<h3>2.5.9: Aug 9 2003</h3>
1389<ul>
1390 <li>bugfixes: IPv6 portability, xmlHasNsProp (Markus Keim), Windows build
1391 (Wiliam Brake, Jesse Pelton, Igor), Schemas (Peter Sobisch), threading
1392 (Rob Richards), hexBinary type (), UTF-16 BOM (Dodji Seketeli),
1393 xmlReader, Relax-NG schemas compilation, namespace handling, EXSLT (Sean
1394 Griffin), HTML parsing problem (William Brack), DTD validation for mixed
1395 content + namespaces, HTML serialization, library initialization,
1396 progressive HTML parser</li>
1397 <li>better interfaces for Relax-NG error handling (Joachim Bauch, )</li>
1398 <li>adding xmlXIncludeProcessTree() for XInclud'ing in a subtree</li>
1399 <li>doc fixes and improvements (John Fleck)</li>
1400 <li>configure flag for -with-fexceptions when embedding in C++</li>
1401 <li>couple of new UTF-8 helper functions (William Brack)</li>
1402 <li>general encoding cleanup + ISO-8859-x without iconv (Peter Jacobi)</li>
1403 <li>xmlTextReader cleanup + enum for node types (Bjorn Reese)</li>
1404 <li>general compilation/warning cleanup Solaris/HP-UX/... (William
1405 Brack)</li>
1406</ul>
1407
Daniel Veillard560c2a42003-07-06 21:13:49 +00001408<h3>2.5.8: Jul 6 2003</h3>
1409<ul>
1410 <li>bugfixes: XPath, XInclude, file/URI mapping, UTF-16 save (Mark
1411 Itzcovitz), UTF-8 checking, URI saving, error printing (William Brack),
1412 PI related memleak, compilation without schemas or without xpath (Joerg
1413 Schmitz-Linneweber/Garry Pennington), xmlUnlinkNode problem with DTDs,
1414 rpm problem on , i86_64, removed a few compilation problems from 2.5.7,
1415 xmlIOParseDTD, and xmlSAXParseDTD (Malcolm Tredinnick)</li>
1416 <li>portability: DJGPP (MsDos) , OpenVMS (Craig A. Berry)</li>
1417 <li>William Brack fixed multithreading lock problems</li>
1418 <li>IPv6 patch for FTP and HTTP accesses (Archana Shah/Wipro)</li>
1419 <li>Windows fixes (Igor Zlatkovic, Eric Zurcher), threading (Stéphane
1420 Bidoul)</li>
1421 <li>A few W3C Schemas Structure improvements</li>
1422 <li>W3C Schemas Datatype improvements (Charlie Bozeman)</li>
1423 <li>Python bindings for thread globals (Stéphane Bidoul), and method/class
Daniel Veillard83ee40d2003-08-09 22:24:09 +00001424 generator</li>
1425 <li>added --nonet option to xmllint</li>
Daniel Veillard560c2a42003-07-06 21:13:49 +00001426 <li>documentation improvements (John Fleck)</li>
1427</ul>
1428
Daniel Veillard92fc02c2003-04-24 23:12:35 +00001429<h3>2.5.7: Apr 25 2003</h3>
1430<ul>
1431 <li>Relax-NG: Compiling to regexp and streaming validation on top of the
1432 xmlReader interface, added to xmllint --stream</li>
1433 <li>xmlReader: Expand(), Next() and DOM access glue, bug fixes</li>
1434 <li>Support for large files: RGN validated a 4.5GB instance</li>
1435 <li>Thread support is now configured in by default</li>
1436 <li>Fixes: update of the Trio code (Bjorn), WXS Date and Duration fixes
1437 (Charles Bozeman), DTD and namespaces (Brent Hendricks), HTML push parser
1438 and zero bytes handling, some missing Windows file path conversions,
1439 behaviour of the parser and validator in the presence of "out of memory"
Daniel Veillard93d95252003-04-29 20:25:40 +00001440 error conditions</li>
Daniel Veillard92fc02c2003-04-24 23:12:35 +00001441 <li>extended the API to be able to plug a garbage collecting memory
1442 allocator, added xmlMallocAtomic() and modified the allocations
1443 accordingly.</li>
1444 <li>Performances: removed excessive malloc() calls, speedup of the push and
1445 xmlReader interfaces, removed excessive thread locking</li>
1446 <li>Documentation: man page (John Fleck), xmlReader documentation</li>
1447 <li>Python: adding binding for xmlCatalogAddLocal (Brent M Hendricks)</li>
1448</ul>
1449
Daniel Veillardc2d4a932003-04-01 11:13:05 +00001450<h3>2.5.6: Apr 1 2003</h3>
1451<ul>
1452 <li>Fixed W3C XML Schemas datatype, should be compliant now except for
1453 binHex and base64 which are not supported yet.</li>
1454 <li>bug fixes: non-ASCII IDs, HTML output, XInclude on large docs and
1455 XInclude entities handling, encoding detection on external subsets, XML
1456 Schemas bugs and memory leaks, HTML parser (James Bursa)</li>
1457 <li>portability: python/trio (Albert Chin), Sun compiler warnings</li>
1458 <li>documentation: added --relaxng option to xmllint man page (John)</li>
1459 <li>improved error reporting: xml:space, start/end tag mismatches, Relax NG
1460 errors</li>
1461</ul>
1462
1463<h3>2.5.5: Mar 24 2003</h3>
Daniel Veillardd8da01c2003-03-24 15:58:23 +00001464<ul>
1465 <li>Lot of fixes on the Relax NG implementation. More testing including
1466 DocBook and TEI examples.</li>
1467 <li>Increased the support for W3C XML Schemas datatype</li>
1468 <li>Several bug fixes in the URI handling layer</li>
1469 <li>Bug fixes: HTML parser, xmlReader, DTD validation, XPath, encoding
1470 conversion, line counting in the parser.</li>
1471 <li>Added support for $XMLLINT_INDENT environment variable, FTP delete</li>
1472 <li>Fixed the RPM spec file name</li>
1473</ul>
1474
Daniel Veillard17bed982003-02-24 20:11:43 +00001475<h3>2.5.4: Feb 20 2003</h3>
1476<ul>
1477 <li>Conformance testing and lot of fixes on Relax NG and XInclude
1478 implementation</li>
1479 <li>Implementation of XPointer element() scheme</li>
1480 <li>Bug fixes: XML parser, XInclude entities merge, validity checking on
1481 namespaces,
1482 <p>2 serialization bugs, node info generation problems, a DTD regexp
1483 generation problem.</p>
1484 </li>
1485 <li>Portability: windows updates and path canonicalization (Igor)</li>
1486 <li>A few typo fixes (Kjartan Maraas)</li>
1487 <li>Python bindings generator fixes (Stephane Bidoul)</li>
1488</ul>
1489
Daniel Veillard1d788d22003-02-10 16:21:58 +00001490<h3>2.5.3: Feb 10 2003</h3>
1491<ul>
1492 <li>RelaxNG and XML Schemas datatypes improvements, and added a first
1493 version of RelaxNG Python bindings</li>
1494 <li>Fixes: XLink (Sean Chittenden), XInclude (Sean Chittenden), API fix for
1495 serializing namespace nodes, encoding conversion bug, XHTML1
1496 serialization</li>
1497 <li>Portability fixes: Windows (Igor), AMD 64bits RPM spec file</li>
1498</ul>
1499
Daniel Veillard72fef162003-02-05 14:31:19 +00001500<h3>2.5.2: Feb 5 2003</h3>
1501<ul>
1502 <li>First implementation of RelaxNG, added --relaxng flag to xmllint</li>
1503 <li>Schemas support now compiled in by default.</li>
1504 <li>Bug fixes: DTD validation, namespace checking, XInclude and entities,
1505 delegateURI in XML Catalogs, HTML parser, XML reader (Stéphane Bidoul),
1506 XPath parser and evaluation, UTF8ToUTF8 serialization, XML reader memory
1507 consumption, HTML parser, HTML serialization in the presence of
1508 namespaces</li>
1509 <li>added an HTML API to check elements and attributes.</li>
1510 <li>Documentation improvement, PDF for the tutorial (John Fleck), doc
1511 patches (Stefan Kost)</li>
1512 <li>Portability fixes: NetBSD (Julio Merino), Windows (Igor Zlatkovic)</li>
1513 <li>Added python bindings for XPointer, contextual error reporting
1514 (Stéphane Bidoul)</li>
1515 <li>URI/file escaping problems (Stefano Zacchiroli)</li>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +00001516</ul>
1517
Daniel Veillarde2830f12003-01-08 17:47:49 +00001518<h3>2.5.1: Jan 8 2003</h3>
1519<ul>
1520 <li>Fixes a memory leak and configuration/compilation problems in 2.5.0</li>
1521 <li>documentation updates (John)</li>
1522 <li>a couple of XmlTextReader fixes</li>
1523</ul>
1524
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00001525<h3>2.5.0: Jan 6 2003</h3>
1526<ul>
1527 <li>New <a href="xmlreader.html">XmltextReader interface</a> based on C#
1528 API (with help of Stéphane Bidoul)</li>
1529 <li>Windows: more exports, including the new API (Igor)</li>
1530 <li>XInclude fallback fix</li>
1531 <li>Python: bindings for the new API, packaging (Stéphane Bidoul),
1532 drv_libxml2.py Python xml.sax driver (Stéphane Bidoul), fixes, speedup
1533 and iterators for Python-2.2 (Hannu Krosing)</li>
1534 <li>Tutorial fixes (john Fleck and Niraj Tolia) xmllint man update
1535 (John)</li>
1536 <li>Fix an XML parser bug raised by Vyacheslav Pindyura</li>
1537 <li>Fix for VMS serialization (Nigel Hall) and config (Craig A. Berry)</li>
1538 <li>Entities handling fixes</li>
1539 <li>new API to optionally track node creation and deletion (Lukas
1540 Schroeder)</li>
1541 <li>Added documentation for the XmltextReader interface and some <a
1542 href="guidelines.html">XML guidelines</a></li>
1543</ul>
1544
Daniel Veillardc1eed322002-12-12 11:01:32 +00001545<h3>2.4.30: Dec 12 2002</h3>
1546<ul>
1547 <li>2.4.29 broke the python bindings, rereleasing</li>
1548 <li>Improvement/fixes of the XML API generator, and couple of minor code
1549 fixes.</li>
1550</ul>
1551
Daniel Veillard9b4bb4d2002-12-11 19:28:47 +00001552<h3>2.4.29: Dec 11 2002</h3>
1553<ul>
1554 <li>Windows fixes (Igor): Windows CE port, pthread linking, python bindings
1555 (Stéphane Bidoul), Mingw (Magnus Henoch), and export list updates</li>
1556 <li>Fix for prev in python bindings (ERDI Gergo)</li>
1557 <li>Fix for entities handling (Marcus Clarke)</li>
1558 <li>Refactored the XML and HTML dumps to a single code path, fixed XHTML1
1559 dump</li>
1560 <li>Fix for URI parsing when handling URNs with fragment identifiers</li>
1561 <li>Fix for HTTP URL escaping problem</li>
1562 <li>added an TextXmlReader (C#) like API (work in progress)</li>
1563 <li>Rewrote the API in XML generation script, includes a C parser and saves
1564 more informations needed for C# bindings</li>
1565</ul>
1566
Daniel Veillardf9c4cad2002-11-22 15:57:07 +00001567<h3>2.4.28: Nov 22 2002</h3>
1568<ul>
1569 <li>a couple of python binding fixes</li>
1570 <li>2 bug fixes in the XML push parser</li>
1571 <li>potential memory leak removed (Martin Stoilov)</li>
1572 <li>fix to the configure script for Unix (Dimitri Papadopoulos)</li>
1573 <li>added encoding support for XInclude parse="text"</li>
1574 <li>autodetection of XHTML1 and specific serialization rules added</li>
Daniel Veillard9b4bb4d2002-12-11 19:28:47 +00001575 <li>nasty threading bug fixed (William Brack)</li>
Daniel Veillardf9c4cad2002-11-22 15:57:07 +00001576</ul>
1577
Daniel Veillarddad3f682002-11-17 16:47:27 +00001578<h3>2.4.27: Nov 17 2002</h3>
1579<ul>
1580 <li>fixes for the Python bindings</li>
1581 <li>a number of bug fixes: SGML catalogs, xmlParseBalancedChunkMemory(),
1582 HTML parser, Schemas (Charles Bozeman), document fragment support
1583 (Christian Glahn), xmlReconciliateNs (Brian Stafford), XPointer,
1584 xmlFreeNode(), xmlSAXParseMemory (Peter Jones), xmlGetNodePath (Petr
1585 Pajas), entities processing</li>
1586 <li>added grep to xmllint --shell</li>
1587 <li>VMS update patch from Craig A. Berry</li>
1588 <li>cleanup of the Windows build with support for more compilers (Igor),
1589 better thread support on Windows</li>
1590 <li>cleanup of Unix Makefiles and spec file</li>
1591 <li>Improvements to the documentation (John Fleck)</li>
1592</ul>
1593
Daniel Veillard48267432002-10-18 11:21:38 +00001594<h3>2.4.26: Oct 18 2002</h3>
1595<ul>
1596 <li>Patches for Windows CE port, improvements on Windows paths handling</li>
1597 <li>Fixes to the validation code (DTD and Schemas), xmlNodeGetPath() ,
1598 HTML serialization, Namespace compliance, and a number of small
1599 problems</li>
1600</ul>
1601
Daniel Veillarde16b5742002-09-26 17:50:03 +00001602<h3>2.4.25: Sep 26 2002</h3>
1603<ul>
1604 <li>A number of bug fixes: XPath, validation, Python bindings, DOM and
1605 tree, xmlI/O, Html</li>
1606 <li>Serious rewrite of XInclude</li>
1607 <li>Made XML Schemas regexp part of the default build and APIs, small fix
1608 and improvement of the regexp core</li>
1609 <li>Changed the validation code to reuse XML Schemas regexp APIs</li>
1610 <li>Better handling of Windows file paths, improvement of Makefiles (Igor,
1611 Daniel Gehriger, Mark Vakoc)</li>
1612 <li>Improved the python I/O bindings, the tests, added resolver and regexp
Daniel Veillard321be0c2002-10-08 21:26:42 +00001613 APIs</li>
Daniel Veillarde16b5742002-09-26 17:50:03 +00001614 <li>New logos from Marc Liyanage</li>
1615 <li>Tutorial improvements: John Fleck, Christopher Harris</li>
1616 <li>Makefile: Fixes for AMD x86_64 (Mandrake), DESTDIR (Christophe
1617 Merlet)</li>
1618 <li>removal of all stderr/perror use for error reporting</li>
1619 <li>Better error reporting: XPath and DTD validation</li>
1620 <li>update of the trio portability layer (Bjorn Reese)</li>
1621</ul>
1622
Daniel Veillard42766c02002-08-22 20:52:17 +00001623<p><strong>2.4.24: Aug 22 2002</strong></p>
1624<ul>
1625 <li>XPath fixes (William), xf:escape-uri() (Wesley Terpstra)</li>
1626 <li>Python binding fixes: makefiles (William), generator, rpm build, x86-64
1627 (fcrozat)</li>
1628 <li>HTML &lt;style&gt; and boolean attributes serializer fixes</li>
1629 <li>C14N improvements by Aleksey</li>
Daniel Veillarde1662542002-08-28 11:50:59 +00001630 <li>doc cleanups: Rick Jones</li>
Daniel Veillard42766c02002-08-22 20:52:17 +00001631 <li>Windows compiler makefile updates: Igor and Elizabeth Barham</li>
1632 <li>XInclude: implementation of fallback and xml:base fixup added</li>
1633</ul>
1634
Daniel Veillard782afda2002-07-08 15:12:49 +00001635<h3>2.4.23: July 6 2002</h3>
1636<ul>
1637 <li>performances patches: Peter Jacobi</li>
1638 <li>c14n fixes, testsuite and performances: Aleksey Sanin</li>
1639 <li>added xmlDocFormatDump: Chema Celorio</li>
1640 <li>new tutorial: John Fleck</li>
1641 <li>new hash functions and performances: Sander Vesik, portability fix from
1642 Peter Jacobi</li>
1643 <li>a number of bug fixes: XPath (William Brack, Richard Jinks), XML and
1644 HTML parsers, ID lookup function</li>
1645 <li>removal of all remaining sprintf: Aleksey Sanin</li>
1646</ul>
1647
Daniel Veillardc0801af2002-05-28 16:28:42 +00001648<h3>2.4.22: May 27 2002</h3>
1649<ul>
1650 <li>a number of bug fixes: configure scripts, base handling, parser, memory
1651 usage, HTML parser, XPath, documentation (Christian Cornelssen),
Daniel Veillard21473672002-06-17 07:29:22 +00001652 indentation, URI parsing</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00001653 <li>Optimizations for XMLSec, fixing and making public some of the network
1654 protocol handlers (Aleksey)</li>
1655 <li>performance patch from Gary Pennington</li>
1656 <li>Charles Bozeman provided date and time support for XML Schemas
1657 datatypes</li>
1658</ul>
1659
Daniel Veillardcf27f7c2002-04-30 07:12:39 +00001660<h3>2.4.21: Apr 29 2002</h3>
1661
1662<p>This release is both a bug fix release and also contains the early XML
1663Schemas <a href="http://www.w3.org/TR/xmlschema-1/">structures</a> and <a
1664href="http://www.w3.org/TR/xmlschema-2/">datatypes</a> code, beware, all
1665interfaces are likely to change, there is huge holes, it is clearly a work in
1666progress and don't even think of putting this code in a production system,
Daniel Veillarde6d8e202002-05-02 06:11:10 +00001667it's actually not compiled in by default. The real fixes are:</p>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +00001668<ul>
1669 <li>a couple of bugs or limitations introduced in 2.4.20</li>
1670 <li>patches for Borland C++ and MSC by Igor</li>
1671 <li>some fixes on XPath strings and conformance patches by Richard
1672 Jinks</li>
1673 <li>patch from Aleksey for the ExcC14N specification</li>
1674 <li>OSF/1 bug fix by Bjorn</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00001675</ul>
1676
Daniel Veillarda7084cd2002-04-15 17:12:47 +00001677<h3>2.4.20: Apr 15 2002</h3>
1678<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00001679 <li>bug fixes: file descriptor leak, XPath, HTML output, DTD validation</li>
Daniel Veillarda7084cd2002-04-15 17:12:47 +00001680 <li>XPath conformance testing by Richard Jinks</li>
1681 <li>Portability fixes: Solaris, MPE/iX, Windows, OSF/1, python bindings,
1682 libxml.m4</li>
1683</ul>
1684
Daniel Veillard19274092002-03-25 16:48:03 +00001685<h3>2.4.19: Mar 25 2002</h3>
1686<ul>
1687 <li>bug fixes: half a dozen XPath bugs, Validation, ISO-Latin to UTF8
1688 encoder</li>
1689 <li>portability fixes in the HTTP code</li>
Daniel Veillardb2fb8ed2002-04-01 09:33:12 +00001690 <li>memory allocation checks using valgrind, and profiling tests</li>
Daniel Veillard19274092002-03-25 16:48:03 +00001691 <li>revamp of the Windows build and Makefiles</li>
1692</ul>
1693
Daniel Veillard34ce8be2002-03-18 19:37:11 +00001694<h3>2.4.18: Mar 18 2002</h3>
1695<ul>
1696 <li>bug fixes: tree, SAX, canonicalization, validation, portability,
Daniel Veillard63d83142002-05-20 06:51:05 +00001697 XPath</li>
Daniel Veillard34ce8be2002-03-18 19:37:11 +00001698 <li>removed the --with-buffer option it was becoming unmaintainable</li>
1699 <li>serious cleanup of the Python makefiles</li>
1700 <li>speedup patch to XPath very effective for DocBook stylesheets</li>
1701 <li>Fixes for Windows build, cleanup of the documentation</li>
1702</ul>
1703
Daniel Veillardaf43f632002-03-08 15:05:20 +00001704<h3>2.4.17: Mar 8 2002</h3>
1705<ul>
1706 <li>a lot of bug fixes, including "namespace nodes have no parents in
1707 XPath"</li>
1708 <li>fixed/improved the Python wrappers, added more examples and more
1709 regression tests, XPath extension functions can now return node-sets</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001710 <li>added the XML Canonicalization support from Aleksey Sanin</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001711</ul>
1712
Daniel Veillard5f4b5992002-02-20 10:22:49 +00001713<h3>2.4.16: Feb 20 2002</h3>
1714<ul>
1715 <li>a lot of bug fixes, most of them were triggered by the XML Testsuite
1716 from OASIS and W3C. Compliance has been significantly improved.</li>
1717 <li>a couple of portability fixes too.</li>
1718</ul>
1719
Daniel Veillard397ff112002-02-11 18:27:20 +00001720<h3>2.4.15: Feb 11 2002</h3>
1721<ul>
1722 <li>Fixed the Makefiles, especially the python module ones</li>
1723 <li>A few bug fixes and cleanup</li>
1724 <li>Includes cleanup</li>
1725</ul>
1726
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +00001727<h3>2.4.14: Feb 8 2002</h3>
1728<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00001729 <li>Change of License to the <a
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +00001730 href="http://www.opensource.org/licenses/mit-license.html">MIT
Daniel Veillard63d83142002-05-20 06:51:05 +00001731 License</a> basically for integration in XFree86 codebase, and removing
1732 confusion around the previous dual-licensing</li>
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +00001733 <li>added Python bindings, beta software but should already be quite
1734 complete</li>
1735 <li>a large number of fixes and cleanups, especially for all tree
1736 manipulations</li>
1737 <li>cleanup of the headers, generation of a reference API definition in
1738 XML</li>
1739</ul>
1740
1741<h3>2.4.13: Jan 14 2002</h3>
Daniel Veillard744683d2002-01-14 17:30:20 +00001742<ul>
1743 <li>update of the documentation: John Fleck and Charlie Bozeman</li>
1744 <li>cleanup of timing code from Justin Fletcher</li>
1745 <li>fixes for Windows and initial thread support on Win32: Igor and Serguei
1746 Narojnyi</li>
1747 <li>Cygwin patch from Robert Collins</li>
1748 <li>added xmlSetEntityReferenceFunc() for Keith Isdale work on xsldbg</li>
1749</ul>
1750
Daniel Veillardef90ba72001-12-07 14:24:22 +00001751<h3>2.4.12: Dec 7 2001</h3>
1752<ul>
1753 <li>a few bug fixes: thread (Gary Pennington), xmllint (Geert Kloosterman),
1754 XML parser (Robin Berjon), XPointer (Danny Jamshy), I/O cleanups
1755 (robert)</li>
1756 <li>Eric Lavigne contributed project files for MacOS</li>
1757 <li>some makefiles cleanups</li>
1758</ul>
1759
Daniel Veillarda4871052001-11-26 13:19:48 +00001760<h3>2.4.11: Nov 26 2001</h3>
1761<ul>
1762 <li>fixed a couple of errors in the includes, fixed a few bugs, some code
1763 cleanups</li>
1764 <li>xmllint man pages improvement by Heiko Rupp</li>
1765 <li>updated VMS build instructions from John A Fotheringham</li>
1766 <li>Windows Makefiles updates from Igor</li>
1767</ul>
1768
Daniel Veillard43d3f612001-11-10 11:57:23 +00001769<h3>2.4.10: Nov 10 2001</h3>
1770<ul>
1771 <li>URI escaping fix (Joel Young)</li>
1772 <li>added xmlGetNodePath() (for paths or XPointers generation)</li>
1773 <li>Fixes namespace handling problems when using DTD and validation</li>
1774 <li>improvements on xmllint: Morus Walter patches for --format and
1775 --encode, Stefan Kost and Heiko Rupp improvements on the --shell</li>
1776 <li>fixes for xmlcatalog linking pointed by Weiqi Gao</li>
1777 <li>fixes to the HTML parser</li>
1778</ul>
1779
1780<h3>2.4.9: Nov 6 2001</h3>
1781<ul>
1782 <li>fixes more catalog bugs</li>
1783 <li>avoid a compilation problem, improve xmlGetLineNo()</li>
1784</ul>
1785
Daniel Veillarded421aa2001-11-04 21:22:45 +00001786<h3>2.4.8: Nov 4 2001</h3>
1787<ul>
1788 <li>fixed SGML catalogs broken in previous release, updated xmlcatalog
1789 tool</li>
1790 <li>fixed a compile errors and some includes troubles.</li>
1791</ul>
1792
Daniel Veillard52dcab32001-10-30 12:51:17 +00001793<h3>2.4.7: Oct 30 2001</h3>
1794<ul>
1795 <li>exported some debugging interfaces</li>
1796 <li>serious rewrite of the catalog code</li>
1797 <li>integrated Gary Pennington thread safety patch, added configure option
1798 and regression tests</li>
1799 <li>removed an HTML parser bug</li>
1800 <li>fixed a couple of potentially serious validation bugs</li>
1801 <li>integrated the SGML DocBook support in xmllint</li>
1802 <li>changed the nanoftp anonymous login passwd</li>
1803 <li>some I/O cleanup and a couple of interfaces for Perl wrapper</li>
1804 <li>general bug fixes</li>
1805 <li>updated xmllint man page by John Fleck</li>
1806 <li>some VMS and Windows updates</li>
1807</ul>
1808
Daniel Veillard60087f32001-10-10 09:45:09 +00001809<h3>2.4.6: Oct 10 2001</h3>
1810<ul>
Daniel Veillard52dcab32001-10-30 12:51:17 +00001811 <li>added an updated man pages by John Fleck</li>
Daniel Veillard60087f32001-10-10 09:45:09 +00001812 <li>portability and configure fixes</li>
1813 <li>an infinite loop on the HTML parser was removed (William)</li>
1814 <li>Windows makefile patches from Igor</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001815 <li>fixed half a dozen bugs reported for libxml or libxslt</li>
Daniel Veillard60087f32001-10-10 09:45:09 +00001816 <li>updated xmlcatalog to be able to modify SGML super catalogs</li>
1817</ul>
1818
Daniel Veillarddadd0872001-09-15 09:21:44 +00001819<h3>2.4.5: Sep 14 2001</h3>
1820<ul>
1821 <li>Remove a few annoying bugs in 2.4.4</li>
1822 <li>forces the HTML serializer to output decimal charrefs since some
1823 version of Netscape can't handle hexadecimal ones</li>
1824</ul>
1825
1826<h3>1.8.16: Sep 14 2001</h3>
1827<ul>
1828 <li>maintenance release of the old libxml1 branch, couple of bug and
1829 portability fixes</li>
1830</ul>
1831
Daniel Veillard04382ae2001-09-12 18:51:30 +00001832<h3>2.4.4: Sep 12 2001</h3>
1833<ul>
1834 <li>added --convert to xmlcatalog, bug fixes and cleanups of XML
1835 Catalog</li>
1836 <li>a few bug fixes and some portability changes</li>
1837 <li>some documentation cleanups</li>
1838</ul>
1839
Daniel Veillard39936902001-08-24 00:49:01 +00001840<h3>2.4.3: Aug 23 2001</h3>
1841<ul>
1842 <li>XML Catalog support see the doc</li>
1843 <li>New NaN/Infinity floating point code</li>
1844 <li>A few bug fixes</li>
1845</ul>
1846
1847<h3>2.4.2: Aug 15 2001</h3>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001848<ul>
1849 <li>adds xmlLineNumbersDefault() to control line number generation</li>
1850 <li>lot of bug fixes</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001851 <li>the Microsoft MSC projects files should now be up to date</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001852 <li>inheritance of namespaces from DTD defaulted attributes</li>
1853 <li>fixes a serious potential security bug</li>
1854 <li>added a --format option to xmllint</li>
1855</ul>
1856
1857<h3>2.4.1: July 24 2001</h3>
1858<ul>
1859 <li>possibility to keep line numbers in the tree</li>
1860 <li>some computation NaN fixes</li>
1861 <li>extension of the XPath API</li>
1862 <li>cleanup for alpha and ia64 targets</li>
1863 <li>patch to allow saving through HTTP PUT or POST</li>
Daniel Veillard09ab7e12001-07-10 15:49:44 +00001864</ul>
1865
1866<h3>2.4.0: July 10 2001</h3>
1867<ul>
1868 <li>Fixed a few bugs in XPath, validation, and tree handling.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001869 <li>Fixed XML Base implementation, added a couple of examples to the
Daniel Veillard09ab7e12001-07-10 15:49:44 +00001870 regression tests</li>
1871 <li>A bit of cleanup</li>
Daniel Veillardab8500d2000-10-15 21:06:19 +00001872</ul>
1873
Daniel Veillard5b43fde2001-07-05 23:31:40 +00001874<h3>2.3.14: July 5 2001</h3>
1875<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00001876 <li>fixed some entities problems and reduce memory requirement when
1877 substituting them</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +00001878 <li>lots of improvements in the XPath queries interpreter can be
Daniel Veillard63d83142002-05-20 06:51:05 +00001879 substantially faster</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +00001880 <li>Makefiles and configure cleanups</li>
1881 <li>Fixes to XPath variable eval, and compare on empty node set</li>
1882 <li>HTML tag closing bug fixed</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001883 <li>Fixed an URI reference computation problem when validating</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +00001884</ul>
1885
Daniel Veillard2adbb512001-06-28 16:20:36 +00001886<h3>2.3.13: June 28 2001</h3>
1887<ul>
1888 <li>2.3.12 configure.in was broken as well as the push mode XML parser</li>
1889 <li>a few more fixes for compilation on Windows MSC by Yon Derek</li>
1890</ul>
1891
1892<h3>1.8.14: June 28 2001</h3>
1893<ul>
1894 <li>Zbigniew Chyla gave a patch to use the old XML parser in push mode</li>
1895 <li>Small Makefile fix</li>
1896</ul>
1897
Daniel Veillard11648102001-06-26 16:08:24 +00001898<h3>2.3.12: June 26 2001</h3>
1899<ul>
1900 <li>lots of cleanup</li>
1901 <li>a couple of validation fix</li>
1902 <li>fixed line number counting</li>
1903 <li>fixed serious problems in the XInclude processing</li>
1904 <li>added support for UTF8 BOM at beginning of entities</li>
1905 <li>fixed a strange gcc optimizer bugs in xpath handling of float, gcc-3.0
1906 miscompile uri.c (William), Thomas Leitner provided a fix for the
1907 optimizer on Tru64</li>
1908 <li>incorporated Yon Derek and Igor Zlatkovic fixes and improvements for
1909 compilation on Windows MSC</li>
1910 <li>update of libxml-doc.el (Felix Natter)</li>
1911 <li>fixed 2 bugs in URI normalization code</li>
1912</ul>
1913
Daniel Veillarde3c81b52001-06-17 14:50:34 +00001914<h3>2.3.11: June 17 2001</h3>
1915<ul>
1916 <li>updates to trio, Makefiles and configure should fix some portability
1917 problems (alpha)</li>
1918 <li>fixed some HTML serialization problems (pre, script, and block/inline
1919 handling), added encoding aware APIs, cleanup of this code</li>
1920 <li>added xmlHasNsProp()</li>
1921 <li>implemented a specific PI for encoding support in the DocBook SGML
1922 parser</li>
1923 <li>some XPath fixes (-Infinity, / as a function parameter and namespaces
1924 node selection)</li>
1925 <li>fixed a performance problem and an error in the validation code</li>
1926 <li>fixed XInclude routine to implement the recursive behaviour</li>
1927 <li>fixed xmlFreeNode problem when libxml is included statically twice</li>
1928 <li>added --version to xmllint for bug reports</li>
1929</ul>
1930
Daniel Veillard2e4f1882001-06-01 10:11:57 +00001931<h3>2.3.10: June 1 2001</h3>
1932<ul>
1933 <li>fixed the SGML catalog support</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001934 <li>a number of reported bugs got fixed, in XPath, iconv detection,
1935 XInclude processing</li>
Daniel Veillard2e4f1882001-06-01 10:11:57 +00001936 <li>XPath string function should now handle unicode correctly</li>
1937</ul>
1938
Daniel Veillard4623acd2001-05-19 15:13:15 +00001939<h3>2.3.9: May 19 2001</h3>
1940
1941<p>Lots of bugfixes, and added a basic SGML catalog support:</p>
1942<ul>
1943 <li>HTML push bugfix #54891 and another patch from Jonas Borgström</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001944 <li>some serious speed optimization again</li>
Daniel Veillard4623acd2001-05-19 15:13:15 +00001945 <li>some documentation cleanups</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001946 <li>trying to get better linking on Solaris (-R)</li>
Daniel Veillard4623acd2001-05-19 15:13:15 +00001947 <li>XPath API cleanup from Thomas Broyer</li>
1948 <li>Validation bug fixed #54631, added a patch from Gary Pennington, fixed
1949 xmlValidGetValidElements()</li>
1950 <li>Added an INSTALL file</li>
1951 <li>Attribute removal added to API: #54433</li>
1952 <li>added a basic support for SGML catalogs</li>
1953 <li>fixed xmlKeepBlanksDefault(0) API</li>
1954 <li>bugfix in xmlNodeGetLang()</li>
1955 <li>fixed a small configure portability problem</li>
1956 <li>fixed an inversion of SYSTEM and PUBLIC identifier in HTML document</li>
1957</ul>
1958
Daniel Veillarda265af72001-05-14 11:13:58 +00001959<h3>1.8.13: May 14 2001</h3>
1960<ul>
1961 <li>bugfixes release of the old libxml1 branch used by Gnome</li>
1962</ul>
1963
Daniel Veillard3bbbe6f2001-05-03 11:15:37 +00001964<h3>2.3.8: May 3 2001</h3>
1965<ul>
1966 <li>Integrated an SGML DocBook parser for the Gnome project</li>
1967 <li>Fixed a few things in the HTML parser</li>
1968 <li>Fixed some XPath bugs raised by XSLT use, tried to fix the floating
1969 point portability issue</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001970 <li>Speed improvement (8M/s for SAX, 3M/s for DOM, 1.5M/s for
1971 DOM+validation using the XML REC as input and a 700MHz celeron).</li>
Daniel Veillard3bbbe6f2001-05-03 11:15:37 +00001972 <li>incorporated more Windows cleanup</li>
1973 <li>added xmlSaveFormatFile()</li>
1974 <li>fixed problems in copying nodes with entities references (gdome)</li>
1975 <li>removed some troubles surrounding the new validation module</li>
1976</ul>
1977
Daniel Veillarda41123c2001-04-22 19:31:20 +00001978<h3>2.3.7: April 22 2001</h3>
1979<ul>
1980 <li>lots of small bug fixes, corrected XPointer</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001981 <li>Non deterministic content model validation support</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +00001982 <li>added xmlDocCopyNode for gdome2</li>
1983 <li>revamped the way the HTML parser handles end of tags</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001984 <li>XPath: corrections of namespaces support and number formatting</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +00001985 <li>Windows: Igor Zlatkovic patches for MSC compilation</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001986 <li>HTML output fixes from P C Chow and William M. Brack</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +00001987 <li>Improved validation speed sensible for DocBook</li>
1988 <li>fixed a big bug with ID declared in external parsed entities</li>
1989 <li>portability fixes, update of Trio from Bjorn Reese</li>
1990</ul>
1991
Daniel Veillardafc73112001-04-11 11:51:41 +00001992<h3>2.3.6: April 8 2001</h3>
1993<ul>
1994 <li>Code cleanup using extreme gcc compiler warning options, found and
1995 cleared half a dozen potential problem</li>
1996 <li>the Eazel team found an XML parser bug</li>
1997 <li>cleaned up the user of some of the string formatting function. used the
1998 trio library code to provide the one needed when the platform is missing
1999 them</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002000 <li>xpath: removed a memory leak and fixed the predicate evaluation
2001 problem, extended the testsuite and cleaned up the result. XPointer seems
2002 broken ...</li>
Daniel Veillardafc73112001-04-11 11:51:41 +00002003</ul>
2004
Daniel Veillard56a4cb82001-03-24 17:00:36 +00002005<h3>2.3.5: Mar 23 2001</h3>
2006<ul>
2007 <li>Biggest change is separate parsing and evaluation of XPath expressions,
2008 there is some new APIs for this too</li>
2009 <li>included a number of bug fixes(XML push parser, 51876, notations,
2010 52299)</li>
2011 <li>Fixed some portability issues</li>
2012</ul>
2013
Daniel Veillarde356c282001-03-10 12:32:04 +00002014<h3>2.3.4: Mar 10 2001</h3>
2015<ul>
2016 <li>Fixed bugs #51860 and #51861</li>
2017 <li>Added a global variable xmlDefaultBufferSize to allow default buffer
2018 size to be application tunable.</li>
2019 <li>Some cleanup in the validation code, still a bug left and this part
2020 should probably be rewritten to support ambiguous content model :-\</li>
2021 <li>Fix a couple of serious bugs introduced or raised by changes in 2.3.3
2022 parser</li>
2023 <li>Fixed another bug in xmlNodeGetContent()</li>
2024 <li>Bjorn fixed XPath node collection and Number formatting</li>
2025 <li>Fixed a loop reported in the HTML parsing</li>
2026 <li>blank space are reported even if the Dtd content model proves that they
Daniel Veillard63d83142002-05-20 06:51:05 +00002027 are formatting spaces, this is for XML conformance</li>
Daniel Veillarde356c282001-03-10 12:32:04 +00002028</ul>
2029
Daniel Veillardb402c072001-03-01 17:28:58 +00002030<h3>2.3.3: Mar 1 2001</h3>
2031<ul>
2032 <li>small change in XPath for XSLT</li>
2033 <li>documentation cleanups</li>
2034 <li>fix in validation by Gary Pennington</li>
2035 <li>serious parsing performances improvements</li>
2036</ul>
2037
Daniel Veillardec70e912001-02-26 20:10:45 +00002038<h3>2.3.2: Feb 24 2001</h3>
Daniel Veillard71681102001-02-24 17:48:53 +00002039<ul>
2040 <li>chasing XPath bugs, found a bunch, completed some TODO</li>
2041 <li>fixed a Dtd parsing bug</li>
2042 <li>fixed a bug in xmlNodeGetContent</li>
2043 <li>ID/IDREF support partly rewritten by Gary Pennington</li>
2044</ul>
2045
Daniel Veillardec70e912001-02-26 20:10:45 +00002046<h3>2.3.1: Feb 15 2001</h3>
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +00002047<ul>
2048 <li>some XPath and HTML bug fixes for XSLT</li>
2049 <li>small extension of the hash table interfaces for DOM gdome2
2050 implementation</li>
2051 <li>A few bug fixes</li>
2052</ul>
2053
Daniel Veillardec70e912001-02-26 20:10:45 +00002054<h3>2.3.0: Feb 8 2001 (2.2.12 was on 25 Jan but I didn't kept track)</h3>
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +00002055<ul>
2056 <li>Lots of XPath bug fixes</li>
2057 <li>Add a mode with Dtd lookup but without validation error reporting for
2058 XSLT</li>
2059 <li>Add support for text node without escaping (XSLT)</li>
2060 <li>bug fixes for xmlCheckFilename</li>
2061 <li>validation code bug fixes from Gary Pennington</li>
2062 <li>Patch from Paul D. Smith correcting URI path normalization</li>
2063 <li>Patch to allow simultaneous install of libxml-devel and
2064 libxml2-devel</li>
2065 <li>the example Makefile is now fixed</li>
2066 <li>added HTML to the RPM packages</li>
2067 <li>tree copying bugfixes</li>
2068 <li>updates to Windows makefiles</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002069 <li>optimization patch from Bjorn Reese</li>
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +00002070</ul>
2071
Daniel Veillardec70e912001-02-26 20:10:45 +00002072<h3>2.2.11: Jan 4 2001</h3>
Daniel Veillard503b8932001-01-05 06:36:31 +00002073<ul>
2074 <li>bunch of bug fixes (memory I/O, xpath, ftp/http, ...)</li>
2075 <li>added htmlHandleOmittedElem()</li>
2076 <li>Applied Bjorn Reese's IPV6 first patch</li>
2077 <li>Applied Paul D. Smith patches for validation of XInclude results</li>
Daniel Veillard82687162001-01-22 15:32:01 +00002078 <li>added XPointer xmlns() new scheme support</li>
Daniel Veillard503b8932001-01-05 06:36:31 +00002079</ul>
2080
Daniel Veillard2ddd23d2000-11-25 10:42:19 +00002081<h3>2.2.10: Nov 25 2000</h3>
Daniel Veillard9d343c42000-11-25 10:12:43 +00002082<ul>
2083 <li>Fix the Windows problems of 2.2.8</li>
2084 <li>integrate OpenVMS patches</li>
2085 <li>better handling of some nasty HTML input</li>
2086 <li>Improved the XPointer implementation</li>
2087 <li>integrate a number of provided patches</li>
2088</ul>
2089
Daniel Veillard2ddd23d2000-11-25 10:42:19 +00002090<h3>2.2.9: Nov 25 2000</h3>
2091<ul>
2092 <li>erroneous release :-(</li>
2093</ul>
2094
Daniel Veillard28929b22000-11-13 18:22:49 +00002095<h3>2.2.8: Nov 13 2000</h3>
2096<ul>
2097 <li>First version of <a href="http://www.w3.org/TR/xinclude">XInclude</a>
2098 support</li>
2099 <li>Patch in conditional section handling</li>
2100 <li>updated MS compiler project</li>
2101 <li>fixed some XPath problems</li>
2102 <li>added an URI escaping function</li>
2103 <li>some other bug fixes</li>
2104</ul>
2105
2106<h3>2.2.7: Oct 31 2000</h3>
2107<ul>
2108 <li>added message redirection</li>
2109 <li>XPath improvements (thanks TOM !)</li>
2110 <li>xmlIOParseDTD() added</li>
2111 <li>various small fixes in the HTML, URI, HTTP and XPointer support</li>
2112 <li>some cleanup of the Makefile, autoconf and the distribution content</li>
2113</ul>
2114
Daniel Veillard29a11cc2000-10-25 13:32:39 +00002115<h3>2.2.6: Oct 25 2000:</h3>
2116<ul>
2117 <li>Added an hash table module, migrated a number of internal structure to
2118 those</li>
2119 <li>Fixed a posteriori validation problems</li>
2120 <li>HTTP module cleanups</li>
2121 <li>HTML parser improvements (tag errors, script/style handling, attribute
2122 normalization)</li>
2123 <li>coalescing of adjacent text nodes</li>
2124 <li>couple of XPath bug fixes, exported the internal API</li>
2125</ul>
2126
Daniel Veillardab8500d2000-10-15 21:06:19 +00002127<h3>2.2.5: Oct 15 2000:</h3>
Daniel Veillard4c3a2031999-11-19 17:46:26 +00002128<ul>
Daniel Veillard189446d2000-10-13 10:23:06 +00002129 <li>XPointer implementation and testsuite</li>
2130 <li>Lot of XPath fixes, added variable and functions registration, more
2131 tests</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002132 <li>Portability fixes, lots of enhancements toward an easy Windows build
2133 and release</li>
Daniel Veillard189446d2000-10-13 10:23:06 +00002134 <li>Late validation fixes</li>
2135 <li>Integrated a lot of contributed patches</li>
2136 <li>added memory management docs</li>
Daniel Veillardab8500d2000-10-15 21:06:19 +00002137 <li>a performance problem when using large buffer seems fixed</li>
Daniel Veillard189446d2000-10-13 10:23:06 +00002138</ul>
2139
2140<h3>2.2.4: Oct 1 2000:</h3>
2141<ul>
2142 <li>main XPath problem fixed</li>
2143 <li>Integrated portability patches for Windows</li>
2144 <li>Serious bug fixes on the URI and HTML code</li>
Daniel Veillard361d8452000-04-03 19:48:13 +00002145</ul>
2146
Daniel Veillardd5f97f82000-09-17 16:38:14 +00002147<h3>2.2.3: Sep 17 2000</h3>
2148<ul>
2149 <li>bug fixes</li>
2150 <li>cleanup of entity handling code</li>
2151 <li>overall review of all loops in the parsers, all sprintf usage has been
2152 checked too</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002153 <li>Far better handling of larges Dtd. Validating against DocBook XML Dtd
Daniel Veillardd5f97f82000-09-17 16:38:14 +00002154 works smoothly now.</li>
2155</ul>
2156
2157<h3>1.8.10: Sep 6 2000</h3>
2158<ul>
2159 <li>bug fix release for some Gnome projects</li>
2160</ul>
2161
2162<h3>2.2.2: August 12 2000</h3>
Daniel Veillard786d7c82000-08-12 23:38:57 +00002163<ul>
2164 <li>mostly bug fixes</li>
Daniel Veillardec78c0f2000-08-25 10:25:23 +00002165 <li>started adding routines to access xml parser context options</li>
Daniel Veillard786d7c82000-08-12 23:38:57 +00002166</ul>
2167
Daniel Veillardd5f97f82000-09-17 16:38:14 +00002168<h3>2.2.1: July 21 2000</h3>
Daniel Veillarda2679fa2000-07-22 02:38:15 +00002169<ul>
2170 <li>a purely bug fixes release</li>
2171 <li>fixed an encoding support problem when parsing from a memory block</li>
2172 <li>fixed a DOCTYPE parsing problem</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002173 <li>removed a bug in the function allowing to override the memory
2174 allocation routines</li>
Daniel Veillarda2679fa2000-07-22 02:38:15 +00002175</ul>
2176
Daniel Veillardd5f97f82000-09-17 16:38:14 +00002177<h3>2.2.0: July 14 2000</h3>
Daniel Veillard94e90602000-07-17 14:38:19 +00002178<ul>
2179 <li>applied a lot of portability fixes</li>
2180 <li>better encoding support/cleanup and saving (content is now always
2181 encoded in UTF-8)</li>
2182 <li>the HTML parser now correctly handles encodings</li>
2183 <li>added xmlHasProp()</li>
2184 <li>fixed a serious problem with &amp;#38;</li>
2185 <li>propagated the fix to FTP client</li>
2186 <li>cleanup, bugfixes, etc ...</li>
2187 <li>Added a page about <a href="encoding.html">libxml Internationalization
2188 support</a></li>
2189</ul>
2190
Daniel Veillard60979bd2000-07-10 12:17:33 +00002191<h3>1.8.9: July 9 2000</h3>
2192<ul>
2193 <li>fixed the spec the RPMs should be better</li>
2194 <li>fixed a serious bug in the FTP implementation, released 1.8.9 to solve
2195 rpmfind users problem</li>
2196</ul>
2197
Daniel Veillard6388e172000-07-03 16:07:19 +00002198<h3>2.1.1: July 1 2000</h3>
2199<ul>
2200 <li>fixes a couple of bugs in the 2.1.0 packaging</li>
2201 <li>improvements on the HTML parser</li>
2202</ul>
2203
Daniel Veillard3f6f7f62000-06-30 17:58:25 +00002204<h3>2.1.0 and 1.8.8: June 29 2000</h3>
2205<ul>
Daniel Veillardc0801af2002-05-28 16:28:42 +00002206 <li>1.8.8 is mostly a commodity package for upgrading to libxml2 according
2207 to <a href="upgrade.html">new instructions</a>. It fixes a nasty problem
Daniel Veillard3f6f7f62000-06-30 17:58:25 +00002208 about &amp;#38; charref parsing</li>
2209 <li>2.1.0 also ease the upgrade from libxml v1 to the recent version. it
2210 also contains numerous fixes and enhancements:
2211 <ul>
2212 <li>added xmlStopParser() to stop parsing</li>
2213 <li>improved a lot parsing speed when there is large CDATA blocs</li>
2214 <li>includes XPath patches provided by Picdar Technology</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002215 <li>tried to fix as much as possible DTD validation and namespace
Daniel Veillard3f6f7f62000-06-30 17:58:25 +00002216 related problems</li>
2217 <li>output to a given encoding has been added/tested</li>
2218 <li>lot of various fixes</li>
2219 </ul>
2220 </li>
2221</ul>
2222
Daniel Veillarde0aed302000-04-16 08:52:20 +00002223<h3>2.0.0: Apr 12 2000</h3>
Daniel Veillard361d8452000-04-03 19:48:13 +00002224<ul>
2225 <li>First public release of libxml2. If you are using libxml, it's a good
Daniel Veillard63d83142002-05-20 06:51:05 +00002226 idea to check the 1.x to 2.x upgrade instructions. NOTE: while initially
2227 scheduled for Apr 3 the release occurred only on Apr 12 due to massive
Daniel Veillarde0aed302000-04-16 08:52:20 +00002228 workload.</li>
Daniel Veillard361d8452000-04-03 19:48:13 +00002229 <li>The include are now located under $prefix/include/libxml (instead of
Daniel Veillarde0aed302000-04-16 08:52:20 +00002230 $prefix/include/gnome-xml), they also are referenced by
Daniel Veillard60979bd2000-07-10 12:17:33 +00002231 <pre>#include &lt;libxml/xxx.h&gt;</pre>
Daniel Veillarde0aed302000-04-16 08:52:20 +00002232 <p>instead of</p>
Daniel Veillard361d8452000-04-03 19:48:13 +00002233 <pre>#include "xxx.h"</pre>
2234 </li>
Daniel Veillard8f621982000-03-20 13:07:15 +00002235 <li>a new URI module for parsing URIs and following strictly RFC 2396</li>
2236 <li>the memory allocation routines used by libxml can now be overloaded
2237 dynamically by using xmlMemSetup()</li>
Daniel Veillard361d8452000-04-03 19:48:13 +00002238 <li>The previously CVS only tool tester has been renamed
2239 <strong>xmllint</strong> and is now installed as part of the libxml2
2240 package</li>
Daniel Veillarde0aed302000-04-16 08:52:20 +00002241 <li>The I/O interface has been revamped. There is now ways to plug in
2242 specific I/O modules, either at the URI scheme detection level using
2243 xmlRegisterInputCallbacks() or by passing I/O functions when creating a
2244 parser context using xmlCreateIOParserCtxt()</li>
2245 <li>there is a C preprocessor macro LIBXML_VERSION providing the version
2246 number of the libxml module in use</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002247 <li>a number of optional features of libxml can now be excluded at
2248 configure time (FTP/HTTP/HTML/XPath/Debug)</li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002249</ul>
2250
2251<h3>2.0.0beta: Mar 14 2000</h3>
2252<ul>
2253 <li>This is a first Beta release of libxml version 2</li>
Daniel Veillarde356c282001-03-10 12:32:04 +00002254 <li>It's available only from<a href="ftp://xmlsoft.org/">xmlsoft.org
2255 FTP</a>, it's packaged as libxml2-2.0.0beta and available as tar and
2256 RPMs</li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002257 <li>This version is now the head in the Gnome CVS base, the old one is
2258 available under the tag LIB_XML_1_X</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00002259 <li>This includes a very large set of changes. From a programmatic point
2260 of view applications should not have to be modified too much, check the
2261 <a href="upgrade.html">upgrade page</a></li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002262 <li>Some interfaces may changes (especially a bit about encoding).</li>
2263 <li>the updates includes:
Daniel Veillard6c8b1172000-03-01 00:40:41 +00002264 <ul>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002265 <li>fix I18N support. ISO-Latin-x/UTF-8/UTF-16 (nearly) seems correctly
2266 handled now</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002267 <li>Better handling of entities, especially well-formedness checking
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002268 and proper PEref extensions in external subsets</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +00002269 <li>DTD conditional sections</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002270 <li>Validation now correctly handle entities content</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +00002271 <li><a href="http://rpmfind.net/tools/gdome/messages/0039.html">change
Daniel Veillard63d83142002-05-20 06:51:05 +00002272 structures to accommodate DOM</a></li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +00002273 </ul>
2274 </li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002275 <li>Serious progress were made toward compliance, <a
2276 href="conf/result.html">here are the result of the test</a> against the
Daniel Veillard63d83142002-05-20 06:51:05 +00002277 OASIS testsuite (except the Japanese tests since I don't support that
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002278 encoding yet). This URL is rebuilt every couple of hours using the CVS
2279 head version.</li>
Daniel Veillarde41f2b72000-01-30 20:00:07 +00002280</ul>
2281
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002282<h3>1.8.7: Mar 6 2000</h3>
2283<ul>
2284 <li>This is a bug fix release:</li>
2285 <li>It is possible to disable the ignorable blanks heuristic used by
2286 libxml-1.x, a new function xmlKeepBlanksDefault(0) will allow this. Note
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002287 that for adherence to XML spec, this behaviour will be disabled by
2288 default in 2.x . The same function will allow to keep compatibility for
2289 old code.</li>
Daniel Veillard60979bd2000-07-10 12:17:33 +00002290 <li>Blanks in &lt;a&gt; &lt;/a&gt; constructs are not ignored anymore,
2291 avoiding heuristic is really the Right Way :-\</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002292 <li>The unchecked use of snprintf which was breaking libxml-1.8.6
2293 compilation on some platforms has been fixed</li>
2294 <li>nanoftp.c nanohttp.c: Fixed '#' and '?' stripping when processing
2295 URIs</li>
2296</ul>
2297
Daniel Veillarde41f2b72000-01-30 20:00:07 +00002298<h3>1.8.6: Jan 31 2000</h3>
2299<ul>
2300 <li>added a nanoFTP transport module, debugged until the new version of <a
2301 href="http://rpmfind.net/linux/rpm2html/rpmfind.html">rpmfind</a> can use
2302 it without troubles</li>
Daniel Veillardda07c342000-01-25 18:31:22 +00002303</ul>
2304
2305<h3>1.8.5: Jan 21 2000</h3>
2306<ul>
Daniel Veillard0142b842000-01-14 14:45:24 +00002307 <li>adding APIs to parse a well balanced chunk of XML (production <a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002308 href="http://www.w3.org/TR/REC-xml#NT-content">[43] content</a> of the
2309 XML spec)</li>
Daniel Veillard461a66c2000-01-18 18:01:01 +00002310 <li>fixed a hideous bug in xmlGetProp pointed by Rune.Djurhuus@fast.no</li>
Daniel Veillard60979bd2000-07-10 12:17:33 +00002311 <li>Jody Goldberg &lt;jgoldberg@home.com&gt; provided another patch trying
2312 to solve the zlib checks problems</li>
Daniel Veillard461a66c2000-01-18 18:01:01 +00002313 <li>The current state in gnome CVS base is expected to ship as 1.8.5 with
2314 gnumeric soon</li>
Daniel Veillard0142b842000-01-14 14:45:24 +00002315</ul>
2316
2317<h3>1.8.4: Jan 13 2000</h3>
2318<ul>
2319 <li>bug fixes, reintroduced xmlNewGlobalNs(), fixed xmlNewNs()</li>
2320 <li>all exit() call should have been removed from libxml</li>
2321 <li>fixed a problem with INCLUDE_WINSOCK on WIN32 platform</li>
2322 <li>added newDocFragment()</li>
Daniel Veillardf84f71f2000-01-05 19:54:23 +00002323</ul>
2324
2325<h3>1.8.3: Jan 5 2000</h3>
2326<ul>
2327 <li>a Push interface for the XML and HTML parsers</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002328 <li>a shell-like interface to the document tree (try tester --shell :-)</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002329 <li>lots of bug fixes and improvement added over XMas holidays</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +00002330 <li>fixed the DTD parsing code to work with the xhtml DTD</li>
Daniel Veillardf84f71f2000-01-05 19:54:23 +00002331 <li>added xmlRemoveProp(), xmlRemoveID() and xmlRemoveRef()</li>
2332 <li>Fixed bugs in xmlNewNs()</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +00002333 <li>External entity loading code has been revamped, now it uses
Daniel Veillardf84f71f2000-01-05 19:54:23 +00002334 xmlLoadExternalEntity(), some fix on entities processing were added</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +00002335 <li>cleaned up WIN32 includes of socket stuff</li>
Daniel Veillard5cb5ab81999-12-21 15:35:29 +00002336</ul>
2337
2338<h3>1.8.2: Dec 21 1999</h3>
2339<ul>
Daniel Veillardb24054a1999-12-18 15:32:46 +00002340 <li>I got another problem with includes and C++, I hope this issue is fixed
2341 for good this time</li>
Daniel Veillard5cb5ab81999-12-21 15:35:29 +00002342 <li>Added a few tree modification functions: xmlReplaceNode,
2343 xmlAddPrevSibling, xmlAddNextSibling, xmlNodeSetName and
2344 xmlDocSetRootElement</li>
2345 <li>Tried to improve the HTML output with help from <a
2346 href="mailto:clahey@umich.edu">Chris Lahey</a></li>
Daniel Veillarde4e51311999-12-18 15:32:46 +00002347</ul>
Daniel Veillardb24054a1999-12-18 15:32:46 +00002348
Daniel Veillarde4e51311999-12-18 15:32:46 +00002349<h3>1.8.1: Dec 18 1999</h3>
2350<ul>
2351 <li>various patches to avoid troubles when using libxml with C++ compilers
2352 the "namespace" keyword and C escaping in include files</li>
2353 <li>a problem in one of the core macros IS_CHAR was corrected</li>
2354 <li>fixed a bug introduced in 1.8.0 breaking default namespace processing,
2355 and more specifically the Dia application</li>
Daniel Veillard944b5ff1999-12-15 19:08:24 +00002356 <li>fixed a posteriori validation (validation after parsing, or by using a
2357 Dtd not specified in the original document)</li>
Daniel Veillardb24054a1999-12-18 15:32:46 +00002358 <li>fixed a bug in</li>
Daniel Veillard10a2c651999-12-12 13:03:50 +00002359</ul>
2360
2361<h3>1.8.0: Dec 12 1999</h3>
2362<ul>
2363 <li>cleanup, especially memory wise</li>
2364 <li>the parser should be more reliable, especially the HTML one, it should
2365 not crash, whatever the input !</li>
2366 <li>Integrated various patches, especially a speedup improvement for large
2367 dataset from <a href="mailto:cnygard@bellatlantic.net">Carl Nygard</a>,
2368 configure with --with-buffers to enable them.</li>
2369 <li>attribute normalization, oops should have been added long ago !</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002370 <li>attributes defaulted from DTDs should be available, xmlSetProp() now
2371 does entities escaping by default.</li>
Daniel Veillard4c3a2031999-11-19 17:46:26 +00002372</ul>
Daniel Veillard35008381999-10-25 13:15:52 +00002373
2374<h3>1.7.4: Oct 25 1999</h3>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002375<ul>
Daniel Veillard35008381999-10-25 13:15:52 +00002376 <li>Lots of HTML improvement</li>
2377 <li>Fixed some errors when saving both XML and HTML</li>
2378 <li>More examples, the regression tests should now look clean</li>
2379 <li>Fixed a bug with contiguous charref</li>
2380</ul>
2381
2382<h3>1.7.3: Sep 29 1999</h3>
2383<ul>
2384 <li>portability problems fixed</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002385 <li>snprintf was used unconditionally, leading to link problems on system
Daniel Veillard35008381999-10-25 13:15:52 +00002386 were it's not available, fixed</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002387</ul>
2388
2389<h3>1.7.1: Sep 24 1999</h3>
2390<ul>
2391 <li>The basic type for strings manipulated by libxml has been renamed in
2392 1.7.1 from <strong>CHAR</strong> to <strong>xmlChar</strong>. The reason
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002393 is that CHAR was conflicting with a predefined type on Windows. However
2394 on non WIN32 environment, compatibility is provided by the way of a
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002395 <strong>#define </strong>.</li>
2396 <li>Changed another error : the use of a structure field called errno, and
2397 leading to troubles on platforms where it's a macro</li>
2398</ul>
2399
Daniel Veillard63d83142002-05-20 06:51:05 +00002400<h3>1.7.0: Sep 23 1999</h3>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002401<ul>
2402 <li>Added the ability to fetch remote DTD or parsed entities, see the <a
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00002403 href="html/libxml-nanohttp.html">nanohttp</a> module.</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002404 <li>Added an errno to report errors by another mean than a simple printf
2405 like callback</li>
2406 <li>Finished ID/IDREF support and checking when validation</li>
2407 <li>Serious memory leaks fixed (there is now a <a
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00002408 href="html/libxml-xmlmemory.html">memory wrapper</a> module)</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002409 <li>Improvement of <a href="http://www.w3.org/TR/xpath">XPath</a>
2410 implementation</li>
2411 <li>Added an HTML parser front-end</li>
2412</ul>
2413
2414<h2><a name="XML">XML</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002415
Daniel Veillard402e8c82000-02-29 22:57:47 +00002416<p><a href="http://www.w3.org/TR/REC-xml">XML is a standard</a> for
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002417markup-based structured documents. Here is <a name="example">an example XML
2418document</a>:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00002419<pre>&lt;?xml version="1.0"?&gt;
2420&lt;EXAMPLE prop1="gnome is great" prop2="&amp;amp; linux too"&gt;
2421 &lt;head&gt;
2422 &lt;title&gt;Welcome to Gnome&lt;/title&gt;
2423 &lt;/head&gt;
2424 &lt;chapter&gt;
2425 &lt;title&gt;The Linux adventure&lt;/title&gt;
2426 &lt;p&gt;bla bla bla ...&lt;/p&gt;
2427 &lt;image href="linus.gif"/&gt;
2428 &lt;p&gt;...&lt;/p&gt;
2429 &lt;/chapter&gt;
2430&lt;/EXAMPLE&gt;</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002431
Daniel Veillard0b28e882002-07-24 23:47:05 +00002432<p>The first line specifies that it is an XML document and gives useful
Daniel Veillard42766c02002-08-22 20:52:17 +00002433information about its encoding. Then the rest of the document is a text
2434format whose structure is specified by tags between brackets. <strong>Each
2435tag opened has to be closed</strong>. XML is pedantic about this. However, if
2436a tag is empty (no content), a single tag can serve as both the opening and
2437closing tag if it ends with <code>/&gt;</code> rather than with
2438<code>&gt;</code>. Note that, for example, the image tag has no content (just
2439an attribute) and is closed by ending the tag with <code>/&gt;</code>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +00002440
Daniel Veillard42766c02002-08-22 20:52:17 +00002441<p>XML can be applied successfully to a wide range of tasks, ranging from
2442long term structured document maintenance (where it follows the steps of
2443SGML) to simple data encoding mechanisms like configuration file formatting
2444(glade), spreadsheets (gnumeric), or even shorter lived documents such as
2445WebDAV where it is used to encode remote calls between a client and a
2446server.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002447
Daniel Veillard82687162001-01-22 15:32:01 +00002448<h2><a name="XSLT">XSLT</a></h2>
2449
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +00002450<p>Check <a href="http://xmlsoft.org/XSLT">the separate libxslt page</a></p>
2451
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002452<p><a href="http://www.w3.org/TR/xslt">XSL Transformations</a>, is a
2453language for transforming XML documents into other XML documents (or
2454HTML/textual output).</p>
Daniel Veillard82687162001-01-22 15:32:01 +00002455
Daniel Veillard560c2a42003-07-06 21:13:49 +00002456<p>A separate library called libxslt is available implementing XSLT-1.0 for
2457libxml2. This module "libxslt" too can be found in the Gnome CVS base.</p>
Daniel Veillard82687162001-01-22 15:32:01 +00002458
Daniel Veillard29f61002005-08-06 09:07:15 +00002459<p>You can check the progresses on the libxslt <a
2460href="http://xmlsoft.org/XSLT/ChangeLog.html">Changelog</a>.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002461
2462<h2><a name="Python">Python and bindings</a></h2>
2463
Daniel Veillard42766c02002-08-22 20:52:17 +00002464<p>There are a number of language bindings and wrappers available for
2465libxml2, the list below is not exhaustive. Please contact the <a
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002466href="http://mail.gnome.org/mailman/listinfo/xml-bindings">xml-bindings@gnome.org</a>
2467(<a href="http://mail.gnome.org/archives/xml-bindings/">archives</a>) in
2468order to get updates to this list or to discuss the specific topic of libxml2
2469or libxslt wrappers or bindings:</p>
2470<ul>
Daniel Veillardc14401e2002-11-20 14:28:17 +00002471 <li><a href="http://libxmlplusplus.sourceforge.net/">Libxml++</a> seems the
2472 most up-to-date C++ bindings for libxml2, check the <a
2473 href="http://libxmlplusplus.sourceforge.net/reference/html/hierarchy.html">documentation</a>
2474 and the <a
2475 href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/libxmlplusplus/libxml%2b%2b/examples/">examples</a>.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002476 <li>There is another <a href="http://libgdome-cpp.berlios.de/">C++ wrapper
Daniel Veillard0b28e882002-07-24 23:47:05 +00002477 based on the gdome2 bindings</a> maintained by Tobias Peters.</li>
Daniel Veillard9b6fd302002-05-13 12:06:47 +00002478 <li>and a third C++ wrapper by Peter Jones &lt;pjones@pmade.org&gt;
2479 <p>Website: <a
2480 href="http://pmade.org/pjones/software/xmlwrapp/">http://pmade.org/pjones/software/xmlwrapp/</a></p>
2481 </li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002482 <li><a
2483 href="http://mail.gnome.org/archives/xml/2001-March/msg00014.html">Matt
Daniel Veillard63d83142002-05-20 06:51:05 +00002484 Sergeant</a> developed <a
2485 href="http://axkit.org/download/">XML::LibXSLT</a>, a Perl wrapper for
Daniel Veillardaf43f632002-03-08 15:05:20 +00002486 libxml2/libxslt as part of the <a href="http://axkit.com/">AxKit XML
Daniel Veillard0b28e882002-07-24 23:47:05 +00002487 application server</a>.</li>
Daniel Veillard4ac494b2003-09-18 15:08:00 +00002488 <li>If you're interested into scripting XML processing, have a look at <a
2489 href="http://xsh.sourceforge.net/">XSH</a> an XML editing shell based on
2490 Libxml2 Perl bindings.</li>
Daniel Veillard21473672002-06-17 07:29:22 +00002491 <li><a href="mailto:dkuhlman@cutter.rexx.com">Dave Kuhlman</a> provides an
Daniel Veillardaf43f632002-03-08 15:05:20 +00002492 earlier version of the libxml/libxslt <a
Daniel Veillard0b28e882002-07-24 23:47:05 +00002493 href="http://www.rexx.com/~dkuhlman">wrappers for Python</a>.</li>
Daniel Veillard21473672002-06-17 07:29:22 +00002494 <li>Gopal.V and Peter Minten develop <a
2495 href="http://savannah.gnu.org/projects/libxmlsharp">libxml#</a>, a set of
Daniel Veillard0b28e882002-07-24 23:47:05 +00002496 C# libxml2 bindings.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002497 <li>Petr Kozelka provides <a
2498 href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
Daniel Veillard0b28e882002-07-24 23:47:05 +00002499 libxml2</a> with Kylix, Delphi and other Pascal compilers.</li>
Daniel Veillardb2fb8ed2002-04-01 09:33:12 +00002500 <li>Uwe Fechner also provides <a
2501 href="http://sourceforge.net/projects/idom2-pas/">idom2</a>, a DOM2
Daniel Veillard0b28e882002-07-24 23:47:05 +00002502 implementation for Kylix2/D5/D6 from Borland.</li>
Daniel Veillard67952602006-01-05 15:29:44 +00002503 <li>There is <a href="http://rubyforge.org/projects/xml-tools/">bindings
2504 for Ruby</a> and libxml2 bindings are also available in Ruby through the
2505 <a href="http://libgdome-ruby.berlios.de/">libgdome-ruby</a> module
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002506 maintained by Tobias Peters.</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002507 <li>Steve Ball and contributors maintains <a
2508 href="http://tclxml.sourceforge.net/">libxml2 and libxslt bindings for
Daniel Veillard0b28e882002-07-24 23:47:05 +00002509 Tcl</a>.</li>
Daniel Veillard142fb212005-04-07 12:48:10 +00002510 <li>libxml2 and libxslt is the default XML library for PHP5.</li>
Daniel Veillard41b01a82003-02-27 11:09:06 +00002511 <li><a href="http://savannah.gnu.org/projects/classpathx/">LibxmlJ</a> is
Daniel Veillard806cada2003-03-19 21:58:59 +00002512 an effort to create a 100% JAXP-compatible Java wrapper for libxml2 and
2513 libxslt as part of GNU ClasspathX project.</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +00002514 <li>Patrick McPhee provides Rexx bindings fof libxml2 and libxslt, look for
2515 <a href="http://www.interlog.com/~ptjm/software.html">RexxXML</a>.</li>
Daniel Veillard67952602006-01-05 15:29:44 +00002516 <li><a
2517 href="http://www.satimage.fr/software/en/xml_suite.html">Satimage</a>
Daniel Veillardb78757b2004-12-30 21:30:23 +00002518 provides <a
2519 href="http://www.satimage.fr/software/en/downloads_osaxen.html">XMLLib
2520 osax</a>. This is an osax for Mac OS X with a set of commands to
2521 implement in AppleScript the XML DOM, XPATH and XSLT. Also includes
Daniel Veillardc7426092005-01-05 15:11:41 +00002522 commands for Property-lists (Apple's fast lookup table XML format.)</li>
Daniel Veillard67952602006-01-05 15:29:44 +00002523 <li>Francesco Montorsi developped <a
2524 href="https://sourceforge.net/project/showfiles.php?group_id=51305&amp;package_id=45182">wxXml2</a>
Daniel Veillardc7426092005-01-05 15:11:41 +00002525 wrappers that interface libxml2, allowing wxWidgets applications to
2526 load/save/edit XML instances.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002527</ul>
2528
Daniel Veillardc0801af2002-05-28 16:28:42 +00002529<p>The distribution includes a set of Python bindings, which are guaranteed
2530to be maintained as part of the library in the future, though the Python
Daniel Veillard41b01a82003-02-27 11:09:06 +00002531interface have not yet reached the completeness of the C API.</p>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00002532
Daniel Veillard929746e2005-05-11 11:08:22 +00002533<p>Note that some of the Python purist dislike the default set of Python
Daniel Veillard67952602006-01-05 15:29:44 +00002534bindings, rather than complaining I suggest they have a look at <a
2535href="http://codespeak.net/lxml/">lxml the more pythonic bindings for libxml2
2536and libxslt</a> and <a
2537href="http://codespeak.net/mailman/listinfo/lxml-dev">help Martijn
2538Faassen</a> complete those.</p>
Daniel Veillard929746e2005-05-11 11:08:22 +00002539
Daniel Veillard27907c72002-12-16 16:05:58 +00002540<p><a href="mailto:stephane.bidoul@softwareag.com">Stéphane Bidoul</a>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00002541maintains <a href="http://users.skynet.be/sbi/libxml-python/">a Windows port
2542of the Python bindings</a>.</p>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002543
Daniel Veillard7ef0fcb2002-12-14 10:38:55 +00002544<p>Note to people interested in building bindings, the API is formalized as
2545<a href="libxml2-api.xml">an XML API description file</a> which allows to
2546automate a large part of the Python bindings, this includes function
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00002547descriptions, enums, structures, typedefs, etc... The Python script used to
2548build the bindings is python/generator.py in the source distribution.</p>
Daniel Veillard7ef0fcb2002-12-14 10:38:55 +00002549
Daniel Veillardaf43f632002-03-08 15:05:20 +00002550<p>To install the Python bindings there are 2 options:</p>
Daniel Veillard0b79dfe2002-02-23 13:02:31 +00002551<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002552 <li>If you use an RPM based distribution, simply install the <a
2553 href="http://rpmfind.net/linux/rpm2html/search.php?query=libxml2-python">libxml2-python
2554 RPM</a> (and if needed the <a
2555 href="http://rpmfind.net/linux/rpm2html/search.php?query=libxslt-python">libxslt-python
2556 RPM</a>).</li>
2557 <li>Otherwise use the <a href="ftp://xmlsoft.org/python/">libxml2-python
2558 module distribution</a> corresponding to your installed version of
2559 libxml2 and libxslt. Note that to install it you will need both libxml2
2560 and libxslt installed and run "python setup.py build install" in the
2561 module tree.</li>
Daniel Veillard0b79dfe2002-02-23 13:02:31 +00002562</ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002563
2564<p>The distribution includes a set of examples and regression tests for the
2565python bindings in the <code>python/tests</code> directory. Here are some
Daniel Veillard0b28e882002-07-24 23:47:05 +00002566excerpts from those tests:</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002567
2568<h3>tst.py:</h3>
2569
2570<p>This is a basic test of the file interface and DOM navigation:</p>
MST 2003 John Fleck2dffb762003-11-29 04:41:24 +00002571<pre>import libxml2, sys
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002572
2573doc = libxml2.parseFile("tst.xml")
2574if doc.name != "tst.xml":
2575 print "doc.name failed"
2576 sys.exit(1)
2577root = doc.children
2578if root.name != "doc":
2579 print "root.name failed"
2580 sys.exit(1)
2581child = root.children
2582if child.name != "foo":
2583 print "child.name failed"
2584 sys.exit(1)
2585doc.freeDoc()</pre>
2586
Daniel Veillard0b28e882002-07-24 23:47:05 +00002587<p>The Python module is called libxml2; parseFile is the equivalent of
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002588xmlParseFile (most of the bindings are automatically generated, and the xml
2589prefix is removed and the casing convention are kept). All node seen at the
Daniel Veillard63d83142002-05-20 06:51:05 +00002590binding level share the same subset of accessors:</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002591<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002592 <li><code>name</code> : returns the node name</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00002593 <li><code>type</code> : returns a string indicating the node type</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002594 <li><code>content</code> : returns the content of the node, it is based on
2595 xmlNodeGetContent() and hence is recursive.</li>
2596 <li><code>parent</code> , <code>children</code>, <code>last</code>,
2597 <code>next</code>, <code>prev</code>, <code>doc</code>,
2598 <code>properties</code>: pointing to the associated element in the tree,
2599 those may return None in case no such link exists.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002600</ul>
2601
Daniel Veillard63d83142002-05-20 06:51:05 +00002602<p>Also note the need to explicitly deallocate documents with freeDoc() .
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002603Reference counting for libxml2 trees would need quite a lot of work to
2604function properly, and rather than risk memory leaks if not implemented
2605correctly it sounds safer to have an explicit function to free a tree. The
2606wrapper python objects like doc, root or child are them automatically garbage
2607collected.</p>
2608
2609<h3>validate.py:</h3>
2610
2611<p>This test check the validation interfaces and redirection of error
2612messages:</p>
2613<pre>import libxml2
2614
Daniel Veillard63d83142002-05-20 06:51:05 +00002615#deactivate error messages from the validation
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002616def noerr(ctx, str):
2617 pass
2618
2619libxml2.registerErrorHandler(noerr, None)
2620
2621ctxt = libxml2.createFileParserCtxt("invalid.xml")
2622ctxt.validate(1)
2623ctxt.parseDocument()
2624doc = ctxt.doc()
2625valid = ctxt.isValid()
2626doc.freeDoc()
2627if valid != 0:
Daniel Veillard63d83142002-05-20 06:51:05 +00002628 print "validity check failed"</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002629
2630<p>The first thing to notice is the call to registerErrorHandler(), it
2631defines a new error handler global to the library. It is used to avoid seeing
2632the error messages when trying to validate the invalid document.</p>
2633
2634<p>The main interest of that test is the creation of a parser context with
2635createFileParserCtxt() and how the behaviour can be changed before calling
Daniel Veillard63d83142002-05-20 06:51:05 +00002636parseDocument() . Similarly the informations resulting from the parsing phase
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002637are also available using context methods.</p>
2638
2639<p>Contexts like nodes are defined as class and the libxml2 wrappers maps the
2640C function interfaces in terms of objects method as much as possible. The
2641best to get a complete view of what methods are supported is to look at the
2642libxml2.py module containing all the wrappers.</p>
2643
2644<h3>push.py:</h3>
2645
2646<p>This test show how to activate the push parser interface:</p>
2647<pre>import libxml2
2648
2649ctxt = libxml2.createPushParser(None, "&lt;foo", 4, "test.xml")
2650ctxt.parseChunk("/&gt;", 2, 1)
2651doc = ctxt.doc()
2652
2653doc.freeDoc()</pre>
2654
Daniel Veillard63d83142002-05-20 06:51:05 +00002655<p>The context is created with a special call based on the
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002656xmlCreatePushParser() from the C library. The first argument is an optional
Daniel Veillard63d83142002-05-20 06:51:05 +00002657SAX callback object, then the initial set of data, the length and the name of
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002658the resource in case URI-References need to be computed by the parser.</p>
2659
2660<p>Then the data are pushed using the parseChunk() method, the last call
Daniel Veillard63d83142002-05-20 06:51:05 +00002661setting the third argument terminate to 1.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002662
2663<h3>pushSAX.py:</h3>
2664
2665<p>this test show the use of the event based parsing interfaces. In this case
2666the parser does not build a document, but provides callback information as
2667the parser makes progresses analyzing the data being provided:</p>
2668<pre>import libxml2
2669log = ""
2670
2671class callback:
2672 def startDocument(self):
2673 global log
2674 log = log + "startDocument:"
2675
2676 def endDocument(self):
2677 global log
2678 log = log + "endDocument:"
2679
2680 def startElement(self, tag, attrs):
2681 global log
2682 log = log + "startElement %s %s:" % (tag, attrs)
2683
2684 def endElement(self, tag):
2685 global log
2686 log = log + "endElement %s:" % (tag)
2687
2688 def characters(self, data):
2689 global log
2690 log = log + "characters: %s:" % (data)
2691
2692 def warning(self, msg):
2693 global log
2694 log = log + "warning: %s:" % (msg)
2695
2696 def error(self, msg):
2697 global log
2698 log = log + "error: %s:" % (msg)
2699
2700 def fatalError(self, msg):
2701 global log
2702 log = log + "fatalError: %s:" % (msg)
2703
2704handler = callback()
2705
2706ctxt = libxml2.createPushParser(handler, "&lt;foo", 4, "test.xml")
2707chunk = " url='tst'&gt;b"
2708ctxt.parseChunk(chunk, len(chunk), 0)
2709chunk = "ar&lt;/foo&gt;"
2710ctxt.parseChunk(chunk, len(chunk), 1)
2711
Daniel Veillardfcbfa2d2002-02-21 17:54:27 +00002712reference = "startDocument:startElement foo {'url': 'tst'}:" + \
2713 "characters: bar:endElement foo:endDocument:"
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002714if log != reference:
2715 print "Error got: %s" % log
Daniel Veillard63d83142002-05-20 06:51:05 +00002716 print "Expected: %s" % reference</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002717
2718<p>The key object in that test is the handler, it provides a number of entry
2719points which can be called by the parser as it makes progresses to indicate
2720the information set obtained. The full set of callback is larger than what
2721the callback class in that specific example implements (see the SAX
2722definition for a complete list). The wrapper will only call those supplied by
2723the object when activated. The startElement receives the names of the element
Daniel Veillard63d83142002-05-20 06:51:05 +00002724and a dictionary containing the attributes carried by this element.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002725
2726<p>Also note that the reference string generated from the callback shows a
2727single character call even though the string "bar" is passed to the parser
2728from 2 different call to parseChunk()</p>
2729
2730<h3>xpath.py:</h3>
2731
Daniel Veillard63d83142002-05-20 06:51:05 +00002732<p>This is a basic test of XPath wrappers support</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002733<pre>import libxml2
2734
2735doc = libxml2.parseFile("tst.xml")
2736ctxt = doc.xpathNewContext()
2737res = ctxt.xpathEval("//*")
2738if len(res) != 2:
2739 print "xpath query: wrong node set size"
2740 sys.exit(1)
2741if res[0].name != "doc" or res[1].name != "foo":
2742 print "xpath query: wrong node set value"
2743 sys.exit(1)
2744doc.freeDoc()
2745ctxt.xpathFreeContext()</pre>
2746
2747<p>This test parses a file, then create an XPath context to evaluate XPath
2748expression on it. The xpathEval() method execute an XPath query and returns
2749the result mapped in a Python way. String and numbers are natively converted,
2750and node sets are returned as a tuple of libxml2 Python nodes wrappers. Like
Daniel Veillard63d83142002-05-20 06:51:05 +00002751the document, the XPath context need to be freed explicitly, also not that
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002752the result of the XPath query may point back to the document tree and hence
2753the document must be freed after the result of the query is used.</p>
2754
2755<h3>xpathext.py:</h3>
2756
2757<p>This test shows how to extend the XPath engine with functions written in
2758python:</p>
2759<pre>import libxml2
2760
2761def foo(ctx, x):
2762 return x + 1
2763
2764doc = libxml2.parseFile("tst.xml")
2765ctxt = doc.xpathNewContext()
2766libxml2.registerXPathFunction(ctxt._o, "foo", None, foo)
2767res = ctxt.xpathEval("foo(1)")
2768if res != 2:
2769 print "xpath extension failure"
2770doc.freeDoc()
2771ctxt.xpathFreeContext()</pre>
2772
2773<p>Note how the extension function is registered with the context (but that
Daniel Veillard63d83142002-05-20 06:51:05 +00002774part is not yet finalized, this may change slightly in the future).</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002775
2776<h3>tstxpath.py:</h3>
2777
Daniel Veillard63d83142002-05-20 06:51:05 +00002778<p>This test is similar to the previous one but shows how the extension
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002779function can access the XPath evaluation context:</p>
2780<pre>def foo(ctx, x):
2781 global called
2782
2783 #
2784 # test that access to the XPath evaluation contexts
2785 #
2786 pctxt = libxml2.xpathParserContext(_obj=ctx)
2787 ctxt = pctxt.context()
2788 called = ctxt.function()
2789 return x + 1</pre>
2790
2791<p>All the interfaces around the XPath parser(or rather evaluation) context
2792are not finalized, but it should be sufficient to do contextual work at the
2793evaluation point.</p>
2794
2795<h3>Memory debugging:</h3>
2796
2797<p>last but not least, all tests starts with the following prologue:</p>
2798<pre>#memory debug specific
Daniel Veillardaf43f632002-03-08 15:05:20 +00002799libxml2.debugMemory(1)</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002800
2801<p>and ends with the following epilogue:</p>
2802<pre>#memory debug specific
2803libxml2.cleanupParser()
2804if libxml2.debugMemory(1) == 0:
2805 print "OK"
2806else:
2807 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
2808 libxml2.dumpMemory()</pre>
2809
2810<p>Those activate the memory debugging interface of libxml2 where all
Daniel Veillard63d83142002-05-20 06:51:05 +00002811allocated block in the library are tracked. The prologue then cleans up the
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002812library state and checks that all allocated memory has been freed. If not it
2813calls dumpMemory() which saves that list in a <code>.memdump</code> file.</p>
Daniel Veillard82687162001-01-22 15:32:01 +00002814
Daniel Veillard8a469172003-06-12 16:05:07 +00002815<h2><a name="architecture">libxml2 architecture</a></h2>
Daniel Veillard4540be42000-08-19 16:40:28 +00002816
Daniel Veillard560c2a42003-07-06 21:13:49 +00002817<p>Libxml2 is made of multiple components; some of them are optional, and
2818most of the block interfaces are public. The main components are:</p>
Daniel Veillard4540be42000-08-19 16:40:28 +00002819<ul>
2820 <li>an Input/Output layer</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002821 <li>FTP and HTTP client layers (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002822 <li>an Internationalization layer managing the encodings support</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002823 <li>a URI module</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002824 <li>the XML parser and its basic SAX interface</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002825 <li>an HTML parser using the same SAX interface (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002826 <li>a SAX tree module to build an in-memory DOM representation</li>
2827 <li>a tree module to manipulate the DOM representation</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002828 <li>a validation module using the DOM representation (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002829 <li>an XPath module for global lookup in a DOM representation
Daniel Veillard91e9d582001-02-26 07:31:12 +00002830 (optional)</li>
2831 <li>a debug module (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002832</ul>
2833
2834<p>Graphically this gives the following:</p>
2835
2836<p><img src="libxml.gif" alt="a graphical view of the various"></p>
2837
2838<p></p>
2839
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002840<h2><a name="tree">The tree output</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002841
2842<p>The parser returns a tree built during the document analysis. The value
Daniel Veillard402e8c82000-02-29 22:57:47 +00002843returned is an <strong>xmlDocPtr</strong> (i.e., a pointer to an
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002844<strong>xmlDoc</strong> structure). This structure contains information such
Daniel Veillard306be992000-07-03 12:38:45 +00002845as the file name, the document type, and a <strong>children</strong> pointer
2846which is the root of the document (or more exactly the first child under the
2847root which is the document). The tree is made of <strong>xmlNode</strong>s,
Daniel Veillard91e9d582001-02-26 07:31:12 +00002848chained in double-linked lists of siblings and with a children&lt;-&gt;parent
Daniel Veillard306be992000-07-03 12:38:45 +00002849relationship. An xmlNode can also carry properties (a chain of xmlAttr
2850structures). An attribute may have a value which is a list of TEXT or
2851ENTITY_REF nodes.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002852
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002853<p>Here is an example (erroneous with respect to the XML spec since there
2854should be only one ELEMENT under the root):</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002855
2856<p><img src="structure.gif" alt=" structure.gif "></p>
2857
2858<p>In the source package there is a small program (not installed by default)
Daniel Veillard361d8452000-04-03 19:48:13 +00002859called <strong>xmllint</strong> which parses XML files given as argument and
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002860prints them back as parsed. This is useful for detecting errors both in XML
2861code and in the XML parser itself. It has an option <strong>--debug</strong>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002862which prints the actual in-memory structure of the document; here is the
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002863result with the <a href="#example">example</a> given before:</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002864<pre>DOCUMENT
2865version=1.0
2866standalone=true
2867 ELEMENT EXAMPLE
2868 ATTRIBUTE prop1
2869 TEXT
2870 content=gnome is great
2871 ATTRIBUTE prop2
2872 ENTITY_REF
2873 TEXT
Daniel Veillard0142b842000-01-14 14:45:24 +00002874 content= linux too
Daniel Veillard402e8c82000-02-29 22:57:47 +00002875 ELEMENT head
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002876 ELEMENT title
Daniel Veillard25940b71998-10-29 05:51:30 +00002877 TEXT
2878 content=Welcome to Gnome
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002879 ELEMENT chapter
2880 ELEMENT title
Daniel Veillard25940b71998-10-29 05:51:30 +00002881 TEXT
2882 content=The Linux adventure
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002883 ELEMENT p
Daniel Veillard25940b71998-10-29 05:51:30 +00002884 TEXT
2885 content=bla bla bla ...
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002886 ELEMENT image
2887 ATTRIBUTE href
2888 TEXT
2889 content=linus.gif
2890 ELEMENT p
Daniel Veillard25940b71998-10-29 05:51:30 +00002891 TEXT
2892 content=...</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002893
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002894<p>This should be useful for learning the internal representation model.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +00002895
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002896<h2><a name="interface">The SAX interface</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002897
Daniel Veillard402e8c82000-02-29 22:57:47 +00002898<p>Sometimes the DOM tree output is just too large to fit reasonably into
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002899memory. In that case (and if you don't expect to save back the XML document
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002900loaded using libxml), it's better to use the SAX interface of libxml. SAX is
2901a <strong>callback-based interface</strong> to the parser. Before parsing,
2902the application layer registers a customized set of callbacks which are
2903called by the library as it progresses through the XML input.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002904
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002905<p>To get more detailed step-by-step guidance on using the SAX interface of
Daniel Veillard4540be42000-08-19 16:40:28 +00002906libxml, see the <a
2907href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">nice
2908documentation</a>.written by <a href="mailto:james@daa.com.au">James
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002909Henstridge</a>.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002910
2911<p>You can debug the SAX behaviour by using the <strong>testSAX</strong>
2912program located in the gnome-xml module (it's usually not shipped in the
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002913binary packages of libxml, but you can find it in the tar source
Daniel Veillard402e8c82000-02-29 22:57:47 +00002914distribution). Here is the sequence of callbacks that would be reported by
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002915testSAX when parsing the example XML document shown earlier:</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002916<pre>SAX.setDocumentLocator()
2917SAX.startDocument()
2918SAX.getEntity(amp)
2919SAX.startElement(EXAMPLE, prop1='gnome is great', prop2='&amp;amp; linux too')
2920SAX.characters( , 3)
2921SAX.startElement(head)
2922SAX.characters( , 4)
2923SAX.startElement(title)
2924SAX.characters(Welcome to Gnome, 16)
2925SAX.endElement(title)
2926SAX.characters( , 3)
2927SAX.endElement(head)
2928SAX.characters( , 3)
2929SAX.startElement(chapter)
2930SAX.characters( , 4)
2931SAX.startElement(title)
2932SAX.characters(The Linux adventure, 19)
2933SAX.endElement(title)
2934SAX.characters( , 4)
2935SAX.startElement(p)
2936SAX.characters(bla bla bla ..., 15)
2937SAX.endElement(p)
2938SAX.characters( , 4)
2939SAX.startElement(image, href='linus.gif')
2940SAX.endElement(image)
2941SAX.characters( , 4)
2942SAX.startElement(p)
2943SAX.characters(..., 3)
2944SAX.endElement(p)
2945SAX.characters( , 3)
2946SAX.endElement(chapter)
2947SAX.characters( , 1)
2948SAX.endElement(EXAMPLE)
2949SAX.endDocument()</pre>
2950
Daniel Veillard8a469172003-06-12 16:05:07 +00002951<p>Most of the other interfaces of libxml2 are based on the DOM tree-building
Daniel Veillardec70e912001-02-26 20:10:45 +00002952facility, so nearly everything up to the end of this document presupposes the
2953use of the standard DOM tree build. Note that the DOM tree itself is built by
2954a set of registered default callbacks, without internal specific
2955interface.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002956
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002957<h2><a name="Validation">Validation &amp; DTDs</a></h2>
2958
2959<p>Table of Content:</p>
2960<ol>
2961 <li><a href="#General5">General overview</a></li>
2962 <li><a href="#definition">The definition</a></li>
2963 <li><a href="#Simple">Simple rules</a>
2964 <ol>
Daniel Veillard9c466822001-10-25 12:03:39 +00002965 <li><a href="#reference">How to reference a DTD from a document</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002966 <li><a href="#Declaring">Declaring elements</a></li>
2967 <li><a href="#Declaring1">Declaring attributes</a></li>
2968 </ol>
2969 </li>
2970 <li><a href="#Some">Some examples</a></li>
2971 <li><a href="#validate">How to validate</a></li>
2972 <li><a href="#Other">Other resources</a></li>
2973</ol>
2974
2975<h3><a name="General5">General overview</a></h3>
2976
2977<p>Well what is validation and what is a DTD ?</p>
2978
2979<p>DTD is the acronym for Document Type Definition. This is a description of
Daniel Veillard63d83142002-05-20 06:51:05 +00002980the content for a family of XML files. This is part of the XML 1.0
Daniel Veillard0b28e882002-07-24 23:47:05 +00002981specification, and allows one to describe and verify that a given document
2982instance conforms to the set of rules detailing its structure and content.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002983
2984<p>Validation is the process of checking a document against a DTD (more
2985generally against a set of construction rules).</p>
2986
2987<p>The validation process and building DTDs are the two most difficult parts
Daniel Veillard0b28e882002-07-24 23:47:05 +00002988of the XML life cycle. Briefly a DTD defines all the possible elements to be
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002989found within your document, what is the formal shape of your document tree
Daniel Veillard0b28e882002-07-24 23:47:05 +00002990(by defining the allowed content of an element; either text, a regular
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002991expression for the allowed list of children, or mixed content i.e. both text
Daniel Veillard42766c02002-08-22 20:52:17 +00002992and children). The DTD also defines the valid attributes for all elements and
2993the types of those attributes.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002994
2995<h3><a name="definition1">The definition</a></h3>
2996
2997<p>The <a href="http://www.w3.org/TR/REC-xml">W3C XML Recommendation</a> (<a
2998href="http://www.xml.com/axml/axml.html">Tim Bray's annotated version of
2999Rev1</a>):</p>
3000<ul>
3001 <li><a href="http://www.w3.org/TR/REC-xml#elemdecls">Declaring
3002 elements</a></li>
3003 <li><a href="http://www.w3.org/TR/REC-xml#attdecls">Declaring
3004 attributes</a></li>
3005</ul>
3006
3007<p>(unfortunately) all this is inherited from the SGML world, the syntax is
3008ancient...</p>
3009
3010<h3><a name="Simple1">Simple rules</a></h3>
3011
Daniel Veillard42766c02002-08-22 20:52:17 +00003012<p>Writing DTDs can be done in many ways. The rules to build them if you need
3013something permanent or something which can evolve over time can be radically
3014different. Really complex DTDs like DocBook ones are flexible but quite
3015harder to design. I will just focus on DTDs for a formats with a fixed simple
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003016structure. It is just a set of basic rules, and definitely not exhaustive nor
Daniel Veillard63d83142002-05-20 06:51:05 +00003017usable for complex DTD design.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003018
3019<h4><a name="reference1">How to reference a DTD from a document</a>:</h4>
3020
3021<p>Assuming the top element of the document is <code>spec</code> and the dtd
3022is placed in the file <code>mydtd</code> in the subdirectory
3023<code>dtds</code> of the directory from where the document were loaded:</p>
3024
3025<p><code>&lt;!DOCTYPE spec SYSTEM "dtds/mydtd"&gt;</code></p>
3026
3027<p>Notes:</p>
3028<ul>
Daniel Veillard0b28e882002-07-24 23:47:05 +00003029 <li>The system string is actually an URI-Reference (as defined in <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003030 href="http://www.ietf.org/rfc/rfc2396.txt">RFC 2396</a>) so you can use a
Daniel Veillard0b28e882002-07-24 23:47:05 +00003031 full URL string indicating the location of your DTD on the Web. This is a
3032 really good thing to do if you want others to validate your document.</li>
3033 <li>It is also possible to associate a <code>PUBLIC</code> identifier (a
Daniel Veillard63d83142002-05-20 06:51:05 +00003034 magic string) so that the DTD is looked up in catalogs on the client side
Daniel Veillard0b28e882002-07-24 23:47:05 +00003035 without having to locate it on the web.</li>
3036 <li>A DTD contains a set of element and attribute declarations, but they
Daniel Veillard63d83142002-05-20 06:51:05 +00003037 don't define what the root of the document should be. This is explicitly
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003038 told to the parser/validator as the first element of the
3039 <code>DOCTYPE</code> declaration.</li>
3040</ul>
3041
3042<h4><a name="Declaring2">Declaring elements</a>:</h4>
3043
3044<p>The following declares an element <code>spec</code>:</p>
3045
3046<p><code>&lt;!ELEMENT spec (front, body, back?)&gt;</code></p>
3047
Daniel Veillard0b28e882002-07-24 23:47:05 +00003048<p>It also expresses that the spec element contains one <code>front</code>,
Daniel Veillardc0801af2002-05-28 16:28:42 +00003049one <code>body</code> and one optional <code>back</code> children elements in
3050this order. The declaration of one element of the structure and its content
3051are done in a single declaration. Similarly the following declares
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003052<code>div1</code> elements:</p>
3053
Daniel Veillard51737272002-01-23 23:10:38 +00003054<p><code>&lt;!ELEMENT div1 (head, (p | list | note)*, div2?)&gt;</code></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003055
Daniel Veillard0b28e882002-07-24 23:47:05 +00003056<p>which means div1 contains one <code>head</code> then a series of optional
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003057<code>p</code>, <code>list</code>s and <code>note</code>s and then an
3058optional <code>div2</code>. And last but not least an element can contain
3059text:</p>
3060
3061<p><code>&lt;!ELEMENT b (#PCDATA)&gt;</code></p>
3062
3063<p><code>b</code> contains text or being of mixed content (text and elements
3064in no particular order):</p>
3065
3066<p><code>&lt;!ELEMENT p (#PCDATA|a|ul|b|i|em)*&gt;</code></p>
3067
3068<p><code>p </code>can contain text or <code>a</code>, <code>ul</code>,
3069<code>b</code>, <code>i </code>or <code>em</code> elements in no particular
3070order.</p>
3071
3072<h4><a name="Declaring1">Declaring attributes</a>:</h4>
3073
Daniel Veillard0b28e882002-07-24 23:47:05 +00003074<p>Again the attributes declaration includes their content definition:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003075
3076<p><code>&lt;!ATTLIST termdef name CDATA #IMPLIED&gt;</code></p>
3077
3078<p>means that the element <code>termdef</code> can have a <code>name</code>
Daniel Veillard63d83142002-05-20 06:51:05 +00003079attribute containing text (<code>CDATA</code>) and which is optional
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003080(<code>#IMPLIED</code>). The attribute value can also be defined within a
3081set:</p>
3082
3083<p><code>&lt;!ATTLIST list type (bullets|ordered|glossary)
3084"ordered"&gt;</code></p>
3085
3086<p>means <code>list</code> element have a <code>type</code> attribute with 3
3087allowed values "bullets", "ordered" or "glossary" and which default to
Daniel Veillard63d83142002-05-20 06:51:05 +00003088"ordered" if the attribute is not explicitly specified.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003089
3090<p>The content type of an attribute can be text (<code>CDATA</code>),
3091anchor/reference/references
3092(<code>ID</code>/<code>IDREF</code>/<code>IDREFS</code>), entity(ies)
3093(<code>ENTITY</code>/<code>ENTITIES</code>) or name(s)
3094(<code>NMTOKEN</code>/<code>NMTOKENS</code>). The following defines that a
3095<code>chapter</code> element can have an optional <code>id</code> attribute
3096of type <code>ID</code>, usable for reference from attribute of type
3097IDREF:</p>
3098
3099<p><code>&lt;!ATTLIST chapter id ID #IMPLIED&gt;</code></p>
3100
3101<p>The last value of an attribute definition can be <code>#REQUIRED
3102</code>meaning that the attribute has to be given, <code>#IMPLIED</code>
3103meaning that it is optional, or the default value (possibly prefixed by
3104<code>#FIXED</code> if it is the only allowed).</p>
3105
3106<p>Notes:</p>
3107<ul>
Daniel Veillard0b28e882002-07-24 23:47:05 +00003108 <li>Usually the attributes pertaining to a given element are declared in a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003109 single expression, but it is just a convention adopted by a lot of DTD
3110 writers:
3111 <pre>&lt;!ATTLIST termdef
3112 id ID #REQUIRED
3113 name CDATA #IMPLIED&gt;</pre>
3114 <p>The previous construct defines both <code>id</code> and
Daniel Veillard0b28e882002-07-24 23:47:05 +00003115 <code>name</code> attributes for the element <code>termdef</code>.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003116 </li>
3117</ul>
3118
3119<h3><a name="Some1">Some examples</a></h3>
3120
Daniel Veillard8a469172003-06-12 16:05:07 +00003121<p>The directory <code>test/valid/dtds/</code> in the libxml2 distribution
Daniel Veillard42766c02002-08-22 20:52:17 +00003122contains some complex DTD examples. The example in the file
3123<code>test/valid/dia.xml</code> shows an XML file where the simple DTD is
3124directly included within the document.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003125
3126<h3><a name="validate1">How to validate</a></h3>
3127
Daniel Veillard0b28e882002-07-24 23:47:05 +00003128<p>The simplest way is to use the xmllint program included with libxml. The
3129<code>--valid</code> option turns-on validation of the files given as input.
3130For example the following validates a copy of the first revision of the XML
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000031311.0 specification:</p>
3132
3133<p><code>xmllint --valid --noout test/valid/REC-xml-19980210.xml</code></p>
3134
Daniel Veillard0b28e882002-07-24 23:47:05 +00003135<p>the -- noout is used to disable output of the resulting tree.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003136
Daniel Veillard42766c02002-08-22 20:52:17 +00003137<p>The <code>--dtdvalid dtd</code> allows validation of the document(s)
3138against a given DTD.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003139
Daniel Veillard8a469172003-06-12 16:05:07 +00003140<p>Libxml2 exports an API to handle DTDs and validation, check the <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003141href="http://xmlsoft.org/html/libxml-valid.html">associated
3142description</a>.</p>
3143
3144<h3><a name="Other1">Other resources</a></h3>
3145
3146<p>DTDs are as old as SGML. So there may be a number of examples on-line, I
3147will just list one for now, others pointers welcome:</p>
3148<ul>
3149 <li><a href="http://www.xml101.com:8081/dtd/">XML-101 DTD</a></li>
3150</ul>
3151
3152<p>I suggest looking at the examples found under test/valid/dtd and any of
3153the large number of books available on XML. The dia example in test/valid
3154should be both simple and complete enough to allow you to build your own.</p>
3155
3156<p></p>
3157
3158<h2><a name="Memory">Memory Management</a></h2>
3159
3160<p>Table of Content:</p>
3161<ol>
3162 <li><a href="#General3">General overview</a></li>
Daniel Veillard8a469172003-06-12 16:05:07 +00003163 <li><a href="#setting">Setting libxml2 set of memory routines</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003164 <li><a href="#cleanup">Cleaning up after parsing</a></li>
3165 <li><a href="#Debugging">Debugging routines</a></li>
3166 <li><a href="#General4">General memory requirements</a></li>
3167</ol>
3168
3169<h3><a name="General3">General overview</a></h3>
3170
3171<p>The module <code><a
3172href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlmemory.h</a></code>
Daniel Veillard8a469172003-06-12 16:05:07 +00003173provides the interfaces to the libxml2 memory system:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003174<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +00003175 <li>libxml2 does not use the libc memory allocator directly but xmlFree(),
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003176 xmlMalloc() and xmlRealloc()</li>
3177 <li>those routines can be reallocated to a specific set of routine, by
3178 default the libc ones i.e. free(), malloc() and realloc()</li>
3179 <li>the xmlmemory.c module includes a set of debugging routine</li>
3180</ul>
3181
Daniel Veillard8a469172003-06-12 16:05:07 +00003182<h3><a name="setting">Setting libxml2 set of memory routines</a></h3>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003183
3184<p>It is sometimes useful to not use the default memory allocator, either for
3185debugging, analysis or to implement a specific behaviour on memory management
3186(like on embedded systems). Two function calls are available to do so:</p>
3187<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +00003188 <li><a href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemGet
3189 ()</a> which return the current set of functions in use by the parser</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003190 <li><a
3191 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemSetup()</a>
Daniel Veillardaf43f632002-03-08 15:05:20 +00003192 which allow to set up a new set of memory allocation functions</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003193</ul>
3194
3195<p>Of course a call to xmlMemSetup() should probably be done before calling
Daniel Veillard8a469172003-06-12 16:05:07 +00003196any other libxml2 routines (unless you are sure your allocations routines are
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003197compatibles).</p>
3198
3199<h3><a name="cleanup">Cleaning up after parsing</a></h3>
3200
Daniel Veillard8a469172003-06-12 16:05:07 +00003201<p>Libxml2 is not stateless, there is a few set of memory structures needing
Daniel Veillard63d83142002-05-20 06:51:05 +00003202allocation before the parser is fully functional (some encoding structures
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003203for example). This also mean that once parsing is finished there is a tiny
3204amount of memory (a few hundred bytes) which can be recollected if you don't
3205reuse the parser immediately:</p>
3206<ul>
3207 <li><a href="http://xmlsoft.org/html/libxml-parser.html">xmlCleanupParser
Daniel Veillardaf43f632002-03-08 15:05:20 +00003208 ()</a> is a centralized routine to free the parsing states. Note that it
3209 won't deallocate any produced tree if any (use the xmlFreeDoc() and
3210 related routines for this).</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003211 <li><a href="http://xmlsoft.org/html/libxml-parser.html">xmlInitParser
Daniel Veillardaf43f632002-03-08 15:05:20 +00003212 ()</a> is the dual routine allowing to preallocate the parsing state
3213 which can be useful for example to avoid initialization reentrancy
Daniel Veillard8a469172003-06-12 16:05:07 +00003214 problems when using libxml2 in multithreaded applications</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003215</ul>
3216
3217<p>Generally xmlCleanupParser() is safe, if needed the state will be rebuild
3218at the next invocation of parser routines, but be careful of the consequences
3219in multithreaded applications.</p>
3220
3221<h3><a name="Debugging">Debugging routines</a></h3>
3222
Daniel Veillard8a469172003-06-12 16:05:07 +00003223<p>When configured using --with-mem-debug flag (off by default), libxml2 uses
Daniel Veillard63d83142002-05-20 06:51:05 +00003224a set of memory allocation debugging routines keeping track of all allocated
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003225blocks and the location in the code where the routine was called. A couple of
3226other debugging routines allow to dump the memory allocated infos to a file
3227or call a specific routine when a given block number is allocated:</p>
3228<ul>
3229 <li><a
3230 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMallocLoc()</a>
Daniel Veillardaf43f632002-03-08 15:05:20 +00003231 <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003232 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlReallocLoc()</a>
3233 and <a
3234 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemStrdupLoc()</a>
3235 are the memory debugging replacement allocation routines</li>
3236 <li><a href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemoryDump
Daniel Veillardaf43f632002-03-08 15:05:20 +00003237 ()</a> dumps all the informations about the allocated memory block lefts
3238 in the <code>.memdump</code> file</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003239</ul>
3240
Daniel Veillard8a469172003-06-12 16:05:07 +00003241<p>When developing libxml2 memory debug is enabled, the tests programs call
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003242xmlMemoryDump () and the "make test" regression tests will check for any
3243memory leak during the full regression test sequence, this helps a lot
Daniel Veillard8a469172003-06-12 16:05:07 +00003244ensuring that libxml2 does not leak memory and bullet proof memory
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003245allocations use (some libc implementations are known to be far too permissive
3246resulting in major portability problems!).</p>
3247
3248<p>If the .memdump reports a leak, it displays the allocation function and
3249also tries to give some informations about the content and structure of the
3250allocated blocks left. This is sufficient in most cases to find the culprit,
Daniel Veillard63d83142002-05-20 06:51:05 +00003251but not always. Assuming the allocation problem is reproducible, it is
3252possible to find more easily:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003253<ol>
3254 <li>write down the block number xxxx not allocated</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00003255 <li>export the environment variable XML_MEM_BREAKPOINT=xxxx , the easiest
Daniel Veillard75794822002-04-11 16:24:32 +00003256 when using GDB is to simply give the command
3257 <p><code>set environment XML_MEM_BREAKPOINT xxxx</code></p>
3258 <p>before running the program.</p>
3259 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003260 <li>run the program under a debugger and set a breakpoint on
3261 xmlMallocBreakpoint() a specific function called when this precise block
3262 is allocated</li>
3263 <li>when the breakpoint is reached you can then do a fine analysis of the
3264 allocation an step to see the condition resulting in the missing
3265 deallocation.</li>
3266</ol>
3267
Daniel Veillard8a469172003-06-12 16:05:07 +00003268<p>I used to use a commercial tool to debug libxml2 memory problems but after
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003269noticing that it was not detecting memory leaks that simple mechanism was
Daniel Veillard75794822002-04-11 16:24:32 +00003270used and proved extremely efficient until now. Lately I have also used <a
3271href="http://developer.kde.org/~sewardj/">valgrind</a> with quite some
3272success, it is tied to the i386 architecture since it works by emulating the
3273processor and instruction set, it is slow but extremely efficient, i.e. it
3274spot memory usage errors in a very precise way.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003275
3276<h3><a name="General4">General memory requirements</a></h3>
3277
Daniel Veillard8a469172003-06-12 16:05:07 +00003278<p>How much libxml2 memory require ? It's hard to tell in average it depends
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003279of a number of things:</p>
3280<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00003281 <li>the parser itself should work in a fixed amount of memory, except for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003282 information maintained about the stacks of names and entities locations.
3283 The I/O and encoding handlers will probably account for a few KBytes.
3284 This is true for both the XML and HTML parser (though the HTML parser
3285 need more state).</li>
3286 <li>If you are generating the DOM tree then memory requirements will grow
Daniel Veillard63d83142002-05-20 06:51:05 +00003287 nearly linear with the size of the data. In general for a balanced
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003288 textual document the internal memory requirement is about 4 times the
Daniel Veillard63d83142002-05-20 06:51:05 +00003289 size of the UTF8 serialization of this document (example the XML-1.0
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003290 recommendation is a bit more of 150KBytes and takes 650KBytes of main
3291 memory when parsed). Validation will add a amount of memory required for
3292 maintaining the external Dtd state which should be linear with the
3293 complexity of the content model defined by the Dtd</li>
Daniel Veillardce192eb2003-04-16 15:58:05 +00003294 <li>If you need to work with fixed memory requirements or don't need the
3295 full DOM tree then using the <a href="xmlreader.html">xmlReader
3296 interface</a> is probably the best way to proceed, it still allows to
3297 validate or operate on subset of the tree if needed.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +00003298 <li>If you don't care about the advanced features of libxml2 like
Daniel Veillardce192eb2003-04-16 15:58:05 +00003299 validation, DOM, XPath or XPointer, don't use entities, need to work with
3300 fixed memory requirements, and try to get the fastest parsing possible
3301 then the SAX interface should be used, but it has known restrictions.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003302</ul>
3303
3304<p></p>
3305
3306<h2><a name="Encodings">Encodings support</a></h2>
3307
Daniel Veillarde5d68de2005-03-10 15:03:40 +00003308<p>If you are not really familiar with Internationalization (usual shortcut
3309is I18N) , Unicode, characters and glyphs, I suggest you read a <a
3310href="http://www.tbray.org/ongoing/When/200x/2003/04/06/Unicode">presentation</a>
3311by Tim Bray on Unicode and why you should care about it.</p>
Daniel Veillard67952602006-01-05 15:29:44 +00003312
Daniel Veillarde5d68de2005-03-10 15:03:40 +00003313<p>If you don't understand why <b>it does not make sense to have a string
Daniel Veillard67952602006-01-05 15:29:44 +00003314without knowing what encoding it uses</b>, then as Joel Spolsky said <a
3315href="http://www.joelonsoftware.com/articles/Unicode.html">please do not
3316write another line of code until you finish reading that article.</a>. It is
3317a prerequisite to understand this page, and avoid a lot of problems with
3318libxml2, XML or text processing in general.</p>
Daniel Veillarde5d68de2005-03-10 15:03:40 +00003319
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003320<p>Table of Content:</p>
3321<ol>
3322 <li><a href="encoding.html#What">What does internationalization support
3323 mean ?</a></li>
3324 <li><a href="encoding.html#internal">The internal encoding, how and
3325 why</a></li>
3326 <li><a href="encoding.html#implemente">How is it implemented ?</a></li>
3327 <li><a href="encoding.html#Default">Default supported encodings</a></li>
3328 <li><a href="encoding.html#extend">How to extend the existing
3329 support</a></li>
3330</ol>
3331
3332<h3><a name="What">What does internationalization support mean ?</a></h3>
3333
3334<p>XML was designed from the start to allow the support of any character set
3335by using Unicode. Any conformant XML parser has to support the UTF-8 and
3336UTF-16 default encodings which can both express the full unicode ranges. UTF8
Daniel Veillard63d83142002-05-20 06:51:05 +00003337is a variable length encoding whose greatest points are to reuse the same
3338encoding for ASCII and to save space for Western encodings, but it is a bit
Daniel Veillardabfca612004-01-07 23:38:02 +00003339more complex to handle in practice. UTF-16 use 2 bytes per character (and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003340sometimes combines two pairs), it makes implementation easier, but looks a
3341bit overkill for Western languages encoding. Moreover the XML specification
Daniel Veillard189f46b2004-01-25 21:03:04 +00003342allows the document to be encoded in other encodings at the condition that
3343they are clearly labeled as such. For example the following is a wellformed
3344XML document encoded in ISO-8859-1 and using accentuated letters that we
3345French like for both markup and content:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003346<pre>&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
3347&lt;très&gt;là&lt;/très&gt;</pre>
3348
Daniel Veillard8a469172003-06-12 16:05:07 +00003349<p>Having internationalization support in libxml2 means the following:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003350<ul>
3351 <li>the document is properly parsed</li>
3352 <li>informations about it's encoding are saved</li>
3353 <li>it can be modified</li>
3354 <li>it can be saved in its original encoding</li>
Daniel Veillard8a469172003-06-12 16:05:07 +00003355 <li>it can also be saved in another encoding supported by libxml2 (for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003356 example straight UTF8 or even an ASCII form)</li>
3357</ul>
3358
Daniel Veillard8a469172003-06-12 16:05:07 +00003359<p>Another very important point is that the whole libxml2 API, with the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003360exception of a few routines to read with a specific encoding or save to a
3361specific encoding, is completely agnostic about the original encoding of the
3362document.</p>
3363
Daniel Veillard8a469172003-06-12 16:05:07 +00003364<p>It should be noted too that the HTML parser embedded in libxml2 now obey
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003365the same rules too, the following document will be (as of 2.2.2) handled in
Daniel Veillard8a469172003-06-12 16:05:07 +00003366an internationalized fashion by libxml2 too:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003367<pre>&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
3368 "http://www.w3.org/TR/REC-html40/loose.dtd"&gt;
3369&lt;html lang="fr"&gt;
3370&lt;head&gt;
3371 &lt;META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"&gt;
3372&lt;/head&gt;
3373&lt;body&gt;
3374&lt;p&gt;W3C crée des standards pour le Web.&lt;/body&gt;
3375&lt;/html&gt;</pre>
3376
3377<h3><a name="internal">The internal encoding, how and why</a></h3>
3378
Daniel Veillardabfca612004-01-07 23:38:02 +00003379<p>One of the core decisions was to force all documents to be converted to a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003380default internal encoding, and that encoding to be UTF-8, here are the
Daniel Veillardabfca612004-01-07 23:38:02 +00003381rationales for those choices:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003382<ul>
3383 <li>keeping the native encoding in the internal form would force the libxml
3384 users (or the code associated) to be fully aware of the encoding of the
3385 original document, for examples when adding a text node to a document,
3386 the content would have to be provided in the document encoding, i.e. the
3387 client code would have to check it before hand, make sure it's conformant
3388 to the encoding, etc ... Very hard in practice, though in some specific
3389 cases this may make sense.</li>
3390 <li>the second decision was which encoding. From the XML spec only UTF8 and
3391 UTF16 really makes sense as being the two only encodings for which there
Daniel Veillard63d83142002-05-20 06:51:05 +00003392 is mandatory support. UCS-4 (32 bits fixed size encoding) could be
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003393 considered an intelligent choice too since it's a direct Unicode mapping
3394 support. I selected UTF-8 on the basis of efficiency and compatibility
3395 with surrounding software:
3396 <ul>
3397 <li>UTF-8 while a bit more complex to convert from/to (i.e. slightly
3398 more costly to import and export CPU wise) is also far more compact
3399 than UTF-16 (and UCS-4) for a majority of the documents I see it used
3400 for right now (RPM RDF catalogs, advogato data, various configuration
3401 file formats, etc.) and the key point for today's computer
3402 architecture is efficient uses of caches. If one nearly double the
3403 memory requirement to store the same amount of data, this will trash
3404 caches (main memory/external caches/internal caches) and my take is
3405 that this harms the system far more than the CPU requirements needed
3406 for the conversion to UTF-8</li>
Daniel Veillard8a469172003-06-12 16:05:07 +00003407 <li>Most of libxml2 version 1 users were using it with straight ASCII
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003408 most of the time, doing the conversion with an internal encoding
3409 requiring all their code to be rewritten was a serious show-stopper
3410 for using UTF-16 or UCS-4.</li>
3411 <li>UTF-8 is being used as the de-facto internal encoding standard for
3412 related code like the <a href="http://www.pango.org/">pango</a>
Daniel Veillardabfca612004-01-07 23:38:02 +00003413 upcoming Gnome text widget, and a lot of Unix code (yet another place
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003414 where Unix programmer base takes a different approach from Microsoft
3415 - they are using UTF-16)</li>
3416 </ul>
3417 </li>
3418</ul>
3419
Daniel Veillard8a469172003-06-12 16:05:07 +00003420<p>What does this mean in practice for the libxml2 user:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003421<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +00003422 <li>xmlChar, the libxml2 data type is a byte, those bytes must be assembled
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003423 as UTF-8 valid strings. The proper way to terminate an xmlChar * string
3424 is simply to append 0 byte, as usual.</li>
3425 <li>One just need to make sure that when using chars outside the ASCII set,
3426 the values has been properly converted to UTF-8</li>
3427</ul>
3428
3429<h3><a name="implemente">How is it implemented ?</a></h3>
3430
3431<p>Let's describe how all this works within libxml, basically the I18N
3432(internationalization) support get triggered only during I/O operation, i.e.
3433when reading a document or saving one. Let's look first at the reading
3434sequence:</p>
3435<ol>
3436 <li>when a document is processed, we usually don't know the encoding, a
Daniel Veillard189f46b2004-01-25 21:03:04 +00003437 simple heuristic allows to detect UTF-16 and UCS-4 from encodings where
3438 the ASCII range (0-0x7F) maps with ASCII</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003439 <li>the xml declaration if available is parsed, including the encoding
3440 declaration. At that point, if the autodetected encoding is different
3441 from the one declared a call to xmlSwitchEncoding() is issued.</li>
3442 <li>If there is no encoding declaration, then the input has to be in either
3443 UTF-8 or UTF-16, if it is not then at some point when processing the
3444 input, the converter/checker of UTF-8 form will raise an encoding error.
3445 You may end-up with a garbled document, or no document at all ! Example:
3446 <pre>~/XML -&gt; ./xmllint err.xml
3447err.xml:1: error: Input is not proper UTF-8, indicate encoding !
3448&lt;très&gt;là&lt;/très&gt;
3449 ^
3450err.xml:1: error: Bytes: 0xE8 0x73 0x3E 0x6C
3451&lt;très&gt;là&lt;/très&gt;
3452 ^</pre>
3453 </li>
Daniel Veillard63d83142002-05-20 06:51:05 +00003454 <li>xmlSwitchEncoding() does an encoding name lookup, canonicalize it, and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003455 then search the default registered encoding converters for that encoding.
3456 If it's not within the default set and iconv() support has been compiled
3457 it, it will ask iconv for such an encoder. If this fails then the parser
3458 will report an error and stops processing:
3459 <pre>~/XML -&gt; ./xmllint err2.xml
3460err2.xml:1: error: Unsupported encoding UnsupportedEnc
3461&lt;?xml version="1.0" encoding="UnsupportedEnc"?&gt;
3462 ^</pre>
3463 </li>
Daniel Veillard46c5c1d2002-05-20 07:15:54 +00003464 <li>From that point the encoder processes progressively the input (it is
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003465 plugged as a front-end to the I/O module) for that entity. It captures
Daniel Veillardabfca612004-01-07 23:38:02 +00003466 and converts on-the-fly the document to be parsed to UTF-8. The parser
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003467 itself just does UTF-8 checking of this input and process it
3468 transparently. The only difference is that the encoding information has
3469 been added to the parsing context (more precisely to the input
3470 corresponding to this entity).</li>
3471 <li>The result (when using DOM) is an internal form completely in UTF-8
3472 with just an encoding information on the document node.</li>
3473</ol>
3474
Daniel Veillard63d83142002-05-20 06:51:05 +00003475<p>Ok then what happens when saving the document (assuming you
3476collected/built an xmlDoc DOM like structure) ? It depends on the function
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003477called, xmlSaveFile() will just try to save in the original encoding, while
3478xmlSaveFileTo() and xmlSaveFileEnc() can optionally save to a given
3479encoding:</p>
3480<ol>
Daniel Veillard8a469172003-06-12 16:05:07 +00003481 <li>if no encoding is given, libxml2 will look for an encoding value
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003482 associated to the document and if it exists will try to save to that
3483 encoding,
3484 <p>otherwise everything is written in the internal form, i.e. UTF-8</p>
3485 </li>
3486 <li>so if an encoding was specified, either at the API level or on the
Daniel Veillard8a469172003-06-12 16:05:07 +00003487 document, libxml2 will again canonicalize the encoding name, lookup for a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003488 converter in the registered set or through iconv. If not found the
3489 function will return an error code</li>
3490 <li>the converter is placed before the I/O buffer layer, as another kind of
Daniel Veillard8a469172003-06-12 16:05:07 +00003491 buffer, then libxml2 will simply push the UTF-8 serialization to through
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003492 that buffer, which will then progressively be converted and pushed onto
3493 the I/O layer.</li>
3494 <li>It is possible that the converter code fails on some input, for example
Daniel Veillard63d83142002-05-20 06:51:05 +00003495 trying to push an UTF-8 encoded Chinese character through the UTF-8 to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003496 ISO-8859-1 converter won't work. Since the encoders are progressive they
3497 will just report the error and the number of bytes converted, at that
Daniel Veillard8a469172003-06-12 16:05:07 +00003498 point libxml2 will decode the offending character, remove it from the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003499 buffer and replace it with the associated charRef encoding &amp;#123; and
Daniel Veillard63d83142002-05-20 06:51:05 +00003500 resume the conversion. This guarantees that any document will be saved
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003501 without losses (except for markup names where this is not legal, this is
Daniel Veillard63d83142002-05-20 06:51:05 +00003502 a problem in the current version, in practice avoid using non-ascii
Daniel Veillard189f46b2004-01-25 21:03:04 +00003503 characters for tag or attribute names). A special "ascii" encoding name
3504 is used to save documents to a pure ascii form can be used when
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003505 portability is really crucial</li>
3506</ol>
3507
Daniel Veillardabfca612004-01-07 23:38:02 +00003508<p>Here are a few examples based on the same test document:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003509<pre>~/XML -&gt; ./xmllint isolat1
3510&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
3511&lt;très&gt;là&lt;/très&gt;
3512~/XML -&gt; ./xmllint --encode UTF-8 isolat1
3513&lt;?xml version="1.0" encoding="UTF-8"?&gt;
Daniel Veillard67952602006-01-05 15:29:44 +00003514&lt;très&gt;là &nbsp;&lt;/très&gt;
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003515~/XML -&gt; </pre>
3516
3517<p>The same processing is applied (and reuse most of the code) for HTML I18N
3518processing. Looking up and modifying the content encoding is a bit more
3519difficult since it is located in a &lt;meta&gt; tag under the &lt;head&gt;,
3520so a couple of functions htmlGetMetaEncoding() and htmlSetMetaEncoding() have
3521been provided. The parser also attempts to switch encoding on the fly when
3522detecting such a tag on input. Except for that the processing is the same
3523(and again reuses the same code).</p>
3524
3525<h3><a name="Default">Default supported encodings</a></h3>
3526
Daniel Veillard8a469172003-06-12 16:05:07 +00003527<p>libxml2 has a set of default converters for the following encodings
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003528(located in encoding.c):</p>
3529<ol>
3530 <li>UTF-8 is supported by default (null handlers)</li>
3531 <li>UTF-16, both little and big endian</li>
3532 <li>ISO-Latin-1 (ISO-8859-1) covering most western languages</li>
3533 <li>ASCII, useful mostly for saving</li>
3534 <li>HTML, a specific handler for the conversion of UTF-8 to ASCII with HTML
3535 predefined entities like &amp;copy; for the Copyright sign.</li>
3536</ol>
3537
Daniel Veillardc0801af2002-05-28 16:28:42 +00003538<p>More over when compiled on an Unix platform with iconv support the full
3539set of encodings supported by iconv can be instantly be used by libxml. On a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003540linux machine with glibc-2.1 the list of supported encodings and aliases fill
35413 full pages, and include UCS-4, the full set of ISO-Latin encodings, and the
3542various Japanese ones.</p>
Daniel Veillard67952602006-01-05 15:29:44 +00003543
Daniel Veillardfdba0de2005-09-16 08:19:43 +00003544<p>To convert from the UTF-8 values returned from the API to another encoding
Daniel Veillard67952602006-01-05 15:29:44 +00003545then it is possible to use the function provided from <a
3546href="html/libxml-encoding.html">the encoding module</a> like <a
3547href="html/libxml-encoding.html#UTF8Toisolat1">UTF8Toisolat1</a>, or use the
3548POSIX <a
3549href="http://www.opengroup.org/onlinepubs/009695399/functions/iconv.html">iconv()</a>
3550API directly.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003551
3552<h4>Encoding aliases</h4>
3553
Daniel Veillard8a469172003-06-12 16:05:07 +00003554<p>From 2.2.3, libxml2 has support to register encoding names aliases. The
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003555goal is to be able to parse document whose encoding is supported but where
3556the name differs (for example from the default set of names accepted by
3557iconv). The following functions allow to register and handle new aliases for
Daniel Veillard8a469172003-06-12 16:05:07 +00003558existing encodings. Once registered libxml2 will automatically lookup the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003559aliases when handling a document:</p>
3560<ul>
3561 <li>int xmlAddEncodingAlias(const char *name, const char *alias);</li>
3562 <li>int xmlDelEncodingAlias(const char *alias);</li>
3563 <li>const char * xmlGetEncodingAlias(const char *alias);</li>
3564 <li>void xmlCleanupEncodingAliases(void);</li>
3565</ul>
3566
3567<h3><a name="extend">How to extend the existing support</a></h3>
3568
3569<p>Well adding support for new encoding, or overriding one of the encoders
Daniel Veillardabfca612004-01-07 23:38:02 +00003570(assuming it is buggy) should not be hard, just write input and output
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003571conversion routines to/from UTF-8, and register them using
3572xmlNewCharEncodingHandler(name, xxxToUTF8, UTF8Toxxx), and they will be
3573called automatically if the parser(s) encounter such an encoding name
3574(register it uppercase, this will help). The description of the encoders,
3575their arguments and expected return values are described in the encoding.h
3576header.</p>
3577
3578<p>A quick note on the topic of subverting the parser to use a different
3579internal encoding than UTF-8, in some case people will absolutely want to
3580keep the internal encoding different, I think it's still possible (but the
3581encoding must be compliant with ASCII on the same subrange) though I didn't
3582tried it. The key is to override the default conversion routines (by
3583registering null encoders/decoders for your charsets), and bypass the UTF-8
3584checking of the parser by setting the parser context charset
3585(ctxt-&gt;charset) to something different than XML_CHAR_ENCODING_UTF8, but
Daniel Veillard63d83142002-05-20 06:51:05 +00003586there is no guarantee that this will work. You may also have some troubles
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003587saving back.</p>
3588
3589<p>Basically proper I18N support is important, this requires at least
3590libxml-2.0.0, but a lot of features and corrections are really available only
3591starting 2.2.</p>
3592
3593<h2><a name="IO">I/O Interfaces</a></h2>
3594
3595<p>Table of Content:</p>
3596<ol>
3597 <li><a href="#General1">General overview</a></li>
3598 <li><a href="#basic">The basic buffer type</a></li>
3599 <li><a href="#Input">Input I/O handlers</a></li>
3600 <li><a href="#Output">Output I/O handlers</a></li>
3601 <li><a href="#entities">The entities loader</a></li>
3602 <li><a href="#Example2">Example of customized I/O</a></li>
3603</ol>
3604
3605<h3><a name="General1">General overview</a></h3>
3606
3607<p>The module <code><a
3608href="http://xmlsoft.org/html/libxml-xmlio.html">xmlIO.h</a></code> provides
Daniel Veillard8a469172003-06-12 16:05:07 +00003609the interfaces to the libxml2 I/O system. This consists of 4 main parts:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003610<ul>
3611 <li>Entities loader, this is a routine which tries to fetch the entities
3612 (files) based on their PUBLIC and SYSTEM identifiers. The default loader
Daniel Veillard8a469172003-06-12 16:05:07 +00003613 don't look at the public identifier since libxml2 do not maintain a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003614 catalog. You can redefine you own entity loader by using
3615 <code>xmlGetExternalEntityLoader()</code> and
Daniel Veillard9c466822001-10-25 12:03:39 +00003616 <code>xmlSetExternalEntityLoader()</code>. <a href="#entities">Check the
3617 example</a>.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003618 <li>Input I/O buffers which are a commodity structure used by the parser(s)
3619 input layer to handle fetching the informations to feed the parser. This
3620 provides buffering and is also a placeholder where the encoding
Daniel Veillard63d83142002-05-20 06:51:05 +00003621 converters to UTF8 are piggy-backed.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003622 <li>Output I/O buffers are similar to the Input ones and fulfill similar
3623 task but when generating a serialization from a tree.</li>
3624 <li>A mechanism to register sets of I/O callbacks and associate them with
3625 specific naming schemes like the protocol part of the URIs.
3626 <p>This affect the default I/O operations and allows to use specific I/O
3627 handlers for certain names.</p>
3628 </li>
3629</ul>
3630
3631<p>The general mechanism used when loading http://rpmfind.net/xml.html for
3632example in the HTML parser is the following:</p>
3633<ol>
3634 <li>The default entity loader calls <code>xmlNewInputFromFile()</code> with
3635 the parsing context and the URI string.</li>
3636 <li>the URI string is checked against the existing registered handlers
3637 using their match() callback function, if the HTTP module was compiled
3638 in, it is registered and its match() function will succeeds</li>
3639 <li>the open() function of the handler is called and if successful will
3640 return an I/O Input buffer</li>
3641 <li>the parser will the start reading from this buffer and progressively
3642 fetch information from the resource, calling the read() function of the
3643 handler until the resource is exhausted</li>
3644 <li>if an encoding change is detected it will be installed on the input
3645 buffer, providing buffering and efficient use of the conversion
3646 routines</li>
3647 <li>once the parser has finished, the close() function of the handler is
Daniel Veillard63d83142002-05-20 06:51:05 +00003648 called once and the Input buffer and associated resources are
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003649 deallocated.</li>
3650</ol>
3651
3652<p>The user defined callbacks are checked first to allow overriding of the
Daniel Veillard8a469172003-06-12 16:05:07 +00003653default libxml2 I/O routines.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003654
3655<h3><a name="basic">The basic buffer type</a></h3>
3656
3657<p>All the buffer manipulation handling is done using the
3658<code>xmlBuffer</code> type define in <code><a
3659href="http://xmlsoft.org/html/libxml-tree.html">tree.h</a> </code>which is a
3660resizable memory buffer. The buffer allocation strategy can be selected to be
3661either best-fit or use an exponential doubling one (CPU vs. memory use
Daniel Veillard63d83142002-05-20 06:51:05 +00003662trade-off). The values are <code>XML_BUFFER_ALLOC_EXACT</code> and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003663<code>XML_BUFFER_ALLOC_DOUBLEIT</code>, and can be set individually or on a
3664system wide basis using <code>xmlBufferSetAllocationScheme()</code>. A number
3665of functions allows to manipulate buffers with names starting with the
3666<code>xmlBuffer...</code> prefix.</p>
3667
3668<h3><a name="Input">Input I/O handlers</a></h3>
3669
3670<p>An Input I/O handler is a simple structure
3671<code>xmlParserInputBuffer</code> containing a context associated to the
3672resource (file descriptor, or pointer to a protocol handler), the read() and
3673close() callbacks to use and an xmlBuffer. And extra xmlBuffer and a charset
3674encoding handler are also present to support charset conversion when
3675needed.</p>
3676
3677<h3><a name="Output">Output I/O handlers</a></h3>
3678
3679<p>An Output handler <code>xmlOutputBuffer</code> is completely similar to an
3680Input one except the callbacks are write() and close().</p>
3681
3682<h3><a name="entities">The entities loader</a></h3>
3683
3684<p>The entity loader resolves requests for new entities and create inputs for
3685the parser. Creating an input from a filename or an URI string is done
3686through the xmlNewInputFromFile() routine. The default entity loader do not
3687handle the PUBLIC identifier associated with an entity (if any). So it just
3688calls xmlNewInputFromFile() with the SYSTEM identifier (which is mandatory in
3689XML).</p>
3690
3691<p>If you want to hook up a catalog mechanism then you simply need to
3692override the default entity loader, here is an example:</p>
3693<pre>#include &lt;libxml/xmlIO.h&gt;
3694
3695xmlExternalEntityLoader defaultLoader = NULL;
3696
3697xmlParserInputPtr
3698xmlMyExternalEntityLoader(const char *URL, const char *ID,
3699 xmlParserCtxtPtr ctxt) {
3700 xmlParserInputPtr ret;
3701 const char *fileID = NULL;
3702 /* lookup for the fileID depending on ID */
3703
3704 ret = xmlNewInputFromFile(ctxt, fileID);
3705 if (ret != NULL)
3706 return(ret);
3707 if (defaultLoader != NULL)
3708 ret = defaultLoader(URL, ID, ctxt);
3709 return(ret);
3710}
3711
3712int main(..) {
3713 ...
3714
3715 /*
3716 * Install our own entity loader
3717 */
3718 defaultLoader = xmlGetExternalEntityLoader();
3719 xmlSetExternalEntityLoader(xmlMyExternalEntityLoader);
3720
3721 ...
3722}</pre>
3723
3724<h3><a name="Example2">Example of customized I/O</a></h3>
3725
3726<p>This example come from <a href="http://xmlsoft.org/messages/0708.html">a
3727real use case</a>, xmlDocDump() closes the FILE * passed by the application
3728and this was a problem. The <a
3729href="http://xmlsoft.org/messages/0711.html">solution</a> was to redefine a
3730new output handler with the closing call deactivated:</p>
3731<ol>
Daniel Veillardc0801af2002-05-28 16:28:42 +00003732 <li>First define a new I/O output allocator where the output don't close
3733 the file:
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003734 <pre>xmlOutputBufferPtr
3735xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) {
Daniel Veillard67952602006-01-05 15:29:44 +00003736&nbsp;&nbsp;&nbsp;&nbsp;xmlOutputBufferPtr ret;
3737&nbsp;&nbsp;&nbsp;&nbsp;
3738&nbsp;&nbsp;&nbsp;&nbsp;if (xmlOutputCallbackInitialized == 0)
3739&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;xmlRegisterDefaultOutputCallbacks();
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003740
Daniel Veillard67952602006-01-05 15:29:44 +00003741&nbsp;&nbsp;&nbsp;&nbsp;if (file == NULL) return(NULL);
3742&nbsp;&nbsp;&nbsp;&nbsp;ret = xmlAllocOutputBuffer(encoder);
3743&nbsp;&nbsp;&nbsp;&nbsp;if (ret != NULL) {
3744&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ret-&gt;context = file;
3745&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ret-&gt;writecallback = xmlFileWrite;
3746&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ret-&gt;closecallback = NULL; /* No close callback */
3747&nbsp;&nbsp;&nbsp;&nbsp;}
3748&nbsp;&nbsp;&nbsp;&nbsp;return(ret);
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003749} </pre>
3750 </li>
3751 <li>And then use it to save the document:
3752 <pre>FILE *f;
3753xmlOutputBufferPtr output;
3754xmlDocPtr doc;
3755int res;
3756
3757f = ...
3758doc = ....
3759
3760output = xmlOutputBufferCreateOwn(f, NULL);
3761res = xmlSaveFileTo(output, doc, NULL);
3762 </pre>
3763 </li>
3764</ol>
3765
3766<h2><a name="Catalog">Catalog support</a></h2>
3767
3768<p>Table of Content:</p>
3769<ol>
3770 <li><a href="General2">General overview</a></li>
3771 <li><a href="#definition">The definition</a></li>
3772 <li><a href="#Simple">Using catalogs</a></li>
3773 <li><a href="#Some">Some examples</a></li>
3774 <li><a href="#reference">How to tune catalog usage</a></li>
3775 <li><a href="#validate">How to debug catalog processing</a></li>
3776 <li><a href="#Declaring">How to create and maintain catalogs</a></li>
3777 <li><a href="#implemento">The implementor corner quick review of the
3778 API</a></li>
3779 <li><a href="#Other">Other resources</a></li>
3780</ol>
3781
3782<h3><a name="General2">General overview</a></h3>
3783
3784<p>What is a catalog? Basically it's a lookup mechanism used when an entity
3785(a file or a remote resource) references another entity. The catalog lookup
3786is inserted between the moment the reference is recognized by the software
3787(XML parser, stylesheet processing, or even images referenced for inclusion
3788in a rendering) and the time where loading that resource is actually
3789started.</p>
3790
3791<p>It is basically used for 3 things:</p>
3792<ul>
3793 <li>mapping from "logical" names, the public identifiers and a more
3794 concrete name usable for download (and URI). For example it can associate
3795 the logical name
3796 <p>"-//OASIS//DTD DocBook XML V4.1.2//EN"</p>
3797 <p>of the DocBook 4.1.2 XML DTD with the actual URL where it can be
3798 downloaded</p>
3799 <p>http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd</p>
3800 </li>
3801 <li>remapping from a given URL to another one, like an HTTP indirection
3802 saying that
3803 <p>"http://www.oasis-open.org/committes/tr.xsl"</p>
3804 <p>should really be looked at</p>
3805 <p>"http://www.oasis-open.org/committes/entity/stylesheets/base/tr.xsl"</p>
3806 </li>
3807 <li>providing a local cache mechanism allowing to load the entities
3808 associated to public identifiers or remote resources, this is a really
3809 important feature for any significant deployment of XML or SGML since it
3810 allows to avoid the aleas and delays associated to fetching remote
3811 resources.</li>
3812</ul>
3813
3814<h3><a name="definition">The definitions</a></h3>
3815
3816<p>Libxml, as of 2.4.3 implements 2 kind of catalogs:</p>
3817<ul>
3818 <li>the older SGML catalogs, the official spec is SGML Open Technical
3819 Resolution TR9401:1997, but is better understood by reading <a
3820 href="http://www.jclark.com/sp/catalog.htm">the SP Catalog page</a> from
3821 James Clark. This is relatively old and not the preferred mode of
3822 operation of libxml.</li>
3823 <li><a href="http://www.oasis-open.org/committees/entity/spec.html">XML
Daniel Veillardaf43f632002-03-08 15:05:20 +00003824 Catalogs</a> is far more flexible, more recent, uses an XML syntax and
3825 should scale quite better. This is the default option of libxml.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003826</ul>
3827
3828<p></p>
3829
3830<h3><a name="Simple">Using catalog</a></h3>
3831
Daniel Veillard8a469172003-06-12 16:05:07 +00003832<p>In a normal environment libxml2 will by default check the presence of a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003833catalog in /etc/xml/catalog, and assuming it has been correctly populated,
3834the processing is completely transparent to the document user. To take a
3835concrete example, suppose you are authoring a DocBook document, this one
3836starts with the following DOCTYPE definition:</p>
3837<pre>&lt;?xml version='1.0'?&gt;
3838&lt;!DOCTYPE book PUBLIC "-//Norman Walsh//DTD DocBk XML V3.1.4//EN"
3839 "http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd"&gt;</pre>
3840
3841<p>When validating the document with libxml, the catalog will be
3842automatically consulted to lookup the public identifier "-//Norman Walsh//DTD
3843DocBk XML V3.1.4//EN" and the system identifier
3844"http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd", and if these entities have
3845been installed on your system and the catalogs actually point to them, libxml
3846will fetch them from the local disk.</p>
3847
3848<p style="font-size: 10pt"><strong>Note</strong>: Really don't use this
3849DOCTYPE example it's a really old version, but is fine as an example.</p>
3850
Daniel Veillard8a469172003-06-12 16:05:07 +00003851<p>Libxml2 will check the catalog each time that it is requested to load an
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003852entity, this includes DTD, external parsed entities, stylesheets, etc ... If
3853your system is correctly configured all the authoring phase and processing
3854should use only local files, even if your document stays portable because it
3855uses the canonical public and system ID, referencing the remote document.</p>
3856
3857<h3><a name="Some">Some examples:</a></h3>
3858
Daniel Veillard8a469172003-06-12 16:05:07 +00003859<p>Here is a couple of fragments from XML Catalogs used in libxml2 early
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003860regression tests in <code>test/catalogs</code> :</p>
3861<pre>&lt;?xml version="1.0"?&gt;
3862&lt;!DOCTYPE catalog PUBLIC
3863 "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
3864 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3865&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"&gt;
3866 &lt;public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
3867 uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/&gt;
3868...</pre>
3869
3870<p>This is the beginning of a catalog for DocBook 4.1.2, XML Catalogs are
3871written in XML, there is a specific namespace for catalog elements
3872"urn:oasis:names:tc:entity:xmlns:xml:catalog". The first entry in this
3873catalog is a <code>public</code> mapping it allows to associate a Public
3874Identifier with an URI.</p>
3875<pre>...
3876 &lt;rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/"
3877 rewritePrefix="file:///usr/share/xml/docbook/"/&gt;
3878...</pre>
3879
3880<p>A <code>rewriteSystem</code> is a very powerful instruction, it says that
3881any URI starting with a given prefix should be looked at another URI
3882constructed by replacing the prefix with an new one. In effect this acts like
3883a cache system for a full area of the Web. In practice it is extremely useful
3884with a file prefix if you have installed a copy of those resources on your
3885local system.</p>
3886<pre>...
3887&lt;delegatePublic publicIdStartString="-//OASIS//DTD XML Catalog //"
3888 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3889&lt;delegatePublic publicIdStartString="-//OASIS//ENTITIES DocBook XML"
3890 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3891&lt;delegatePublic publicIdStartString="-//OASIS//DTD DocBook XML"
3892 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3893&lt;delegateSystem systemIdStartString="http://www.oasis-open.org/docbook/"
3894 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3895&lt;delegateURI uriStartString="http://www.oasis-open.org/docbook/"
3896 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3897...</pre>
3898
3899<p>Delegation is the core features which allows to build a tree of catalogs,
3900easier to maintain than a single catalog, based on Public Identifier, System
3901Identifier or URI prefixes it instructs the catalog software to look up
3902entries in another resource. This feature allow to build hierarchies of
3903catalogs, the set of entries presented should be sufficient to redirect the
3904resolution of all DocBook references to the specific catalog in
3905<code>/usr/share/xml/docbook.xml</code> this one in turn could delegate all
3906references for DocBook 4.2.1 to a specific catalog installed at the same time
3907as the DocBook resources on the local machine.</p>
3908
3909<h3><a name="reference">How to tune catalog usage:</a></h3>
3910
3911<p>The user can change the default catalog behaviour by redirecting queries
3912to its own set of catalogs, this can be done by setting the
3913<code>XML_CATALOG_FILES</code> environment variable to a list of catalogs, an
3914empty one should deactivate loading the default <code>/etc/xml/catalog</code>
3915default catalog</p>
3916
3917<h3><a name="validate">How to debug catalog processing:</a></h3>
3918
3919<p>Setting up the <code>XML_DEBUG_CATALOG</code> environment variable will
Daniel Veillard8a469172003-06-12 16:05:07 +00003920make libxml2 output debugging informations for each catalog operations, for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003921example:</p>
3922<pre>orchis:~/XML -&gt; xmllint --memory --noout test/ent2
3923warning: failed to load external entity "title.xml"
3924orchis:~/XML -&gt; export XML_DEBUG_CATALOG=
3925orchis:~/XML -&gt; xmllint --memory --noout test/ent2
3926Failed to parse catalog /etc/xml/catalog
3927Failed to parse catalog /etc/xml/catalog
3928warning: failed to load external entity "title.xml"
3929Catalogs cleanup
3930orchis:~/XML -&gt; </pre>
3931
3932<p>The test/ent2 references an entity, running the parser from memory makes
3933the base URI unavailable and the the "title.xml" entity cannot be loaded.
3934Setting up the debug environment variable allows to detect that an attempt is
3935made to load the <code>/etc/xml/catalog</code> but since it's not present the
3936resolution fails.</p>
3937
3938<p>But the most advanced way to debug XML catalog processing is to use the
3939<strong>xmlcatalog</strong> command shipped with libxml2, it allows to load
3940catalogs and make resolution queries to see what is going on. This is also
3941used for the regression tests:</p>
3942<pre>orchis:~/XML -&gt; ./xmlcatalog test/catalogs/docbook.xml \
3943 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3944http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3945orchis:~/XML -&gt; </pre>
3946
3947<p>For debugging what is going on, adding one -v flags increase the verbosity
3948level to indicate the processing done (adding a second flag also indicate
3949what elements are recognized at parsing):</p>
3950<pre>orchis:~/XML -&gt; ./xmlcatalog -v test/catalogs/docbook.xml \
3951 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3952Parsing catalog test/catalogs/docbook.xml's content
3953Found public match -//OASIS//DTD DocBook XML V4.1.2//EN
3954http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3955Catalogs cleanup
3956orchis:~/XML -&gt; </pre>
3957
3958<p>A shell interface is also available to debug and process multiple queries
3959(and for regression tests):</p>
3960<pre>orchis:~/XML -&gt; ./xmlcatalog -shell test/catalogs/docbook.xml \
3961 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3962&gt; help
3963Commands available:
3964public PublicID: make a PUBLIC identifier lookup
3965system SystemID: make a SYSTEM identifier lookup
3966resolve PublicID SystemID: do a full resolver lookup
3967add 'type' 'orig' 'replace' : add an entry
3968del 'values' : remove values
3969dump: print the current catalog state
3970debug: increase the verbosity level
3971quiet: decrease the verbosity level
3972exit: quit the shell
3973&gt; public "-//OASIS//DTD DocBook XML V4.1.2//EN"
3974http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3975&gt; quit
3976orchis:~/XML -&gt; </pre>
3977
3978<p>This should be sufficient for most debugging purpose, this was actually
3979used heavily to debug the XML Catalog implementation itself.</p>
3980
3981<h3><a name="Declaring">How to create and maintain</a> catalogs:</h3>
3982
3983<p>Basically XML Catalogs are XML files, you can either use XML tools to
3984manage them or use <strong>xmlcatalog</strong> for this. The basic step is
3985to create a catalog the -create option provide this facility:</p>
3986<pre>orchis:~/XML -&gt; ./xmlcatalog --create tst.xml
3987&lt;?xml version="1.0"?&gt;
3988&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
3989 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3990&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/&gt;
3991orchis:~/XML -&gt; </pre>
3992
3993<p>By default xmlcatalog does not overwrite the original catalog and save the
3994result on the standard output, this can be overridden using the -noout
3995option. The <code>-add</code> command allows to add entries in the
3996catalog:</p>
3997<pre>orchis:~/XML -&gt; ./xmlcatalog --noout --create --add "public" \
3998 "-//OASIS//DTD DocBook XML V4.1.2//EN" \
3999 http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd tst.xml
4000orchis:~/XML -&gt; cat tst.xml
4001&lt;?xml version="1.0"?&gt;
4002&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" \
4003 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
4004&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"&gt;
4005&lt;public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
4006 uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/&gt;
4007&lt;/catalog&gt;
4008orchis:~/XML -&gt; </pre>
4009
4010<p>The <code>-add</code> option will always take 3 parameters even if some of
4011the XML Catalog constructs (like nextCatalog) will have only a single
4012argument, just pass a third empty string, it will be ignored.</p>
4013
4014<p>Similarly the <code>-del</code> option remove matching entries from the
4015catalog:</p>
4016<pre>orchis:~/XML -&gt; ./xmlcatalog --del \
4017 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" tst.xml
4018&lt;?xml version="1.0"?&gt;
4019&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
4020 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
4021&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/&gt;
4022orchis:~/XML -&gt; </pre>
4023
4024<p>The catalog is now empty. Note that the matching of <code>-del</code> is
4025exact and would have worked in a similar fashion with the Public ID
4026string.</p>
4027
4028<p>This is rudimentary but should be sufficient to manage a not too complex
4029catalog tree of resources.</p>
4030
4031<h3><a name="implemento">The implementor corner quick review of the
4032API:</a></h3>
4033
4034<p>First, and like for every other module of libxml, there is an
4035automatically generated <a href="html/libxml-catalog.html">API page for
4036catalog support</a>.</p>
4037
4038<p>The header for the catalog interfaces should be included as:</p>
4039<pre>#include &lt;libxml/catalog.h&gt;</pre>
4040
4041<p>The API is voluntarily kept very simple. First it is not obvious that
4042applications really need access to it since it is the default behaviour of
Daniel Veillard560c2a42003-07-06 21:13:49 +00004043libxml2 (Note: it is possible to completely override libxml2 default catalog
4044by using <a href="html/libxml-parser.html">xmlSetExternalEntityLoader</a> to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004045plug an application specific resolver).</p>
4046
Daniel Veillard8a469172003-06-12 16:05:07 +00004047<p>Basically libxml2 support 2 catalog lists:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004048<ul>
4049 <li>the default one, global shared by all the application</li>
4050 <li>a per-document catalog, this one is built if the document uses the
4051 <code>oasis-xml-catalog</code> PIs to specify its own catalog list, it is
4052 associated to the parser context and destroyed when the parsing context
4053 is destroyed.</li>
4054</ul>
4055
4056<p>the document one will be used first if it exists.</p>
4057
4058<h4>Initialization routines:</h4>
4059
4060<p>xmlInitializeCatalog(), xmlLoadCatalog() and xmlLoadCatalogs() should be
4061used at startup to initialize the catalog, if the catalog should be
4062initialized with specific values xmlLoadCatalog() or xmlLoadCatalogs()
4063should be called before xmlInitializeCatalog() which would otherwise do a
4064default initialization first.</p>
4065
4066<p>The xmlCatalogAddLocal() call is used by the parser to grow the document
4067own catalog list if needed.</p>
4068
4069<h4>Preferences setup:</h4>
4070
4071<p>The XML Catalog spec requires the possibility to select default
4072preferences between public and system delegation,
4073xmlCatalogSetDefaultPrefer() allows this, xmlCatalogSetDefaults() and
4074xmlCatalogGetDefaults() allow to control if XML Catalogs resolution should
4075be forbidden, allowed for global catalog, for document catalog or both, the
4076default is to allow both.</p>
4077
4078<p>And of course xmlCatalogSetDebug() allows to generate debug messages
4079(through the xmlGenericError() mechanism).</p>
4080
4081<h4>Querying routines:</h4>
4082
4083<p>xmlCatalogResolve(), xmlCatalogResolveSystem(), xmlCatalogResolvePublic()
4084and xmlCatalogResolveURI() are relatively explicit if you read the XML
4085Catalog specification they correspond to section 7 algorithms, they should
4086also work if you have loaded an SGML catalog with a simplified semantic.</p>
4087
4088<p>xmlCatalogLocalResolve() and xmlCatalogLocalResolveURI() are the same but
4089operate on the document catalog list</p>
4090
4091<h4>Cleanup and Miscellaneous:</h4>
4092
4093<p>xmlCatalogCleanup() free-up the global catalog, xmlCatalogFreeLocal() is
4094the per-document equivalent.</p>
4095
4096<p>xmlCatalogAdd() and xmlCatalogRemove() are used to dynamically modify the
4097first catalog in the global list, and xmlCatalogDump() allows to dump a
4098catalog state, those routines are primarily designed for xmlcatalog, I'm not
4099sure that exposing more complex interfaces (like navigation ones) would be
4100really useful.</p>
4101
4102<p>The xmlParseCatalogFile() is a function used to load XML Catalog files,
4103it's similar as xmlParseFile() except it bypass all catalog lookups, it's
4104provided because this functionality may be useful for client tools.</p>
4105
4106<h4>threaded environments:</h4>
4107
4108<p>Since the catalog tree is built progressively, some care has been taken to
4109try to avoid troubles in multithreaded environments. The code is now thread
Daniel Veillard8a469172003-06-12 16:05:07 +00004110safe assuming that the libxml2 library has been compiled with threads
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004111support.</p>
4112
4113<p></p>
4114
4115<h3><a name="Other">Other resources</a></h3>
4116
4117<p>The XML Catalog specification is relatively recent so there isn't much
4118literature to point at:</p>
4119<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00004120 <li>You can find a good rant from Norm Walsh about <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004121 href="http://www.arbortext.com/Think_Tank/XML_Resources/Issue_Three/issue_three.html">the
4122 need for catalogs</a>, it provides a lot of context informations even if
Daniel Veillard93d3a472002-04-26 14:04:55 +00004123 I don't agree with everything presented. Norm also wrote a more recent
4124 article <a
4125 href="http://wwws.sun.com/software/xml/developers/resolver/article/">XML
4126 entities and URI resolvers</a> describing them.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004127 <li>An <a href="http://home.ccil.org/~cowan/XML/XCatalog.html">old XML
4128 catalog proposal</a> from John Cowan</li>
4129 <li>The <a href="http://www.rddl.org/">Resource Directory Description
4130 Language</a> (RDDL) another catalog system but more oriented toward
4131 providing metadata for XML namespaces.</li>
4132 <li>the page from the OASIS Technical <a
4133 href="http://www.oasis-open.org/committees/entity/">Committee on Entity
4134 Resolution</a> who maintains XML Catalog, you will find pointers to the
4135 specification update, some background and pointers to others tools
4136 providing XML Catalog support</li>
Daniel Veillardabfca612004-01-07 23:38:02 +00004137 <li>There is a <a href="buildDocBookCatalog">shell script</a> to generate
Daniel Veillard35e937a2002-01-19 22:21:54 +00004138 XML Catalogs for DocBook 4.1.2 . If it can write to the /etc/xml/
4139 directory, it will set-up /etc/xml/catalog and /etc/xml/docbook based on
4140 the resources found on the system. Otherwise it will just create
4141 ~/xmlcatalog and ~/dbkxmlcatalog and doing:
Daniel Veillard8594de92003-04-25 10:08:44 +00004142 <p><code>export XML_CATALOG_FILES=$HOME/xmlcatalog</code></p>
Daniel Veillard35e937a2002-01-19 22:21:54 +00004143 <p>should allow to process DocBook documentations without requiring
Daniel Veillard63d83142002-05-20 06:51:05 +00004144 network accesses for the DTD or stylesheets</p>
Daniel Veillard35e937a2002-01-19 22:21:54 +00004145 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004146 <li>I have uploaded <a href="ftp://xmlsoft.org/test/dbk412catalog.tar.gz">a
Daniel Veillard35e937a2002-01-19 22:21:54 +00004147 small tarball</a> containing XML Catalogs for DocBook 4.1.2 which seems
4148 to work fine for me too</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004149 <li>The <a href="http://www.xmlsoft.org/xmlcatalog_man.html">xmlcatalog
4150 manual page</a></li>
4151</ul>
4152
4153<p>If you have suggestions for corrections or additions, simply contact
4154me:</p>
4155
4156<h2><a name="library">The parser interfaces</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004157
4158<p>This section is directly intended to help programmers getting bootstrapped
Daniel Veillard8a469172003-06-12 16:05:07 +00004159using the XML tollkit from the C language. It is not intended to be
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004160extensive. I hope the automatically generated documents will provide the
4161completeness required, but as a separate set of documents. The interfaces of
Daniel Veillard560c2a42003-07-06 21:13:49 +00004162the XML parser are by principle low level, Those interested in a higher level
4163API should <a href="#DOM">look at DOM</a>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +00004164
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00004165<p>The <a href="html/libxml-parser.html">parser interfaces for XML</a> are
4166separated from the <a href="html/libxml-htmlparser.html">HTML parser
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004167interfaces</a>. Let's have a look at how the XML parser can be called:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +00004168
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004169<h3><a name="Invoking">Invoking the parser : the pull method</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004170
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004171<p>Usually, the first thing to do is to read an XML input. The parser accepts
4172documents either from in-memory strings or from files. The functions are
Daniel Veillardb05deb71999-08-10 19:04:08 +00004173defined in "parser.h":</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004174<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004175 <dt><code>xmlDocPtr xmlParseMemory(char *buffer, int size);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004176 <dd><p>Parse a null-terminated string containing the document.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004177 </dd>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004178</dl>
4179<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004180 <dt><code>xmlDocPtr xmlParseFile(const char *filename);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004181 <dd><p>Parse an XML document contained in a (possibly compressed)
4182 file.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004183 </dd>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004184</dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004185
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004186<p>The parser returns a pointer to the document structure (or NULL in case of
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004187failure).</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004188
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004189<h3 id="Invoking1">Invoking the parser: the push method</h3>
Daniel Veillard0142b842000-01-14 14:45:24 +00004190
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004191<p>In order for the application to keep the control when the document is
Daniel Veillard560c2a42003-07-06 21:13:49 +00004192being fetched (which is common for GUI based programs) libxml2 provides a
4193push interface, too, as of version 1.8.3. Here are the interface
4194functions:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +00004195<pre>xmlParserCtxtPtr xmlCreatePushParserCtxt(xmlSAXHandlerPtr sax,
4196 void *user_data,
4197 const char *chunk,
4198 int size,
4199 const char *filename);
4200int xmlParseChunk (xmlParserCtxtPtr ctxt,
4201 const char *chunk,
4202 int size,
4203 int terminate);</pre>
4204
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004205<p>and here is a simple example showing how to use the interface:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +00004206<pre> FILE *f;
4207
4208 f = fopen(filename, "r");
4209 if (f != NULL) {
4210 int res, size = 1024;
4211 char chars[1024];
4212 xmlParserCtxtPtr ctxt;
4213
4214 res = fread(chars, 1, 4, f);
Daniel Veillard60979bd2000-07-10 12:17:33 +00004215 if (res &gt; 0) {
Daniel Veillard0142b842000-01-14 14:45:24 +00004216 ctxt = xmlCreatePushParserCtxt(NULL, NULL,
4217 chars, res, filename);
Daniel Veillard60979bd2000-07-10 12:17:33 +00004218 while ((res = fread(chars, 1, size, f)) &gt; 0) {
Daniel Veillard0142b842000-01-14 14:45:24 +00004219 xmlParseChunk(ctxt, chars, res, 0);
4220 }
4221 xmlParseChunk(ctxt, chars, 0, 1);
Daniel Veillard60979bd2000-07-10 12:17:33 +00004222 doc = ctxt-&gt;myDoc;
Daniel Veillard0142b842000-01-14 14:45:24 +00004223 xmlFreeParserCtxt(ctxt);
4224 }
4225 }</pre>
4226
Daniel Veillard8a469172003-06-12 16:05:07 +00004227<p>The HTML parser embedded into libxml2 also has a push interface; the
Daniel Veillardec70e912001-02-26 20:10:45 +00004228functions are just prefixed by "html" rather than "xml".</p>
Daniel Veillard0142b842000-01-14 14:45:24 +00004229
4230<h3 id="Invoking2">Invoking the parser: the SAX interface</h3>
4231
Daniel Veillardec70e912001-02-26 20:10:45 +00004232<p>The tree-building interface makes the parser memory-hungry, first loading
4233the document in memory and then building the tree itself. Reading a document
4234without building the tree is possible using the SAX interfaces (see SAX.h and
4235<a href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">James
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004236Henstridge's documentation</a>). Note also that the push interface can be
Daniel Veillard91e9d582001-02-26 07:31:12 +00004237limited to SAX: just use the two first arguments of
Daniel Veillard0142b842000-01-14 14:45:24 +00004238<code>xmlCreatePushParserCtxt()</code>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +00004239
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004240<h3><a name="Building">Building a tree from scratch</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004241
4242<p>The other way to get an XML tree in memory is by building it. Basically
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004243there is a set of functions dedicated to building new elements. (These are
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004244also described in &lt;libxml/tree.h&gt;.) For example, here is a piece of
4245code that produces the XML document used in the previous examples:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004246<pre> #include &lt;libxml/tree.h&gt;
Daniel Veillard361d8452000-04-03 19:48:13 +00004247 xmlDocPtr doc;
Daniel Veillard25940b71998-10-29 05:51:30 +00004248 xmlNodePtr tree, subtree;
4249
4250 doc = xmlNewDoc("1.0");
Daniel Veillard60979bd2000-07-10 12:17:33 +00004251 doc-&gt;children = xmlNewDocNode(doc, NULL, "EXAMPLE", NULL);
4252 xmlSetProp(doc-&gt;children, "prop1", "gnome is great");
4253 xmlSetProp(doc-&gt;children, "prop2", "&amp; linux too");
4254 tree = xmlNewChild(doc-&gt;children, NULL, "head", NULL);
Daniel Veillard25940b71998-10-29 05:51:30 +00004255 subtree = xmlNewChild(tree, NULL, "title", "Welcome to Gnome");
Daniel Veillard60979bd2000-07-10 12:17:33 +00004256 tree = xmlNewChild(doc-&gt;children, NULL, "chapter", NULL);
Daniel Veillard25940b71998-10-29 05:51:30 +00004257 subtree = xmlNewChild(tree, NULL, "title", "The Linux adventure");
4258 subtree = xmlNewChild(tree, NULL, "p", "bla bla bla ...");
4259 subtree = xmlNewChild(tree, NULL, "image", NULL);
4260 xmlSetProp(subtree, "href", "linus.gif");</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004261
4262<p>Not really rocket science ...</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004263
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004264<h3><a name="Traversing">Traversing the tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004265
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00004266<p>Basically by <a href="html/libxml-tree.html">including "tree.h"</a> your
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004267code has access to the internal structure of all the elements of the tree.
4268The names should be somewhat simple like <strong>parent</strong>,
Daniel Veillard306be992000-07-03 12:38:45 +00004269<strong>children</strong>, <strong>next</strong>, <strong>prev</strong>,
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004270<strong>properties</strong>, etc... For example, still with the previous
Daniel Veillard0142b842000-01-14 14:45:24 +00004271example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004272<pre><code>doc-&gt;children-&gt;children-&gt;children</code></pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004273
4274<p>points to the title element,</p>
Daniel Veillard91e9d582001-02-26 07:31:12 +00004275<pre>doc-&gt;children-&gt;children-&gt;next-&gt;children-&gt;children</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004276
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004277<p>points to the text node containing the chapter title "The Linux
4278adventure".</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004279
Daniel Veillardb24054a1999-12-18 15:32:46 +00004280<p><strong>NOTE</strong>: XML allows <em>PI</em>s and <em>comments</em> to be
Daniel Veillard60979bd2000-07-10 12:17:33 +00004281present before the document root, so <code>doc-&gt;children</code> may point
Daniel Veillard91e9d582001-02-26 07:31:12 +00004282to an element which is not the document Root Element; a function
Daniel Veillard5cb5ab81999-12-21 15:35:29 +00004283<code>xmlDocGetRootElement()</code> was added for this purpose.</p>
Daniel Veillardb24054a1999-12-18 15:32:46 +00004284
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004285<h3><a name="Modifying">Modifying the tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004286
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004287<p>Functions are provided for reading and writing the document content. Here
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00004288is an excerpt from the <a href="html/libxml-tree.html">tree API</a>:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004289<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004290 <dt><code>xmlAttrPtr xmlSetProp(xmlNodePtr node, const xmlChar *name, const
4291 xmlChar *value);</code></dt>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004292 <dd><p>This sets (or changes) an attribute carried by an ELEMENT node.
4293 The value can be NULL.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004294 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004295</dl>
4296<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004297 <dt><code>const xmlChar *xmlGetProp(xmlNodePtr node, const xmlChar
Daniel Veillardb05deb71999-08-10 19:04:08 +00004298 *name);</code></dt>
Daniel Veillardc92c3042000-09-29 02:42:04 +00004299 <dd><p>This function returns a pointer to new copy of the property
4300 content. Note that the user must deallocate the result.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004301 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004302</dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004303
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004304<p>Two functions are provided for reading and writing the text associated
4305with elements:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004306<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004307 <dt><code>xmlNodePtr xmlStringGetNodeList(xmlDocPtr doc, const xmlChar
Daniel Veillardb05deb71999-08-10 19:04:08 +00004308 *value);</code></dt>
Daniel Veillardec70e912001-02-26 20:10:45 +00004309 <dd><p>This function takes an "external" string and converts it to one
4310 text node or possibly to a list of entity and text nodes. All
4311 non-predefined entity references like &amp;Gnome; will be stored
4312 internally as entity nodes, hence the result of the function may not be
4313 a single node.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004314 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004315</dl>
4316<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004317 <dt><code>xmlChar *xmlNodeListGetString(xmlDocPtr doc, xmlNodePtr list, int
Daniel Veillardb05deb71999-08-10 19:04:08 +00004318 inLine);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004319 <dd><p>This function is the inverse of
4320 <code>xmlStringGetNodeList()</code>. It generates a new string
4321 containing the content of the text and entity nodes. Note the extra
4322 argument inLine. If this argument is set to 1, the function will expand
4323 entity references. For example, instead of returning the &amp;Gnome;
4324 XML encoding in the string, it will substitute it with its value (say,
Daniel Veillard91e9d582001-02-26 07:31:12 +00004325 "GNU Network Object Model Environment").</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004326 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004327</dl>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004328
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004329<h3><a name="Saving">Saving a tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004330
4331<p>Basically 3 options are possible:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004332<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004333 <dt><code>void xmlDocDumpMemory(xmlDocPtr cur, xmlChar**mem, int
Daniel Veillardb05deb71999-08-10 19:04:08 +00004334 *size);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004335 <dd><p>Returns a buffer into which the document has been saved.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004336 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004337</dl>
4338<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004339 <dt><code>extern void xmlDocDump(FILE *f, xmlDocPtr doc);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004340 <dd><p>Dumps a document to an open file descriptor.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004341 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004342</dl>
4343<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004344 <dt><code>int xmlSaveFile(const char *filename, xmlDocPtr cur);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004345 <dd><p>Saves the document to a file. In this case, the compression
4346 interface is triggered if it has been turned on.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004347 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004348</dl>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004349
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004350<h3><a name="Compressio">Compression</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004351
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004352<p>The library transparently handles compression when doing file-based
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004353accesses. The level of compression on saves can be turned on either globally
4354or individually for one file:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004355<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004356 <dt><code>int xmlGetDocCompressMode (xmlDocPtr doc);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004357 <dd><p>Gets the document compression ratio (0-9).</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004358 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004359</dl>
4360<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004361 <dt><code>void xmlSetDocCompressMode (xmlDocPtr doc, int mode);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004362 <dd><p>Sets the document compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004363 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004364</dl>
4365<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004366 <dt><code>int xmlGetCompressMode(void);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004367 <dd><p>Gets the default compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004368 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004369</dl>
4370<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004371 <dt><code>void xmlSetCompressMode(int mode);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004372 <dd><p>Sets the default compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004373 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004374</dl>
4375
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004376<h2><a name="Entities">Entities or no entities</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004377
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004378<p>Entities in principle are similar to simple C macros. An entity defines an
4379abbreviation for a given string that you can reuse many times throughout the
4380content of your document. Entities are especially useful when a given string
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004381may occur frequently within a document, or to confine the change needed to a
4382document to a restricted area in the internal subset of the document (at the
4383beginning). Example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004384<pre>1 &lt;?xml version="1.0"?&gt;
Daniel Veillardc8eab3a1999-09-04 18:27:23 +000043852 &lt;!DOCTYPE EXAMPLE SYSTEM "example.dtd" [
Daniel Veillard60979bd2000-07-10 12:17:33 +000043863 &lt;!ENTITY xml "Extensible Markup Language"&gt;
43874 ]&gt;
43885 &lt;EXAMPLE&gt;
Daniel Veillardc8eab3a1999-09-04 18:27:23 +000043896 &amp;xml;
Daniel Veillard60979bd2000-07-10 12:17:33 +000043907 &lt;/EXAMPLE&gt;</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004391
4392<p>Line 3 declares the xml entity. Line 6 uses the xml entity, by prefixing
Daniel Veillard91e9d582001-02-26 07:31:12 +00004393its name with '&amp;' and following it by ';' without any spaces added. There
Daniel Veillard8a469172003-06-12 16:05:07 +00004394are 5 predefined entities in libxml2 allowing you to escape characters with
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004395predefined meaning in some parts of the xml document content:
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004396<strong>&amp;lt;</strong> for the character '&lt;', <strong>&amp;gt;</strong>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004397for the character '&gt;', <strong>&amp;apos;</strong> for the character ''',
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004398<strong>&amp;quot;</strong> for the character '"', and
4399<strong>&amp;amp;</strong> for the character '&amp;'.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004400
4401<p>One of the problems related to entities is that you may want the parser to
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004402substitute an entity's content so that you can see the replacement text in
4403your application. Or you may prefer to keep entity references as such in the
4404content to be able to save the document back without losing this usually
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004405precious information (if the user went through the pain of explicitly
4406defining entities, he may have a a rather negative attitude if you blindly
Daniel Veillard63d83142002-05-20 06:51:05 +00004407substitute them as saving time). The <a
Daniel Veillard5373ea12003-07-24 13:09:13 +00004408href="html/libxml-parser.html#xmlSubstituteEntitiesDefault">xmlSubstituteEntitiesDefault()</a>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004409function allows you to check and change the behaviour, which is to not
4410substitute entities by default.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004411
Daniel Veillard8a469172003-06-12 16:05:07 +00004412<p>Here is the DOM tree built by libxml2 for the previous document in the
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004413default case:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004414<pre>/gnome/src/gnome-xml -&gt; ./xmllint --debug test/ent1
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004415DOCUMENT
4416version=1.0
4417 ELEMENT EXAMPLE
4418 TEXT
4419 content=
4420 ENTITY_REF
4421 INTERNAL_GENERAL_ENTITY xml
4422 content=Extensible Markup Language
4423 TEXT
4424 content=</pre>
4425
4426<p>And here is the result when substituting entities:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004427<pre>/gnome/src/gnome-xml -&gt; ./tester --debug --noent test/ent1
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004428DOCUMENT
4429version=1.0
4430 ELEMENT EXAMPLE
4431 TEXT
4432 content= Extensible Markup Language</pre>
4433
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004434<p>So, entities or no entities? Basically, it depends on your use case. I
4435suggest that you keep the non-substituting default behaviour and avoid using
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004436entities in your XML document or data if you are not willing to handle the
4437entity references elements in the DOM tree.</p>
4438
Daniel Veillard8a469172003-06-12 16:05:07 +00004439<p>Note that at save time libxml2 enforces the conversion of the predefined
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004440entities where necessary to prevent well-formedness problems, and will also
Daniel Veillard91e9d582001-02-26 07:31:12 +00004441transparently replace those with chars (i.e. it will not generate entity
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004442reference elements in the DOM tree or call the reference() SAX callback when
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004443finding them in the input).</p>
4444
Daniel Veillard7b9c4b72000-08-25 16:26:50 +00004445<p><span style="background-color: #FF0000">WARNING</span>: handling entities
Daniel Veillard8a469172003-06-12 16:05:07 +00004446on top of the libxml2 SAX interface is difficult!!! If you plan to use
Daniel Veillard63d83142002-05-20 06:51:05 +00004447non-predefined entities in your documents, then the learning curve to handle
Daniel Veillard91e9d582001-02-26 07:31:12 +00004448then using the SAX API may be long. If you plan to use complex documents, I
Daniel Veillard7b9c4b72000-08-25 16:26:50 +00004449strongly suggest you consider using the DOM interface instead and let libxml
Daniel Veillard8c6d6af2000-08-25 17:14:13 +00004450deal with the complexity rather than trying to do it yourself.</p>
Daniel Veillard7b9c4b72000-08-25 16:26:50 +00004451
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004452<h2><a name="Namespaces">Namespaces</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004453
Daniel Veillard8a469172003-06-12 16:05:07 +00004454<p>The libxml2 library implements <a
Daniel Veillardec303412000-03-24 13:41:54 +00004455href="http://www.w3.org/TR/REC-xml-names/">XML namespaces</a> support by
Daniel Veillard63d83142002-05-20 06:51:05 +00004456recognizing namespace constructs in the input, and does namespace lookup
Daniel Veillardec303412000-03-24 13:41:54 +00004457automatically when building the DOM tree. A namespace declaration is
4458associated with an in-memory structure and all elements or attributes within
4459that namespace point to it. Hence testing the namespace is a simple and fast
4460equality operation at the user level.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004461
Daniel Veillard8a469172003-06-12 16:05:07 +00004462<p>I suggest that people using libxml2 use a namespace, and declare it in the
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004463root element of their document as the default namespace. Then they don't need
4464to use the prefix in the content but we will have a basis for future semantic
Daniel Veillard91e9d582001-02-26 07:31:12 +00004465refinement and merging of data from different sources. This doesn't increase
Daniel Veillardec70e912001-02-26 20:10:45 +00004466the size of the XML output significantly, but significantly increases its
4467value in the long-term. Example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004468<pre>&lt;mydoc xmlns="http://mydoc.example.org/schemas/"&gt;
4469 &lt;elem1&gt;...&lt;/elem1&gt;
4470 &lt;elem2&gt;...&lt;/elem2&gt;
4471&lt;/mydoc&gt;</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004472
Daniel Veillardec70e912001-02-26 20:10:45 +00004473<p>The namespace value has to be an absolute URL, but the URL doesn't have to
4474point to any existing resource on the Web. It will bind all the element and
Daniel Veillardc0801af2002-05-28 16:28:42 +00004475attributes with that URL. I suggest to use an URL within a domain you
4476control, and that the URL should contain some kind of version information if
4477possible. For example, <code>"http://www.gnome.org/gnumeric/1.0/"</code> is a
4478good namespace scheme.</p>
Daniel Veillardec303412000-03-24 13:41:54 +00004479
4480<p>Then when you load a file, make sure that a namespace carrying the
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004481version-independent prefix is installed on the root element of your document,
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004482and if the version information don't match something you know, warn the user
4483and be liberal in what you accept as the input. Also do *not* try to base
Daniel Veillard60979bd2000-07-10 12:17:33 +00004484namespace checking on the prefix value. &lt;foo:text&gt; may be exactly the
Daniel Veillard91e9d582001-02-26 07:31:12 +00004485same as &lt;bar:text&gt; in another document. What really matters is the URI
Daniel Veillard60979bd2000-07-10 12:17:33 +00004486associated with the element or the attribute, not the prefix string (which is
Daniel Veillard91e9d582001-02-26 07:31:12 +00004487just a shortcut for the full URI). In libxml, element and attributes have an
Daniel Veillardec303412000-03-24 13:41:54 +00004488<code>ns</code> field pointing to an xmlNs structure detailing the namespace
Daniel Veillard91e9d582001-02-26 07:31:12 +00004489prefix and its URI.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004490
4491<p>@@Interfaces@@</p>
Daniel Veillard3e35f8e2003-10-21 00:05:38 +00004492<pre>xmlNodePtr node;
Daniel Veillardfc8dc352003-10-18 09:07:46 +00004493if(!strncmp(node-&gt;name,"mytag",5)
4494 &amp;&amp; node-&gt;ns
4495 &amp;&amp; !strcmp(node-&gt;ns-&gt;href,"http://www.mysite.com/myns/1.0")) {
4496 ...
Daniel Veillard3e35f8e2003-10-21 00:05:38 +00004497}</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004498
Daniel Veillard91e9d582001-02-26 07:31:12 +00004499<p>Usually people object to using namespaces together with validity checking.
4500I will try to make sure that using namespaces won't break validity checking,
4501so even if you plan to use or currently are using validation I strongly
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004502suggest adding namespaces to your document. A default namespace scheme
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004503<code>xmlns="http://...."</code> should not break validity even on less
Daniel Veillard91e9d582001-02-26 07:31:12 +00004504flexible parsers. Using namespaces to mix and differentiate content coming
Daniel Veillard3e35f8e2003-10-21 00:05:38 +00004505from multiple DTDs will certainly break current validation schemes. To check
4506such documents one needs to use schema-validation, which is supported in
4507libxml2 as well. See <a href="http://www.relaxng.org/">relagx-ng</a> and <a
4508href="http://www.w3c.org/XML/Schema">w3c-schema</a>.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004509
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004510<h2><a name="Upgrading">Upgrading 1.x code</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004511
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004512<p>Incompatible changes:</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004513
Daniel Veillard8a469172003-06-12 16:05:07 +00004514<p>Version 2 of libxml2 is the first version introducing serious backward
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004515incompatible changes. The main goals were:</p>
4516<ul>
4517 <li>a general cleanup. A number of mistakes inherited from the very early
4518 versions couldn't be changed due to compatibility constraints. Example
4519 the "childs" element in the nodes.</li>
4520 <li>Uniformization of the various nodes, at least for their header and link
4521 parts (doc, parent, children, prev, next), the goal is a simpler
4522 programming model and simplifying the task of the DOM implementors.</li>
4523 <li>better conformances to the XML specification, for example version 1.x
4524 had an heuristic to try to detect ignorable white spaces. As a result the
4525 SAX event generated were ignorableWhitespace() while the spec requires
4526 character() in that case. This also mean that a number of DOM node
4527 containing blank text may populate the DOM tree which were not present
4528 before.</li>
4529</ul>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004530
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004531<h3>How to fix libxml-1.x code:</h3>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004532
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004533<p>So client code of libxml designed to run with version 1.x may have to be
4534changed to compile against version 2.x of libxml. Here is a list of changes
4535that I have collected, they may not be sufficient, so in case you find other
Daniel Veillardfc8dc352003-10-18 09:07:46 +00004536change which are required, <a href="mailto:Daniel.Veillard@w3.org">drop me a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004537mail</a>:</p>
4538<ol>
4539 <li>The package name have changed from libxml to libxml2, the library name
4540 is now -lxml2 . There is a new xml2-config script which should be used to
4541 select the right parameters libxml2</li>
4542 <li>Node <strong>childs</strong> field has been renamed
4543 <strong>children</strong> so s/childs/children/g should be applied
Daniel Veillard63d83142002-05-20 06:51:05 +00004544 (probability of having "childs" anywhere else is close to 0+</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004545 <li>The document don't have anymore a <strong>root</strong> element it has
4546 been replaced by <strong>children</strong> and usually you will get a
4547 list of element here. For example a Dtd element for the internal subset
4548 and it's declaration may be found in that list, as well as processing
4549 instructions or comments found before or after the document root element.
4550 Use <strong>xmlDocGetRootElement(doc)</strong> to get the root element of
Daniel Veillard63d83142002-05-20 06:51:05 +00004551 a document. Alternatively if you are sure to not reference DTDs nor have
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004552 PIs or comments before or after the root element
4553 s/-&gt;root/-&gt;children/g will probably do it.</li>
4554 <li>The white space issue, this one is more complex, unless special case of
4555 validating parsing, the line breaks and spaces usually used for indenting
4556 and formatting the document content becomes significant. So they are
4557 reported by SAX and if your using the DOM tree, corresponding nodes are
4558 generated. Too approach can be taken:
4559 <ol>
4560 <li>lazy one, use the compatibility call
4561 <strong>xmlKeepBlanksDefault(0)</strong> but be aware that you are
4562 relying on a special (and possibly broken) set of heuristics of
4563 libxml to detect ignorable blanks. Don't complain if it breaks or
4564 make your application not 100% clean w.r.t. to it's input.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00004565 <li>the Right Way: change you code to accept possibly insignificant
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004566 blanks characters, or have your tree populated with weird blank text
Daniel Veillard63d83142002-05-20 06:51:05 +00004567 nodes. You can spot them using the commodity function
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004568 <strong>xmlIsBlankNode(node)</strong> returning 1 for such blank
4569 nodes.</li>
4570 </ol>
4571 <p>Note also that with the new default the output functions don't add any
4572 extra indentation when saving a tree in order to be able to round trip
4573 (read and save) without inflating the document with extra formatting
4574 chars.</p>
4575 </li>
4576 <li>The include path has changed to $prefix/libxml/ and the includes
4577 themselves uses this new prefix in includes instructions... If you are
4578 using (as expected) the
4579 <pre>xml2-config --cflags</pre>
4580 <p>output to generate you compile commands this will probably work out of
4581 the box</p>
4582 </li>
Daniel Veillard63d83142002-05-20 06:51:05 +00004583 <li>xmlDetectCharEncoding takes an extra argument indicating the length in
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004584 byte of the head of the document available for character detection.</li>
4585</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004586
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004587<h3>Ensuring both libxml-1.x and libxml-2.x compatibility</h3>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004588
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004589<p>Two new version of libxml (1.8.11) and libxml2 (2.3.4) have been released
Daniel Veillard63d83142002-05-20 06:51:05 +00004590to allow smooth upgrade of existing libxml v1code while retaining
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004591compatibility. They offers the following:</p>
4592<ol>
4593 <li>similar include naming, one should use
4594 <strong>#include&lt;libxml/...&gt;</strong> in both cases.</li>
4595 <li>similar identifiers defined via macros for the child and root fields:
4596 respectively <strong>xmlChildrenNode</strong> and
4597 <strong>xmlRootNode</strong></li>
4598 <li>a new macro <strong>LIBXML_TEST_VERSION</strong> which should be
4599 inserted once in the client code</li>
4600</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004601
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004602<p>So the roadmap to upgrade your existing libxml applications is the
4603following:</p>
4604<ol>
4605 <li>install the libxml-1.8.8 (and libxml-devel-1.8.8) packages</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00004606 <li>find all occurrences where the xmlDoc <strong>root</strong> field is
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004607 used and change it to <strong>xmlRootNode</strong></li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00004608 <li>similarly find all occurrences where the xmlNode
4609 <strong>childs</strong> field is used and change it to
4610 <strong>xmlChildrenNode</strong></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004611 <li>add a <strong>LIBXML_TEST_VERSION</strong> macro somewhere in your
4612 <strong>main()</strong> or in the library init entry point</li>
4613 <li>Recompile, check compatibility, it should still work</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00004614 <li>Change your configure script to look first for xml2-config and fall
4615 back using xml-config . Use the --cflags and --libs output of the command
4616 as the Include and Linking parameters needed to use libxml.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004617 <li>install libxml2-2.3.x and libxml2-devel-2.3.x (libxml-1.8.y and
4618 libxml-devel-1.8.y can be kept simultaneously)</li>
4619 <li>remove your config.cache, relaunch your configuration mechanism, and
4620 recompile, if steps 2 and 3 were done right it should compile as-is</li>
4621 <li>Test that your application is still running correctly, if not this may
4622 be due to extra empty nodes due to formating spaces being kept in libxml2
4623 contrary to libxml1, in that case insert xmlKeepBlanksDefault(1) in your
4624 code before calling the parser (next to
4625 <strong>LIBXML_TEST_VERSION</strong> is a fine place).</li>
4626</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004627
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004628<p>Following those steps should work. It worked for some of my own code.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004629
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004630<p>Let me put some emphasis on the fact that there is far more changes from
4631libxml 1.x to 2.x than the ones you may have to patch for. The overall code
4632has been considerably cleaned up and the conformance to the XML specification
4633has been drastically improved too. Don't take those changes as an excuse to
4634not upgrade, it may cost a lot on the long term ...</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004635
Daniel Veillard52dcab32001-10-30 12:51:17 +00004636<h2><a name="Thread">Thread safety</a></h2>
4637
Daniel Veillard8a469172003-06-12 16:05:07 +00004638<p>Starting with 2.4.7, libxml2 makes provisions to ensure that concurrent
Daniel Veillard52dcab32001-10-30 12:51:17 +00004639threads can safely work in parallel parsing different documents. There is
4640however a couple of things to do to ensure it:</p>
4641<ul>
4642 <li>configure the library accordingly using the --with-threads options</li>
4643 <li>call xmlInitParser() in the "main" thread before using any of the
Daniel Veillard8a469172003-06-12 16:05:07 +00004644 libxml2 API (except possibly selecting a different memory allocator)</li>
Daniel Veillard52dcab32001-10-30 12:51:17 +00004645</ul>
4646
4647<p>Note that the thread safety cannot be ensured for multiple threads sharing
4648the same document, the locking must be done at the application level, libxml
4649exports a basic mutex and reentrant mutexes API in &lt;libxml/threads.h&gt;.
4650The parts of the library checked for thread safety are:</p>
4651<ul>
4652 <li>concurrent loading</li>
4653 <li>file access resolution</li>
4654 <li>catalog access</li>
4655 <li>catalog building</li>
4656 <li>entities lookup/accesses</li>
4657 <li>validation</li>
4658 <li>global variables per-thread override</li>
4659 <li>memory handling</li>
4660</ul>
4661
4662<p>XPath is supposed to be thread safe now, but this wasn't tested
4663seriously.</p>
4664
Daniel Veillard35008381999-10-25 13:15:52 +00004665<h2><a name="DOM"></a><a name="Principles">DOM Principles</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004666
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004667<p><a href="http://www.w3.org/DOM/">DOM</a> stands for the <em>Document
4668Object Model</em>; this is an API for accessing XML or HTML structured
4669documents. Native support for DOM in Gnome is on the way (module gnome-dom),
4670and will be based on gnome-xml. This will be a far cleaner interface to
4671manipulate XML files within Gnome since it won't expose the internal
4672structure.</p>
Daniel Veillard14fff061999-06-22 21:49:07 +00004673
Daniel Veillard8a469172003-06-12 16:05:07 +00004674<p>The current DOM implementation on top of libxml2 is the <a
Daniel Veillarda47fb3d2001-03-25 17:23:49 +00004675href="http://cvs.gnome.org/lxr/source/gdome2/">gdome2 Gnome module</a>, this
4676is a full DOM interface, thanks to Paolo Casarini, check the <a
4677href="http://www.cs.unibo.it/~casarini/gdome2/">Gdome2 homepage</a> for more
4678informations.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004679
Daniel Veillard35008381999-10-25 13:15:52 +00004680<h2><a name="Example"></a><a name="real">A real example</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004681
4682<p>Here is a real size example, where the actual content of the application
4683data is not kept in the DOM tree but uses internal structures. It is based on
Daniel Veillard14fff061999-06-22 21:49:07 +00004684a proposal to keep a database of jobs related to Gnome, with an XML based
Daniel Veillardb05deb71999-08-10 19:04:08 +00004685storage structure. Here is an <a href="gjobs.xml">XML encoded jobs
4686base</a>:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004687<pre>&lt;?xml version="1.0"?&gt;
4688&lt;gjob:Helping xmlns:gjob="http://www.gnome.org/some-location"&gt;
4689 &lt;gjob:Jobs&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004690
Daniel Veillard60979bd2000-07-10 12:17:33 +00004691 &lt;gjob:Job&gt;
4692 &lt;gjob:Project ID="3"/&gt;
4693 &lt;gjob:Application&gt;GBackup&lt;/gjob:Application&gt;
4694 &lt;gjob:Category&gt;Development&lt;/gjob:Category&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004695
Daniel Veillard60979bd2000-07-10 12:17:33 +00004696 &lt;gjob:Update&gt;
4697 &lt;gjob:Status&gt;Open&lt;/gjob:Status&gt;
4698 &lt;gjob:Modified&gt;Mon, 07 Jun 1999 20:27:45 -0400 MET DST&lt;/gjob:Modified&gt;
4699 &lt;gjob:Salary&gt;USD 0.00&lt;/gjob:Salary&gt;
4700 &lt;/gjob:Update&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004701
Daniel Veillard60979bd2000-07-10 12:17:33 +00004702 &lt;gjob:Developers&gt;
4703 &lt;gjob:Developer&gt;
4704 &lt;/gjob:Developer&gt;
4705 &lt;/gjob:Developers&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004706
Daniel Veillard60979bd2000-07-10 12:17:33 +00004707 &lt;gjob:Contact&gt;
4708 &lt;gjob:Person&gt;Nathan Clemons&lt;/gjob:Person&gt;
4709 &lt;gjob:Email&gt;nathan@windsofstorm.net&lt;/gjob:Email&gt;
4710 &lt;gjob:Company&gt;
4711 &lt;/gjob:Company&gt;
4712 &lt;gjob:Organisation&gt;
4713 &lt;/gjob:Organisation&gt;
4714 &lt;gjob:Webpage&gt;
4715 &lt;/gjob:Webpage&gt;
4716 &lt;gjob:Snailmail&gt;
4717 &lt;/gjob:Snailmail&gt;
4718 &lt;gjob:Phone&gt;
4719 &lt;/gjob:Phone&gt;
4720 &lt;/gjob:Contact&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004721
Daniel Veillard60979bd2000-07-10 12:17:33 +00004722 &lt;gjob:Requirements&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004723 The program should be released as free software, under the GPL.
Daniel Veillard60979bd2000-07-10 12:17:33 +00004724 &lt;/gjob:Requirements&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004725
Daniel Veillard60979bd2000-07-10 12:17:33 +00004726 &lt;gjob:Skills&gt;
4727 &lt;/gjob:Skills&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004728
Daniel Veillard60979bd2000-07-10 12:17:33 +00004729 &lt;gjob:Details&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004730 A GNOME based system that will allow a superuser to configure
4731 compressed and uncompressed files and/or file systems to be backed
4732 up with a supported media in the system. This should be able to
4733 perform via find commands generating a list of files that are passed
4734 to tar, dd, cpio, cp, gzip, etc., to be directed to the tape machine
4735 or via operations performed on the filesystem itself. Email
4736 notification and GUI status display very important.
Daniel Veillard60979bd2000-07-10 12:17:33 +00004737 &lt;/gjob:Details&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004738
Daniel Veillard60979bd2000-07-10 12:17:33 +00004739 &lt;/gjob:Job&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004740
Daniel Veillard60979bd2000-07-10 12:17:33 +00004741 &lt;/gjob:Jobs&gt;
4742&lt;/gjob:Helping&gt;</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004743
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004744<p>While loading the XML file into an internal DOM tree is a matter of
Daniel Veillard63d83142002-05-20 06:51:05 +00004745calling only a couple of functions, browsing the tree to gather the data and
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004746generate the internal structures is harder, and more error prone.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004747
4748<p>The suggested principle is to be tolerant with respect to the input
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004749structure. For example, the ordering of the attributes is not significant,
4750the XML specification is clear about it. It's also usually a good idea not to
Daniel Veillardec70e912001-02-26 20:10:45 +00004751depend on the order of the children of a given node, unless it really makes
4752things harder. Here is some code to parse the information for a person:</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004753<pre>/*
Daniel Veillard14fff061999-06-22 21:49:07 +00004754 * A person record
4755 */
4756typedef struct person {
4757 char *name;
4758 char *email;
4759 char *company;
4760 char *organisation;
4761 char *smail;
4762 char *webPage;
4763 char *phone;
4764} person, *personPtr;
4765
4766/*
4767 * And the code needed to parse it
4768 */
4769personPtr parsePerson(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
4770 personPtr ret = NULL;
4771
4772DEBUG("parsePerson\n");
4773 /*
4774 * allocate the struct
4775 */
4776 ret = (personPtr) malloc(sizeof(person));
4777 if (ret == NULL) {
4778 fprintf(stderr,"out of memory\n");
Daniel Veillardb05deb71999-08-10 19:04:08 +00004779 return(NULL);
Daniel Veillard14fff061999-06-22 21:49:07 +00004780 }
4781 memset(ret, 0, sizeof(person));
4782
4783 /* We don't care what the top level element name is */
Daniel Veillard60979bd2000-07-10 12:17:33 +00004784 cur = cur-&gt;xmlChildrenNode;
Daniel Veillard14fff061999-06-22 21:49:07 +00004785 while (cur != NULL) {
Daniel Veillard60979bd2000-07-10 12:17:33 +00004786 if ((!strcmp(cur-&gt;name, "Person")) &amp;&amp; (cur-&gt;ns == ns))
4787 ret-&gt;name = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4788 if ((!strcmp(cur-&gt;name, "Email")) &amp;&amp; (cur-&gt;ns == ns))
4789 ret-&gt;email = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4790 cur = cur-&gt;next;
Daniel Veillard14fff061999-06-22 21:49:07 +00004791 }
4792
4793 return(ret);
Daniel Veillardb05deb71999-08-10 19:04:08 +00004794}</pre>
4795
Daniel Veillard91e9d582001-02-26 07:31:12 +00004796<p>Here are a couple of things to notice:</p>
Daniel Veillard14fff061999-06-22 21:49:07 +00004797<ul>
Daniel Veillard91e9d582001-02-26 07:31:12 +00004798 <li>Usually a recursive parsing style is the more convenient one: XML data
Daniel Veillard63d83142002-05-20 06:51:05 +00004799 is by nature subject to repetitive constructs and usually exhibits highly
4800 structured patterns.</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004801 <li>The two arguments of type <em>xmlDocPtr</em> and <em>xmlNsPtr</em>,
4802 i.e. the pointer to the global XML document and the namespace reserved to
4803 the application. Document wide information are needed for example to
4804 decode entities and it's a good coding practice to define a namespace for
4805 your application set of data and test that the element and attributes
4806 you're analyzing actually pertains to your application space. This is
4807 done by a simple equality test (cur-&gt;ns == ns).</li>
Daniel Veillardec70e912001-02-26 20:10:45 +00004808 <li>To retrieve text and attributes value, you can use the function
4809 <em>xmlNodeListGetString</em> to gather all the text and entity reference
4810 nodes generated by the DOM output and produce an single text string.</li>
Daniel Veillard14fff061999-06-22 21:49:07 +00004811</ul>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004812
4813<p>Here is another piece of code used to parse another level of the
4814structure:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004815<pre>#include &lt;libxml/tree.h&gt;
Daniel Veillard361d8452000-04-03 19:48:13 +00004816/*
Daniel Veillard14fff061999-06-22 21:49:07 +00004817 * a Description for a Job
4818 */
4819typedef struct job {
4820 char *projectID;
4821 char *application;
4822 char *category;
4823 personPtr contact;
4824 int nbDevelopers;
4825 personPtr developers[100]; /* using dynamic alloc is left as an exercise */
4826} job, *jobPtr;
4827
4828/*
4829 * And the code needed to parse it
4830 */
4831jobPtr parseJob(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
4832 jobPtr ret = NULL;
4833
4834DEBUG("parseJob\n");
4835 /*
4836 * allocate the struct
4837 */
4838 ret = (jobPtr) malloc(sizeof(job));
4839 if (ret == NULL) {
4840 fprintf(stderr,"out of memory\n");
Daniel Veillardb05deb71999-08-10 19:04:08 +00004841 return(NULL);
Daniel Veillard14fff061999-06-22 21:49:07 +00004842 }
4843 memset(ret, 0, sizeof(job));
4844
4845 /* We don't care what the top level element name is */
Daniel Veillard60979bd2000-07-10 12:17:33 +00004846 cur = cur-&gt;xmlChildrenNode;
Daniel Veillard14fff061999-06-22 21:49:07 +00004847 while (cur != NULL) {
4848
Daniel Veillard60979bd2000-07-10 12:17:33 +00004849 if ((!strcmp(cur-&gt;name, "Project")) &amp;&amp; (cur-&gt;ns == ns)) {
4850 ret-&gt;projectID = xmlGetProp(cur, "ID");
4851 if (ret-&gt;projectID == NULL) {
Daniel Veillardb05deb71999-08-10 19:04:08 +00004852 fprintf(stderr, "Project has no ID\n");
4853 }
4854 }
Daniel Veillard60979bd2000-07-10 12:17:33 +00004855 if ((!strcmp(cur-&gt;name, "Application")) &amp;&amp; (cur-&gt;ns == ns))
4856 ret-&gt;application = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4857 if ((!strcmp(cur-&gt;name, "Category")) &amp;&amp; (cur-&gt;ns == ns))
4858 ret-&gt;category = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4859 if ((!strcmp(cur-&gt;name, "Contact")) &amp;&amp; (cur-&gt;ns == ns))
4860 ret-&gt;contact = parsePerson(doc, ns, cur);
4861 cur = cur-&gt;next;
Daniel Veillard14fff061999-06-22 21:49:07 +00004862 }
4863
4864 return(ret);
Daniel Veillardb05deb71999-08-10 19:04:08 +00004865}</pre>
Daniel Veillard14fff061999-06-22 21:49:07 +00004866
Daniel Veillardec70e912001-02-26 20:10:45 +00004867<p>Once you are used to it, writing this kind of code is quite simple, but
Daniel Veillard63d83142002-05-20 06:51:05 +00004868boring. Ultimately, it could be possible to write stubbers taking either C
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004869data structure definitions, a set of XML examples or an XML DTD and produce
4870the code needed to import and export the content between C data and XML
4871storage. This is left as an exercise to the reader :-)</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004872
Daniel Veillard6f0adb52000-07-03 11:41:26 +00004873<p>Feel free to use <a href="example/gjobread.c">the code for the full C
4874parsing example</a> as a template, it is also available with Makefile in the
4875Gnome CVS base under gnome-xml/example</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004876
Daniel Veillardc310d562000-06-23 18:32:15 +00004877<h2><a name="Contributi">Contributions</a></h2>
4878<ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004879 <li>Bjorn Reese, William Brack and Thomas Broyer have provided a number of
4880 patches, Gary Pennington worked on the validation API, threading support
4881 and Solaris port.</li>
4882 <li>John Fleck helps maintaining the documentation and man pages.</li>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00004883 <li><a href="mailto:igor@zlatkovic.com">Igor Zlatkovic</a> is now the
4884 maintainer of the Windows port, <a
4885 href="http://www.zlatkovic.com/projects/libxml/index.html">he provides
4886 binaries</a></li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00004887 <li><a href="mailto:Gary.Pennington@sun.com">Gary Pennington</a> provides
4888 <a href="http://garypennington.net/libxml2/">Solaris binaries</a></li>
Daniel Veillarde356c282001-03-10 12:32:04 +00004889 <li><a
4890 href="http://mail.gnome.org/archives/xml/2001-March/msg00014.html">Matt
Daniel Veillard63d83142002-05-20 06:51:05 +00004891 Sergeant</a> developed <a
4892 href="http://axkit.org/download/">XML::LibXSLT</a>, a Perl wrapper for
Daniel Veillardaf43f632002-03-08 15:05:20 +00004893 libxml2/libxslt as part of the <a href="http://axkit.com/">AxKit XML
4894 application server</a></li>
4895 <li><a href="mailto:fnatter@gmx.net">Felix Natter</a> and <a
4896 href="mailto:geertk@ai.rug.nl">Geert Kloosterman</a> provide <a
Daniel Veillardca989762001-06-23 17:39:29 +00004897 href="libxml-doc.el">an emacs module</a> to lookup libxml(2) functions
Daniel Veillard3f6f7f62000-06-30 17:58:25 +00004898 documentation</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00004899 <li><a href="mailto:sherwin@nlm.nih.gov">Ziying Sherwin</a> provided <a
4900 href="http://xmlsoft.org/messages/0488.html">man pages</a></li>
Daniel Veillard5168dbf2001-07-07 00:18:23 +00004901 <li>there is a module for <a
4902 href="http://acs-misc.sourceforge.net/nsxml.html">libxml/libxslt support
4903 in OpenNSD/AOLServer</a></li>
Daniel Veillard2d347fa2002-03-17 10:34:11 +00004904 <li><a href="mailto:dkuhlman@cutter.rexx.com">Dave Kuhlman</a> provided the
4905 first version of libxml/libxslt <a
4906 href="http://www.rexx.com/~dkuhlman">wrappers for Python</a></li>
Daniel Veillard1aadc442001-11-28 13:10:32 +00004907 <li>Petr Kozelka provides <a
4908 href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
4909 libxml2</a> with Kylix and Delphi and other Pascal compilers</li>
Daniel Veillard2d347fa2002-03-17 10:34:11 +00004910 <li><a href="mailto:aleksey@aleksey.com">Aleksey Sanin</a> implemented the
4911 <a href="http://www.w3.org/Signature/">XML Canonicalization and XML
4912 Digital Signature</a> <a
4913 href="http://www.aleksey.com/xmlsec/">implementations for libxml2</a></li>
Daniel Veillard67952602006-01-05 15:29:44 +00004914 <li><a href="mailto:Steve.Ball@explain.com.au">Steve Ball</a> and
4915 contributors maintain <a href="http://tclxml.sourceforge.net/">tcl
4916 bindings for libxml2 and libxslt</a>, as well as <a
Daniel Veillard17bed982003-02-24 20:11:43 +00004917 href="http://tclxml.sf.net/tkxmllint.html">tkxmllint</a> a GUI for
4918 xmllint and <a href="http://tclxml.sf.net/tkxsltproc.html">tkxsltproc</a>
4919 a GUI for xsltproc.</li>
Daniel Veillardc310d562000-06-23 18:32:15 +00004920</ul>
4921
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004922<p></p>
Daniel Veillardccb09631998-10-27 06:21:04 +00004923</body>
4924</html>