blob: 7f5dec6453a7a7b46a1a3d14d92e5c0ebf00eafb [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 Veillardaf43f632002-03-08 15:05:20 +00006 <meta name="GENERATOR" content="amaya 5.1">
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 Veillard6a0baa02005-12-10 11:11:12 +000013<h1>Note: this is the flat content of the <a href="index.html">web site</a></h1>
Daniel Veillard9c466822001-10-25 12:03:39 +000014
Daniel Veillardc9484202001-10-24 12:35:52 +000015<h1 style="text-align: center">libxml, a.k.a. gnome-xml</h1>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +000016
17<p></p>
Daniel Veillard9c466822001-10-25 12:03:39 +000018
Daniel Veillard7ebac022004-02-25 22:36:35 +000019<p
20style="text-align: right; font-style: italic; font-size: 10pt">"Programming
21with libxml2 is like the thrilling embrace of an exotic stranger." <a
22href="http://diveintomark.org/archives/2004/02/18/libxml2">Mark
23Pilgrim</a></p>
24
Daniel Veillard598bec32003-07-06 10:02:03 +000025<p>Libxml2 is the XML C parser and toolkit developed for the Gnome project
Daniel Veillard23a52c52003-08-18 10:01:18 +000026(but usable outside of the Gnome platform), it is free software available
Daniel Veillardeec1ae92003-09-09 13:11:01 +000027under the <a href="http://www.opensource.org/licenses/mit-license.html">MIT
28License</a>. XML itself is a metalanguage to design markup languages, i.e.
29text language where semantic and structure are added to the content using
30extra "markup" information enclosed between angle brackets. HTML is the most
31well-known markup language. Though the library is written in C <a
32href="python.html">a variety of language bindings</a> make it available in
33other environments.</p>
Daniel Veillard9c466822001-10-25 12:03:39 +000034
Daniel Veillard710823b2003-03-04 10:05:52 +000035<p>Libxml2 is known to be very portable, the library should build and work
36without serious troubles on a variety of systems (Linux, Unix, Windows,
37CygWin, MacOS, MacOS X, RISC Os, OS/2, VMS, QNX, MVS, ...)</p>
38
Daniel Veillard9c466822001-10-25 12:03:39 +000039<p>Libxml2 implements a number of existing standards related to markup
40languages:</p>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +000041<ul>
Daniel Veillard9c466822001-10-25 12:03:39 +000042 <li>the XML standard: <a
43 href="http://www.w3.org/TR/REC-xml">http://www.w3.org/TR/REC-xml</a></li>
44 <li>Namespaces in XML: <a
45 href="http://www.w3.org/TR/REC-xml-names/">http://www.w3.org/TR/REC-xml-names/</a></li>
46 <li>XML Base: <a
47 href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a></li>
Daniel Veillardaf43f632002-03-08 15:05:20 +000048 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc2396.txt">RFC 2396</a> :
49 Uniform Resource Identifiers <a
Daniel Veillard9c466822001-10-25 12:03:39 +000050 href="http://www.ietf.org/rfc/rfc2396.txt">http://www.ietf.org/rfc/rfc2396.txt</a></li>
51 <li>XML Path Language (XPath) 1.0: <a
52 href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a></li>
53 <li>HTML4 parser: <a
54 href="http://www.w3.org/TR/html401/">http://www.w3.org/TR/html401/</a></li>
Daniel Veillard23a52c52003-08-18 10:01:18 +000055 <li>XML Pointer Language (XPointer) Version 1.0: <a
Daniel Veillard9c466822001-10-25 12:03:39 +000056 href="http://www.w3.org/TR/xptr">http://www.w3.org/TR/xptr</a></li>
57 <li>XML Inclusions (XInclude) Version 1.0: <a
58 href="http://www.w3.org/TR/xinclude/">http://www.w3.org/TR/xinclude/</a></li>
Daniel Veillard23a52c52003-08-18 10:01:18 +000059 <li>ISO-8859-x encodings, as well as <a
Daniel Veillard9c466822001-10-25 12:03:39 +000060 href="http://www.cis.ohio-state.edu/rfc/rfc2044.txt">rfc2044</a> [UTF-8]
61 and <a href="http://www.cis.ohio-state.edu/rfc/rfc2781.txt">rfc2781</a>
Daniel Veillard23a52c52003-08-18 10:01:18 +000062 [UTF-16] Unicode encodings, and more if using iconv support</li>
Daniel Veillard9c466822001-10-25 12:03:39 +000063 <li>part of SGML Open Technical Resolution TR9401:1997</li>
64 <li>XML Catalogs Working Draft 06 August 2001: <a
65 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 +000066 <li>Canonical XML Version 1.0: <a
67 href="http://www.w3.org/TR/xml-c14n">http://www.w3.org/TR/xml-c14n</a>
Daniel Veillard2d347fa2002-03-17 10:34:11 +000068 and the Exclusive XML Canonicalization CR draft <a
69 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 +000070 <li>Relax NG, ISO/IEC 19757-2:2003, <a
Daniel Veillard17bed982003-02-24 20:11:43 +000071 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 +000072 <li>W3C XML Schemas Part 2: Datatypes <a
73 href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">REC 02 May
Daniel Veillard7ecced52003-12-18 14:22:09 +000074 2001</a></li>
Daniel Veillardeca726d2004-04-18 21:47:34 +000075 <li>W3C <a href="http://www.w3.org/TR/xml-id/">xml:id</a> Working Draft 7
76 April 2004</li>
Daniel Veillard96984452000-08-31 13:50:12 +000077</ul>
78
Daniel Veillard560c2a42003-07-06 21:13:49 +000079<p>In most cases libxml2 tries to implement the specifications in a
Daniel Veillard7c4eb632004-04-19 21:29:12 +000080relatively strictly compliant way. As of release 2.4.16, libxml2 passed all
Daniel Veillard560c2a42003-07-06 21:13:49 +0000811800+ tests from the <a
Daniel Veillarda5393562002-02-20 11:40:49 +000082href="http://www.oasis-open.org/committees/xml-conformance/">OASIS XML Tests
83Suite</a>.</p>
Daniel Veillard5b16f582002-02-20 11:38:46 +000084
Daniel Veillard0b28e882002-07-24 23:47:05 +000085<p>To some extent libxml2 provides support for the following additional
86specifications but doesn't claim to implement them completely:</p>
Daniel Veillard9c466822001-10-25 12:03:39 +000087<ul>
88 <li>Document Object Model (DOM) <a
89 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 +000090 the document model, but it doesn't implement the API itself, gdome2 does
91 this on top of libxml2</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +000092 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc959.txt">RFC 959</a> :
Daniel Veillard8a469172003-06-12 16:05:07 +000093 libxml2 implements a basic FTP client code</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +000094 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc1945.txt">RFC 1945</a> :
95 HTTP/1.0, again a basic HTTP client code</li>
Daniel Veillard7c4eb632004-04-19 21:29:12 +000096 <li>SAX: a SAX2 like interface and a minimal SAX1 implementation compatible
97 with early expat versions</li>
Daniel Veillard9c466822001-10-25 12:03:39 +000098</ul>
99
Daniel Veillardf83a2c72003-04-08 13:48:40 +0000100<p>A partial implementation of <a
101href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">XML Schemas Part
1021: Structure</a> is being worked on but it would be far too early to make any
103conformance statement about it at the moment.</p>
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000104
Daniel Veillard96984452000-08-31 13:50:12 +0000105<p>Separate documents:</p>
106<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000107 <li><a href="http://xmlsoft.org/XSLT/">the libxslt page</a> providing an
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000108 implementation of XSLT 1.0 and common extensions like EXSLT for
109 libxml2</li>
Daniel Veillardc6271d22001-10-27 07:50:58 +0000110 <li><a href="http://www.cs.unibo.it/~casarini/gdome2/">the gdome2 page</a>
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000111 : a standard DOM2 implementation for libxml2</li>
112 <li><a href="http://www.aleksey.com/xmlsec/">the XMLSec page</a>: an
113 implementation of <a href="http://www.w3.org/TR/xmldsig-core/">W3C XML
114 Digital Signature</a> for libxml2</li>
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000115 <li>also check the related links section below for more related and active
116 projects.</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000117</ul>
Daniel Veillard252004d2004-03-23 12:32:32 +0000118<!----------------<p>Results of the <a
Daniel Veillard806cada2003-03-19 21:58:59 +0000119href="http://xmlbench.sourceforge.net/results/benchmark/index.html">xmlbench
Daniel Veillard31ae4622004-02-16 07:45:44 +0000120benchmark</a> on sourceforge February 2004 (smaller is better):</p>
Daniel Veillardd8da01c2003-03-24 15:58:23 +0000121
Daniel Veillard31ae4622004-02-16 07:45:44 +0000122<p align="center"><img src="benchmark.png"
Daniel Veillardd8da01c2003-03-24 15:58:23 +0000123alt="benchmark results for Expat Xerces libxml2 Oracle and Sun toolkits"></p>
Daniel Veillardcf80b782004-03-07 19:32:19 +0000124-------------->
Daniel Veillard806cada2003-03-19 21:58:59 +0000125
Daniel Veillard252004d2004-03-23 12:32:32 +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>
William M. Brack99906ad2005-01-09 17:02:42 +0000317 <li><em>I want to install my own copy of libxml2 in my home directory and link
318 my programs against it, but it doesn't work</em>
319 <p>There are many different ways to accomplish this. Here is one way to
320 do this under Linux. Suppose your home directory is <code>/home/user.
321 </code>Then:</p>
322 <ul><li>Create a subdirectory, let's call it <code>myxml</code></li>
323 <li>unpack the libxml2 distribution into that subdirectory</li>
324 <li>chdir into the unpacked distribution (<code>/home/user/myxml/libxml2
325 </code>)</li>
326 <li>configure the library using the "<code>--prefix</code>" switch,
327 specifying an installation subdirectory in <code>/home/user/myxml</code>,
328 e.g.
329 <p><code>./configure --prefix /home/user/myxml/xmlinst</code> {other
330 configuration options}</p></li>
331 <li>now run <code>make</code> followed by <code>make install</code></li>
332 <li>At this point, the installation subdirectory contains the complete
333 "private" include files, library files and binary program files (e.g.
334 xmllint), located in
335 <p> <code>/home/user/myxml/xmlinst/lib, /home/user/myxml/xmlinst/include
336 </code> and <code> /home/user/myxml/xmlinst/bin</code></p>
337 respectively.</li>
338 <li>In order to use this "private" library, you should first add it
339 to the beginning of your default PATH (so that your own private
340 program files such as xmllint will be used instead of the normal
341 system ones). To do this, the Bash command would be
342 <p><code>export PATH=/home/user/myxml/xmlinst/bin:$PATH</code></p></li>
343 <li>Now suppose you have a program <code>test1.c</code> that you would
344 like to compile with your "private" library. Simply compile it
345 using the command <p><code>gcc `xml2-config --cflags --libs` -o test
346 test.c</code></p> Note that, because your PATH has been set with <code>
347 /home/user/myxml/xmlinst/bin</code> at the beginning, the
348 xml2-config program which you just installed will be used instead of
349 the system default one, and this will <em>automatically</em> get the
350 correct libraries linked with your program.</li></ul>
351 </li><p/>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000352 <li><em>xmlDocDump() generates output on one line.</em>
Daniel Veillard8a469172003-06-12 16:05:07 +0000353 <p>Libxml2 will not <strong>invent</strong> spaces in the content of a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000354 document since <strong>all spaces in the content of a document are
355 significant</strong>. If you build a tree from the API and want
356 indentation:</p>
357 <ol>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000358 <li>the correct way is to generate those yourself too.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000359 <li>the dangerous way is to ask libxml2 to add those blanks to your
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000360 content <strong>modifying the content of your document in the
361 process</strong>. The result may not be what you expect. There is
362 <strong>NO</strong> way to guarantee that such a modification won't
Daniel Veillard0b28e882002-07-24 23:47:05 +0000363 affect other parts of the content of your document. See <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000364 href="http://xmlsoft.org/html/libxml-parser.html#xmlKeepBlanksDefault">xmlKeepBlanksDefault
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000365 ()</a> and <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000366 href="http://xmlsoft.org/html/libxml-tree.html#xmlSaveFormatFile">xmlSaveFormatFile
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000367 ()</a></li>
368 </ol>
369 </li>
370 <li>Extra nodes in the document:
371 <p><em>For a XML file as below:</em></p>
372 <pre>&lt;?xml version="1.0"?&gt;
373&lt;PLAN xmlns="http://www.argus.ca/autotest/1.0/"&gt;
374&lt;NODE CommFlag="0"/&gt;
375&lt;NODE CommFlag="1"/&gt;
376&lt;/PLAN&gt;</pre>
377 <p><em>after parsing it with the function
378 pxmlDoc=xmlParseFile(...);</em></p>
379 <p><em>I want to the get the content of the first node (node with the
380 CommFlag="0")</em></p>
381 <p><em>so I did it as following;</em></p>
Daniel Veillard63d83142002-05-20 06:51:05 +0000382 <pre>xmlNodePtr pnode;
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000383pnode=pxmlDoc-&gt;children-&gt;children;</pre>
384 <p><em>but it does not work. If I change it to</em></p>
385 <pre>pnode=pxmlDoc-&gt;children-&gt;children-&gt;next;</pre>
386 <p><em>then it works. Can someone explain it to me.</em></p>
387 <p></p>
388 <p>In XML all characters in the content of the document are significant
389 <strong>including blanks and formatting line breaks</strong>.</p>
390 <p>The extra nodes you are wondering about are just that, text nodes with
Daniel Veillard63d83142002-05-20 06:51:05 +0000391 the formatting spaces which are part of the document but that people tend
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000392 to forget. There is a function <a
393 href="http://xmlsoft.org/html/libxml-parser.html">xmlKeepBlanksDefault
394 ()</a> to remove those at parse time, but that's an heuristic, and its
Daniel Veillard0b28e882002-07-24 23:47:05 +0000395 use should be limited to cases where you are certain there is no
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000396 mixed-content in the document.</p>
397 </li>
398 <li><em>I get compilation errors of existing code like when accessing
Daniel Veillard0b28e882002-07-24 23:47:05 +0000399 <strong>root</strong> or <strong>child fields</strong> of nodes.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000400 <p>You are compiling code developed for libxml version 1 and using a
401 libxml2 development environment. Either switch back to libxml v1 devel or
402 even better fix the code to compile with libxml2 (or both) by <a
403 href="upgrade.html">following the instructions</a>.</p>
404 </li>
405 <li><em>I get compilation errors about non existing
406 <strong>xmlRootNode</strong> or <strong>xmlChildrenNode</strong>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000407 fields.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000408 <p>The source code you are using has been <a
409 href="upgrade.html">upgraded</a> to be able to compile with both libxml
410 and libxml2, but you need to install a more recent version:
411 libxml(-devel) &gt;= 1.8.8 or libxml2(-devel) &gt;= 2.1.0</p>
412 </li>
413 <li><em>XPath implementation looks seriously broken</em>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000414 <p>XPath implementation prior to 2.3.0 was really incomplete. Upgrade to
415 a recent version, there are no known bugs in the current version.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000416 </li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000417 <li><em>The example provided in the web page does not compile.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000418 <p>It's hard to maintain the documentation in sync with the code
419 &lt;grin/&gt; ...</p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000420 <p>Check the previous points 1/ and 2/ raised before, and please send
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000421 patches.</p>
422 </li>
Daniel Veillard8d7b5c72003-11-15 18:24:36 +0000423 <li><em>Where can I get more examples and information than provided on the
Daniel Veillard42766c02002-08-22 20:52:17 +0000424 web page?</em>
Daniel Veillard8a469172003-06-12 16:05:07 +0000425 <p>Ideally a libxml2 book would be nice. I have no such plan ... But you
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000426 can:</p>
427 <ul>
428 <li>check more deeply the <a href="html/libxml-lib.html">existing
429 generated doc</a></li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000430 <li>have a look at <a href="examples/index.html">the set of
431 examples</a>.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000432 <li>look for examples of use for libxml2 function using the Gnome code.
Daniel Veillard0b28e882002-07-24 23:47:05 +0000433 For example the following will query the full Gnome CVS base for the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000434 use of the <strong>xmlAddChild()</strong> function:
435 <p><a
436 href="http://cvs.gnome.org/lxr/search?string=xmlAddChild">http://cvs.gnome.org/lxr/search?string=xmlAddChild</a></p>
437 <p>This may be slow, a large hardware donation to the gnome project
438 could cure this :-)</p>
439 </li>
440 <li><a
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000441 href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gnome-xml">Browse
442 the libxml2 source</a> , I try to write code as clean and documented
Daniel Veillard42766c02002-08-22 20:52:17 +0000443 as possible, so looking at it may be helpful. In particular the code
444 of xmllint.c and of the various testXXX.c test programs should
445 provide good examples of how to do things with the library.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000446 </ul>
447 </li>
448 <li>What about C++ ?
Daniel Veillard8a469172003-06-12 16:05:07 +0000449 <p>libxml2 is written in pure C in order to allow easy reuse on a number
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000450 of platforms, including embedded systems. I don't intend to convert to
451 C++.</p>
Daniel Veillard91e69c52003-08-04 01:43:07 +0000452 <p>There is however a C++ wrapper which may fulfill your needs:</p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000453 <ul>
454 <li>by Ari Johnson &lt;ari@btigate.com&gt;:
455 <p>Website: <a
Daniel Veillard91e69c52003-08-04 01:43:07 +0000456 href="http://libxmlplusplus.sourceforge.net/">http://libxmlplusplus.sourceforge.net/</a></p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000457 <p>Download: <a
Daniel Veillard91e69c52003-08-04 01:43:07 +0000458 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 +0000459 </li>
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000460 <!-- Website is currently unavailable as of 2003-08-02
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000461 <li>by Peter Jones &lt;pjones@pmade.org&gt;
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000462 <p>Website: <a
463 href="http://pmade.org/pjones/software/xmlwrapp/">http://pmade.org/pjones/software/xmlwrapp/</a></p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000464 </li>
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000465 -->
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000466 </ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000467 </li>
468 <li>How to validate a document a posteriori ?
469 <p>It is possible to validate documents which had not been validated at
Daniel Veillard42766c02002-08-22 20:52:17 +0000470 initial parsing time or documents which have been built from scratch
471 using the API. Use the <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000472 href="http://xmlsoft.org/html/libxml-valid.html#xmlValidateDtd">xmlValidateDtd()</a>
Daniel Veillard63d83142002-05-20 06:51:05 +0000473 function. It is also possible to simply add a DTD to an existing
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000474 document:</p>
475 <pre>xmlDocPtr doc; /* your existing document */
Daniel Veillard0b28e882002-07-24 23:47:05 +0000476xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
477
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000478 dtd-&gt;name = xmlStrDup((xmlChar*)"root_name"); /* use the given root */
479
480 doc-&gt;intSubset = dtd;
481 if (doc-&gt;children == NULL) xmlAddChild((xmlNodePtr)doc, (xmlNodePtr)dtd);
482 else xmlAddPrevSibling(doc-&gt;children, (xmlNodePtr)dtd);
483 </pre>
484 </li>
Daniel Veillarddad3f682002-11-17 16:47:27 +0000485 <li>So what is this funky "xmlChar" used all the time?
486 <p>It is a null terminated sequence of utf-8 characters. And only utf-8!
487 You need to convert strings encoded in different ways to utf-8 before
488 passing them to the API. This can be accomplished with the iconv library
489 for instance.</p>
John Fleck61f6fb62002-10-31 15:23:29 +0000490 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000491 <li>etc ...</li>
492</ol>
493
494<p></p>
495
Daniel Veillard66f68e72003-08-18 16:39:51 +0000496<h2><a name="Documentat">Developer Menu</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000497
Daniel Veillard0b28e882002-07-24 23:47:05 +0000498<p>There are several on-line resources related to using libxml:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000499<ol>
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000500 <li>Use the <a href="search.php">search engine</a> to look up
501 information.</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000502 <li>Check the <a href="FAQ.html">FAQ.</a></li>
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000503 <li>Check the <a href="http://xmlsoft.org/html/libxml-lib.html">extensive
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000504 documentation</a> automatically extracted from code comments.</li>
Daniel Veillard8d869642000-07-14 12:12:59 +0000505 <li>Look at the documentation about <a href="encoding.html">libxml
Daniel Veillard0b28e882002-07-24 23:47:05 +0000506 internationalization support</a>.</li>
Daniel Veillardbc66f852002-01-14 09:49:20 +0000507 <li>This page provides a global overview and <a href="example.html">some
Daniel Veillard402e8c82000-02-29 22:57:47 +0000508 examples</a> on how to use libxml.</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000509 <li><a href="examples/index.html">Code examples</a></li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000510 <li>John Fleck's libxml2 tutorial: <a href="tutorial/index.html">html</a>
511 or <a href="tutorial/xmltutorial.pdf">pdf</a>.</li>
Daniel Veillard1177ca42003-04-26 22:29:54 +0000512 <li>If you need to parse large files, check the <a
513 href="xmlreader.html">xmlReader</a> API tutorial</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000514 <li><a href="mailto:james@daa.com.au">James Henstridge</a> wrote <a
Daniel Veillard402e8c82000-02-29 22:57:47 +0000515 href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">some nice
516 documentation</a> explaining how to use the libxml SAX interface.</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000517 <li>George Lebl wrote <a
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000518 href="http://www-106.ibm.com/developerworks/library/l-gnome3/">an article
Daniel Veillard402e8c82000-02-29 22:57:47 +0000519 for IBM developerWorks</a> about using libxml.</li>
Daniel Veillardec303412000-03-24 13:41:54 +0000520 <li>Check <a href="http://cvs.gnome.org/lxr/source/gnome-xml/TODO">the TODO
Daniel Veillard0b28e882002-07-24 23:47:05 +0000521 file</a>.</li>
Daniel Veillard42766c02002-08-22 20:52:17 +0000522 <li>Read the <a href="upgrade.html">1.x to 2.x upgrade path</a>
523 description. If you are starting a new project using libxml you should
524 really use the 2.x version.</li>
Daniel Veillard845cce42002-01-09 11:51:37 +0000525 <li>And don't forget to look at the <a
526 href="http://mail.gnome.org/archives/xml/">mailing-list archive</a>.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000527</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000528
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000529<h2><a name="Reporting">Reporting bugs and getting help</a></h2>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000530
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000531<p>Well, bugs or missing features are always possible, and I will make a
532point of fixing them in a timely fashion. The best way to report a bug is to
Daniel Veillardccf996f2003-08-14 10:48:38 +0000533use the <a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome
Daniel Veillard42766c02002-08-22 20:52:17 +0000534bug tracking database</a> (make sure to use the "libxml2" module name). I
535look at reports there regularly and it's good to have a reminder when a bug
536is still open. Be sure to specify that the bug is for the package libxml2.</p>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000537
Daniel Veillard4ac494b2003-09-18 15:08:00 +0000538<p>For small problems you can try to get help on IRC, the #xml channel on
539irc.gnome.org (port 6667) usually have a few person subscribed which may help
540(but there is no garantee and if a real issue is raised it should go on the
541mailing-list for archival).</p>
Daniel Veillard9582d6c2003-09-16 11:40:04 +0000542
Daniel Veillard0142b842000-01-14 14:45:24 +0000543<p>There is also a mailing-list <a
Daniel Veillard3197f162001-04-04 00:40:08 +0000544href="mailto:xml@gnome.org">xml@gnome.org</a> for libxml, with an <a
545href="http://mail.gnome.org/archives/xml/">on-line archive</a> (<a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000546href="http://xmlsoft.org/messages">old</a>). To subscribe to this list,
547please visit the <a
548href="http://mail.gnome.org/mailman/listinfo/xml">associated Web</a> page and
549follow the instructions. <strong>Do not send code, I won't debug it</strong>
550(but patches are really appreciated!).</p>
Daniel Veillardd99224d2004-04-06 10:04:16 +0000551
552<p>Please note that with the current amount of virus and SPAM, sending mail
553to the list without being subscribed won't work. There is *far too many
554bounces* (in the order of a thousand a day !) I cannot approve them manually
555anymore. If your mail to the list bounced waiting for administrator approval,
556it is LOST ! Repost it and fix the problem triggering the error.</p>
Daniel Veillard234547b2001-07-05 09:46:10 +0000557
Daniel Veillard008186f2001-09-13 14:24:44 +0000558<p>Check the following <strong><span style="color: #FF0000">before
559posting</span></strong>:</p>
Daniel Veillard234547b2001-07-05 09:46:10 +0000560<ul>
Daniel Veillard321be0c2002-10-08 21:26:42 +0000561 <li>Read the <a href="FAQ.html">FAQ</a> and <a href="search.php">use the
Daniel Veillarda37aab82003-06-09 09:10:36 +0000562 search engine</a> to get information related to your problem.</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000563 <li>Make sure you are <a href="ftp://xmlsoft.org/">using a recent
564 version</a>, and that the problem still shows up in a recent version.</li>
565 <li>Check the <a href="http://mail.gnome.org/archives/xml/">list
566 archives</a> to see if the problem was reported already. In this case
Daniel Veillard63d83142002-05-20 06:51:05 +0000567 there is probably a fix available, similarly check the <a
Daniel Veillardccf996f2003-08-14 10:48:38 +0000568 href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">registered
Daniel Veillard0b28e882002-07-24 23:47:05 +0000569 open bugs</a>.</li>
570 <li>Make sure you can reproduce the bug with xmllint or one of the test
571 programs found in source in the distribution.</li>
Daniel Veillard234547b2001-07-05 09:46:10 +0000572 <li>Please send the command showing the error as well as the input (as an
Daniel Veillard63d83142002-05-20 06:51:05 +0000573 attachment)</li>
Daniel Veillard234547b2001-07-05 09:46:10 +0000574</ul>
Daniel Veillard0142b842000-01-14 14:45:24 +0000575
Daniel Veillarda37aab82003-06-09 09:10:36 +0000576<p>Then send the bug with associated information to reproduce it to the <a
Daniel Veillard33a67802001-03-07 09:44:02 +0000577href="mailto:xml@gnome.org">xml@gnome.org</a> list; if it's really libxml
Daniel Veillard98d071d2003-01-10 09:22:44 +0000578related I will approve it. Please do not send mail to me directly, it makes
Daniel Veillard0b28e882002-07-24 23:47:05 +0000579things really hard to track and in some cases I am not the best person to
Daniel Veillard98d071d2003-01-10 09:22:44 +0000580answer a given question, ask on the list.</p>
581
582<p>To <span style="color: #E50000">be really clear about support</span>:</p>
583<ul>
Daniel Veillarda37aab82003-06-09 09:10:36 +0000584 <li>Support or help <span style="color: #E50000">requests MUST be sent to
Daniel Veillard98d071d2003-01-10 09:22:44 +0000585 the list or on bugzilla</span> in case of problems, so that the Question
586 and Answers can be shared publicly. Failing to do so carries the implicit
587 message "I want free support but I don't want to share the benefits with
Daniel Veillard831e8fd2003-01-25 11:45:34 +0000588 others" and is not welcome. I will automatically Carbon-Copy the
589 xml@gnome.org mailing list for any technical reply made about libxml2 or
590 libxslt.</li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000591 <li>There is <span style="color: #E50000">no garantee of support</span>, if
592 your question remains unanswered after a week, repost it, making sure you
593 gave all the detail needed and the information requested.</li>
Daniel Veillarda37aab82003-06-09 09:10:36 +0000594 <li>Failing to provide information as requested or double checking first
Daniel Veillard98d071d2003-01-10 09:22:44 +0000595 for prior feedback also carries the implicit message "the time of the
596 library maintainers is less valuable than my time" and might not be
597 welcome.</li>
598</ul>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000599
Daniel Veillard91e9d582001-02-26 07:31:12 +0000600<p>Of course, bugs reported with a suggested patch for fixing them will
Daniel Veillard0b28e882002-07-24 23:47:05 +0000601probably be processed faster than those without.</p>
Daniel Veillardec303412000-03-24 13:41:54 +0000602
603<p>If you're looking for help, a quick look at <a
Daniel Veillardf7ed3362001-08-17 12:01:21 +0000604href="http://mail.gnome.org/archives/xml/">the list archive</a> may actually
Daniel Veillard560c2a42003-07-06 21:13:49 +0000605provide the answer. I usually send source samples when answering libxml2
606usage questions. The <a
607href="http://xmlsoft.org/html/book1.html">auto-generated documentation</a> is
608not as polished as I would like (i need to learn more about DocBook), but
609it's a good starting point.</p>
Daniel Veillardec303412000-03-24 13:41:54 +0000610
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000611<h2><a name="help">How to help</a></h2>
612
613<p>You can help the project in various ways, the best thing to do first is to
614subscribe to the mailing-list as explained before, check the <a
Daniel Veillardf7ed3362001-08-17 12:01:21 +0000615href="http://mail.gnome.org/archives/xml/">archives </a>and the <a
Daniel Veillardccf996f2003-08-14 10:48:38 +0000616href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome bug
Daniel Veillard0b28e882002-07-24 23:47:05 +0000617database</a>:</p>
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000618<ol>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000619 <li>Provide patches when you find problems.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000620 <li>Provide the diffs when you port libxml2 to a new platform. They may not
Daniel Veillardab8500d2000-10-15 21:06:19 +0000621 be integrated in all cases but help pinpointing portability problems
622 and</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000623 <li>Provide documentation fixes (either as patches to the code comments or
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000624 as HTML diffs).</li>
Daniel Veillard42766c02002-08-22 20:52:17 +0000625 <li>Provide new documentations pieces (translations, examples, etc
626 ...).</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000627 <li>Check the TODO file and try to close one of the items.</li>
628 <li>Take one of the points raised in the archive or the bug database and
Daniel Veillarde7ead2d2001-08-22 23:44:09 +0000629 provide a fix. <a href="mailto:daniel@veillard.com">Get in touch with me
630 </a>before to avoid synchronization problems and check that the suggested
631 fix will fit in nicely :-)</li>
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000632</ol>
633
Daniel Veillard10a2c651999-12-12 13:03:50 +0000634<h2><a name="Downloads">Downloads</a></h2>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000635
Daniel Veillard688f6692004-03-26 10:57:38 +0000636<p>The latest versions of libxml2 can be found on the <a
Daniel Veillardeca726d2004-04-18 21:47:34 +0000637href="ftp://xmlsoft.org/">xmlsoft.org</a> server ( <a
638href="http://xmlsoft.org/sources/">HTTP</a>, <a
639href="ftp://xmlsoft.org/">FTP</a> and rsync are available), there is also
Daniel Veillard210818b2004-09-29 15:50:37 +0000640mirrors (<a href="ftp://ftp.planetmirror.com/pub/xmlsoft/">Australia</a>( <a
641href="http://xmlsoft.planetmirror.com/">Web</a>), <a
Daniel Veillard20c8cf22001-06-26 22:47:36 +0000642href="ftp://fr.rpmfind.net/pub/libxml/">France</a>) or on the <a
Daniel Veillardd99224d2004-04-06 10:04:16 +0000643href="ftp://ftp.gnome.org/pub/GNOME/MIRRORS.html">Gnome FTP server</a> as <a
644href="ftp://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/">source archive</a>
Daniel Veillard688f6692004-03-26 10:57:38 +0000645, Antonin Sprinzl also provide <a href="ftp://gd.tuwien.ac.at/pub/libxml/">a
Daniel Veillarde16b5742002-09-26 17:50:03 +0000646mirror in Austria</a>. (NOTE that you need both the <a
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000647href="http://rpmfind.net/linux/RPM/libxml2.html">libxml(2)</a> and <a
648href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml(2)-devel</a>
Daniel Veillardb46a5732003-04-08 13:35:48 +0000649packages installed to compile applications using libxml.)</p>
Daniel Veillardeca726d2004-04-18 21:47:34 +0000650
651<p>You can find all the history of libxml(2) and libxslt releases in the <a
Daniel Veillardd4cfcef2004-05-06 18:55:27 +0000652href="http://xmlsoft.org/sources/old/">old</a> directory. The precompiled
Daniel Veillardf81a8e82004-08-03 21:58:41 +0000653Windows binaries made by Igor Zlatovic are available in the <a
654href="http://xmlsoft.org/sources/win32/">win32</a> directory.</p>
Daniel Veillardb46a5732003-04-08 13:35:48 +0000655
656<p>Binary ports:</p>
657<ul>
658 <li>Red Hat RPMs for i386 are available directly on <a
659 href="ftp://xmlsoft.org/">xmlsoft.org</a>, the source RPM will compile on
660 any architecture supported by Red Hat.</li>
Daniel Veillardb331fff2004-08-22 14:21:57 +0000661 <li><a href="mailto:igor@zlatkovic.com">Igor Zlatkovic</a> is now the
662 maintainer of the Windows port, <a
Daniel Veillardb46a5732003-04-08 13:35:48 +0000663 href="http://www.zlatkovic.com/projects/libxml/index.html">he provides
Daniel Veillardb11f5b92004-08-03 22:09:36 +0000664 binaries</a>.</li>
MST 2004 John Fleckb759b302004-12-21 15:14:08 +0000665 <li>Blastwave provides
666 <a href="http://www.blastwave.org/packages.php/libxml2">Solaris binaries</a>.</li>
Daniel Veillardd49370e2005-04-11 23:28:16 +0000667 <li><a href="mailto:Steve.Ball@explain.com.au">Steve Ball</a> provides <a
668 href="http://www.explain.com.au/oss/libxml2xslt.html">Mac Os X
Daniel Veillardb46a5732003-04-08 13:35:48 +0000669 binaries</a>.</li>
670 <li>The HP-UX porting center provides <a
671 href="http://hpux.connect.org.uk/hppd/hpux/Gnome/">HP-UX binaries</a></li>
Daniel Veillard9a27b862005-09-01 09:25:47 +0000672 <li>Bull provides precompiled <a href="http://gnome.bullfreeware.com/new_index.html">RPMs for AIX</a> as patr of their GNOME packages</li>
Daniel Veillardb46a5732003-04-08 13:35:48 +0000673</ul>
674
675<p>If you know other supported binary ports, please <a
676href="http://veillard.com/">contact me</a>.</p>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000677
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000678<p><a name="Snapshot">Snapshot:</a></p>
679<ul>
Daniel Veillard3cef1192004-08-18 09:30:31 +0000680 <li>Code from the W3C cvs base libxml2 module, updated hourly <a
Daniel Veillardfc263f12004-08-31 07:02:04 +0000681 href="ftp://xmlsoft.org/libxml2-cvs-snapshot.tar.gz">libxml2-cvs-snapshot.tar.gz</a>.</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000682 <li>Docs, content of the web site, the list archive included <a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000683 href="ftp://xmlsoft.org/libxml-docs.tar.gz">libxml-docs.tar.gz</a>.</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000684</ul>
685
Daniel Veillardc6271d22001-10-27 07:50:58 +0000686<p><a name="Contribs">Contributions:</a></p>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000687
688<p>I do accept external contributions, especially if compiling on another
Daniel Veillardd99224d2004-04-06 10:04:16 +0000689platform, get in touch with the list to upload the package, wrappers for
690various languages have been provided, and can be found in the <a
691href="python.html">bindings section</a></p>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000692
Daniel Veillard8a469172003-06-12 16:05:07 +0000693<p>Libxml2 is also available from CVS:</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000694<ul>
Daniel Veillardb331fff2004-08-22 14:21:57 +0000695 <li><p>The <a href="http://cvs.gnome.org/viewcvs/libxml2/">Gnome CVS
696 base</a>. Check the <a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000697 href="http://developer.gnome.org/tools/cvs.html">Gnome CVS Tools</a>
Daniel Veillardd99224d2004-04-06 10:04:16 +0000698 page; the CVS module is <b>libxml2</b>.</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000699 </li>
Daniel Veillard82687162001-01-22 15:32:01 +0000700 <li>The <strong>libxslt</strong> module is also present there</li>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000701</ul>
702
Daniel Veillard78fed532004-10-09 19:44:48 +0000703<h2><a name="News">Releases</a></h2>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000704
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000705<p>Items not finished and worked on, get in touch with the list if you want
Daniel Veillard688f6692004-03-26 10:57:38 +0000706to help those</p>
Daniel Veillardab8500d2000-10-15 21:06:19 +0000707<ul>
Daniel Veillard72fef162003-02-05 14:31:19 +0000708 <li>More testing on RelaxNG</li>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +0000709 <li>Finishing up <a href="http://www.w3.org/TR/xmlschema-1/">XML
Daniel Veillard72fef162003-02-05 14:31:19 +0000710 Schemas</a></li>
711</ul>
712
Daniel Veillard2d908032004-08-10 10:16:36 +0000713<p>The <a href="ChangeLog.html">change log</a> describes the recents commits
714to the <a href="http://cvs.gnome.org/viewcvs/libxml2/">CVS</a> code base.</p>
715
Daniel Veillardd99224d2004-04-06 10:04:16 +0000716<p>There is the list of public releases:</p>
717
Daniel Veillard33b20b72005-09-12 21:43:20 +0000718<h3>2.6.22: Sep 12 2005</h3>
719<ul>
720 <li>build fixes: compile without schematron (Stéphane Bidoul)</li>
721 <li>bug fixes: xmlDebugDumpNode on namespace node (Oleg Paraschenko)i,
722 CDATA push parser bug, xmlElemDump problem with XHTML1 doc,
723 XML_FEATURE_xxx clash with expat headers renamed XML_WITH_xxx,
724 fix some output formatting for meta element (Rob Richards),
725 script and style XHTML1 serialization (David Madore), Attribute
726 derivation fixups in XSD (Kasimier Buchcik), better IDC error
727 reports (Kasimier Buchcik)
728 </li>
729 <li>improvements: add XML_SAVE_NO_EMPTY xmlSaveOption (Rob Richards),
730 add XML_SAVE_NO_XHTML xmlSaveOption, XML Schemas improvements
731 preparing for derive (Kasimier Buchcik).</li>
732 <li>documentation: generation of gtk-doc like docs, integration with
733 devhelp.</li>
734</ul>
Daniel Veillardb3d14912005-09-04 20:47:39 +0000735<h3>2.6.21: Sep 4 2005</h3>
736<ul>
737 <li>build fixes: Cygwin portability fixes (Gerrit P. Haase), calling
738 convention problems on Windows (Marcus Boerger), cleanups based on
739 Linus' sparse tool, update of win32/configure.js (Rob Richards),
740 remove warnings on Windows(Marcus Boerger), compilation without SAX1,
741 detection of the Python binary, use $GCC inestad of $CC = 'gcc' (Andrew
742 W. Nosenko), compilation/link with threads and old gcc, compile
743 problem by C370 on Z/OS, </li>
744 <li>bug fixes: http_proxy environments (Peter Breitenlohner), HTML UTF-8
745 bug (Jiri Netolicky), XPath NaN compare bug (William Brack),
746 htmlParseScript potential bug, Schemas regexp handling of spaces,
747 Base64 Schemas comparisons NIST passes, automata build error xsd:all,
748 xmlGetNodePath for namespaced attributes (Alexander Pohoyda),
749 xmlSchemas foreign namespaces handling, XML Schemas facet comparison
750 (Kupriyanov Anatolij), xmlSchemaPSimpleTypeErr error report (Kasimier
751 Buchcik), xml: namespace ahndling in Schemas (Kasimier), empty model
752 group in Schemas (Kasimier), wilcard in Schemas (Kasimier), URI
753 composition (William), xs:anyType in Schemas (Kasimier), Python resolver
754 emmitting error messages directly, Python xmlAttr.parent (Jakub Piotr
755 Clapa), trying to fix the file path/URI conversion,
756 xmlTextReaderGetAttribute fix (Rob Richards), xmlSchemaFreeAnnot memleak
757 (Kasimier), HTML UTF-8 serialization, streaming XPath, Schemas determinism
758 detection problem, XInclude bug, Schemas context type (Dean Hill),
759 validation fix (Derek Poon), xmlTextReaderGetAttribute[Ns] namespaces
760 (Rob Richards), Schemas type fix (Kuba Nowakowski), UTF-8 parser bug,
761 error in encoding handling, xmlGetLineNo fixes, bug on entities handling,
762 entity name extraction in error handling with XInclude, text nodes
763 in HTML body tags (Gary Coady), xml:id and IDness at the treee level
764 fixes, XPath streaming patterns bugs.</li>
765 <li>improvements: structured interfaces for schemas and RNG error reports
766 (Marcus Boerger), optimization of the char data inner loop parsing
767 (thanks to Behdad Esfahbod for the idea), schematron validation
768 though not finished yet, xmlSaveOption to omit XML declaration,
769 keyref match error reports (Kasimier), formal expression handling
770 code not plugged yet, more lax mode for the HTML parser,
771 parser XML_PARSE_COMPACT option for text nodes allocation.</li>
772 <li>documentation: xmllint man page had --nonet duplicated</li>
773</ul>
Daniel Veillard78dfc9f2005-07-10 22:30:30 +0000774<h3>2.6.20: Jul 10 2005</h3>
775<ul>
776 <li> build fixes: Windows build (Rob Richards), Mingw compilation (Igor
777 Zlatkovic), Windows Makefile (Igor), gcc warnings (Kasimier and
778 andriy@google.com), use gcc weak references to pthread to avoid the
779 pthread dependancy on Linux, compilation problem (Steve Nairn),
780 compiling of subset (Morten Welinder), IPv6/ss_family compilation
781 (William Brack), compilation when disabling parts of the library,
782 standalone test distribution.
783 </li>
784 <li> bug fixes: bug in lang(), memory cleanup on errors (William Brack),
785 HTTP query strings (Aron Stansvik), memory leak in DTD (William),
786 integer overflow in XPath (William), nanoftp buffer size, pattern
787 "." apth fixup (Kasimier), leak in tree reported by Malcolm Rowe,
788 replaceNode patch (Brent Hendricks), CDATA with NULL content
789 (Mark Vakoc), xml:base fixup on XInclude (William), pattern
790 fixes (William), attribute bug in exclusive c14n (Aleksey Sanin),
791 xml:space and xml:lang with SAX2 (Rob Richards), namespace
792 trouble in complex parsing (Malcolm Rowe), XSD type QNames fixes
793 (Kasimier), XPath streaming fixups (William), RelaxNG bug (Rob Richards),
794 Schemas for Schemas fixes (Kasimier), removal of ID (Rob Richards),
795 a small RelaxNG leak, HTML parsing in push mode bug (James Bursa),
796 failure to detect UTF-8 parsing bugs in CDATA sections, areBlanks()
797 heuristic failure, duplicate attributes in DTD bug (William).
798 </li>
799 <li> improvements: lot of work on Schemas by Kasimier Buchcik both on
800 conformance and streaming, Schemas validation messages (Kasimier
801 Buchcik, Matthew Burgess), namespace removal at the python level
802 (Brent Hendricks), Update to new Schemas regression tests from
803 W3C/Nist (Kasimier), xmlSchemaValidateFile() (Kasimier), implementation
804 of xmlTextReaderReadInnerXml and xmlTextReaderReadOuterXml (James Wert),
805 standalone test framework and programs, new DOM import APIs
806 xmlDOMWrapReconcileNamespaces() xmlDOMWrapAdoptNode() and
807 xmlDOMWrapRemoveNode(), extension of xmllint capabilities for
808 SAX and Schemas regression tests, xmlStopParser() available in
809 pull mode too, ienhancement to xmllint --shell namespaces support,
810 Windows port of the standalone testing tools (Kasimier and William),
811 xmlSchemaValidateStream() xmlSchemaSAXPlug() and xmlSchemaSAXUnplug()
812 SAX Schemas APIs, Schemas xmlReader support.
813 </li>
814</ul>
Daniel Veillard771971f2005-04-02 10:49:51 +0000815<h3>2.6.19: Apr 02 2005</h3>
816<ul>
817 <li> build fixes: drop .la from RPMs, --with-minimum build fix (William
818 Brack), use XML_SOCKLEN_T instead of SOCKLEN_T because it breaks with
819 AIX 5.3 compiler, fixed elfgcchack.h generation and PLT reduction
820 code on Linux/ELF/gcc4</li>
821 <li> bug fixes: schemas type decimal fixups (William Brack), xmmlint return
822 code (Gerry Murphy), small schemas fixes (Matthew Burgess and
823 GUY Fabrice), workaround "DAV:" namespace brokeness in c14n (Aleksey
824 Sanin), segfault in Schemas (Kasimier Buchcik), Schemas attribute
825 validation (Kasimier), Prop related functions and xmlNewNodeEatName
826 (Rob Richards), HTML serialization of name attribute on a elements,
827 Python error handlers leaks and improvement (Brent Hendricks),
828 uninitialized variable in encoding code, Relax-NG validation bug,
829 potential crash if gnorableWhitespace is NULL, xmlSAXParseDoc and
830 xmlParseDoc signatures, switched back to assuming UTF-8 in case
831 no encoding is given at serialization time</li>
Daniel Veillard0dcc50a2005-04-04 09:34:15 +0000832 <li> improvements: lot of work on Schemas by Kasimier Buchcik on facets
Daniel Veillard771971f2005-04-02 10:49:51 +0000833 checking and also mixed handling.</li>
834 <li></li>
835</ul>
Daniel Veillard57c000e2005-03-13 18:34:29 +0000836<h3>2.6.18: Mar 13 2005</h3>
837<ul>
838 <li> build fixes: warnings (Peter Breitenlohner), testapi.c generation,
839 Bakefile support (Francesco Montorsi), Windows compilation (Joel Reed),
840 some gcc4 fixes, HP-UX portability fixes (Rick Jones).</li>
841 <li> bug fixes: xmlSchemaElementDump namespace (Kasimier Buchcik), push and
842 xmlreader stopping on non-fatal errors, thread support for dictionnaries
843 reference counting (Gary Coady), internal subset and push problem,
844 URL saved in xmlCopyDoc, various schemas bug fixes (Kasimier), Python
845 paths fixup (Stephane Bidoul), xmlGetNodePath and namespaces,
846 xmlSetNsProp fix (Mike Hommey), warning should not count as error
847 (William Brack), xmlCreatePushParser empty chunk, XInclude parser
848 flags (William), cleanup FTP and HTTP code to reuse the uri parsing
849 and IPv6 (William), xmlTextWriterStartAttributeNS fix (Rob Richards),
850 XMLLINT_INDENT being empty (William), xmlWriter bugs (Rob Richards),
851 multithreading on Windows (Rich Salz), xmlSearchNsByHref fix (Kasimier),
852 Python binding leak (Brent Hendricks), aliasing bug exposed by gcc4
853 on s390, xmlTextReaderNext bug (Rob Richards), Schemas decimal type
854 fixes (William Brack), xmlByteConsumed static buffer (Ben Maurer).</li>
855 <li> improvement: speedup parsing comments and DTDs, dictionnary support for
856 hash tables, Schemas Identity constraints (Kasimier), streaming XPath
857 subset, xmlTextReaderReadString added (Bjorn Reese), Schemas canonical
858 values handling (Kasimier), add xmlTextReaderByteConsumed (Aron
859 Stansvik), </li>
860 <li> Documentation: Wiki support (Joel Reed)
861</ul>
Daniel Veillard298d9642005-01-16 20:01:55 +0000862<h3>2.6.17: Jan 16 2005</h3>
863<ul>
864 <li>build fixes: Windows, warnings removal (William Brack),
865 maintainer-clean dependency(William), build in a different directory
866 (William), fixing --with-minimum configure build (William), BeOS
867 build (Marcin Konicki), Python-2.4 detection (William), compilation
868 on AIX (Dan McNichol)</li>
869 <li>bug fixes: xmlTextReaderHasAttributes (Rob Richards), xmlCtxtReadFile()
870 to use the catalog(s), loop on output (William Brack), XPath memory leak,
871 ID deallocation problem (Steve Shepard), debugDumpNode crash (William),
872 warning not using error callback (William), xmlStopParser bug (William),
873 UTF-16 with BOM on DTDs (William), namespace bug on empty elements
874 in push mode (Rob Richards), line and col computations fixups (Aleksey
875 Sanin), xmlURIEscape fix (William), xmlXPathErr on bad range (William),
876 patterns with too many steps, bug in RNG choice optimization, line
877 number sometimes missing.
878 </li>
879 <li>improvements: XSD Schemas (Kasimier Buchcik), python generator (William),
880 xmlUTF8Strpos speedup (William), unicode Python strings (William),
881 XSD error reports (Kasimier Buchcik), Python __str__ call serialize().
882 </li>
883 <li>new APIs: added xmlDictExists(), GetLineNumber and GetColumnNumber
884 for the xmlReader (Aleksey Sanin), Dynamic Shared Libraries APIs
885 (mostly Joel Reed), error extraction API from regexps, new XMLSave
886 option for format (Phil Shafer)</li>
887 <li>documentation: site improvement (John Fleck), FAQ entries (William).</li>
888</ul>
889
Daniel Veillardc3d7cb42004-11-10 14:34:45 +0000890<h3>2.6.16: Nov 10 2004</h3>
891<ul>
892 <li>general hardening and bug fixing crossing all the API based on new
893 automated regression testing</li>
894 <li>build fix: IPv6 build and test on AIX (Dodji Seketeli)</li>
895 <li>bug fixes: problem with XML::Libxml reported by Petr Pajas, encoding
896 conversion functions return values, UTF-8 bug affecting XPath reported by
897 Markus Bertheau, catalog problem with NULL entries (William Brack)</li>
898 <li>documentation: fix to xmllint man page, some API function descritpion
899 were updated.</li>
900 <li>improvements: DTD validation APIs provided at the Python level (Brent
901 Hendricks) </li>
902</ul>
903
Daniel Veillardc2f83d12004-10-27 22:59:21 +0000904<h3>2.6.15: Oct 27 2004</h3>
Daniel Veillard6927b102004-10-27 17:29:04 +0000905<ul>
906 <li>security fixes on the nanoftp and nanohttp modules</li>
907 <li>build fixes: xmllint detection bug in configure, building outside the
908 source tree (Thomas Fitzsimmons)</li>
909 <li>bug fixes: HTML parser on broken ASCII chars in names (William), Python
910 paths (Malcolm Tredinnick), xmlHasNsProp and default namespace (William),
911 saving to python file objects (Malcolm Tredinnick), DTD lookup fix
912 (Malcolm), save back &lt;group&gt; in catalogs (William), tree build
913 fixes (DV and Rob Richards), Schemas memory bug, structured error handler
914 on Python 64bits, thread local memory deallocation, memory leak reported
915 by Volker Roth, xmlValidateDtd in the presence of an internal subset,
916 entities and _private problem (William), xmlBuildRelativeURI error
917 (William).</li>
918 <li>improvements: better XInclude error reports (William), tree debugging
919 module and tests, convenience functions at the Reader API (Graham
920 Bennett), add support for PI in the HTML parser.</li>
921</ul>
922
Daniel Veillard210818b2004-09-29 15:50:37 +0000923<h3>2.6.14: Sep 29 2004</h3>
924<ul>
925 <li>build fixes: configure paths for xmllint and xsltproc, compilation
926 without HTML parser, compilation warning cleanups (William Brack &amp;
Daniel Veillard6927b102004-10-27 17:29:04 +0000927 Malcolm Tredinnick), VMS makefile update (Craig Berry),</li>
Daniel Veillard210818b2004-09-29 15:50:37 +0000928 <li>bug fixes: xmlGetUTF8Char (William Brack), QName properties (Kasimier
929 Buchcik), XInclude testing, Notation serialization, UTF8ToISO8859x
930 transcoding (Mark Itzcovitz), lots of XML Schemas cleanup and fixes
931 (Kasimier), ChangeLog cleanup (Stepan Kasal), memory fixes (Mark Vakoc),
932 handling of failed realloc(), out of bound array adressing in Schemas
933 date handling, Python space/tabs cleanups (Malcolm Tredinnick), NMTOKENS
Daniel Veillard6927b102004-10-27 17:29:04 +0000934 E20 validation fix (Malcolm),</li>
Daniel Veillard210818b2004-09-29 15:50:37 +0000935 <li>improvements: added W3C XML Schemas testsuite (Kasimier Buchcik), add
936 xmlSchemaValidateOneElement (Kasimier), Python exception hierearchy
937 (Malcolm Tredinnick), Python libxml2 driver improvement (Malcolm
938 Tredinnick), Schemas support for xsi:schemaLocation,
939 xsi:noNamespaceSchemaLocation, xsi:type (Kasimier Buchcik)</li>
940</ul>
941
Daniel Veillardd1de4a32004-08-31 13:43:07 +0000942<h3>2.6.13: Aug 31 2004</h3>
943<ul>
944 <li>build fixes: Windows and zlib (Igor Zlatkovic), -O flag with gcc,
Daniel Veillard210818b2004-09-29 15:50:37 +0000945 Solaris compiler warning, fixing RPM BuildRequires,</li>
Daniel Veillardd1de4a32004-08-31 13:43:07 +0000946 <li>fixes: DTD loading on Windows (Igor), Schemas error reports APIs
947 (Kasimier Buchcik), Schemas validation crash, xmlCheckUTF8 (William Brack
948 and Julius Mittenzwei), Schemas facet check (Kasimier), default namespace
949 problem (William), Schemas hexbinary empty values, encoding error could
950 genrate a serialization loop.</li>
951 <li>Improvements: Schemas validity improvements (Kasimier), added --path
952 and --load-trace options to xmllint</li>
953 <li>documentation: tutorial update (John Fleck)</li>
954</ul>
955
Daniel Veillardb331fff2004-08-22 14:21:57 +0000956<h3>2.6.12: Aug 22 2004</h3>
957<ul>
958 <li>build fixes: fix --with-minimum, elfgcchack.h fixes (Peter
959 Breitenlohner), perl path lookup (William), diff on Solaris (Albert
960 Chin), some 64bits cleanups.</li>
961 <li>Python: avoid a warning with 2.3 (William Brack), tab and space mixes
962 (William), wrapper generator fixes (William), Cygwin support (Gerrit P.
963 Haase), node wrapper fix (Marc-Antoine Parent), XML Schemas support
964 (Torkel Lyng)</li>
965 <li>Schemas: a lot of bug fixes and improvements from Kasimier Buchcik</li>
966 <li>fixes: RVT fixes (William), XPath context resets bug (William), memory
967 debug (Steve Hay), catalog white space handling (Peter Breitenlohner),
968 xmlReader state after attribute reading (William), structured error
969 handler (William), XInclude generated xml:base fixup (William), Windows
970 memory reallocation problem (Steve Hay), Out of Memory conditions
971 handling (William and Olivier Andrieu), htmlNewDoc() charset bug,
972 htmlReadMemory init (William), a posteriori validation DTD base
973 (William), notations serialization missing, xmlGetNodePath (Dodji),
974 xmlCheckUTF8 (Diego Tartara), missing line numbers on entity
975 (William)</li>
976 <li>improvements: DocBook catalog build scrip (William), xmlcatalog tool
977 (Albert Chin), xmllint --c14n option, no_proxy environment (Mike Hommey),
978 xmlParseInNodeContext() addition, extend xmllint --shell, allow XInclude
979 to not generate start/end nodes, extend xmllint --version to include CVS
980 tag (William)</li>
981 <li>documentation: web pages fixes, validity API docs fixes (William)
982 schemas API fix (Eric Haszlakiewicz), xmllint man page (John Fleck)</li>
983</ul>
984
Daniel Veillard45cb0f42004-07-05 17:45:35 +0000985<h3>2.6.11: July 5 2004</h3>
986<ul>
987 <li>Schemas: a lot of changes and improvements by Kasimier Buchcik for
988 attributes, namespaces and simple types.</li>
989 <li>build fixes: --with-minimum (William Brack), some gcc cleanup
990 (William), --with-thread-alloc (William)</li>
991 <li>portability: Windows binary package change (Igor Zlatkovic), Catalog
992 path on Windows</li>
993 <li>documentation: update to the tutorial (John Fleck), xmllint return code
Daniel Veillardb331fff2004-08-22 14:21:57 +0000994 (John Fleck), man pages (Ville Skytta),</li>
Daniel Veillard45cb0f42004-07-05 17:45:35 +0000995 <li>bug fixes: C14N bug serializing namespaces (Aleksey Sanin), testSAX
996 properly initialize the library (William), empty node set in XPath
997 (William), xmlSchemas errors (William), invalid charref problem pointed
998 by Morus Walter, XInclude xml:base generation (William), Relax-NG bug
Daniel Veillardb331fff2004-08-22 14:21:57 +0000999 with div processing (William), XPointer and xml:base problem(William),
Daniel Veillard45cb0f42004-07-05 17:45:35 +00001000 Reader and entities, xmllint return code for schemas (William), reader
1001 streaming problem (Steve Ball), DTD serialization problem (William),
1002 libxml.m4 fixes (Mike Hommey), do not provide destructors as methods on
1003 Python classes, xmlReader buffer bug, Python bindings memory interfaces
1004 improvement (with Stéphane Bidoul), Fixed the push parser to be back to
1005 synchronous behaviour.</li>
1006 <li>improvement: custom per-thread I/O enhancement (Rob Richards), register
1007 namespace in debug shell (Stefano Debenedetti), Python based regression
1008 test for non-Unix users (William), dynamically increase the number of
1009 XPath extension functions in Python and fix a memory leak (Marc-Antoine
1010 Parent and William)</li>
1011 <li>performance: hack done with Arjan van de Ven to reduce ELF footprint
1012 and generated code on Linux, plus use gcc runtime profiling to optimize
1013 the code generated in the RPM packages.</li>
1014</ul>
1015
Daniel Veillard81205012004-05-18 03:06:41 +00001016<h3>2.6.10: May 17 2004</h3>
1017<ul>
1018 <li>Web page generated for ChangeLog</li>
1019 <li>build fixes: --without-html problems, make check without make all</li>
1020 <li>portability: problem with xpath.c on Windows (MSC and Borland), memcmp
1021 vs. strncmp on Solaris, XPath tests on Windows (Mark Vakoc), C++ do not
1022 use "list" as parameter name, make tests work with Python 1.5 (Ed
1023 Davis),</li>
1024 <li>improvements: made xmlTextReaderMode public, small buffers resizing
1025 (Morten Welinder), add --maxmem option to xmllint, add
1026 xmlPopInputCallback() for Matt Sergeant, refactoring of serialization
Daniel Veillard45cb0f42004-07-05 17:45:35 +00001027 escaping, added escaping customization</li>
Daniel Veillard81205012004-05-18 03:06:41 +00001028 <li>bugfixes: xsd:extension (Taihei Goi), assorted regexp bugs (William
1029 Brack), xmlReader end of stream problem, node deregistration with reader,
1030 URI escaping and filemanes, XHTML1 formatting (Nick Wellnhofer), regexp
1031 transition reduction (William), various XSD Schemas fixes (Kasimier
1032 Buchcik), XInclude fallback problem (William), weird problems with DTD
1033 (William), structured error handler callback context (William), reverse
1034 xmlEncodeSpecialChars() behaviour back to escaping '"'</li>
1035</ul>
1036
Daniel Veillardeca726d2004-04-18 21:47:34 +00001037<h3>2.6.9: Apr 18 2004</h3>
1038<ul>
1039 <li>implement xml:id Working Draft, relaxed XPath id() checking</li>
1040 <li>bugfixes: xmlCtxtReset (Brent Hendricks), line number and CDATA (Dave
1041 Beckett), Relax-NG compilation (William Brack), Regexp patches (with
1042 William), xmlUriEscape (Mark Vakoc), a Relax-NG notAllowed problem (with
1043 William), Relax-NG name classes compares (William), XInclude duplicate
1044 fallback (William), external DTD encoding detection (William), a DTD
1045 validation bug (William), xmlReader Close() fix, recusive extention
1046 schemas</li>
1047 <li>improvements: use xmlRead* APIs in test tools (Mark Vakoc), indenting
1048 save optimization, better handle IIS broken HTTP redirect behaviour (Ian
1049 Hummel), HTML parser frameset (James Bursa), libxml2-python RPM
1050 dependancy, XML Schemas union support (Kasimier Buchcik), warning removal
1051 clanup (William), keep ChangeLog compressed when installing from RPMs</li>
1052 <li>documentation: examples and xmlDocDumpMemory docs (John Fleck), new
Daniel Veillardd4cfcef2004-05-06 18:55:27 +00001053 example (load, xpath, modify, save), xmlCatalogDump() comments,</li>
Daniel Veillardeca726d2004-04-18 21:47:34 +00001054 <li>Windows: Borland C++ builder (Eric Zurcher), work around Microsoft
1055 compiler NaN handling bug (Mark Vakoc)</li>
1056</ul>
1057
Daniel Veillard252004d2004-03-23 12:32:32 +00001058<h3>2.6.8: Mar 23 2004</h3>
1059<ul>
1060 <li>First step of the cleanup of the serialization code and APIs</li>
1061 <li>XML Schemas: mixed content (Adam Dickmeiss), QName handling fixes (Adam
1062 Dickmeiss), anyURI for "" (John Belmonte)</li>
1063 <li>Python: Canonicalization C14N support added (Anthony Carrico)</li>
1064 <li>xmlDocCopyNode() extension (William)</li>
1065 <li>Relax-NG: fix when processing XInclude results (William), external
1066 reference in interleave (William), missing error on &lt;choice&gt;
1067 failure (William), memory leak in schemas datatype facets.</li>
1068 <li>xmlWriter: patch for better DTD support (Alfred Mickautsch)</li>
1069 <li>bug fixes: xmlXPathLangFunction memory leak (Mike Hommey and William
1070 Brack), no ID errors if using HTML_PARSE_NOERROR, xmlcatalog fallbacks to
1071 URI on SYSTEM lookup failure, XInclude parse flags inheritance (William),
1072 XInclude and XPointer fixes for entities (William), XML parser bug
1073 reported by Holger Rauch, nanohttp fd leak (William), regexps char
1074 groups '-' handling (William), dictionnary reference counting problems,
Daniel Veillardd99224d2004-04-06 10:04:16 +00001075 do not close stderr.</li>
Daniel Veillard252004d2004-03-23 12:32:32 +00001076 <li>performance patches from Petr Pajas</li>
1077 <li>Documentation fixes: XML_CATALOG_FILES in man pages (Mike Hommey)</li>
1078 <li>compilation and portability fixes: --without-valid, catalog cleanups
1079 (Peter Breitenlohner), MingW patch (Roland Schwingel), cross-compilation
1080 to Windows (Christophe de Vienne), --with-html-dir fixup (Julio Merino
1081 Vidal), Windows build (Eric Zurcher)</li>
1082</ul>
1083
Daniel Veillard92914492004-02-23 16:33:21 +00001084<h3>2.6.7: Feb 23 2004</h3>
1085<ul>
1086 <li>documentation: tutorial updates (John Fleck), benchmark results</li>
1087 <li>xmlWriter: updates and fixes (Alfred Mickautsch, Lucas Brasilino)</li>
1088 <li>XPath optimization (Petr Pajas)</li>
1089 <li>DTD ID handling optimization</li>
1090 <li>bugfixes: xpath number with &gt; 19 fractional (William Brack), push
1091 mode with unescaped '&gt;' characters, fix xmllint --stream --timing, fix
1092 xmllint --memory --stream memory usage, xmlAttrSerializeTxtContent
1093 handling NULL, trying to fix Relax-NG/Perl interface.</li>
1094 <li>python: 2.3 compatibility, whitespace fixes (Malcolm Tredinnick)</li>
1095 <li>Added relaxng option to xmllint --shell</li>
1096</ul>
1097
Daniel Veillard5c9547e2004-02-12 15:31:49 +00001098<h3>2.6.6: Feb 12 2004</h3>
1099<ul>
1100 <li>nanohttp and nanoftp: buffer overflow error on URI parsing (Igor and
1101 William) reported by Yuuichi Teranishi</li>
1102 <li>bugfixes: make test and path issues, xmlWriter attribute serialization
1103 (William Brack), xmlWriter indentation (William), schemas validation
1104 (Eric Haszlakiewicz), XInclude dictionnaries issues (William and Oleg
1105 Paraschenko), XInclude empty fallback (William), HTML warnings (William),
1106 XPointer in XInclude (William), Python namespace serialization,
1107 isolat1ToUTF8 bound error (Alfred Mickautsch), output of parameter
1108 entities in internal subset (William), internal subset bug in push mode,
1109 &lt;xs:all&gt; fix (Alexey Sarytchev)</li>
1110 <li>Build: fix for automake-1.8 (Alexander Winston), warnings removal
1111 (Philip Ludlam), SOCKLEN_T detection fixes (Daniel Richard), fix
1112 --with-minimum configuration.</li>
1113 <li>XInclude: allow the 2001 namespace without warning.</li>
1114 <li>Documentation: missing example/index.html (John Fleck), version
1115 dependancies (John Fleck)</li>
1116 <li>reader API: structured error reporting (Steve Ball)</li>
1117 <li>Windows compilation: mingw, msys (Mikhail Grushinskiy), function
1118 prototype (Cameron Johnson), MSVC6 compiler warnings, _WINSOCKAPI_
1119 patch</li>
1120 <li>Parsers: added xmlByteConsumed(ctxt) API to get the byte offest in
1121 input.</li>
1122</ul>
1123
Daniel Veillard189f46b2004-01-25 21:03:04 +00001124<h3>2.6.5: Jan 25 2004</h3>
1125<ul>
1126 <li>Bugfixes: dictionnaries for schemas (William Brack), regexp segfault
1127 (William), xs:all problem (William), a number of XPointer bugfixes
1128 (William), xmllint error go to stderr, DTD validation problem with
1129 namespace, memory leak (William), SAX1 cleanup and minimal options fixes
1130 (Mark Vadoc), parser context reset on error (Shaun McCance), XPath union
1131 evaluation problem (William) , xmlReallocLoc with NULL (Aleksey Sanin),
1132 XML Schemas double free (Steve Ball), XInclude with no href, argument
1133 callbacks order for XPath callbacks (Frederic Peters)</li>
1134 <li>Documentation: python scripts (William Brack), xslt stylesheets (John
1135 Fleck), doc (Sven Zimmerman), I/O example.</li>
1136 <li>Python bindings: fixes (William), enum support (Stéphane Bidoul),
1137 structured error reporting (Stéphane Bidoul)</li>
1138 <li>XInclude: various fixes for conformance, problem related to dictionnary
1139 references (William &amp; me), recursion (William)</li>
1140 <li>xmlWriter: indentation (Lucas Brasilino), memory leaks (Alfred
Daniel Veillard5c9547e2004-02-12 15:31:49 +00001141 Mickautsch),</li>
Daniel Veillard189f46b2004-01-25 21:03:04 +00001142 <li>xmlSchemas: normalizedString datatype (John Belmonte)</li>
1143 <li>code cleanup for strings functions (William)</li>
1144 <li>Windows: compiler patches (Mark Vakoc)</li>
1145 <li>Parser optimizations, a few new XPath and dictionnary APIs for future
1146 XSLT optimizations.</li>
1147</ul>
1148
Daniel Veillarde6e59cd2003-12-24 11:56:44 +00001149<h3>2.6.4: Dec 24 2003</h3>
1150<ul>
1151 <li>Windows build fixes (Igor Zlatkovic)</li>
Daniel Veillard189f46b2004-01-25 21:03:04 +00001152 <li>Some serious XInclude problems reported by Oleg Paraschenko and</li>
1153 <li>Unix and Makefile packaging fixes (me, William Brack,</li>
Daniel Veillarde6e59cd2003-12-24 11:56:44 +00001154 <li>Documentation improvements (John Fleck, William Brack), example fix
1155 (Lucas Brasilino)</li>
1156 <li>bugfixes: xmlTextReaderExpand() with xmlReaderWalker, XPath handling of
1157 NULL strings (William Brack) , API building reader or parser from
1158 filedescriptor should not close it, changed XPath sorting to be stable
1159 again (William Brack), xmlGetNodePath() generating '(null)' (William
1160 Brack), DTD validation and namespace bug (William Brack), XML Schemas
1161 double inclusion behaviour</li>
1162</ul>
1163
Daniel Veillardc480c4e2003-12-10 13:24:38 +00001164<h3>2.6.3: Dec 10 2003</h3>
1165<ul>
1166 <li>documentation updates and cleanup (DV, William Brack, John Fleck)</li>
1167 <li>added a repository of examples, examples from Aleksey Sanin, Dodji
Daniel Veillarde6e59cd2003-12-24 11:56:44 +00001168 Seketeli, Alfred Mickautsch</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +00001169 <li>Windows updates: Mark Vakoc, Igor Zlatkovic, Eric Zurcher, Mingw
1170 (Kenneth Haley)</li>
1171 <li>Unicode range checking (William Brack)</li>
1172 <li>code cleanup (William Brack)</li>
1173 <li>Python bindings: doc (John Fleck), bug fixes</li>
1174 <li>UTF-16 cleanup and BOM issues (William Brack)</li>
1175 <li>bug fixes: ID and xmlReader validation, XPath (William Brack),
1176 xmlWriter (Alfred Mickautsch), hash.h inclusion problem, HTML parser
1177 (James Bursa), attribute defaulting and validation, some serialization
1178 cleanups, XML_GET_LINE macro, memory debug when using threads (William
1179 Brack), serialization of attributes and entities content, xmlWriter
1180 (Daniel Schulman)</li>
1181 <li>XInclude bugfix, new APIs and update to the last version including the
1182 namespace change.</li>
1183 <li>XML Schemas improvements: include (Robert Stepanek), import and
1184 namespace handling, fixed the regression tests troubles, added examples
Daniel Veillarde6e59cd2003-12-24 11:56:44 +00001185 based on Eric van der Vlist book, regexp fixes</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +00001186 <li>preliminary pattern support for streaming (needed for schemas
1187 constraints), added xmlTextReaderPreservePattern() to collect subdocument
1188 when streaming.</li>
1189 <li>various fixes in the structured error handling</li>
1190</ul>
1191
Daniel Veillard6d373a22003-11-04 10:26:43 +00001192<h3>2.6.2: Nov 4 2003</h3>
1193<ul>
1194 <li>XPath context unregistration fixes</li>
1195 <li>text node coalescing fixes (Mark Lilback)</li>
1196 <li>API to screate a W3C Schemas from an existing document (Steve Ball)</li>
1197 <li>BeOS patches (Marcin 'Shard' Konicki)</li>
1198 <li>xmlStrVPrintf function added (Aleksey Sanin)</li>
1199 <li>compilation fixes (Mark Vakoc)</li>
1200 <li>stdin parsing fix (William Brack)</li>
1201 <li>a posteriori DTD validation fixes</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +00001202 <li>xmlReader bug fixes: Walker fixes, python bindings</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +00001203 <li>fixed xmlStopParser() to really stop the parser and errors</li>
1204 <li>always generate line numbers when using the new xmlReadxxx
1205 functions</li>
1206 <li>added XInclude support to the xmlReader interface</li>
1207 <li>implemented XML_PARSE_NONET parser option</li>
1208 <li>DocBook XSLT processing bug fixed</li>
1209 <li>HTML serialization for &lt;p&gt; elements (William Brack and me)</li>
1210 <li>XPointer failure in XInclude are now handled as resource errors</li>
1211 <li>fixed xmllint --html to use the HTML serializer on output (added
1212 --xmlout to implement the previous behaviour of saving it using the XML
1213 serializer)</li>
1214</ul>
1215
Daniel Veillarde4e3f5d2003-10-28 23:06:32 +00001216<h3>2.6.1: Oct 28 2003</h3>
1217<ul>
1218 <li>Mostly bugfixes after the big 2.6.0 changes</li>
1219 <li>Unix compilation patches: libxml.m4 (Patrick Welche), warnings cleanup
1220 (William Brack)</li>
1221 <li>Windows compilation patches (Joachim Bauch, Stephane Bidoul, Igor
1222 Zlatkovic)</li>
1223 <li>xmlWriter bugfix (Alfred Mickautsch)</li>
1224 <li>chvalid.[ch]: couple of fixes from Stephane Bidoul</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +00001225 <li>context reset: error state reset, push parser reset (Graham
1226 Bennett)</li>
Daniel Veillarde4e3f5d2003-10-28 23:06:32 +00001227 <li>context reuse: generate errors if file is not readable</li>
1228 <li>defaulted attributes for element coming from internal entities
1229 (Stephane Bidoul)</li>
1230 <li>Python: tab and spaces mix (William Brack)</li>
1231 <li>Error handler could crash in DTD validation in 2.6.0</li>
1232 <li>xmlReader: do not use the document or element _private field</li>
1233 <li>testSAX.c: avoid a problem with some PIs (Massimo Morara)</li>
1234 <li>general bug fixes: mandatory encoding in text decl, serializing
1235 Document Fragment nodes, xmlSearchNs 2.6.0 problem (Kasimier Buchcik),
1236 XPath errors not reported, slow HTML parsing of large documents.</li>
1237</ul>
1238
Daniel Veillard3e35f8e2003-10-21 00:05:38 +00001239<h3>2.6.0: Oct 20 2003</h3>
1240<ul>
1241 <li>Major revision release: should be API and ABI compatible but got a lot
1242 of change</li>
1243 <li>Increased the library modularity, far more options can be stripped out,
1244 a --with-minimum configuration will weight around 160KBytes</li>
1245 <li>Use per parser and per document dictionnary, allocate names and small
1246 text nodes from the dictionnary</li>
1247 <li>Switch to a SAX2 like parser rewrote most of the XML parser core,
1248 provides namespace resolution and defaulted attributes, minimize memory
1249 allocations and copies, namespace checking and specific error handling,
1250 immutable buffers, make predefined entities static structures, etc...</li>
1251 <li>rewrote all the error handling in the library, all errors can be
1252 intercepted at a structured level, with precise information
1253 available.</li>
1254 <li>New simpler and more generic XML and HTML parser APIs, allowing to
1255 easilly modify the parsing options and reuse parser context for multiple
1256 consecutive documents.</li>
1257 <li>Similar new APIs for the xmlReader, for options and reuse, provided new
1258 functions to access content as const strings, use them for Python
1259 bindings</li>
1260 <li>a lot of other smaller API improvements: xmlStrPrintf (Aleksey Sanin),
1261 Walker i.e. reader on a document tree based on Alfred Mickautsch code,
1262 make room in nodes for line numbers, reference counting and future PSVI
1263 extensions, generation of character ranges to be checked with faster
1264 algorithm (William), xmlParserMaxDepth (Crutcher Dunnavant), buffer
1265 access</li>
1266 <li>New xmlWriter API provided by Alfred Mickautsch</li>
1267 <li>Schemas: base64 support by Anthony Carrico</li>
1268 <li>Parser&lt;-&gt;HTTP integration fix, proper processing of the Mime-Type
1269 and charset informations if available.</li>
1270 <li>Relax-NG: bug fixes including the one reported by Martijn Faassen and
1271 zeroOrMore, better error reporting.</li>
1272 <li>Python bindings (Stéphane Bidoul), never use stdout for errors
1273 output</li>
1274 <li>Portability: all the headers have macros for export and calling
1275 convention definitions (Igor Zlatkovic), VMS update (Craig A. Berry),
1276 Windows: threads (Jesse Pelton), Borland compiler (Eric Zurcher, Igor),
1277 Mingw (Igor), typos (Mark Vakoc), beta version (Stephane Bidoul),
1278 warning cleanups on AIX and MIPS compilers (William Brack), BeOS (Marcin
1279 'Shard' Konicki)</li>
1280 <li>Documentation fixes and README (William Brack), search fix (William),
1281 tutorial updates (John Fleck), namespace docs (Stefan Kost)</li>
1282 <li>Bug fixes: xmlCleanupParser (Dave Beckett), threading uninitialized
1283 mutexes, HTML doctype lowercase, SAX/IO (William), compression detection
1284 and restore (William), attribute declaration in DTDs (William), namespace
1285 on attribute in HTML output (William), input filename (Rob Richards),
1286 namespace DTD validation, xmlReplaceNode (Chris Ryland), I/O callbacks
1287 (Markus Keim), CDATA serialization (Shaun McCance), xmlReader (Peter
1288 Derr), high codepoint charref like &amp;#x10FFFF;, buffer access in push
1289 mode (Justin Fletcher), TLS threads on Windows (Jesse Pelton), XPath bug
1290 (William), xmlCleanupParser (Marc Liyanage), CDATA output (William), HTTP
1291 error handling.</li>
1292 <li>xmllint options: --dtdvalidfpi for Tobias Reif, --sax1 for compat
1293 testing, --nodict for building without tree dictionnary, --nocdata to
1294 replace CDATA by text, --nsclean to remove surperfluous namespace
1295 declarations</li>
1296 <li>added xml2-config --libtool-libs option from Kevin P. Fleming</li>
1297 <li>a lot of profiling and tuning of the code, speedup patch for
1298 xmlSearchNs() by Luca Padovani. The xmlReader should do far less
1299 allocation and it speed should get closer to SAX. Chris Anderson worked
1300 on speeding and cleaning up repetitive checking code.</li>
1301 <li>cleanup of "make tests"</li>
1302 <li>libxml-2.0-uninstalled.pc from Malcolm Tredinnick</li>
1303 <li>deactivated the broken docBook SGML parser code and plugged the XML
1304 parser instead.</li>
1305</ul>
1306
Daniel Veillardeec1ae92003-09-09 13:11:01 +00001307<h3>2.5.11: Sep 9 2003</h3>
1308
1309<p>A bugfix only release:</p>
1310<ul>
1311 <li>risk of crash in Relax-NG</li>
1312 <li>risk of crash when using multithreaded programs</li>
1313</ul>
1314
Daniel Veillardcfba2fe2003-08-15 00:33:43 +00001315<h3>2.5.10: Aug 15 2003</h3>
1316
1317<p>A bugfixes only release</p>
1318<ul>
1319 <li>Windows Makefiles (William Brack)</li>
1320 <li>UTF-16 support fixes (Mark Itzcovitz)</li>
1321 <li>Makefile and portability (William Brack) automake, Linux alpha, Mingw
Daniel Veillardeec1ae92003-09-09 13:11:01 +00001322 on Windows (Mikhail Grushinskiy)</li>
Daniel Veillardcfba2fe2003-08-15 00:33:43 +00001323 <li>HTML parser (Oliver Stoeneberg)</li>
1324 <li>XInclude performance problem reported by Kevin Ruscoe</li>
1325 <li>XML parser performance problem reported by Grant Goodale</li>
1326 <li>xmlSAXParseDTD() bug fix from Malcolm Tredinnick</li>
Daniel Veillardeec1ae92003-09-09 13:11:01 +00001327 <li>and a couple other cleanup</li>
Daniel Veillardcfba2fe2003-08-15 00:33:43 +00001328</ul>
1329
Daniel Veillard83ee40d2003-08-09 22:24:09 +00001330<h3>2.5.9: Aug 9 2003</h3>
1331<ul>
1332 <li>bugfixes: IPv6 portability, xmlHasNsProp (Markus Keim), Windows build
1333 (Wiliam Brake, Jesse Pelton, Igor), Schemas (Peter Sobisch), threading
1334 (Rob Richards), hexBinary type (), UTF-16 BOM (Dodji Seketeli),
1335 xmlReader, Relax-NG schemas compilation, namespace handling, EXSLT (Sean
1336 Griffin), HTML parsing problem (William Brack), DTD validation for mixed
1337 content + namespaces, HTML serialization, library initialization,
1338 progressive HTML parser</li>
1339 <li>better interfaces for Relax-NG error handling (Joachim Bauch, )</li>
1340 <li>adding xmlXIncludeProcessTree() for XInclud'ing in a subtree</li>
1341 <li>doc fixes and improvements (John Fleck)</li>
1342 <li>configure flag for -with-fexceptions when embedding in C++</li>
1343 <li>couple of new UTF-8 helper functions (William Brack)</li>
1344 <li>general encoding cleanup + ISO-8859-x without iconv (Peter Jacobi)</li>
1345 <li>xmlTextReader cleanup + enum for node types (Bjorn Reese)</li>
1346 <li>general compilation/warning cleanup Solaris/HP-UX/... (William
1347 Brack)</li>
1348</ul>
1349
Daniel Veillard560c2a42003-07-06 21:13:49 +00001350<h3>2.5.8: Jul 6 2003</h3>
1351<ul>
1352 <li>bugfixes: XPath, XInclude, file/URI mapping, UTF-16 save (Mark
1353 Itzcovitz), UTF-8 checking, URI saving, error printing (William Brack),
1354 PI related memleak, compilation without schemas or without xpath (Joerg
1355 Schmitz-Linneweber/Garry Pennington), xmlUnlinkNode problem with DTDs,
1356 rpm problem on , i86_64, removed a few compilation problems from 2.5.7,
1357 xmlIOParseDTD, and xmlSAXParseDTD (Malcolm Tredinnick)</li>
1358 <li>portability: DJGPP (MsDos) , OpenVMS (Craig A. Berry)</li>
1359 <li>William Brack fixed multithreading lock problems</li>
1360 <li>IPv6 patch for FTP and HTTP accesses (Archana Shah/Wipro)</li>
1361 <li>Windows fixes (Igor Zlatkovic, Eric Zurcher), threading (Stéphane
1362 Bidoul)</li>
1363 <li>A few W3C Schemas Structure improvements</li>
1364 <li>W3C Schemas Datatype improvements (Charlie Bozeman)</li>
1365 <li>Python bindings for thread globals (Stéphane Bidoul), and method/class
Daniel Veillard83ee40d2003-08-09 22:24:09 +00001366 generator</li>
1367 <li>added --nonet option to xmllint</li>
Daniel Veillard560c2a42003-07-06 21:13:49 +00001368 <li>documentation improvements (John Fleck)</li>
1369</ul>
1370
Daniel Veillard92fc02c2003-04-24 23:12:35 +00001371<h3>2.5.7: Apr 25 2003</h3>
1372<ul>
1373 <li>Relax-NG: Compiling to regexp and streaming validation on top of the
1374 xmlReader interface, added to xmllint --stream</li>
1375 <li>xmlReader: Expand(), Next() and DOM access glue, bug fixes</li>
1376 <li>Support for large files: RGN validated a 4.5GB instance</li>
1377 <li>Thread support is now configured in by default</li>
1378 <li>Fixes: update of the Trio code (Bjorn), WXS Date and Duration fixes
1379 (Charles Bozeman), DTD and namespaces (Brent Hendricks), HTML push parser
1380 and zero bytes handling, some missing Windows file path conversions,
1381 behaviour of the parser and validator in the presence of "out of memory"
Daniel Veillard93d95252003-04-29 20:25:40 +00001382 error conditions</li>
Daniel Veillard92fc02c2003-04-24 23:12:35 +00001383 <li>extended the API to be able to plug a garbage collecting memory
1384 allocator, added xmlMallocAtomic() and modified the allocations
1385 accordingly.</li>
1386 <li>Performances: removed excessive malloc() calls, speedup of the push and
1387 xmlReader interfaces, removed excessive thread locking</li>
1388 <li>Documentation: man page (John Fleck), xmlReader documentation</li>
1389 <li>Python: adding binding for xmlCatalogAddLocal (Brent M Hendricks)</li>
1390</ul>
1391
Daniel Veillardc2d4a932003-04-01 11:13:05 +00001392<h3>2.5.6: Apr 1 2003</h3>
1393<ul>
1394 <li>Fixed W3C XML Schemas datatype, should be compliant now except for
1395 binHex and base64 which are not supported yet.</li>
1396 <li>bug fixes: non-ASCII IDs, HTML output, XInclude on large docs and
1397 XInclude entities handling, encoding detection on external subsets, XML
1398 Schemas bugs and memory leaks, HTML parser (James Bursa)</li>
1399 <li>portability: python/trio (Albert Chin), Sun compiler warnings</li>
1400 <li>documentation: added --relaxng option to xmllint man page (John)</li>
1401 <li>improved error reporting: xml:space, start/end tag mismatches, Relax NG
1402 errors</li>
1403</ul>
1404
1405<h3>2.5.5: Mar 24 2003</h3>
Daniel Veillardd8da01c2003-03-24 15:58:23 +00001406<ul>
1407 <li>Lot of fixes on the Relax NG implementation. More testing including
1408 DocBook and TEI examples.</li>
1409 <li>Increased the support for W3C XML Schemas datatype</li>
1410 <li>Several bug fixes in the URI handling layer</li>
1411 <li>Bug fixes: HTML parser, xmlReader, DTD validation, XPath, encoding
1412 conversion, line counting in the parser.</li>
1413 <li>Added support for $XMLLINT_INDENT environment variable, FTP delete</li>
1414 <li>Fixed the RPM spec file name</li>
1415</ul>
1416
Daniel Veillard17bed982003-02-24 20:11:43 +00001417<h3>2.5.4: Feb 20 2003</h3>
1418<ul>
1419 <li>Conformance testing and lot of fixes on Relax NG and XInclude
1420 implementation</li>
1421 <li>Implementation of XPointer element() scheme</li>
1422 <li>Bug fixes: XML parser, XInclude entities merge, validity checking on
1423 namespaces,
1424 <p>2 serialization bugs, node info generation problems, a DTD regexp
1425 generation problem.</p>
1426 </li>
1427 <li>Portability: windows updates and path canonicalization (Igor)</li>
1428 <li>A few typo fixes (Kjartan Maraas)</li>
1429 <li>Python bindings generator fixes (Stephane Bidoul)</li>
1430</ul>
1431
Daniel Veillard1d788d22003-02-10 16:21:58 +00001432<h3>2.5.3: Feb 10 2003</h3>
1433<ul>
1434 <li>RelaxNG and XML Schemas datatypes improvements, and added a first
1435 version of RelaxNG Python bindings</li>
1436 <li>Fixes: XLink (Sean Chittenden), XInclude (Sean Chittenden), API fix for
1437 serializing namespace nodes, encoding conversion bug, XHTML1
1438 serialization</li>
1439 <li>Portability fixes: Windows (Igor), AMD 64bits RPM spec file</li>
1440</ul>
1441
Daniel Veillard72fef162003-02-05 14:31:19 +00001442<h3>2.5.2: Feb 5 2003</h3>
1443<ul>
1444 <li>First implementation of RelaxNG, added --relaxng flag to xmllint</li>
1445 <li>Schemas support now compiled in by default.</li>
1446 <li>Bug fixes: DTD validation, namespace checking, XInclude and entities,
1447 delegateURI in XML Catalogs, HTML parser, XML reader (Stéphane Bidoul),
1448 XPath parser and evaluation, UTF8ToUTF8 serialization, XML reader memory
1449 consumption, HTML parser, HTML serialization in the presence of
1450 namespaces</li>
1451 <li>added an HTML API to check elements and attributes.</li>
1452 <li>Documentation improvement, PDF for the tutorial (John Fleck), doc
1453 patches (Stefan Kost)</li>
1454 <li>Portability fixes: NetBSD (Julio Merino), Windows (Igor Zlatkovic)</li>
1455 <li>Added python bindings for XPointer, contextual error reporting
1456 (Stéphane Bidoul)</li>
1457 <li>URI/file escaping problems (Stefano Zacchiroli)</li>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +00001458</ul>
1459
Daniel Veillarde2830f12003-01-08 17:47:49 +00001460<h3>2.5.1: Jan 8 2003</h3>
1461<ul>
1462 <li>Fixes a memory leak and configuration/compilation problems in 2.5.0</li>
1463 <li>documentation updates (John)</li>
1464 <li>a couple of XmlTextReader fixes</li>
1465</ul>
1466
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00001467<h3>2.5.0: Jan 6 2003</h3>
1468<ul>
1469 <li>New <a href="xmlreader.html">XmltextReader interface</a> based on C#
1470 API (with help of Stéphane Bidoul)</li>
1471 <li>Windows: more exports, including the new API (Igor)</li>
1472 <li>XInclude fallback fix</li>
1473 <li>Python: bindings for the new API, packaging (Stéphane Bidoul),
1474 drv_libxml2.py Python xml.sax driver (Stéphane Bidoul), fixes, speedup
1475 and iterators for Python-2.2 (Hannu Krosing)</li>
1476 <li>Tutorial fixes (john Fleck and Niraj Tolia) xmllint man update
1477 (John)</li>
1478 <li>Fix an XML parser bug raised by Vyacheslav Pindyura</li>
1479 <li>Fix for VMS serialization (Nigel Hall) and config (Craig A. Berry)</li>
1480 <li>Entities handling fixes</li>
1481 <li>new API to optionally track node creation and deletion (Lukas
1482 Schroeder)</li>
1483 <li>Added documentation for the XmltextReader interface and some <a
1484 href="guidelines.html">XML guidelines</a></li>
1485</ul>
1486
Daniel Veillardc1eed322002-12-12 11:01:32 +00001487<h3>2.4.30: Dec 12 2002</h3>
1488<ul>
1489 <li>2.4.29 broke the python bindings, rereleasing</li>
1490 <li>Improvement/fixes of the XML API generator, and couple of minor code
1491 fixes.</li>
1492</ul>
1493
Daniel Veillard9b4bb4d2002-12-11 19:28:47 +00001494<h3>2.4.29: Dec 11 2002</h3>
1495<ul>
1496 <li>Windows fixes (Igor): Windows CE port, pthread linking, python bindings
1497 (Stéphane Bidoul), Mingw (Magnus Henoch), and export list updates</li>
1498 <li>Fix for prev in python bindings (ERDI Gergo)</li>
1499 <li>Fix for entities handling (Marcus Clarke)</li>
1500 <li>Refactored the XML and HTML dumps to a single code path, fixed XHTML1
1501 dump</li>
1502 <li>Fix for URI parsing when handling URNs with fragment identifiers</li>
1503 <li>Fix for HTTP URL escaping problem</li>
1504 <li>added an TextXmlReader (C#) like API (work in progress)</li>
1505 <li>Rewrote the API in XML generation script, includes a C parser and saves
1506 more informations needed for C# bindings</li>
1507</ul>
1508
Daniel Veillardf9c4cad2002-11-22 15:57:07 +00001509<h3>2.4.28: Nov 22 2002</h3>
1510<ul>
1511 <li>a couple of python binding fixes</li>
1512 <li>2 bug fixes in the XML push parser</li>
1513 <li>potential memory leak removed (Martin Stoilov)</li>
1514 <li>fix to the configure script for Unix (Dimitri Papadopoulos)</li>
1515 <li>added encoding support for XInclude parse="text"</li>
1516 <li>autodetection of XHTML1 and specific serialization rules added</li>
Daniel Veillard9b4bb4d2002-12-11 19:28:47 +00001517 <li>nasty threading bug fixed (William Brack)</li>
Daniel Veillardf9c4cad2002-11-22 15:57:07 +00001518</ul>
1519
Daniel Veillarddad3f682002-11-17 16:47:27 +00001520<h3>2.4.27: Nov 17 2002</h3>
1521<ul>
1522 <li>fixes for the Python bindings</li>
1523 <li>a number of bug fixes: SGML catalogs, xmlParseBalancedChunkMemory(),
1524 HTML parser, Schemas (Charles Bozeman), document fragment support
1525 (Christian Glahn), xmlReconciliateNs (Brian Stafford), XPointer,
1526 xmlFreeNode(), xmlSAXParseMemory (Peter Jones), xmlGetNodePath (Petr
1527 Pajas), entities processing</li>
1528 <li>added grep to xmllint --shell</li>
1529 <li>VMS update patch from Craig A. Berry</li>
1530 <li>cleanup of the Windows build with support for more compilers (Igor),
1531 better thread support on Windows</li>
1532 <li>cleanup of Unix Makefiles and spec file</li>
1533 <li>Improvements to the documentation (John Fleck)</li>
1534</ul>
1535
Daniel Veillard48267432002-10-18 11:21:38 +00001536<h3>2.4.26: Oct 18 2002</h3>
1537<ul>
1538 <li>Patches for Windows CE port, improvements on Windows paths handling</li>
1539 <li>Fixes to the validation code (DTD and Schemas), xmlNodeGetPath() ,
1540 HTML serialization, Namespace compliance, and a number of small
1541 problems</li>
1542</ul>
1543
Daniel Veillarde16b5742002-09-26 17:50:03 +00001544<h3>2.4.25: Sep 26 2002</h3>
1545<ul>
1546 <li>A number of bug fixes: XPath, validation, Python bindings, DOM and
1547 tree, xmlI/O, Html</li>
1548 <li>Serious rewrite of XInclude</li>
1549 <li>Made XML Schemas regexp part of the default build and APIs, small fix
1550 and improvement of the regexp core</li>
1551 <li>Changed the validation code to reuse XML Schemas regexp APIs</li>
1552 <li>Better handling of Windows file paths, improvement of Makefiles (Igor,
1553 Daniel Gehriger, Mark Vakoc)</li>
1554 <li>Improved the python I/O bindings, the tests, added resolver and regexp
Daniel Veillard321be0c2002-10-08 21:26:42 +00001555 APIs</li>
Daniel Veillarde16b5742002-09-26 17:50:03 +00001556 <li>New logos from Marc Liyanage</li>
1557 <li>Tutorial improvements: John Fleck, Christopher Harris</li>
1558 <li>Makefile: Fixes for AMD x86_64 (Mandrake), DESTDIR (Christophe
1559 Merlet)</li>
1560 <li>removal of all stderr/perror use for error reporting</li>
1561 <li>Better error reporting: XPath and DTD validation</li>
1562 <li>update of the trio portability layer (Bjorn Reese)</li>
1563</ul>
1564
Daniel Veillard42766c02002-08-22 20:52:17 +00001565<p><strong>2.4.24: Aug 22 2002</strong></p>
1566<ul>
1567 <li>XPath fixes (William), xf:escape-uri() (Wesley Terpstra)</li>
1568 <li>Python binding fixes: makefiles (William), generator, rpm build, x86-64
1569 (fcrozat)</li>
1570 <li>HTML &lt;style&gt; and boolean attributes serializer fixes</li>
1571 <li>C14N improvements by Aleksey</li>
Daniel Veillarde1662542002-08-28 11:50:59 +00001572 <li>doc cleanups: Rick Jones</li>
Daniel Veillard42766c02002-08-22 20:52:17 +00001573 <li>Windows compiler makefile updates: Igor and Elizabeth Barham</li>
1574 <li>XInclude: implementation of fallback and xml:base fixup added</li>
1575</ul>
1576
Daniel Veillard782afda2002-07-08 15:12:49 +00001577<h3>2.4.23: July 6 2002</h3>
1578<ul>
1579 <li>performances patches: Peter Jacobi</li>
1580 <li>c14n fixes, testsuite and performances: Aleksey Sanin</li>
1581 <li>added xmlDocFormatDump: Chema Celorio</li>
1582 <li>new tutorial: John Fleck</li>
1583 <li>new hash functions and performances: Sander Vesik, portability fix from
1584 Peter Jacobi</li>
1585 <li>a number of bug fixes: XPath (William Brack, Richard Jinks), XML and
1586 HTML parsers, ID lookup function</li>
1587 <li>removal of all remaining sprintf: Aleksey Sanin</li>
1588</ul>
1589
Daniel Veillardc0801af2002-05-28 16:28:42 +00001590<h3>2.4.22: May 27 2002</h3>
1591<ul>
1592 <li>a number of bug fixes: configure scripts, base handling, parser, memory
1593 usage, HTML parser, XPath, documentation (Christian Cornelssen),
Daniel Veillard21473672002-06-17 07:29:22 +00001594 indentation, URI parsing</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00001595 <li>Optimizations for XMLSec, fixing and making public some of the network
1596 protocol handlers (Aleksey)</li>
1597 <li>performance patch from Gary Pennington</li>
1598 <li>Charles Bozeman provided date and time support for XML Schemas
1599 datatypes</li>
1600</ul>
1601
Daniel Veillardcf27f7c2002-04-30 07:12:39 +00001602<h3>2.4.21: Apr 29 2002</h3>
1603
1604<p>This release is both a bug fix release and also contains the early XML
1605Schemas <a href="http://www.w3.org/TR/xmlschema-1/">structures</a> and <a
1606href="http://www.w3.org/TR/xmlschema-2/">datatypes</a> code, beware, all
1607interfaces are likely to change, there is huge holes, it is clearly a work in
1608progress and don't even think of putting this code in a production system,
Daniel Veillarde6d8e202002-05-02 06:11:10 +00001609it's actually not compiled in by default. The real fixes are:</p>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +00001610<ul>
1611 <li>a couple of bugs or limitations introduced in 2.4.20</li>
1612 <li>patches for Borland C++ and MSC by Igor</li>
1613 <li>some fixes on XPath strings and conformance patches by Richard
1614 Jinks</li>
1615 <li>patch from Aleksey for the ExcC14N specification</li>
1616 <li>OSF/1 bug fix by Bjorn</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00001617</ul>
1618
Daniel Veillarda7084cd2002-04-15 17:12:47 +00001619<h3>2.4.20: Apr 15 2002</h3>
1620<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00001621 <li>bug fixes: file descriptor leak, XPath, HTML output, DTD validation</li>
Daniel Veillarda7084cd2002-04-15 17:12:47 +00001622 <li>XPath conformance testing by Richard Jinks</li>
1623 <li>Portability fixes: Solaris, MPE/iX, Windows, OSF/1, python bindings,
1624 libxml.m4</li>
1625</ul>
1626
Daniel Veillard19274092002-03-25 16:48:03 +00001627<h3>2.4.19: Mar 25 2002</h3>
1628<ul>
1629 <li>bug fixes: half a dozen XPath bugs, Validation, ISO-Latin to UTF8
1630 encoder</li>
1631 <li>portability fixes in the HTTP code</li>
Daniel Veillardb2fb8ed2002-04-01 09:33:12 +00001632 <li>memory allocation checks using valgrind, and profiling tests</li>
Daniel Veillard19274092002-03-25 16:48:03 +00001633 <li>revamp of the Windows build and Makefiles</li>
1634</ul>
1635
Daniel Veillard34ce8be2002-03-18 19:37:11 +00001636<h3>2.4.18: Mar 18 2002</h3>
1637<ul>
1638 <li>bug fixes: tree, SAX, canonicalization, validation, portability,
Daniel Veillard63d83142002-05-20 06:51:05 +00001639 XPath</li>
Daniel Veillard34ce8be2002-03-18 19:37:11 +00001640 <li>removed the --with-buffer option it was becoming unmaintainable</li>
1641 <li>serious cleanup of the Python makefiles</li>
1642 <li>speedup patch to XPath very effective for DocBook stylesheets</li>
1643 <li>Fixes for Windows build, cleanup of the documentation</li>
1644</ul>
1645
Daniel Veillardaf43f632002-03-08 15:05:20 +00001646<h3>2.4.17: Mar 8 2002</h3>
1647<ul>
1648 <li>a lot of bug fixes, including "namespace nodes have no parents in
1649 XPath"</li>
1650 <li>fixed/improved the Python wrappers, added more examples and more
1651 regression tests, XPath extension functions can now return node-sets</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001652 <li>added the XML Canonicalization support from Aleksey Sanin</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001653</ul>
1654
Daniel Veillard5f4b5992002-02-20 10:22:49 +00001655<h3>2.4.16: Feb 20 2002</h3>
1656<ul>
1657 <li>a lot of bug fixes, most of them were triggered by the XML Testsuite
1658 from OASIS and W3C. Compliance has been significantly improved.</li>
1659 <li>a couple of portability fixes too.</li>
1660</ul>
1661
Daniel Veillard397ff112002-02-11 18:27:20 +00001662<h3>2.4.15: Feb 11 2002</h3>
1663<ul>
1664 <li>Fixed the Makefiles, especially the python module ones</li>
1665 <li>A few bug fixes and cleanup</li>
1666 <li>Includes cleanup</li>
1667</ul>
1668
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +00001669<h3>2.4.14: Feb 8 2002</h3>
1670<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00001671 <li>Change of License to the <a
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +00001672 href="http://www.opensource.org/licenses/mit-license.html">MIT
Daniel Veillard63d83142002-05-20 06:51:05 +00001673 License</a> basically for integration in XFree86 codebase, and removing
1674 confusion around the previous dual-licensing</li>
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +00001675 <li>added Python bindings, beta software but should already be quite
1676 complete</li>
1677 <li>a large number of fixes and cleanups, especially for all tree
1678 manipulations</li>
1679 <li>cleanup of the headers, generation of a reference API definition in
1680 XML</li>
1681</ul>
1682
1683<h3>2.4.13: Jan 14 2002</h3>
Daniel Veillard744683d2002-01-14 17:30:20 +00001684<ul>
1685 <li>update of the documentation: John Fleck and Charlie Bozeman</li>
1686 <li>cleanup of timing code from Justin Fletcher</li>
1687 <li>fixes for Windows and initial thread support on Win32: Igor and Serguei
1688 Narojnyi</li>
1689 <li>Cygwin patch from Robert Collins</li>
1690 <li>added xmlSetEntityReferenceFunc() for Keith Isdale work on xsldbg</li>
1691</ul>
1692
Daniel Veillardef90ba72001-12-07 14:24:22 +00001693<h3>2.4.12: Dec 7 2001</h3>
1694<ul>
1695 <li>a few bug fixes: thread (Gary Pennington), xmllint (Geert Kloosterman),
1696 XML parser (Robin Berjon), XPointer (Danny Jamshy), I/O cleanups
1697 (robert)</li>
1698 <li>Eric Lavigne contributed project files for MacOS</li>
1699 <li>some makefiles cleanups</li>
1700</ul>
1701
Daniel Veillarda4871052001-11-26 13:19:48 +00001702<h3>2.4.11: Nov 26 2001</h3>
1703<ul>
1704 <li>fixed a couple of errors in the includes, fixed a few bugs, some code
1705 cleanups</li>
1706 <li>xmllint man pages improvement by Heiko Rupp</li>
1707 <li>updated VMS build instructions from John A Fotheringham</li>
1708 <li>Windows Makefiles updates from Igor</li>
1709</ul>
1710
Daniel Veillard43d3f612001-11-10 11:57:23 +00001711<h3>2.4.10: Nov 10 2001</h3>
1712<ul>
1713 <li>URI escaping fix (Joel Young)</li>
1714 <li>added xmlGetNodePath() (for paths or XPointers generation)</li>
1715 <li>Fixes namespace handling problems when using DTD and validation</li>
1716 <li>improvements on xmllint: Morus Walter patches for --format and
1717 --encode, Stefan Kost and Heiko Rupp improvements on the --shell</li>
1718 <li>fixes for xmlcatalog linking pointed by Weiqi Gao</li>
1719 <li>fixes to the HTML parser</li>
1720</ul>
1721
1722<h3>2.4.9: Nov 6 2001</h3>
1723<ul>
1724 <li>fixes more catalog bugs</li>
1725 <li>avoid a compilation problem, improve xmlGetLineNo()</li>
1726</ul>
1727
Daniel Veillarded421aa2001-11-04 21:22:45 +00001728<h3>2.4.8: Nov 4 2001</h3>
1729<ul>
1730 <li>fixed SGML catalogs broken in previous release, updated xmlcatalog
1731 tool</li>
1732 <li>fixed a compile errors and some includes troubles.</li>
1733</ul>
1734
Daniel Veillard52dcab32001-10-30 12:51:17 +00001735<h3>2.4.7: Oct 30 2001</h3>
1736<ul>
1737 <li>exported some debugging interfaces</li>
1738 <li>serious rewrite of the catalog code</li>
1739 <li>integrated Gary Pennington thread safety patch, added configure option
1740 and regression tests</li>
1741 <li>removed an HTML parser bug</li>
1742 <li>fixed a couple of potentially serious validation bugs</li>
1743 <li>integrated the SGML DocBook support in xmllint</li>
1744 <li>changed the nanoftp anonymous login passwd</li>
1745 <li>some I/O cleanup and a couple of interfaces for Perl wrapper</li>
1746 <li>general bug fixes</li>
1747 <li>updated xmllint man page by John Fleck</li>
1748 <li>some VMS and Windows updates</li>
1749</ul>
1750
Daniel Veillard60087f32001-10-10 09:45:09 +00001751<h3>2.4.6: Oct 10 2001</h3>
1752<ul>
Daniel Veillard52dcab32001-10-30 12:51:17 +00001753 <li>added an updated man pages by John Fleck</li>
Daniel Veillard60087f32001-10-10 09:45:09 +00001754 <li>portability and configure fixes</li>
1755 <li>an infinite loop on the HTML parser was removed (William)</li>
1756 <li>Windows makefile patches from Igor</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001757 <li>fixed half a dozen bugs reported for libxml or libxslt</li>
Daniel Veillard60087f32001-10-10 09:45:09 +00001758 <li>updated xmlcatalog to be able to modify SGML super catalogs</li>
1759</ul>
1760
Daniel Veillarddadd0872001-09-15 09:21:44 +00001761<h3>2.4.5: Sep 14 2001</h3>
1762<ul>
1763 <li>Remove a few annoying bugs in 2.4.4</li>
1764 <li>forces the HTML serializer to output decimal charrefs since some
1765 version of Netscape can't handle hexadecimal ones</li>
1766</ul>
1767
1768<h3>1.8.16: Sep 14 2001</h3>
1769<ul>
1770 <li>maintenance release of the old libxml1 branch, couple of bug and
1771 portability fixes</li>
1772</ul>
1773
Daniel Veillard04382ae2001-09-12 18:51:30 +00001774<h3>2.4.4: Sep 12 2001</h3>
1775<ul>
1776 <li>added --convert to xmlcatalog, bug fixes and cleanups of XML
1777 Catalog</li>
1778 <li>a few bug fixes and some portability changes</li>
1779 <li>some documentation cleanups</li>
1780</ul>
1781
Daniel Veillard39936902001-08-24 00:49:01 +00001782<h3>2.4.3: Aug 23 2001</h3>
1783<ul>
1784 <li>XML Catalog support see the doc</li>
1785 <li>New NaN/Infinity floating point code</li>
1786 <li>A few bug fixes</li>
1787</ul>
1788
1789<h3>2.4.2: Aug 15 2001</h3>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001790<ul>
1791 <li>adds xmlLineNumbersDefault() to control line number generation</li>
1792 <li>lot of bug fixes</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001793 <li>the Microsoft MSC projects files should now be up to date</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001794 <li>inheritance of namespaces from DTD defaulted attributes</li>
1795 <li>fixes a serious potential security bug</li>
1796 <li>added a --format option to xmllint</li>
1797</ul>
1798
1799<h3>2.4.1: July 24 2001</h3>
1800<ul>
1801 <li>possibility to keep line numbers in the tree</li>
1802 <li>some computation NaN fixes</li>
1803 <li>extension of the XPath API</li>
1804 <li>cleanup for alpha and ia64 targets</li>
1805 <li>patch to allow saving through HTTP PUT or POST</li>
Daniel Veillard09ab7e12001-07-10 15:49:44 +00001806</ul>
1807
1808<h3>2.4.0: July 10 2001</h3>
1809<ul>
1810 <li>Fixed a few bugs in XPath, validation, and tree handling.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001811 <li>Fixed XML Base implementation, added a couple of examples to the
Daniel Veillard09ab7e12001-07-10 15:49:44 +00001812 regression tests</li>
1813 <li>A bit of cleanup</li>
Daniel Veillardab8500d2000-10-15 21:06:19 +00001814</ul>
1815
Daniel Veillard5b43fde2001-07-05 23:31:40 +00001816<h3>2.3.14: July 5 2001</h3>
1817<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00001818 <li>fixed some entities problems and reduce memory requirement when
1819 substituting them</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +00001820 <li>lots of improvements in the XPath queries interpreter can be
Daniel Veillard63d83142002-05-20 06:51:05 +00001821 substantially faster</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +00001822 <li>Makefiles and configure cleanups</li>
1823 <li>Fixes to XPath variable eval, and compare on empty node set</li>
1824 <li>HTML tag closing bug fixed</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001825 <li>Fixed an URI reference computation problem when validating</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +00001826</ul>
1827
Daniel Veillard2adbb512001-06-28 16:20:36 +00001828<h3>2.3.13: June 28 2001</h3>
1829<ul>
1830 <li>2.3.12 configure.in was broken as well as the push mode XML parser</li>
1831 <li>a few more fixes for compilation on Windows MSC by Yon Derek</li>
1832</ul>
1833
1834<h3>1.8.14: June 28 2001</h3>
1835<ul>
1836 <li>Zbigniew Chyla gave a patch to use the old XML parser in push mode</li>
1837 <li>Small Makefile fix</li>
1838</ul>
1839
Daniel Veillard11648102001-06-26 16:08:24 +00001840<h3>2.3.12: June 26 2001</h3>
1841<ul>
1842 <li>lots of cleanup</li>
1843 <li>a couple of validation fix</li>
1844 <li>fixed line number counting</li>
1845 <li>fixed serious problems in the XInclude processing</li>
1846 <li>added support for UTF8 BOM at beginning of entities</li>
1847 <li>fixed a strange gcc optimizer bugs in xpath handling of float, gcc-3.0
1848 miscompile uri.c (William), Thomas Leitner provided a fix for the
1849 optimizer on Tru64</li>
1850 <li>incorporated Yon Derek and Igor Zlatkovic fixes and improvements for
1851 compilation on Windows MSC</li>
1852 <li>update of libxml-doc.el (Felix Natter)</li>
1853 <li>fixed 2 bugs in URI normalization code</li>
1854</ul>
1855
Daniel Veillarde3c81b52001-06-17 14:50:34 +00001856<h3>2.3.11: June 17 2001</h3>
1857<ul>
1858 <li>updates to trio, Makefiles and configure should fix some portability
1859 problems (alpha)</li>
1860 <li>fixed some HTML serialization problems (pre, script, and block/inline
1861 handling), added encoding aware APIs, cleanup of this code</li>
1862 <li>added xmlHasNsProp()</li>
1863 <li>implemented a specific PI for encoding support in the DocBook SGML
1864 parser</li>
1865 <li>some XPath fixes (-Infinity, / as a function parameter and namespaces
1866 node selection)</li>
1867 <li>fixed a performance problem and an error in the validation code</li>
1868 <li>fixed XInclude routine to implement the recursive behaviour</li>
1869 <li>fixed xmlFreeNode problem when libxml is included statically twice</li>
1870 <li>added --version to xmllint for bug reports</li>
1871</ul>
1872
Daniel Veillard2e4f1882001-06-01 10:11:57 +00001873<h3>2.3.10: June 1 2001</h3>
1874<ul>
1875 <li>fixed the SGML catalog support</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001876 <li>a number of reported bugs got fixed, in XPath, iconv detection,
1877 XInclude processing</li>
Daniel Veillard2e4f1882001-06-01 10:11:57 +00001878 <li>XPath string function should now handle unicode correctly</li>
1879</ul>
1880
Daniel Veillard4623acd2001-05-19 15:13:15 +00001881<h3>2.3.9: May 19 2001</h3>
1882
1883<p>Lots of bugfixes, and added a basic SGML catalog support:</p>
1884<ul>
1885 <li>HTML push bugfix #54891 and another patch from Jonas Borgström</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001886 <li>some serious speed optimization again</li>
Daniel Veillard4623acd2001-05-19 15:13:15 +00001887 <li>some documentation cleanups</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001888 <li>trying to get better linking on Solaris (-R)</li>
Daniel Veillard4623acd2001-05-19 15:13:15 +00001889 <li>XPath API cleanup from Thomas Broyer</li>
1890 <li>Validation bug fixed #54631, added a patch from Gary Pennington, fixed
1891 xmlValidGetValidElements()</li>
1892 <li>Added an INSTALL file</li>
1893 <li>Attribute removal added to API: #54433</li>
1894 <li>added a basic support for SGML catalogs</li>
1895 <li>fixed xmlKeepBlanksDefault(0) API</li>
1896 <li>bugfix in xmlNodeGetLang()</li>
1897 <li>fixed a small configure portability problem</li>
1898 <li>fixed an inversion of SYSTEM and PUBLIC identifier in HTML document</li>
1899</ul>
1900
Daniel Veillarda265af72001-05-14 11:13:58 +00001901<h3>1.8.13: May 14 2001</h3>
1902<ul>
1903 <li>bugfixes release of the old libxml1 branch used by Gnome</li>
1904</ul>
1905
Daniel Veillard3bbbe6f2001-05-03 11:15:37 +00001906<h3>2.3.8: May 3 2001</h3>
1907<ul>
1908 <li>Integrated an SGML DocBook parser for the Gnome project</li>
1909 <li>Fixed a few things in the HTML parser</li>
1910 <li>Fixed some XPath bugs raised by XSLT use, tried to fix the floating
1911 point portability issue</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001912 <li>Speed improvement (8M/s for SAX, 3M/s for DOM, 1.5M/s for
1913 DOM+validation using the XML REC as input and a 700MHz celeron).</li>
Daniel Veillard3bbbe6f2001-05-03 11:15:37 +00001914 <li>incorporated more Windows cleanup</li>
1915 <li>added xmlSaveFormatFile()</li>
1916 <li>fixed problems in copying nodes with entities references (gdome)</li>
1917 <li>removed some troubles surrounding the new validation module</li>
1918</ul>
1919
Daniel Veillarda41123c2001-04-22 19:31:20 +00001920<h3>2.3.7: April 22 2001</h3>
1921<ul>
1922 <li>lots of small bug fixes, corrected XPointer</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001923 <li>Non deterministic content model validation support</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +00001924 <li>added xmlDocCopyNode for gdome2</li>
1925 <li>revamped the way the HTML parser handles end of tags</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001926 <li>XPath: corrections of namespaces support and number formatting</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +00001927 <li>Windows: Igor Zlatkovic patches for MSC compilation</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00001928 <li>HTML output fixes from P C Chow and William M. Brack</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +00001929 <li>Improved validation speed sensible for DocBook</li>
1930 <li>fixed a big bug with ID declared in external parsed entities</li>
1931 <li>portability fixes, update of Trio from Bjorn Reese</li>
1932</ul>
1933
Daniel Veillardafc73112001-04-11 11:51:41 +00001934<h3>2.3.6: April 8 2001</h3>
1935<ul>
1936 <li>Code cleanup using extreme gcc compiler warning options, found and
1937 cleared half a dozen potential problem</li>
1938 <li>the Eazel team found an XML parser bug</li>
1939 <li>cleaned up the user of some of the string formatting function. used the
1940 trio library code to provide the one needed when the platform is missing
1941 them</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00001942 <li>xpath: removed a memory leak and fixed the predicate evaluation
1943 problem, extended the testsuite and cleaned up the result. XPointer seems
1944 broken ...</li>
Daniel Veillardafc73112001-04-11 11:51:41 +00001945</ul>
1946
Daniel Veillard56a4cb82001-03-24 17:00:36 +00001947<h3>2.3.5: Mar 23 2001</h3>
1948<ul>
1949 <li>Biggest change is separate parsing and evaluation of XPath expressions,
1950 there is some new APIs for this too</li>
1951 <li>included a number of bug fixes(XML push parser, 51876, notations,
1952 52299)</li>
1953 <li>Fixed some portability issues</li>
1954</ul>
1955
Daniel Veillarde356c282001-03-10 12:32:04 +00001956<h3>2.3.4: Mar 10 2001</h3>
1957<ul>
1958 <li>Fixed bugs #51860 and #51861</li>
1959 <li>Added a global variable xmlDefaultBufferSize to allow default buffer
1960 size to be application tunable.</li>
1961 <li>Some cleanup in the validation code, still a bug left and this part
1962 should probably be rewritten to support ambiguous content model :-\</li>
1963 <li>Fix a couple of serious bugs introduced or raised by changes in 2.3.3
1964 parser</li>
1965 <li>Fixed another bug in xmlNodeGetContent()</li>
1966 <li>Bjorn fixed XPath node collection and Number formatting</li>
1967 <li>Fixed a loop reported in the HTML parsing</li>
1968 <li>blank space are reported even if the Dtd content model proves that they
Daniel Veillard63d83142002-05-20 06:51:05 +00001969 are formatting spaces, this is for XML conformance</li>
Daniel Veillarde356c282001-03-10 12:32:04 +00001970</ul>
1971
Daniel Veillardb402c072001-03-01 17:28:58 +00001972<h3>2.3.3: Mar 1 2001</h3>
1973<ul>
1974 <li>small change in XPath for XSLT</li>
1975 <li>documentation cleanups</li>
1976 <li>fix in validation by Gary Pennington</li>
1977 <li>serious parsing performances improvements</li>
1978</ul>
1979
Daniel Veillardec70e912001-02-26 20:10:45 +00001980<h3>2.3.2: Feb 24 2001</h3>
Daniel Veillard71681102001-02-24 17:48:53 +00001981<ul>
1982 <li>chasing XPath bugs, found a bunch, completed some TODO</li>
1983 <li>fixed a Dtd parsing bug</li>
1984 <li>fixed a bug in xmlNodeGetContent</li>
1985 <li>ID/IDREF support partly rewritten by Gary Pennington</li>
1986</ul>
1987
Daniel Veillardec70e912001-02-26 20:10:45 +00001988<h3>2.3.1: Feb 15 2001</h3>
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +00001989<ul>
1990 <li>some XPath and HTML bug fixes for XSLT</li>
1991 <li>small extension of the hash table interfaces for DOM gdome2
1992 implementation</li>
1993 <li>A few bug fixes</li>
1994</ul>
1995
Daniel Veillardec70e912001-02-26 20:10:45 +00001996<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 +00001997<ul>
1998 <li>Lots of XPath bug fixes</li>
1999 <li>Add a mode with Dtd lookup but without validation error reporting for
2000 XSLT</li>
2001 <li>Add support for text node without escaping (XSLT)</li>
2002 <li>bug fixes for xmlCheckFilename</li>
2003 <li>validation code bug fixes from Gary Pennington</li>
2004 <li>Patch from Paul D. Smith correcting URI path normalization</li>
2005 <li>Patch to allow simultaneous install of libxml-devel and
2006 libxml2-devel</li>
2007 <li>the example Makefile is now fixed</li>
2008 <li>added HTML to the RPM packages</li>
2009 <li>tree copying bugfixes</li>
2010 <li>updates to Windows makefiles</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002011 <li>optimization patch from Bjorn Reese</li>
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +00002012</ul>
2013
Daniel Veillardec70e912001-02-26 20:10:45 +00002014<h3>2.2.11: Jan 4 2001</h3>
Daniel Veillard503b8932001-01-05 06:36:31 +00002015<ul>
2016 <li>bunch of bug fixes (memory I/O, xpath, ftp/http, ...)</li>
2017 <li>added htmlHandleOmittedElem()</li>
2018 <li>Applied Bjorn Reese's IPV6 first patch</li>
2019 <li>Applied Paul D. Smith patches for validation of XInclude results</li>
Daniel Veillard82687162001-01-22 15:32:01 +00002020 <li>added XPointer xmlns() new scheme support</li>
Daniel Veillard503b8932001-01-05 06:36:31 +00002021</ul>
2022
Daniel Veillard2ddd23d2000-11-25 10:42:19 +00002023<h3>2.2.10: Nov 25 2000</h3>
Daniel Veillard9d343c42000-11-25 10:12:43 +00002024<ul>
2025 <li>Fix the Windows problems of 2.2.8</li>
2026 <li>integrate OpenVMS patches</li>
2027 <li>better handling of some nasty HTML input</li>
2028 <li>Improved the XPointer implementation</li>
2029 <li>integrate a number of provided patches</li>
2030</ul>
2031
Daniel Veillard2ddd23d2000-11-25 10:42:19 +00002032<h3>2.2.9: Nov 25 2000</h3>
2033<ul>
2034 <li>erroneous release :-(</li>
2035</ul>
2036
Daniel Veillard28929b22000-11-13 18:22:49 +00002037<h3>2.2.8: Nov 13 2000</h3>
2038<ul>
2039 <li>First version of <a href="http://www.w3.org/TR/xinclude">XInclude</a>
2040 support</li>
2041 <li>Patch in conditional section handling</li>
2042 <li>updated MS compiler project</li>
2043 <li>fixed some XPath problems</li>
2044 <li>added an URI escaping function</li>
2045 <li>some other bug fixes</li>
2046</ul>
2047
2048<h3>2.2.7: Oct 31 2000</h3>
2049<ul>
2050 <li>added message redirection</li>
2051 <li>XPath improvements (thanks TOM !)</li>
2052 <li>xmlIOParseDTD() added</li>
2053 <li>various small fixes in the HTML, URI, HTTP and XPointer support</li>
2054 <li>some cleanup of the Makefile, autoconf and the distribution content</li>
2055</ul>
2056
Daniel Veillard29a11cc2000-10-25 13:32:39 +00002057<h3>2.2.6: Oct 25 2000:</h3>
2058<ul>
2059 <li>Added an hash table module, migrated a number of internal structure to
2060 those</li>
2061 <li>Fixed a posteriori validation problems</li>
2062 <li>HTTP module cleanups</li>
2063 <li>HTML parser improvements (tag errors, script/style handling, attribute
2064 normalization)</li>
2065 <li>coalescing of adjacent text nodes</li>
2066 <li>couple of XPath bug fixes, exported the internal API</li>
2067</ul>
2068
Daniel Veillardab8500d2000-10-15 21:06:19 +00002069<h3>2.2.5: Oct 15 2000:</h3>
Daniel Veillard4c3a2031999-11-19 17:46:26 +00002070<ul>
Daniel Veillard189446d2000-10-13 10:23:06 +00002071 <li>XPointer implementation and testsuite</li>
2072 <li>Lot of XPath fixes, added variable and functions registration, more
2073 tests</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002074 <li>Portability fixes, lots of enhancements toward an easy Windows build
2075 and release</li>
Daniel Veillard189446d2000-10-13 10:23:06 +00002076 <li>Late validation fixes</li>
2077 <li>Integrated a lot of contributed patches</li>
2078 <li>added memory management docs</li>
Daniel Veillardab8500d2000-10-15 21:06:19 +00002079 <li>a performance problem when using large buffer seems fixed</li>
Daniel Veillard189446d2000-10-13 10:23:06 +00002080</ul>
2081
2082<h3>2.2.4: Oct 1 2000:</h3>
2083<ul>
2084 <li>main XPath problem fixed</li>
2085 <li>Integrated portability patches for Windows</li>
2086 <li>Serious bug fixes on the URI and HTML code</li>
Daniel Veillard361d8452000-04-03 19:48:13 +00002087</ul>
2088
Daniel Veillardd5f97f82000-09-17 16:38:14 +00002089<h3>2.2.3: Sep 17 2000</h3>
2090<ul>
2091 <li>bug fixes</li>
2092 <li>cleanup of entity handling code</li>
2093 <li>overall review of all loops in the parsers, all sprintf usage has been
2094 checked too</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002095 <li>Far better handling of larges Dtd. Validating against DocBook XML Dtd
Daniel Veillardd5f97f82000-09-17 16:38:14 +00002096 works smoothly now.</li>
2097</ul>
2098
2099<h3>1.8.10: Sep 6 2000</h3>
2100<ul>
2101 <li>bug fix release for some Gnome projects</li>
2102</ul>
2103
2104<h3>2.2.2: August 12 2000</h3>
Daniel Veillard786d7c82000-08-12 23:38:57 +00002105<ul>
2106 <li>mostly bug fixes</li>
Daniel Veillardec78c0f2000-08-25 10:25:23 +00002107 <li>started adding routines to access xml parser context options</li>
Daniel Veillard786d7c82000-08-12 23:38:57 +00002108</ul>
2109
Daniel Veillardd5f97f82000-09-17 16:38:14 +00002110<h3>2.2.1: July 21 2000</h3>
Daniel Veillarda2679fa2000-07-22 02:38:15 +00002111<ul>
2112 <li>a purely bug fixes release</li>
2113 <li>fixed an encoding support problem when parsing from a memory block</li>
2114 <li>fixed a DOCTYPE parsing problem</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002115 <li>removed a bug in the function allowing to override the memory
2116 allocation routines</li>
Daniel Veillarda2679fa2000-07-22 02:38:15 +00002117</ul>
2118
Daniel Veillardd5f97f82000-09-17 16:38:14 +00002119<h3>2.2.0: July 14 2000</h3>
Daniel Veillard94e90602000-07-17 14:38:19 +00002120<ul>
2121 <li>applied a lot of portability fixes</li>
2122 <li>better encoding support/cleanup and saving (content is now always
2123 encoded in UTF-8)</li>
2124 <li>the HTML parser now correctly handles encodings</li>
2125 <li>added xmlHasProp()</li>
2126 <li>fixed a serious problem with &amp;#38;</li>
2127 <li>propagated the fix to FTP client</li>
2128 <li>cleanup, bugfixes, etc ...</li>
2129 <li>Added a page about <a href="encoding.html">libxml Internationalization
2130 support</a></li>
2131</ul>
2132
Daniel Veillard60979bd2000-07-10 12:17:33 +00002133<h3>1.8.9: July 9 2000</h3>
2134<ul>
2135 <li>fixed the spec the RPMs should be better</li>
2136 <li>fixed a serious bug in the FTP implementation, released 1.8.9 to solve
2137 rpmfind users problem</li>
2138</ul>
2139
Daniel Veillard6388e172000-07-03 16:07:19 +00002140<h3>2.1.1: July 1 2000</h3>
2141<ul>
2142 <li>fixes a couple of bugs in the 2.1.0 packaging</li>
2143 <li>improvements on the HTML parser</li>
2144</ul>
2145
Daniel Veillard3f6f7f62000-06-30 17:58:25 +00002146<h3>2.1.0 and 1.8.8: June 29 2000</h3>
2147<ul>
Daniel Veillardc0801af2002-05-28 16:28:42 +00002148 <li>1.8.8 is mostly a commodity package for upgrading to libxml2 according
2149 to <a href="upgrade.html">new instructions</a>. It fixes a nasty problem
Daniel Veillard3f6f7f62000-06-30 17:58:25 +00002150 about &amp;#38; charref parsing</li>
2151 <li>2.1.0 also ease the upgrade from libxml v1 to the recent version. it
2152 also contains numerous fixes and enhancements:
2153 <ul>
2154 <li>added xmlStopParser() to stop parsing</li>
2155 <li>improved a lot parsing speed when there is large CDATA blocs</li>
2156 <li>includes XPath patches provided by Picdar Technology</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002157 <li>tried to fix as much as possible DTD validation and namespace
Daniel Veillard3f6f7f62000-06-30 17:58:25 +00002158 related problems</li>
2159 <li>output to a given encoding has been added/tested</li>
2160 <li>lot of various fixes</li>
2161 </ul>
2162 </li>
2163</ul>
2164
Daniel Veillarde0aed302000-04-16 08:52:20 +00002165<h3>2.0.0: Apr 12 2000</h3>
Daniel Veillard361d8452000-04-03 19:48:13 +00002166<ul>
2167 <li>First public release of libxml2. If you are using libxml, it's a good
Daniel Veillard63d83142002-05-20 06:51:05 +00002168 idea to check the 1.x to 2.x upgrade instructions. NOTE: while initially
2169 scheduled for Apr 3 the release occurred only on Apr 12 due to massive
Daniel Veillarde0aed302000-04-16 08:52:20 +00002170 workload.</li>
Daniel Veillard361d8452000-04-03 19:48:13 +00002171 <li>The include are now located under $prefix/include/libxml (instead of
Daniel Veillarde0aed302000-04-16 08:52:20 +00002172 $prefix/include/gnome-xml), they also are referenced by
Daniel Veillard60979bd2000-07-10 12:17:33 +00002173 <pre>#include &lt;libxml/xxx.h&gt;</pre>
Daniel Veillarde0aed302000-04-16 08:52:20 +00002174 <p>instead of</p>
Daniel Veillard361d8452000-04-03 19:48:13 +00002175 <pre>#include "xxx.h"</pre>
2176 </li>
Daniel Veillard8f621982000-03-20 13:07:15 +00002177 <li>a new URI module for parsing URIs and following strictly RFC 2396</li>
2178 <li>the memory allocation routines used by libxml can now be overloaded
2179 dynamically by using xmlMemSetup()</li>
Daniel Veillard361d8452000-04-03 19:48:13 +00002180 <li>The previously CVS only tool tester has been renamed
2181 <strong>xmllint</strong> and is now installed as part of the libxml2
2182 package</li>
Daniel Veillarde0aed302000-04-16 08:52:20 +00002183 <li>The I/O interface has been revamped. There is now ways to plug in
2184 specific I/O modules, either at the URI scheme detection level using
2185 xmlRegisterInputCallbacks() or by passing I/O functions when creating a
2186 parser context using xmlCreateIOParserCtxt()</li>
2187 <li>there is a C preprocessor macro LIBXML_VERSION providing the version
2188 number of the libxml module in use</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002189 <li>a number of optional features of libxml can now be excluded at
2190 configure time (FTP/HTTP/HTML/XPath/Debug)</li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002191</ul>
2192
2193<h3>2.0.0beta: Mar 14 2000</h3>
2194<ul>
2195 <li>This is a first Beta release of libxml version 2</li>
Daniel Veillarde356c282001-03-10 12:32:04 +00002196 <li>It's available only from<a href="ftp://xmlsoft.org/">xmlsoft.org
2197 FTP</a>, it's packaged as libxml2-2.0.0beta and available as tar and
2198 RPMs</li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002199 <li>This version is now the head in the Gnome CVS base, the old one is
2200 available under the tag LIB_XML_1_X</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00002201 <li>This includes a very large set of changes. From a programmatic point
2202 of view applications should not have to be modified too much, check the
2203 <a href="upgrade.html">upgrade page</a></li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002204 <li>Some interfaces may changes (especially a bit about encoding).</li>
2205 <li>the updates includes:
Daniel Veillard6c8b1172000-03-01 00:40:41 +00002206 <ul>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002207 <li>fix I18N support. ISO-Latin-x/UTF-8/UTF-16 (nearly) seems correctly
2208 handled now</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002209 <li>Better handling of entities, especially well-formedness checking
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002210 and proper PEref extensions in external subsets</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +00002211 <li>DTD conditional sections</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002212 <li>Validation now correctly handle entities content</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +00002213 <li><a href="http://rpmfind.net/tools/gdome/messages/0039.html">change
Daniel Veillard63d83142002-05-20 06:51:05 +00002214 structures to accommodate DOM</a></li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +00002215 </ul>
2216 </li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002217 <li>Serious progress were made toward compliance, <a
2218 href="conf/result.html">here are the result of the test</a> against the
Daniel Veillard63d83142002-05-20 06:51:05 +00002219 OASIS testsuite (except the Japanese tests since I don't support that
Daniel Veillardedfb29b2000-03-14 19:59:05 +00002220 encoding yet). This URL is rebuilt every couple of hours using the CVS
2221 head version.</li>
Daniel Veillarde41f2b72000-01-30 20:00:07 +00002222</ul>
2223
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002224<h3>1.8.7: Mar 6 2000</h3>
2225<ul>
2226 <li>This is a bug fix release:</li>
2227 <li>It is possible to disable the ignorable blanks heuristic used by
2228 libxml-1.x, a new function xmlKeepBlanksDefault(0) will allow this. Note
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002229 that for adherence to XML spec, this behaviour will be disabled by
2230 default in 2.x . The same function will allow to keep compatibility for
2231 old code.</li>
Daniel Veillard60979bd2000-07-10 12:17:33 +00002232 <li>Blanks in &lt;a&gt; &lt;/a&gt; constructs are not ignored anymore,
2233 avoiding heuristic is really the Right Way :-\</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002234 <li>The unchecked use of snprintf which was breaking libxml-1.8.6
2235 compilation on some platforms has been fixed</li>
2236 <li>nanoftp.c nanohttp.c: Fixed '#' and '?' stripping when processing
2237 URIs</li>
2238</ul>
2239
Daniel Veillarde41f2b72000-01-30 20:00:07 +00002240<h3>1.8.6: Jan 31 2000</h3>
2241<ul>
2242 <li>added a nanoFTP transport module, debugged until the new version of <a
2243 href="http://rpmfind.net/linux/rpm2html/rpmfind.html">rpmfind</a> can use
2244 it without troubles</li>
Daniel Veillardda07c342000-01-25 18:31:22 +00002245</ul>
2246
2247<h3>1.8.5: Jan 21 2000</h3>
2248<ul>
Daniel Veillard0142b842000-01-14 14:45:24 +00002249 <li>adding APIs to parse a well balanced chunk of XML (production <a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002250 href="http://www.w3.org/TR/REC-xml#NT-content">[43] content</a> of the
2251 XML spec)</li>
Daniel Veillard461a66c2000-01-18 18:01:01 +00002252 <li>fixed a hideous bug in xmlGetProp pointed by Rune.Djurhuus@fast.no</li>
Daniel Veillard60979bd2000-07-10 12:17:33 +00002253 <li>Jody Goldberg &lt;jgoldberg@home.com&gt; provided another patch trying
2254 to solve the zlib checks problems</li>
Daniel Veillard461a66c2000-01-18 18:01:01 +00002255 <li>The current state in gnome CVS base is expected to ship as 1.8.5 with
2256 gnumeric soon</li>
Daniel Veillard0142b842000-01-14 14:45:24 +00002257</ul>
2258
2259<h3>1.8.4: Jan 13 2000</h3>
2260<ul>
2261 <li>bug fixes, reintroduced xmlNewGlobalNs(), fixed xmlNewNs()</li>
2262 <li>all exit() call should have been removed from libxml</li>
2263 <li>fixed a problem with INCLUDE_WINSOCK on WIN32 platform</li>
2264 <li>added newDocFragment()</li>
Daniel Veillardf84f71f2000-01-05 19:54:23 +00002265</ul>
2266
2267<h3>1.8.3: Jan 5 2000</h3>
2268<ul>
2269 <li>a Push interface for the XML and HTML parsers</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002270 <li>a shell-like interface to the document tree (try tester --shell :-)</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002271 <li>lots of bug fixes and improvement added over XMas holidays</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +00002272 <li>fixed the DTD parsing code to work with the xhtml DTD</li>
Daniel Veillardf84f71f2000-01-05 19:54:23 +00002273 <li>added xmlRemoveProp(), xmlRemoveID() and xmlRemoveRef()</li>
2274 <li>Fixed bugs in xmlNewNs()</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +00002275 <li>External entity loading code has been revamped, now it uses
Daniel Veillardf84f71f2000-01-05 19:54:23 +00002276 xmlLoadExternalEntity(), some fix on entities processing were added</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +00002277 <li>cleaned up WIN32 includes of socket stuff</li>
Daniel Veillard5cb5ab81999-12-21 15:35:29 +00002278</ul>
2279
2280<h3>1.8.2: Dec 21 1999</h3>
2281<ul>
Daniel Veillardb24054a1999-12-18 15:32:46 +00002282 <li>I got another problem with includes and C++, I hope this issue is fixed
2283 for good this time</li>
Daniel Veillard5cb5ab81999-12-21 15:35:29 +00002284 <li>Added a few tree modification functions: xmlReplaceNode,
2285 xmlAddPrevSibling, xmlAddNextSibling, xmlNodeSetName and
2286 xmlDocSetRootElement</li>
2287 <li>Tried to improve the HTML output with help from <a
2288 href="mailto:clahey@umich.edu">Chris Lahey</a></li>
Daniel Veillarde4e51311999-12-18 15:32:46 +00002289</ul>
Daniel Veillardb24054a1999-12-18 15:32:46 +00002290
Daniel Veillarde4e51311999-12-18 15:32:46 +00002291<h3>1.8.1: Dec 18 1999</h3>
2292<ul>
2293 <li>various patches to avoid troubles when using libxml with C++ compilers
2294 the "namespace" keyword and C escaping in include files</li>
2295 <li>a problem in one of the core macros IS_CHAR was corrected</li>
2296 <li>fixed a bug introduced in 1.8.0 breaking default namespace processing,
2297 and more specifically the Dia application</li>
Daniel Veillard944b5ff1999-12-15 19:08:24 +00002298 <li>fixed a posteriori validation (validation after parsing, or by using a
2299 Dtd not specified in the original document)</li>
Daniel Veillardb24054a1999-12-18 15:32:46 +00002300 <li>fixed a bug in</li>
Daniel Veillard10a2c651999-12-12 13:03:50 +00002301</ul>
2302
2303<h3>1.8.0: Dec 12 1999</h3>
2304<ul>
2305 <li>cleanup, especially memory wise</li>
2306 <li>the parser should be more reliable, especially the HTML one, it should
2307 not crash, whatever the input !</li>
2308 <li>Integrated various patches, especially a speedup improvement for large
2309 dataset from <a href="mailto:cnygard@bellatlantic.net">Carl Nygard</a>,
2310 configure with --with-buffers to enable them.</li>
2311 <li>attribute normalization, oops should have been added long ago !</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002312 <li>attributes defaulted from DTDs should be available, xmlSetProp() now
2313 does entities escaping by default.</li>
Daniel Veillard4c3a2031999-11-19 17:46:26 +00002314</ul>
Daniel Veillard35008381999-10-25 13:15:52 +00002315
2316<h3>1.7.4: Oct 25 1999</h3>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002317<ul>
Daniel Veillard35008381999-10-25 13:15:52 +00002318 <li>Lots of HTML improvement</li>
2319 <li>Fixed some errors when saving both XML and HTML</li>
2320 <li>More examples, the regression tests should now look clean</li>
2321 <li>Fixed a bug with contiguous charref</li>
2322</ul>
2323
2324<h3>1.7.3: Sep 29 1999</h3>
2325<ul>
2326 <li>portability problems fixed</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00002327 <li>snprintf was used unconditionally, leading to link problems on system
Daniel Veillard35008381999-10-25 13:15:52 +00002328 were it's not available, fixed</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002329</ul>
2330
2331<h3>1.7.1: Sep 24 1999</h3>
2332<ul>
2333 <li>The basic type for strings manipulated by libxml has been renamed in
2334 1.7.1 from <strong>CHAR</strong> to <strong>xmlChar</strong>. The reason
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002335 is that CHAR was conflicting with a predefined type on Windows. However
2336 on non WIN32 environment, compatibility is provided by the way of a
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002337 <strong>#define </strong>.</li>
2338 <li>Changed another error : the use of a structure field called errno, and
2339 leading to troubles on platforms where it's a macro</li>
2340</ul>
2341
Daniel Veillard63d83142002-05-20 06:51:05 +00002342<h3>1.7.0: Sep 23 1999</h3>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002343<ul>
2344 <li>Added the ability to fetch remote DTD or parsed entities, see the <a
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00002345 href="html/libxml-nanohttp.html">nanohttp</a> module.</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002346 <li>Added an errno to report errors by another mean than a simple printf
2347 like callback</li>
2348 <li>Finished ID/IDREF support and checking when validation</li>
2349 <li>Serious memory leaks fixed (there is now a <a
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00002350 href="html/libxml-xmlmemory.html">memory wrapper</a> module)</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002351 <li>Improvement of <a href="http://www.w3.org/TR/xpath">XPath</a>
2352 implementation</li>
2353 <li>Added an HTML parser front-end</li>
2354</ul>
2355
2356<h2><a name="XML">XML</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002357
Daniel Veillard402e8c82000-02-29 22:57:47 +00002358<p><a href="http://www.w3.org/TR/REC-xml">XML is a standard</a> for
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002359markup-based structured documents. Here is <a name="example">an example XML
2360document</a>:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00002361<pre>&lt;?xml version="1.0"?&gt;
2362&lt;EXAMPLE prop1="gnome is great" prop2="&amp;amp; linux too"&gt;
2363 &lt;head&gt;
2364 &lt;title&gt;Welcome to Gnome&lt;/title&gt;
2365 &lt;/head&gt;
2366 &lt;chapter&gt;
2367 &lt;title&gt;The Linux adventure&lt;/title&gt;
2368 &lt;p&gt;bla bla bla ...&lt;/p&gt;
2369 &lt;image href="linus.gif"/&gt;
2370 &lt;p&gt;...&lt;/p&gt;
2371 &lt;/chapter&gt;
2372&lt;/EXAMPLE&gt;</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002373
Daniel Veillard0b28e882002-07-24 23:47:05 +00002374<p>The first line specifies that it is an XML document and gives useful
Daniel Veillard42766c02002-08-22 20:52:17 +00002375information about its encoding. Then the rest of the document is a text
2376format whose structure is specified by tags between brackets. <strong>Each
2377tag opened has to be closed</strong>. XML is pedantic about this. However, if
2378a tag is empty (no content), a single tag can serve as both the opening and
2379closing tag if it ends with <code>/&gt;</code> rather than with
2380<code>&gt;</code>. Note that, for example, the image tag has no content (just
2381an attribute) and is closed by ending the tag with <code>/&gt;</code>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +00002382
Daniel Veillard42766c02002-08-22 20:52:17 +00002383<p>XML can be applied successfully to a wide range of tasks, ranging from
2384long term structured document maintenance (where it follows the steps of
2385SGML) to simple data encoding mechanisms like configuration file formatting
2386(glade), spreadsheets (gnumeric), or even shorter lived documents such as
2387WebDAV where it is used to encode remote calls between a client and a
2388server.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002389
Daniel Veillard82687162001-01-22 15:32:01 +00002390<h2><a name="XSLT">XSLT</a></h2>
2391
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +00002392<p>Check <a href="http://xmlsoft.org/XSLT">the separate libxslt page</a></p>
2393
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002394<p><a href="http://www.w3.org/TR/xslt">XSL Transformations</a>, is a
2395language for transforming XML documents into other XML documents (or
2396HTML/textual output).</p>
Daniel Veillard82687162001-01-22 15:32:01 +00002397
Daniel Veillard560c2a42003-07-06 21:13:49 +00002398<p>A separate library called libxslt is available implementing XSLT-1.0 for
2399libxml2. This module "libxslt" too can be found in the Gnome CVS base.</p>
Daniel Veillard82687162001-01-22 15:32:01 +00002400
Daniel Veillard29f61002005-08-06 09:07:15 +00002401<p>You can check the progresses on the libxslt <a
2402href="http://xmlsoft.org/XSLT/ChangeLog.html">Changelog</a>.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002403
2404<h2><a name="Python">Python and bindings</a></h2>
2405
Daniel Veillard42766c02002-08-22 20:52:17 +00002406<p>There are a number of language bindings and wrappers available for
2407libxml2, the list below is not exhaustive. Please contact the <a
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002408href="http://mail.gnome.org/mailman/listinfo/xml-bindings">xml-bindings@gnome.org</a>
2409(<a href="http://mail.gnome.org/archives/xml-bindings/">archives</a>) in
2410order to get updates to this list or to discuss the specific topic of libxml2
2411or libxslt wrappers or bindings:</p>
2412<ul>
Daniel Veillardc14401e2002-11-20 14:28:17 +00002413 <li><a href="http://libxmlplusplus.sourceforge.net/">Libxml++</a> seems the
2414 most up-to-date C++ bindings for libxml2, check the <a
2415 href="http://libxmlplusplus.sourceforge.net/reference/html/hierarchy.html">documentation</a>
2416 and the <a
2417 href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/libxmlplusplus/libxml%2b%2b/examples/">examples</a>.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002418 <li>There is another <a href="http://libgdome-cpp.berlios.de/">C++ wrapper
Daniel Veillard0b28e882002-07-24 23:47:05 +00002419 based on the gdome2 bindings</a> maintained by Tobias Peters.</li>
Daniel Veillard9b6fd302002-05-13 12:06:47 +00002420 <li>and a third C++ wrapper by Peter Jones &lt;pjones@pmade.org&gt;
2421 <p>Website: <a
2422 href="http://pmade.org/pjones/software/xmlwrapp/">http://pmade.org/pjones/software/xmlwrapp/</a></p>
2423 </li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002424 <li><a
2425 href="http://mail.gnome.org/archives/xml/2001-March/msg00014.html">Matt
Daniel Veillard63d83142002-05-20 06:51:05 +00002426 Sergeant</a> developed <a
2427 href="http://axkit.org/download/">XML::LibXSLT</a>, a Perl wrapper for
Daniel Veillardaf43f632002-03-08 15:05:20 +00002428 libxml2/libxslt as part of the <a href="http://axkit.com/">AxKit XML
Daniel Veillard0b28e882002-07-24 23:47:05 +00002429 application server</a>.</li>
Daniel Veillard4ac494b2003-09-18 15:08:00 +00002430 <li>If you're interested into scripting XML processing, have a look at <a
2431 href="http://xsh.sourceforge.net/">XSH</a> an XML editing shell based on
2432 Libxml2 Perl bindings.</li>
Daniel Veillard21473672002-06-17 07:29:22 +00002433 <li><a href="mailto:dkuhlman@cutter.rexx.com">Dave Kuhlman</a> provides an
Daniel Veillardaf43f632002-03-08 15:05:20 +00002434 earlier version of the libxml/libxslt <a
Daniel Veillard0b28e882002-07-24 23:47:05 +00002435 href="http://www.rexx.com/~dkuhlman">wrappers for Python</a>.</li>
Daniel Veillard21473672002-06-17 07:29:22 +00002436 <li>Gopal.V and Peter Minten develop <a
2437 href="http://savannah.gnu.org/projects/libxmlsharp">libxml#</a>, a set of
Daniel Veillard0b28e882002-07-24 23:47:05 +00002438 C# libxml2 bindings.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002439 <li>Petr Kozelka provides <a
2440 href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
Daniel Veillard0b28e882002-07-24 23:47:05 +00002441 libxml2</a> with Kylix, Delphi and other Pascal compilers.</li>
Daniel Veillardb2fb8ed2002-04-01 09:33:12 +00002442 <li>Uwe Fechner also provides <a
2443 href="http://sourceforge.net/projects/idom2-pas/">idom2</a>, a DOM2
Daniel Veillard0b28e882002-07-24 23:47:05 +00002444 implementation for Kylix2/D5/D6 from Borland.</li>
Daniel Veillard142fb212005-04-07 12:48:10 +00002445 <li>There is <a
2446 href="http://rubyforge.org/projects/xml-tools/">bindings for Ruby</a> and
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002447 libxml2 bindings are also available in Ruby through the <a
2448 href="http://libgdome-ruby.berlios.de/">libgdome-ruby</a> module
2449 maintained by Tobias Peters.</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002450 <li>Steve Ball and contributors maintains <a
2451 href="http://tclxml.sourceforge.net/">libxml2 and libxslt bindings for
Daniel Veillard0b28e882002-07-24 23:47:05 +00002452 Tcl</a>.</li>
Daniel Veillard142fb212005-04-07 12:48:10 +00002453 <li>libxml2 and libxslt is the default XML library for PHP5.</li>
Daniel Veillard41b01a82003-02-27 11:09:06 +00002454 <li><a href="http://savannah.gnu.org/projects/classpathx/">LibxmlJ</a> is
Daniel Veillard806cada2003-03-19 21:58:59 +00002455 an effort to create a 100% JAXP-compatible Java wrapper for libxml2 and
2456 libxslt as part of GNU ClasspathX project.</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +00002457 <li>Patrick McPhee provides Rexx bindings fof libxml2 and libxslt, look for
2458 <a href="http://www.interlog.com/~ptjm/software.html">RexxXML</a>.</li>
Daniel Veillardb78757b2004-12-30 21:30:23 +00002459 <li><a href="http://www.satimage.fr/software/en/xml_suite.html">Satimage</a>
2460 provides <a
2461 href="http://www.satimage.fr/software/en/downloads_osaxen.html">XMLLib
2462 osax</a>. This is an osax for Mac OS X with a set of commands to
2463 implement in AppleScript the XML DOM, XPATH and XSLT. Also includes
Daniel Veillardc7426092005-01-05 15:11:41 +00002464 commands for Property-lists (Apple's fast lookup table XML format.)</li>
2465 <li>Francesco Montorsi developped
2466<a href="https://sourceforge.net/project/showfiles.php?group_id=51305&amp;package_id=45182">wxXml2</a>
2467 wrappers that interface libxml2, allowing wxWidgets applications to
2468 load/save/edit XML instances.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002469</ul>
2470
Daniel Veillardc0801af2002-05-28 16:28:42 +00002471<p>The distribution includes a set of Python bindings, which are guaranteed
2472to be maintained as part of the library in the future, though the Python
Daniel Veillard41b01a82003-02-27 11:09:06 +00002473interface have not yet reached the completeness of the C API.</p>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00002474
Daniel Veillard929746e2005-05-11 11:08:22 +00002475<p>Note that some of the Python purist dislike the default set of Python
2476bindings, rather than complaining I suggest they have a look at
Daniel Veillard6c6d3c72005-05-11 11:12:30 +00002477<a href="http://codespeak.net/lxml/">lxml the more pythonic bindings for libxml2 and libxslt</a> and
2478<a href="http://codespeak.net/mailman/listinfo/lxml-dev">help Martijn Faassen</a>
2479complete those.</p>
Daniel Veillard929746e2005-05-11 11:08:22 +00002480
Daniel Veillard27907c72002-12-16 16:05:58 +00002481<p><a href="mailto:stephane.bidoul@softwareag.com">Stéphane Bidoul</a>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00002482maintains <a href="http://users.skynet.be/sbi/libxml-python/">a Windows port
2483of the Python bindings</a>.</p>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002484
Daniel Veillard7ef0fcb2002-12-14 10:38:55 +00002485<p>Note to people interested in building bindings, the API is formalized as
2486<a href="libxml2-api.xml">an XML API description file</a> which allows to
2487automate a large part of the Python bindings, this includes function
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00002488descriptions, enums, structures, typedefs, etc... The Python script used to
2489build the bindings is python/generator.py in the source distribution.</p>
Daniel Veillard7ef0fcb2002-12-14 10:38:55 +00002490
Daniel Veillardaf43f632002-03-08 15:05:20 +00002491<p>To install the Python bindings there are 2 options:</p>
Daniel Veillard0b79dfe2002-02-23 13:02:31 +00002492<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002493 <li>If you use an RPM based distribution, simply install the <a
2494 href="http://rpmfind.net/linux/rpm2html/search.php?query=libxml2-python">libxml2-python
2495 RPM</a> (and if needed the <a
2496 href="http://rpmfind.net/linux/rpm2html/search.php?query=libxslt-python">libxslt-python
2497 RPM</a>).</li>
2498 <li>Otherwise use the <a href="ftp://xmlsoft.org/python/">libxml2-python
2499 module distribution</a> corresponding to your installed version of
2500 libxml2 and libxslt. Note that to install it you will need both libxml2
2501 and libxslt installed and run "python setup.py build install" in the
2502 module tree.</li>
Daniel Veillard0b79dfe2002-02-23 13:02:31 +00002503</ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002504
2505<p>The distribution includes a set of examples and regression tests for the
2506python bindings in the <code>python/tests</code> directory. Here are some
Daniel Veillard0b28e882002-07-24 23:47:05 +00002507excerpts from those tests:</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002508
2509<h3>tst.py:</h3>
2510
2511<p>This is a basic test of the file interface and DOM navigation:</p>
MST 2003 John Fleck2dffb762003-11-29 04:41:24 +00002512<pre>import libxml2, sys
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002513
2514doc = libxml2.parseFile("tst.xml")
2515if doc.name != "tst.xml":
2516 print "doc.name failed"
2517 sys.exit(1)
2518root = doc.children
2519if root.name != "doc":
2520 print "root.name failed"
2521 sys.exit(1)
2522child = root.children
2523if child.name != "foo":
2524 print "child.name failed"
2525 sys.exit(1)
2526doc.freeDoc()</pre>
2527
Daniel Veillard0b28e882002-07-24 23:47:05 +00002528<p>The Python module is called libxml2; parseFile is the equivalent of
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002529xmlParseFile (most of the bindings are automatically generated, and the xml
2530prefix is removed and the casing convention are kept). All node seen at the
Daniel Veillard63d83142002-05-20 06:51:05 +00002531binding level share the same subset of accessors:</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002532<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002533 <li><code>name</code> : returns the node name</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00002534 <li><code>type</code> : returns a string indicating the node type</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00002535 <li><code>content</code> : returns the content of the node, it is based on
2536 xmlNodeGetContent() and hence is recursive.</li>
2537 <li><code>parent</code> , <code>children</code>, <code>last</code>,
2538 <code>next</code>, <code>prev</code>, <code>doc</code>,
2539 <code>properties</code>: pointing to the associated element in the tree,
2540 those may return None in case no such link exists.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002541</ul>
2542
Daniel Veillard63d83142002-05-20 06:51:05 +00002543<p>Also note the need to explicitly deallocate documents with freeDoc() .
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002544Reference counting for libxml2 trees would need quite a lot of work to
2545function properly, and rather than risk memory leaks if not implemented
2546correctly it sounds safer to have an explicit function to free a tree. The
2547wrapper python objects like doc, root or child are them automatically garbage
2548collected.</p>
2549
2550<h3>validate.py:</h3>
2551
2552<p>This test check the validation interfaces and redirection of error
2553messages:</p>
2554<pre>import libxml2
2555
Daniel Veillard63d83142002-05-20 06:51:05 +00002556#deactivate error messages from the validation
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002557def noerr(ctx, str):
2558 pass
2559
2560libxml2.registerErrorHandler(noerr, None)
2561
2562ctxt = libxml2.createFileParserCtxt("invalid.xml")
2563ctxt.validate(1)
2564ctxt.parseDocument()
2565doc = ctxt.doc()
2566valid = ctxt.isValid()
2567doc.freeDoc()
2568if valid != 0:
Daniel Veillard63d83142002-05-20 06:51:05 +00002569 print "validity check failed"</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002570
2571<p>The first thing to notice is the call to registerErrorHandler(), it
2572defines a new error handler global to the library. It is used to avoid seeing
2573the error messages when trying to validate the invalid document.</p>
2574
2575<p>The main interest of that test is the creation of a parser context with
2576createFileParserCtxt() and how the behaviour can be changed before calling
Daniel Veillard63d83142002-05-20 06:51:05 +00002577parseDocument() . Similarly the informations resulting from the parsing phase
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002578are also available using context methods.</p>
2579
2580<p>Contexts like nodes are defined as class and the libxml2 wrappers maps the
2581C function interfaces in terms of objects method as much as possible. The
2582best to get a complete view of what methods are supported is to look at the
2583libxml2.py module containing all the wrappers.</p>
2584
2585<h3>push.py:</h3>
2586
2587<p>This test show how to activate the push parser interface:</p>
2588<pre>import libxml2
2589
2590ctxt = libxml2.createPushParser(None, "&lt;foo", 4, "test.xml")
2591ctxt.parseChunk("/&gt;", 2, 1)
2592doc = ctxt.doc()
2593
2594doc.freeDoc()</pre>
2595
Daniel Veillard63d83142002-05-20 06:51:05 +00002596<p>The context is created with a special call based on the
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002597xmlCreatePushParser() from the C library. The first argument is an optional
Daniel Veillard63d83142002-05-20 06:51:05 +00002598SAX callback object, then the initial set of data, the length and the name of
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002599the resource in case URI-References need to be computed by the parser.</p>
2600
2601<p>Then the data are pushed using the parseChunk() method, the last call
Daniel Veillard63d83142002-05-20 06:51:05 +00002602setting the third argument terminate to 1.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002603
2604<h3>pushSAX.py:</h3>
2605
2606<p>this test show the use of the event based parsing interfaces. In this case
2607the parser does not build a document, but provides callback information as
2608the parser makes progresses analyzing the data being provided:</p>
2609<pre>import libxml2
2610log = ""
2611
2612class callback:
2613 def startDocument(self):
2614 global log
2615 log = log + "startDocument:"
2616
2617 def endDocument(self):
2618 global log
2619 log = log + "endDocument:"
2620
2621 def startElement(self, tag, attrs):
2622 global log
2623 log = log + "startElement %s %s:" % (tag, attrs)
2624
2625 def endElement(self, tag):
2626 global log
2627 log = log + "endElement %s:" % (tag)
2628
2629 def characters(self, data):
2630 global log
2631 log = log + "characters: %s:" % (data)
2632
2633 def warning(self, msg):
2634 global log
2635 log = log + "warning: %s:" % (msg)
2636
2637 def error(self, msg):
2638 global log
2639 log = log + "error: %s:" % (msg)
2640
2641 def fatalError(self, msg):
2642 global log
2643 log = log + "fatalError: %s:" % (msg)
2644
2645handler = callback()
2646
2647ctxt = libxml2.createPushParser(handler, "&lt;foo", 4, "test.xml")
2648chunk = " url='tst'&gt;b"
2649ctxt.parseChunk(chunk, len(chunk), 0)
2650chunk = "ar&lt;/foo&gt;"
2651ctxt.parseChunk(chunk, len(chunk), 1)
2652
Daniel Veillardfcbfa2d2002-02-21 17:54:27 +00002653reference = "startDocument:startElement foo {'url': 'tst'}:" + \
2654 "characters: bar:endElement foo:endDocument:"
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002655if log != reference:
2656 print "Error got: %s" % log
Daniel Veillard63d83142002-05-20 06:51:05 +00002657 print "Expected: %s" % reference</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002658
2659<p>The key object in that test is the handler, it provides a number of entry
2660points which can be called by the parser as it makes progresses to indicate
2661the information set obtained. The full set of callback is larger than what
2662the callback class in that specific example implements (see the SAX
2663definition for a complete list). The wrapper will only call those supplied by
2664the object when activated. The startElement receives the names of the element
Daniel Veillard63d83142002-05-20 06:51:05 +00002665and a dictionary containing the attributes carried by this element.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002666
2667<p>Also note that the reference string generated from the callback shows a
2668single character call even though the string "bar" is passed to the parser
2669from 2 different call to parseChunk()</p>
2670
2671<h3>xpath.py:</h3>
2672
Daniel Veillard63d83142002-05-20 06:51:05 +00002673<p>This is a basic test of XPath wrappers support</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002674<pre>import libxml2
2675
2676doc = libxml2.parseFile("tst.xml")
2677ctxt = doc.xpathNewContext()
2678res = ctxt.xpathEval("//*")
2679if len(res) != 2:
2680 print "xpath query: wrong node set size"
2681 sys.exit(1)
2682if res[0].name != "doc" or res[1].name != "foo":
2683 print "xpath query: wrong node set value"
2684 sys.exit(1)
2685doc.freeDoc()
2686ctxt.xpathFreeContext()</pre>
2687
2688<p>This test parses a file, then create an XPath context to evaluate XPath
2689expression on it. The xpathEval() method execute an XPath query and returns
2690the result mapped in a Python way. String and numbers are natively converted,
2691and node sets are returned as a tuple of libxml2 Python nodes wrappers. Like
Daniel Veillard63d83142002-05-20 06:51:05 +00002692the document, the XPath context need to be freed explicitly, also not that
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002693the result of the XPath query may point back to the document tree and hence
2694the document must be freed after the result of the query is used.</p>
2695
2696<h3>xpathext.py:</h3>
2697
2698<p>This test shows how to extend the XPath engine with functions written in
2699python:</p>
2700<pre>import libxml2
2701
2702def foo(ctx, x):
2703 return x + 1
2704
2705doc = libxml2.parseFile("tst.xml")
2706ctxt = doc.xpathNewContext()
2707libxml2.registerXPathFunction(ctxt._o, "foo", None, foo)
2708res = ctxt.xpathEval("foo(1)")
2709if res != 2:
2710 print "xpath extension failure"
2711doc.freeDoc()
2712ctxt.xpathFreeContext()</pre>
2713
2714<p>Note how the extension function is registered with the context (but that
Daniel Veillard63d83142002-05-20 06:51:05 +00002715part is not yet finalized, this may change slightly in the future).</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002716
2717<h3>tstxpath.py:</h3>
2718
Daniel Veillard63d83142002-05-20 06:51:05 +00002719<p>This test is similar to the previous one but shows how the extension
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002720function can access the XPath evaluation context:</p>
2721<pre>def foo(ctx, x):
2722 global called
2723
2724 #
2725 # test that access to the XPath evaluation contexts
2726 #
2727 pctxt = libxml2.xpathParserContext(_obj=ctx)
2728 ctxt = pctxt.context()
2729 called = ctxt.function()
2730 return x + 1</pre>
2731
2732<p>All the interfaces around the XPath parser(or rather evaluation) context
2733are not finalized, but it should be sufficient to do contextual work at the
2734evaluation point.</p>
2735
2736<h3>Memory debugging:</h3>
2737
2738<p>last but not least, all tests starts with the following prologue:</p>
2739<pre>#memory debug specific
Daniel Veillardaf43f632002-03-08 15:05:20 +00002740libxml2.debugMemory(1)</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002741
2742<p>and ends with the following epilogue:</p>
2743<pre>#memory debug specific
2744libxml2.cleanupParser()
2745if libxml2.debugMemory(1) == 0:
2746 print "OK"
2747else:
2748 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
2749 libxml2.dumpMemory()</pre>
2750
2751<p>Those activate the memory debugging interface of libxml2 where all
Daniel Veillard63d83142002-05-20 06:51:05 +00002752allocated block in the library are tracked. The prologue then cleans up the
Daniel Veillard6dbcaf82002-02-20 14:37:47 +00002753library state and checks that all allocated memory has been freed. If not it
2754calls dumpMemory() which saves that list in a <code>.memdump</code> file.</p>
Daniel Veillard82687162001-01-22 15:32:01 +00002755
Daniel Veillard8a469172003-06-12 16:05:07 +00002756<h2><a name="architecture">libxml2 architecture</a></h2>
Daniel Veillard4540be42000-08-19 16:40:28 +00002757
Daniel Veillard560c2a42003-07-06 21:13:49 +00002758<p>Libxml2 is made of multiple components; some of them are optional, and
2759most of the block interfaces are public. The main components are:</p>
Daniel Veillard4540be42000-08-19 16:40:28 +00002760<ul>
2761 <li>an Input/Output layer</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002762 <li>FTP and HTTP client layers (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002763 <li>an Internationalization layer managing the encodings support</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002764 <li>a URI module</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002765 <li>the XML parser and its basic SAX interface</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002766 <li>an HTML parser using the same SAX interface (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002767 <li>a SAX tree module to build an in-memory DOM representation</li>
2768 <li>a tree module to manipulate the DOM representation</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002769 <li>a validation module using the DOM representation (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002770 <li>an XPath module for global lookup in a DOM representation
Daniel Veillard91e9d582001-02-26 07:31:12 +00002771 (optional)</li>
2772 <li>a debug module (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +00002773</ul>
2774
2775<p>Graphically this gives the following:</p>
2776
2777<p><img src="libxml.gif" alt="a graphical view of the various"></p>
2778
2779<p></p>
2780
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002781<h2><a name="tree">The tree output</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002782
2783<p>The parser returns a tree built during the document analysis. The value
Daniel Veillard402e8c82000-02-29 22:57:47 +00002784returned is an <strong>xmlDocPtr</strong> (i.e., a pointer to an
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002785<strong>xmlDoc</strong> structure). This structure contains information such
Daniel Veillard306be992000-07-03 12:38:45 +00002786as the file name, the document type, and a <strong>children</strong> pointer
2787which is the root of the document (or more exactly the first child under the
2788root which is the document). The tree is made of <strong>xmlNode</strong>s,
Daniel Veillard91e9d582001-02-26 07:31:12 +00002789chained in double-linked lists of siblings and with a children&lt;-&gt;parent
Daniel Veillard306be992000-07-03 12:38:45 +00002790relationship. An xmlNode can also carry properties (a chain of xmlAttr
2791structures). An attribute may have a value which is a list of TEXT or
2792ENTITY_REF nodes.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002793
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002794<p>Here is an example (erroneous with respect to the XML spec since there
2795should be only one ELEMENT under the root):</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002796
2797<p><img src="structure.gif" alt=" structure.gif "></p>
2798
2799<p>In the source package there is a small program (not installed by default)
Daniel Veillard361d8452000-04-03 19:48:13 +00002800called <strong>xmllint</strong> which parses XML files given as argument and
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002801prints them back as parsed. This is useful for detecting errors both in XML
2802code and in the XML parser itself. It has an option <strong>--debug</strong>
Daniel Veillard91e9d582001-02-26 07:31:12 +00002803which prints the actual in-memory structure of the document; here is the
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00002804result with the <a href="#example">example</a> given before:</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002805<pre>DOCUMENT
2806version=1.0
2807standalone=true
2808 ELEMENT EXAMPLE
2809 ATTRIBUTE prop1
2810 TEXT
2811 content=gnome is great
2812 ATTRIBUTE prop2
2813 ENTITY_REF
2814 TEXT
Daniel Veillard0142b842000-01-14 14:45:24 +00002815 content= linux too
Daniel Veillard402e8c82000-02-29 22:57:47 +00002816 ELEMENT head
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002817 ELEMENT title
Daniel Veillard25940b71998-10-29 05:51:30 +00002818 TEXT
2819 content=Welcome to Gnome
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002820 ELEMENT chapter
2821 ELEMENT title
Daniel Veillard25940b71998-10-29 05:51:30 +00002822 TEXT
2823 content=The Linux adventure
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002824 ELEMENT p
Daniel Veillard25940b71998-10-29 05:51:30 +00002825 TEXT
2826 content=bla bla bla ...
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00002827 ELEMENT image
2828 ATTRIBUTE href
2829 TEXT
2830 content=linus.gif
2831 ELEMENT p
Daniel Veillard25940b71998-10-29 05:51:30 +00002832 TEXT
2833 content=...</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00002834
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002835<p>This should be useful for learning the internal representation model.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +00002836
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00002837<h2><a name="interface">The SAX interface</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002838
Daniel Veillard402e8c82000-02-29 22:57:47 +00002839<p>Sometimes the DOM tree output is just too large to fit reasonably into
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002840memory. In that case (and if you don't expect to save back the XML document
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00002841loaded using libxml), it's better to use the SAX interface of libxml. SAX is
2842a <strong>callback-based interface</strong> to the parser. Before parsing,
2843the application layer registers a customized set of callbacks which are
2844called by the library as it progresses through the XML input.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002845
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002846<p>To get more detailed step-by-step guidance on using the SAX interface of
Daniel Veillard4540be42000-08-19 16:40:28 +00002847libxml, see the <a
2848href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">nice
2849documentation</a>.written by <a href="mailto:james@daa.com.au">James
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002850Henstridge</a>.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002851
2852<p>You can debug the SAX behaviour by using the <strong>testSAX</strong>
2853program located in the gnome-xml module (it's usually not shipped in the
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002854binary packages of libxml, but you can find it in the tar source
Daniel Veillard402e8c82000-02-29 22:57:47 +00002855distribution). Here is the sequence of callbacks that would be reported by
Daniel Veillard88f00ae2000-03-02 00:15:55 +00002856testSAX when parsing the example XML document shown earlier:</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002857<pre>SAX.setDocumentLocator()
2858SAX.startDocument()
2859SAX.getEntity(amp)
2860SAX.startElement(EXAMPLE, prop1='gnome is great', prop2='&amp;amp; linux too')
2861SAX.characters( , 3)
2862SAX.startElement(head)
2863SAX.characters( , 4)
2864SAX.startElement(title)
2865SAX.characters(Welcome to Gnome, 16)
2866SAX.endElement(title)
2867SAX.characters( , 3)
2868SAX.endElement(head)
2869SAX.characters( , 3)
2870SAX.startElement(chapter)
2871SAX.characters( , 4)
2872SAX.startElement(title)
2873SAX.characters(The Linux adventure, 19)
2874SAX.endElement(title)
2875SAX.characters( , 4)
2876SAX.startElement(p)
2877SAX.characters(bla bla bla ..., 15)
2878SAX.endElement(p)
2879SAX.characters( , 4)
2880SAX.startElement(image, href='linus.gif')
2881SAX.endElement(image)
2882SAX.characters( , 4)
2883SAX.startElement(p)
2884SAX.characters(..., 3)
2885SAX.endElement(p)
2886SAX.characters( , 3)
2887SAX.endElement(chapter)
2888SAX.characters( , 1)
2889SAX.endElement(EXAMPLE)
2890SAX.endDocument()</pre>
2891
Daniel Veillard8a469172003-06-12 16:05:07 +00002892<p>Most of the other interfaces of libxml2 are based on the DOM tree-building
Daniel Veillardec70e912001-02-26 20:10:45 +00002893facility, so nearly everything up to the end of this document presupposes the
2894use of the standard DOM tree build. Note that the DOM tree itself is built by
2895a set of registered default callbacks, without internal specific
2896interface.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00002897
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002898<h2><a name="Validation">Validation &amp; DTDs</a></h2>
2899
2900<p>Table of Content:</p>
2901<ol>
2902 <li><a href="#General5">General overview</a></li>
2903 <li><a href="#definition">The definition</a></li>
2904 <li><a href="#Simple">Simple rules</a>
2905 <ol>
Daniel Veillard9c466822001-10-25 12:03:39 +00002906 <li><a href="#reference">How to reference a DTD from a document</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002907 <li><a href="#Declaring">Declaring elements</a></li>
2908 <li><a href="#Declaring1">Declaring attributes</a></li>
2909 </ol>
2910 </li>
2911 <li><a href="#Some">Some examples</a></li>
2912 <li><a href="#validate">How to validate</a></li>
2913 <li><a href="#Other">Other resources</a></li>
2914</ol>
2915
2916<h3><a name="General5">General overview</a></h3>
2917
2918<p>Well what is validation and what is a DTD ?</p>
2919
2920<p>DTD is the acronym for Document Type Definition. This is a description of
Daniel Veillard63d83142002-05-20 06:51:05 +00002921the content for a family of XML files. This is part of the XML 1.0
Daniel Veillard0b28e882002-07-24 23:47:05 +00002922specification, and allows one to describe and verify that a given document
2923instance conforms to the set of rules detailing its structure and content.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002924
2925<p>Validation is the process of checking a document against a DTD (more
2926generally against a set of construction rules).</p>
2927
2928<p>The validation process and building DTDs are the two most difficult parts
Daniel Veillard0b28e882002-07-24 23:47:05 +00002929of the XML life cycle. Briefly a DTD defines all the possible elements to be
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002930found within your document, what is the formal shape of your document tree
Daniel Veillard0b28e882002-07-24 23:47:05 +00002931(by defining the allowed content of an element; either text, a regular
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002932expression for the allowed list of children, or mixed content i.e. both text
Daniel Veillard42766c02002-08-22 20:52:17 +00002933and children). The DTD also defines the valid attributes for all elements and
2934the types of those attributes.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002935
2936<h3><a name="definition1">The definition</a></h3>
2937
2938<p>The <a href="http://www.w3.org/TR/REC-xml">W3C XML Recommendation</a> (<a
2939href="http://www.xml.com/axml/axml.html">Tim Bray's annotated version of
2940Rev1</a>):</p>
2941<ul>
2942 <li><a href="http://www.w3.org/TR/REC-xml#elemdecls">Declaring
2943 elements</a></li>
2944 <li><a href="http://www.w3.org/TR/REC-xml#attdecls">Declaring
2945 attributes</a></li>
2946</ul>
2947
2948<p>(unfortunately) all this is inherited from the SGML world, the syntax is
2949ancient...</p>
2950
2951<h3><a name="Simple1">Simple rules</a></h3>
2952
Daniel Veillard42766c02002-08-22 20:52:17 +00002953<p>Writing DTDs can be done in many ways. The rules to build them if you need
2954something permanent or something which can evolve over time can be radically
2955different. Really complex DTDs like DocBook ones are flexible but quite
2956harder to design. I will just focus on DTDs for a formats with a fixed simple
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002957structure. It is just a set of basic rules, and definitely not exhaustive nor
Daniel Veillard63d83142002-05-20 06:51:05 +00002958usable for complex DTD design.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002959
2960<h4><a name="reference1">How to reference a DTD from a document</a>:</h4>
2961
2962<p>Assuming the top element of the document is <code>spec</code> and the dtd
2963is placed in the file <code>mydtd</code> in the subdirectory
2964<code>dtds</code> of the directory from where the document were loaded:</p>
2965
2966<p><code>&lt;!DOCTYPE spec SYSTEM "dtds/mydtd"&gt;</code></p>
2967
2968<p>Notes:</p>
2969<ul>
Daniel Veillard0b28e882002-07-24 23:47:05 +00002970 <li>The system string is actually an URI-Reference (as defined in <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002971 href="http://www.ietf.org/rfc/rfc2396.txt">RFC 2396</a>) so you can use a
Daniel Veillard0b28e882002-07-24 23:47:05 +00002972 full URL string indicating the location of your DTD on the Web. This is a
2973 really good thing to do if you want others to validate your document.</li>
2974 <li>It is also possible to associate a <code>PUBLIC</code> identifier (a
Daniel Veillard63d83142002-05-20 06:51:05 +00002975 magic string) so that the DTD is looked up in catalogs on the client side
Daniel Veillard0b28e882002-07-24 23:47:05 +00002976 without having to locate it on the web.</li>
2977 <li>A DTD contains a set of element and attribute declarations, but they
Daniel Veillard63d83142002-05-20 06:51:05 +00002978 don't define what the root of the document should be. This is explicitly
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002979 told to the parser/validator as the first element of the
2980 <code>DOCTYPE</code> declaration.</li>
2981</ul>
2982
2983<h4><a name="Declaring2">Declaring elements</a>:</h4>
2984
2985<p>The following declares an element <code>spec</code>:</p>
2986
2987<p><code>&lt;!ELEMENT spec (front, body, back?)&gt;</code></p>
2988
Daniel Veillard0b28e882002-07-24 23:47:05 +00002989<p>It also expresses that the spec element contains one <code>front</code>,
Daniel Veillardc0801af2002-05-28 16:28:42 +00002990one <code>body</code> and one optional <code>back</code> children elements in
2991this order. The declaration of one element of the structure and its content
2992are done in a single declaration. Similarly the following declares
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002993<code>div1</code> elements:</p>
2994
Daniel Veillard51737272002-01-23 23:10:38 +00002995<p><code>&lt;!ELEMENT div1 (head, (p | list | note)*, div2?)&gt;</code></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002996
Daniel Veillard0b28e882002-07-24 23:47:05 +00002997<p>which means div1 contains one <code>head</code> then a series of optional
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00002998<code>p</code>, <code>list</code>s and <code>note</code>s and then an
2999optional <code>div2</code>. And last but not least an element can contain
3000text:</p>
3001
3002<p><code>&lt;!ELEMENT b (#PCDATA)&gt;</code></p>
3003
3004<p><code>b</code> contains text or being of mixed content (text and elements
3005in no particular order):</p>
3006
3007<p><code>&lt;!ELEMENT p (#PCDATA|a|ul|b|i|em)*&gt;</code></p>
3008
3009<p><code>p </code>can contain text or <code>a</code>, <code>ul</code>,
3010<code>b</code>, <code>i </code>or <code>em</code> elements in no particular
3011order.</p>
3012
3013<h4><a name="Declaring1">Declaring attributes</a>:</h4>
3014
Daniel Veillard0b28e882002-07-24 23:47:05 +00003015<p>Again the attributes declaration includes their content definition:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003016
3017<p><code>&lt;!ATTLIST termdef name CDATA #IMPLIED&gt;</code></p>
3018
3019<p>means that the element <code>termdef</code> can have a <code>name</code>
Daniel Veillard63d83142002-05-20 06:51:05 +00003020attribute containing text (<code>CDATA</code>) and which is optional
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003021(<code>#IMPLIED</code>). The attribute value can also be defined within a
3022set:</p>
3023
3024<p><code>&lt;!ATTLIST list type (bullets|ordered|glossary)
3025"ordered"&gt;</code></p>
3026
3027<p>means <code>list</code> element have a <code>type</code> attribute with 3
3028allowed values "bullets", "ordered" or "glossary" and which default to
Daniel Veillard63d83142002-05-20 06:51:05 +00003029"ordered" if the attribute is not explicitly specified.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003030
3031<p>The content type of an attribute can be text (<code>CDATA</code>),
3032anchor/reference/references
3033(<code>ID</code>/<code>IDREF</code>/<code>IDREFS</code>), entity(ies)
3034(<code>ENTITY</code>/<code>ENTITIES</code>) or name(s)
3035(<code>NMTOKEN</code>/<code>NMTOKENS</code>). The following defines that a
3036<code>chapter</code> element can have an optional <code>id</code> attribute
3037of type <code>ID</code>, usable for reference from attribute of type
3038IDREF:</p>
3039
3040<p><code>&lt;!ATTLIST chapter id ID #IMPLIED&gt;</code></p>
3041
3042<p>The last value of an attribute definition can be <code>#REQUIRED
3043</code>meaning that the attribute has to be given, <code>#IMPLIED</code>
3044meaning that it is optional, or the default value (possibly prefixed by
3045<code>#FIXED</code> if it is the only allowed).</p>
3046
3047<p>Notes:</p>
3048<ul>
Daniel Veillard0b28e882002-07-24 23:47:05 +00003049 <li>Usually the attributes pertaining to a given element are declared in a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003050 single expression, but it is just a convention adopted by a lot of DTD
3051 writers:
3052 <pre>&lt;!ATTLIST termdef
3053 id ID #REQUIRED
3054 name CDATA #IMPLIED&gt;</pre>
3055 <p>The previous construct defines both <code>id</code> and
Daniel Veillard0b28e882002-07-24 23:47:05 +00003056 <code>name</code> attributes for the element <code>termdef</code>.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003057 </li>
3058</ul>
3059
3060<h3><a name="Some1">Some examples</a></h3>
3061
Daniel Veillard8a469172003-06-12 16:05:07 +00003062<p>The directory <code>test/valid/dtds/</code> in the libxml2 distribution
Daniel Veillard42766c02002-08-22 20:52:17 +00003063contains some complex DTD examples. The example in the file
3064<code>test/valid/dia.xml</code> shows an XML file where the simple DTD is
3065directly included within the document.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003066
3067<h3><a name="validate1">How to validate</a></h3>
3068
Daniel Veillard0b28e882002-07-24 23:47:05 +00003069<p>The simplest way is to use the xmllint program included with libxml. The
3070<code>--valid</code> option turns-on validation of the files given as input.
3071For example the following validates a copy of the first revision of the XML
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000030721.0 specification:</p>
3073
3074<p><code>xmllint --valid --noout test/valid/REC-xml-19980210.xml</code></p>
3075
Daniel Veillard0b28e882002-07-24 23:47:05 +00003076<p>the -- noout is used to disable output of the resulting tree.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003077
Daniel Veillard42766c02002-08-22 20:52:17 +00003078<p>The <code>--dtdvalid dtd</code> allows validation of the document(s)
3079against a given DTD.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003080
Daniel Veillard8a469172003-06-12 16:05:07 +00003081<p>Libxml2 exports an API to handle DTDs and validation, check the <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003082href="http://xmlsoft.org/html/libxml-valid.html">associated
3083description</a>.</p>
3084
3085<h3><a name="Other1">Other resources</a></h3>
3086
3087<p>DTDs are as old as SGML. So there may be a number of examples on-line, I
3088will just list one for now, others pointers welcome:</p>
3089<ul>
3090 <li><a href="http://www.xml101.com:8081/dtd/">XML-101 DTD</a></li>
3091</ul>
3092
3093<p>I suggest looking at the examples found under test/valid/dtd and any of
3094the large number of books available on XML. The dia example in test/valid
3095should be both simple and complete enough to allow you to build your own.</p>
3096
3097<p></p>
3098
3099<h2><a name="Memory">Memory Management</a></h2>
3100
3101<p>Table of Content:</p>
3102<ol>
3103 <li><a href="#General3">General overview</a></li>
Daniel Veillard8a469172003-06-12 16:05:07 +00003104 <li><a href="#setting">Setting libxml2 set of memory routines</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003105 <li><a href="#cleanup">Cleaning up after parsing</a></li>
3106 <li><a href="#Debugging">Debugging routines</a></li>
3107 <li><a href="#General4">General memory requirements</a></li>
3108</ol>
3109
3110<h3><a name="General3">General overview</a></h3>
3111
3112<p>The module <code><a
3113href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlmemory.h</a></code>
Daniel Veillard8a469172003-06-12 16:05:07 +00003114provides the interfaces to the libxml2 memory system:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003115<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +00003116 <li>libxml2 does not use the libc memory allocator directly but xmlFree(),
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003117 xmlMalloc() and xmlRealloc()</li>
3118 <li>those routines can be reallocated to a specific set of routine, by
3119 default the libc ones i.e. free(), malloc() and realloc()</li>
3120 <li>the xmlmemory.c module includes a set of debugging routine</li>
3121</ul>
3122
Daniel Veillard8a469172003-06-12 16:05:07 +00003123<h3><a name="setting">Setting libxml2 set of memory routines</a></h3>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003124
3125<p>It is sometimes useful to not use the default memory allocator, either for
3126debugging, analysis or to implement a specific behaviour on memory management
3127(like on embedded systems). Two function calls are available to do so:</p>
3128<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +00003129 <li><a href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemGet
3130 ()</a> which return the current set of functions in use by the parser</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003131 <li><a
3132 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemSetup()</a>
Daniel Veillardaf43f632002-03-08 15:05:20 +00003133 which allow to set up a new set of memory allocation functions</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003134</ul>
3135
3136<p>Of course a call to xmlMemSetup() should probably be done before calling
Daniel Veillard8a469172003-06-12 16:05:07 +00003137any other libxml2 routines (unless you are sure your allocations routines are
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003138compatibles).</p>
3139
3140<h3><a name="cleanup">Cleaning up after parsing</a></h3>
3141
Daniel Veillard8a469172003-06-12 16:05:07 +00003142<p>Libxml2 is not stateless, there is a few set of memory structures needing
Daniel Veillard63d83142002-05-20 06:51:05 +00003143allocation before the parser is fully functional (some encoding structures
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003144for example). This also mean that once parsing is finished there is a tiny
3145amount of memory (a few hundred bytes) which can be recollected if you don't
3146reuse the parser immediately:</p>
3147<ul>
3148 <li><a href="http://xmlsoft.org/html/libxml-parser.html">xmlCleanupParser
Daniel Veillardaf43f632002-03-08 15:05:20 +00003149 ()</a> is a centralized routine to free the parsing states. Note that it
3150 won't deallocate any produced tree if any (use the xmlFreeDoc() and
3151 related routines for this).</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003152 <li><a href="http://xmlsoft.org/html/libxml-parser.html">xmlInitParser
Daniel Veillardaf43f632002-03-08 15:05:20 +00003153 ()</a> is the dual routine allowing to preallocate the parsing state
3154 which can be useful for example to avoid initialization reentrancy
Daniel Veillard8a469172003-06-12 16:05:07 +00003155 problems when using libxml2 in multithreaded applications</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003156</ul>
3157
3158<p>Generally xmlCleanupParser() is safe, if needed the state will be rebuild
3159at the next invocation of parser routines, but be careful of the consequences
3160in multithreaded applications.</p>
3161
3162<h3><a name="Debugging">Debugging routines</a></h3>
3163
Daniel Veillard8a469172003-06-12 16:05:07 +00003164<p>When configured using --with-mem-debug flag (off by default), libxml2 uses
Daniel Veillard63d83142002-05-20 06:51:05 +00003165a set of memory allocation debugging routines keeping track of all allocated
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003166blocks and the location in the code where the routine was called. A couple of
3167other debugging routines allow to dump the memory allocated infos to a file
3168or call a specific routine when a given block number is allocated:</p>
3169<ul>
3170 <li><a
3171 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMallocLoc()</a>
Daniel Veillardaf43f632002-03-08 15:05:20 +00003172 <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003173 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlReallocLoc()</a>
3174 and <a
3175 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemStrdupLoc()</a>
3176 are the memory debugging replacement allocation routines</li>
3177 <li><a href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemoryDump
Daniel Veillardaf43f632002-03-08 15:05:20 +00003178 ()</a> dumps all the informations about the allocated memory block lefts
3179 in the <code>.memdump</code> file</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003180</ul>
3181
Daniel Veillard8a469172003-06-12 16:05:07 +00003182<p>When developing libxml2 memory debug is enabled, the tests programs call
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003183xmlMemoryDump () and the "make test" regression tests will check for any
3184memory leak during the full regression test sequence, this helps a lot
Daniel Veillard8a469172003-06-12 16:05:07 +00003185ensuring that libxml2 does not leak memory and bullet proof memory
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003186allocations use (some libc implementations are known to be far too permissive
3187resulting in major portability problems!).</p>
3188
3189<p>If the .memdump reports a leak, it displays the allocation function and
3190also tries to give some informations about the content and structure of the
3191allocated blocks left. This is sufficient in most cases to find the culprit,
Daniel Veillard63d83142002-05-20 06:51:05 +00003192but not always. Assuming the allocation problem is reproducible, it is
3193possible to find more easily:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003194<ol>
3195 <li>write down the block number xxxx not allocated</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00003196 <li>export the environment variable XML_MEM_BREAKPOINT=xxxx , the easiest
Daniel Veillard75794822002-04-11 16:24:32 +00003197 when using GDB is to simply give the command
3198 <p><code>set environment XML_MEM_BREAKPOINT xxxx</code></p>
3199 <p>before running the program.</p>
3200 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003201 <li>run the program under a debugger and set a breakpoint on
3202 xmlMallocBreakpoint() a specific function called when this precise block
3203 is allocated</li>
3204 <li>when the breakpoint is reached you can then do a fine analysis of the
3205 allocation an step to see the condition resulting in the missing
3206 deallocation.</li>
3207</ol>
3208
Daniel Veillard8a469172003-06-12 16:05:07 +00003209<p>I used to use a commercial tool to debug libxml2 memory problems but after
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003210noticing that it was not detecting memory leaks that simple mechanism was
Daniel Veillard75794822002-04-11 16:24:32 +00003211used and proved extremely efficient until now. Lately I have also used <a
3212href="http://developer.kde.org/~sewardj/">valgrind</a> with quite some
3213success, it is tied to the i386 architecture since it works by emulating the
3214processor and instruction set, it is slow but extremely efficient, i.e. it
3215spot memory usage errors in a very precise way.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003216
3217<h3><a name="General4">General memory requirements</a></h3>
3218
Daniel Veillard8a469172003-06-12 16:05:07 +00003219<p>How much libxml2 memory require ? It's hard to tell in average it depends
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003220of a number of things:</p>
3221<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00003222 <li>the parser itself should work in a fixed amount of memory, except for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003223 information maintained about the stacks of names and entities locations.
3224 The I/O and encoding handlers will probably account for a few KBytes.
3225 This is true for both the XML and HTML parser (though the HTML parser
3226 need more state).</li>
3227 <li>If you are generating the DOM tree then memory requirements will grow
Daniel Veillard63d83142002-05-20 06:51:05 +00003228 nearly linear with the size of the data. In general for a balanced
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003229 textual document the internal memory requirement is about 4 times the
Daniel Veillard63d83142002-05-20 06:51:05 +00003230 size of the UTF8 serialization of this document (example the XML-1.0
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003231 recommendation is a bit more of 150KBytes and takes 650KBytes of main
3232 memory when parsed). Validation will add a amount of memory required for
3233 maintaining the external Dtd state which should be linear with the
3234 complexity of the content model defined by the Dtd</li>
Daniel Veillardce192eb2003-04-16 15:58:05 +00003235 <li>If you need to work with fixed memory requirements or don't need the
3236 full DOM tree then using the <a href="xmlreader.html">xmlReader
3237 interface</a> is probably the best way to proceed, it still allows to
3238 validate or operate on subset of the tree if needed.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +00003239 <li>If you don't care about the advanced features of libxml2 like
Daniel Veillardce192eb2003-04-16 15:58:05 +00003240 validation, DOM, XPath or XPointer, don't use entities, need to work with
3241 fixed memory requirements, and try to get the fastest parsing possible
3242 then the SAX interface should be used, but it has known restrictions.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003243</ul>
3244
3245<p></p>
3246
3247<h2><a name="Encodings">Encodings support</a></h2>
3248
Daniel Veillarde5d68de2005-03-10 15:03:40 +00003249<p>If you are not really familiar with Internationalization (usual shortcut
3250is I18N) , Unicode, characters and glyphs, I suggest you read a <a
3251href="http://www.tbray.org/ongoing/When/200x/2003/04/06/Unicode">presentation</a>
3252by Tim Bray on Unicode and why you should care about it.</p>
3253<p>If you don't understand why <b>it does not make sense to have a string
3254without knowing what encoding it uses</b>, then as Joel Spolsky said
3255<a href="http://www.joelonsoftware.com/articles/Unicode.html">please do
3256not write another line of code until you finish reading that article.</a>.
3257It is a prerequisite to understand this page, and avoid a lot of problems
3258with libxml2, XML or text processing in general.</p>
3259
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003260<p>Table of Content:</p>
3261<ol>
3262 <li><a href="encoding.html#What">What does internationalization support
3263 mean ?</a></li>
3264 <li><a href="encoding.html#internal">The internal encoding, how and
3265 why</a></li>
3266 <li><a href="encoding.html#implemente">How is it implemented ?</a></li>
3267 <li><a href="encoding.html#Default">Default supported encodings</a></li>
3268 <li><a href="encoding.html#extend">How to extend the existing
3269 support</a></li>
3270</ol>
3271
3272<h3><a name="What">What does internationalization support mean ?</a></h3>
3273
3274<p>XML was designed from the start to allow the support of any character set
3275by using Unicode. Any conformant XML parser has to support the UTF-8 and
3276UTF-16 default encodings which can both express the full unicode ranges. UTF8
Daniel Veillard63d83142002-05-20 06:51:05 +00003277is a variable length encoding whose greatest points are to reuse the same
3278encoding for ASCII and to save space for Western encodings, but it is a bit
Daniel Veillardabfca612004-01-07 23:38:02 +00003279more complex to handle in practice. UTF-16 use 2 bytes per character (and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003280sometimes combines two pairs), it makes implementation easier, but looks a
3281bit overkill for Western languages encoding. Moreover the XML specification
Daniel Veillard189f46b2004-01-25 21:03:04 +00003282allows the document to be encoded in other encodings at the condition that
3283they are clearly labeled as such. For example the following is a wellformed
3284XML document encoded in ISO-8859-1 and using accentuated letters that we
3285French like for both markup and content:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003286<pre>&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
3287&lt;très&gt;là&lt;/très&gt;</pre>
3288
Daniel Veillard8a469172003-06-12 16:05:07 +00003289<p>Having internationalization support in libxml2 means the following:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003290<ul>
3291 <li>the document is properly parsed</li>
3292 <li>informations about it's encoding are saved</li>
3293 <li>it can be modified</li>
3294 <li>it can be saved in its original encoding</li>
Daniel Veillard8a469172003-06-12 16:05:07 +00003295 <li>it can also be saved in another encoding supported by libxml2 (for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003296 example straight UTF8 or even an ASCII form)</li>
3297</ul>
3298
Daniel Veillard8a469172003-06-12 16:05:07 +00003299<p>Another very important point is that the whole libxml2 API, with the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003300exception of a few routines to read with a specific encoding or save to a
3301specific encoding, is completely agnostic about the original encoding of the
3302document.</p>
3303
Daniel Veillard8a469172003-06-12 16:05:07 +00003304<p>It should be noted too that the HTML parser embedded in libxml2 now obey
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003305the same rules too, the following document will be (as of 2.2.2) handled in
Daniel Veillard8a469172003-06-12 16:05:07 +00003306an internationalized fashion by libxml2 too:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003307<pre>&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
3308 "http://www.w3.org/TR/REC-html40/loose.dtd"&gt;
3309&lt;html lang="fr"&gt;
3310&lt;head&gt;
3311 &lt;META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"&gt;
3312&lt;/head&gt;
3313&lt;body&gt;
3314&lt;p&gt;W3C crée des standards pour le Web.&lt;/body&gt;
3315&lt;/html&gt;</pre>
3316
3317<h3><a name="internal">The internal encoding, how and why</a></h3>
3318
Daniel Veillardabfca612004-01-07 23:38:02 +00003319<p>One of the core decisions was to force all documents to be converted to a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003320default internal encoding, and that encoding to be UTF-8, here are the
Daniel Veillardabfca612004-01-07 23:38:02 +00003321rationales for those choices:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003322<ul>
3323 <li>keeping the native encoding in the internal form would force the libxml
3324 users (or the code associated) to be fully aware of the encoding of the
3325 original document, for examples when adding a text node to a document,
3326 the content would have to be provided in the document encoding, i.e. the
3327 client code would have to check it before hand, make sure it's conformant
3328 to the encoding, etc ... Very hard in practice, though in some specific
3329 cases this may make sense.</li>
3330 <li>the second decision was which encoding. From the XML spec only UTF8 and
3331 UTF16 really makes sense as being the two only encodings for which there
Daniel Veillard63d83142002-05-20 06:51:05 +00003332 is mandatory support. UCS-4 (32 bits fixed size encoding) could be
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003333 considered an intelligent choice too since it's a direct Unicode mapping
3334 support. I selected UTF-8 on the basis of efficiency and compatibility
3335 with surrounding software:
3336 <ul>
3337 <li>UTF-8 while a bit more complex to convert from/to (i.e. slightly
3338 more costly to import and export CPU wise) is also far more compact
3339 than UTF-16 (and UCS-4) for a majority of the documents I see it used
3340 for right now (RPM RDF catalogs, advogato data, various configuration
3341 file formats, etc.) and the key point for today's computer
3342 architecture is efficient uses of caches. If one nearly double the
3343 memory requirement to store the same amount of data, this will trash
3344 caches (main memory/external caches/internal caches) and my take is
3345 that this harms the system far more than the CPU requirements needed
3346 for the conversion to UTF-8</li>
Daniel Veillard8a469172003-06-12 16:05:07 +00003347 <li>Most of libxml2 version 1 users were using it with straight ASCII
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003348 most of the time, doing the conversion with an internal encoding
3349 requiring all their code to be rewritten was a serious show-stopper
3350 for using UTF-16 or UCS-4.</li>
3351 <li>UTF-8 is being used as the de-facto internal encoding standard for
3352 related code like the <a href="http://www.pango.org/">pango</a>
Daniel Veillardabfca612004-01-07 23:38:02 +00003353 upcoming Gnome text widget, and a lot of Unix code (yet another place
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003354 where Unix programmer base takes a different approach from Microsoft
3355 - they are using UTF-16)</li>
3356 </ul>
3357 </li>
3358</ul>
3359
Daniel Veillard8a469172003-06-12 16:05:07 +00003360<p>What does this mean in practice for the libxml2 user:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003361<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +00003362 <li>xmlChar, the libxml2 data type is a byte, those bytes must be assembled
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003363 as UTF-8 valid strings. The proper way to terminate an xmlChar * string
3364 is simply to append 0 byte, as usual.</li>
3365 <li>One just need to make sure that when using chars outside the ASCII set,
3366 the values has been properly converted to UTF-8</li>
3367</ul>
3368
3369<h3><a name="implemente">How is it implemented ?</a></h3>
3370
3371<p>Let's describe how all this works within libxml, basically the I18N
3372(internationalization) support get triggered only during I/O operation, i.e.
3373when reading a document or saving one. Let's look first at the reading
3374sequence:</p>
3375<ol>
3376 <li>when a document is processed, we usually don't know the encoding, a
Daniel Veillard189f46b2004-01-25 21:03:04 +00003377 simple heuristic allows to detect UTF-16 and UCS-4 from encodings where
3378 the ASCII range (0-0x7F) maps with ASCII</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003379 <li>the xml declaration if available is parsed, including the encoding
3380 declaration. At that point, if the autodetected encoding is different
3381 from the one declared a call to xmlSwitchEncoding() is issued.</li>
3382 <li>If there is no encoding declaration, then the input has to be in either
3383 UTF-8 or UTF-16, if it is not then at some point when processing the
3384 input, the converter/checker of UTF-8 form will raise an encoding error.
3385 You may end-up with a garbled document, or no document at all ! Example:
3386 <pre>~/XML -&gt; ./xmllint err.xml
3387err.xml:1: error: Input is not proper UTF-8, indicate encoding !
3388&lt;très&gt;là&lt;/très&gt;
3389 ^
3390err.xml:1: error: Bytes: 0xE8 0x73 0x3E 0x6C
3391&lt;très&gt;là&lt;/très&gt;
3392 ^</pre>
3393 </li>
Daniel Veillard63d83142002-05-20 06:51:05 +00003394 <li>xmlSwitchEncoding() does an encoding name lookup, canonicalize it, and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003395 then search the default registered encoding converters for that encoding.
3396 If it's not within the default set and iconv() support has been compiled
3397 it, it will ask iconv for such an encoder. If this fails then the parser
3398 will report an error and stops processing:
3399 <pre>~/XML -&gt; ./xmllint err2.xml
3400err2.xml:1: error: Unsupported encoding UnsupportedEnc
3401&lt;?xml version="1.0" encoding="UnsupportedEnc"?&gt;
3402 ^</pre>
3403 </li>
Daniel Veillard46c5c1d2002-05-20 07:15:54 +00003404 <li>From that point the encoder processes progressively the input (it is
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003405 plugged as a front-end to the I/O module) for that entity. It captures
Daniel Veillardabfca612004-01-07 23:38:02 +00003406 and converts on-the-fly the document to be parsed to UTF-8. The parser
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003407 itself just does UTF-8 checking of this input and process it
3408 transparently. The only difference is that the encoding information has
3409 been added to the parsing context (more precisely to the input
3410 corresponding to this entity).</li>
3411 <li>The result (when using DOM) is an internal form completely in UTF-8
3412 with just an encoding information on the document node.</li>
3413</ol>
3414
Daniel Veillard63d83142002-05-20 06:51:05 +00003415<p>Ok then what happens when saving the document (assuming you
3416collected/built an xmlDoc DOM like structure) ? It depends on the function
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003417called, xmlSaveFile() will just try to save in the original encoding, while
3418xmlSaveFileTo() and xmlSaveFileEnc() can optionally save to a given
3419encoding:</p>
3420<ol>
Daniel Veillard8a469172003-06-12 16:05:07 +00003421 <li>if no encoding is given, libxml2 will look for an encoding value
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003422 associated to the document and if it exists will try to save to that
3423 encoding,
3424 <p>otherwise everything is written in the internal form, i.e. UTF-8</p>
3425 </li>
3426 <li>so if an encoding was specified, either at the API level or on the
Daniel Veillard8a469172003-06-12 16:05:07 +00003427 document, libxml2 will again canonicalize the encoding name, lookup for a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003428 converter in the registered set or through iconv. If not found the
3429 function will return an error code</li>
3430 <li>the converter is placed before the I/O buffer layer, as another kind of
Daniel Veillard8a469172003-06-12 16:05:07 +00003431 buffer, then libxml2 will simply push the UTF-8 serialization to through
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003432 that buffer, which will then progressively be converted and pushed onto
3433 the I/O layer.</li>
3434 <li>It is possible that the converter code fails on some input, for example
Daniel Veillard63d83142002-05-20 06:51:05 +00003435 trying to push an UTF-8 encoded Chinese character through the UTF-8 to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003436 ISO-8859-1 converter won't work. Since the encoders are progressive they
3437 will just report the error and the number of bytes converted, at that
Daniel Veillard8a469172003-06-12 16:05:07 +00003438 point libxml2 will decode the offending character, remove it from the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003439 buffer and replace it with the associated charRef encoding &amp;#123; and
Daniel Veillard63d83142002-05-20 06:51:05 +00003440 resume the conversion. This guarantees that any document will be saved
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003441 without losses (except for markup names where this is not legal, this is
Daniel Veillard63d83142002-05-20 06:51:05 +00003442 a problem in the current version, in practice avoid using non-ascii
Daniel Veillard189f46b2004-01-25 21:03:04 +00003443 characters for tag or attribute names). A special "ascii" encoding name
3444 is used to save documents to a pure ascii form can be used when
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003445 portability is really crucial</li>
3446</ol>
3447
Daniel Veillardabfca612004-01-07 23:38:02 +00003448<p>Here are a few examples based on the same test document:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003449<pre>~/XML -&gt; ./xmllint isolat1
3450&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
3451&lt;très&gt;là&lt;/très&gt;
3452~/XML -&gt; ./xmllint --encode UTF-8 isolat1
3453&lt;?xml version="1.0" encoding="UTF-8"?&gt;
3454&lt;très&gt;là  &lt;/très&gt;
3455~/XML -&gt; </pre>
3456
3457<p>The same processing is applied (and reuse most of the code) for HTML I18N
3458processing. Looking up and modifying the content encoding is a bit more
3459difficult since it is located in a &lt;meta&gt; tag under the &lt;head&gt;,
3460so a couple of functions htmlGetMetaEncoding() and htmlSetMetaEncoding() have
3461been provided. The parser also attempts to switch encoding on the fly when
3462detecting such a tag on input. Except for that the processing is the same
3463(and again reuses the same code).</p>
3464
3465<h3><a name="Default">Default supported encodings</a></h3>
3466
Daniel Veillard8a469172003-06-12 16:05:07 +00003467<p>libxml2 has a set of default converters for the following encodings
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003468(located in encoding.c):</p>
3469<ol>
3470 <li>UTF-8 is supported by default (null handlers)</li>
3471 <li>UTF-16, both little and big endian</li>
3472 <li>ISO-Latin-1 (ISO-8859-1) covering most western languages</li>
3473 <li>ASCII, useful mostly for saving</li>
3474 <li>HTML, a specific handler for the conversion of UTF-8 to ASCII with HTML
3475 predefined entities like &amp;copy; for the Copyright sign.</li>
3476</ol>
3477
Daniel Veillardc0801af2002-05-28 16:28:42 +00003478<p>More over when compiled on an Unix platform with iconv support the full
3479set of encodings supported by iconv can be instantly be used by libxml. On a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003480linux machine with glibc-2.1 the list of supported encodings and aliases fill
34813 full pages, and include UCS-4, the full set of ISO-Latin encodings, and the
3482various Japanese ones.</p>
Daniel Veillardfdba0de2005-09-16 08:19:43 +00003483<p>To convert from the UTF-8 values returned from the API to another encoding
3484then it is possible to use the function provided from
3485<a href="html/libxml-encoding.html">the encoding module</a> like
3486<a href="html/libxml-encoding.html#UTF8Toisolat1">UTF8Toisolat1</a>, or
3487use the POSIX
3488<a href="http://www.opengroup.org/onlinepubs/009695399/functions/iconv.html"
3489>iconv()</a> API directly.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003490
3491<h4>Encoding aliases</h4>
3492
Daniel Veillard8a469172003-06-12 16:05:07 +00003493<p>From 2.2.3, libxml2 has support to register encoding names aliases. The
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003494goal is to be able to parse document whose encoding is supported but where
3495the name differs (for example from the default set of names accepted by
3496iconv). The following functions allow to register and handle new aliases for
Daniel Veillard8a469172003-06-12 16:05:07 +00003497existing encodings. Once registered libxml2 will automatically lookup the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003498aliases when handling a document:</p>
3499<ul>
3500 <li>int xmlAddEncodingAlias(const char *name, const char *alias);</li>
3501 <li>int xmlDelEncodingAlias(const char *alias);</li>
3502 <li>const char * xmlGetEncodingAlias(const char *alias);</li>
3503 <li>void xmlCleanupEncodingAliases(void);</li>
3504</ul>
3505
3506<h3><a name="extend">How to extend the existing support</a></h3>
3507
3508<p>Well adding support for new encoding, or overriding one of the encoders
Daniel Veillardabfca612004-01-07 23:38:02 +00003509(assuming it is buggy) should not be hard, just write input and output
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003510conversion routines to/from UTF-8, and register them using
3511xmlNewCharEncodingHandler(name, xxxToUTF8, UTF8Toxxx), and they will be
3512called automatically if the parser(s) encounter such an encoding name
3513(register it uppercase, this will help). The description of the encoders,
3514their arguments and expected return values are described in the encoding.h
3515header.</p>
3516
3517<p>A quick note on the topic of subverting the parser to use a different
3518internal encoding than UTF-8, in some case people will absolutely want to
3519keep the internal encoding different, I think it's still possible (but the
3520encoding must be compliant with ASCII on the same subrange) though I didn't
3521tried it. The key is to override the default conversion routines (by
3522registering null encoders/decoders for your charsets), and bypass the UTF-8
3523checking of the parser by setting the parser context charset
3524(ctxt-&gt;charset) to something different than XML_CHAR_ENCODING_UTF8, but
Daniel Veillard63d83142002-05-20 06:51:05 +00003525there is no guarantee that this will work. You may also have some troubles
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003526saving back.</p>
3527
3528<p>Basically proper I18N support is important, this requires at least
3529libxml-2.0.0, but a lot of features and corrections are really available only
3530starting 2.2.</p>
3531
3532<h2><a name="IO">I/O Interfaces</a></h2>
3533
3534<p>Table of Content:</p>
3535<ol>
3536 <li><a href="#General1">General overview</a></li>
3537 <li><a href="#basic">The basic buffer type</a></li>
3538 <li><a href="#Input">Input I/O handlers</a></li>
3539 <li><a href="#Output">Output I/O handlers</a></li>
3540 <li><a href="#entities">The entities loader</a></li>
3541 <li><a href="#Example2">Example of customized I/O</a></li>
3542</ol>
3543
3544<h3><a name="General1">General overview</a></h3>
3545
3546<p>The module <code><a
3547href="http://xmlsoft.org/html/libxml-xmlio.html">xmlIO.h</a></code> provides
Daniel Veillard8a469172003-06-12 16:05:07 +00003548the interfaces to the libxml2 I/O system. This consists of 4 main parts:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003549<ul>
3550 <li>Entities loader, this is a routine which tries to fetch the entities
3551 (files) based on their PUBLIC and SYSTEM identifiers. The default loader
Daniel Veillard8a469172003-06-12 16:05:07 +00003552 don't look at the public identifier since libxml2 do not maintain a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003553 catalog. You can redefine you own entity loader by using
3554 <code>xmlGetExternalEntityLoader()</code> and
Daniel Veillard9c466822001-10-25 12:03:39 +00003555 <code>xmlSetExternalEntityLoader()</code>. <a href="#entities">Check the
3556 example</a>.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003557 <li>Input I/O buffers which are a commodity structure used by the parser(s)
3558 input layer to handle fetching the informations to feed the parser. This
3559 provides buffering and is also a placeholder where the encoding
Daniel Veillard63d83142002-05-20 06:51:05 +00003560 converters to UTF8 are piggy-backed.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003561 <li>Output I/O buffers are similar to the Input ones and fulfill similar
3562 task but when generating a serialization from a tree.</li>
3563 <li>A mechanism to register sets of I/O callbacks and associate them with
3564 specific naming schemes like the protocol part of the URIs.
3565 <p>This affect the default I/O operations and allows to use specific I/O
3566 handlers for certain names.</p>
3567 </li>
3568</ul>
3569
3570<p>The general mechanism used when loading http://rpmfind.net/xml.html for
3571example in the HTML parser is the following:</p>
3572<ol>
3573 <li>The default entity loader calls <code>xmlNewInputFromFile()</code> with
3574 the parsing context and the URI string.</li>
3575 <li>the URI string is checked against the existing registered handlers
3576 using their match() callback function, if the HTTP module was compiled
3577 in, it is registered and its match() function will succeeds</li>
3578 <li>the open() function of the handler is called and if successful will
3579 return an I/O Input buffer</li>
3580 <li>the parser will the start reading from this buffer and progressively
3581 fetch information from the resource, calling the read() function of the
3582 handler until the resource is exhausted</li>
3583 <li>if an encoding change is detected it will be installed on the input
3584 buffer, providing buffering and efficient use of the conversion
3585 routines</li>
3586 <li>once the parser has finished, the close() function of the handler is
Daniel Veillard63d83142002-05-20 06:51:05 +00003587 called once and the Input buffer and associated resources are
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003588 deallocated.</li>
3589</ol>
3590
3591<p>The user defined callbacks are checked first to allow overriding of the
Daniel Veillard8a469172003-06-12 16:05:07 +00003592default libxml2 I/O routines.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003593
3594<h3><a name="basic">The basic buffer type</a></h3>
3595
3596<p>All the buffer manipulation handling is done using the
3597<code>xmlBuffer</code> type define in <code><a
3598href="http://xmlsoft.org/html/libxml-tree.html">tree.h</a> </code>which is a
3599resizable memory buffer. The buffer allocation strategy can be selected to be
3600either best-fit or use an exponential doubling one (CPU vs. memory use
Daniel Veillard63d83142002-05-20 06:51:05 +00003601trade-off). The values are <code>XML_BUFFER_ALLOC_EXACT</code> and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003602<code>XML_BUFFER_ALLOC_DOUBLEIT</code>, and can be set individually or on a
3603system wide basis using <code>xmlBufferSetAllocationScheme()</code>. A number
3604of functions allows to manipulate buffers with names starting with the
3605<code>xmlBuffer...</code> prefix.</p>
3606
3607<h3><a name="Input">Input I/O handlers</a></h3>
3608
3609<p>An Input I/O handler is a simple structure
3610<code>xmlParserInputBuffer</code> containing a context associated to the
3611resource (file descriptor, or pointer to a protocol handler), the read() and
3612close() callbacks to use and an xmlBuffer. And extra xmlBuffer and a charset
3613encoding handler are also present to support charset conversion when
3614needed.</p>
3615
3616<h3><a name="Output">Output I/O handlers</a></h3>
3617
3618<p>An Output handler <code>xmlOutputBuffer</code> is completely similar to an
3619Input one except the callbacks are write() and close().</p>
3620
3621<h3><a name="entities">The entities loader</a></h3>
3622
3623<p>The entity loader resolves requests for new entities and create inputs for
3624the parser. Creating an input from a filename or an URI string is done
3625through the xmlNewInputFromFile() routine. The default entity loader do not
3626handle the PUBLIC identifier associated with an entity (if any). So it just
3627calls xmlNewInputFromFile() with the SYSTEM identifier (which is mandatory in
3628XML).</p>
3629
3630<p>If you want to hook up a catalog mechanism then you simply need to
3631override the default entity loader, here is an example:</p>
3632<pre>#include &lt;libxml/xmlIO.h&gt;
3633
3634xmlExternalEntityLoader defaultLoader = NULL;
3635
3636xmlParserInputPtr
3637xmlMyExternalEntityLoader(const char *URL, const char *ID,
3638 xmlParserCtxtPtr ctxt) {
3639 xmlParserInputPtr ret;
3640 const char *fileID = NULL;
3641 /* lookup for the fileID depending on ID */
3642
3643 ret = xmlNewInputFromFile(ctxt, fileID);
3644 if (ret != NULL)
3645 return(ret);
3646 if (defaultLoader != NULL)
3647 ret = defaultLoader(URL, ID, ctxt);
3648 return(ret);
3649}
3650
3651int main(..) {
3652 ...
3653
3654 /*
3655 * Install our own entity loader
3656 */
3657 defaultLoader = xmlGetExternalEntityLoader();
3658 xmlSetExternalEntityLoader(xmlMyExternalEntityLoader);
3659
3660 ...
3661}</pre>
3662
3663<h3><a name="Example2">Example of customized I/O</a></h3>
3664
3665<p>This example come from <a href="http://xmlsoft.org/messages/0708.html">a
3666real use case</a>, xmlDocDump() closes the FILE * passed by the application
3667and this was a problem. The <a
3668href="http://xmlsoft.org/messages/0711.html">solution</a> was to redefine a
3669new output handler with the closing call deactivated:</p>
3670<ol>
Daniel Veillardc0801af2002-05-28 16:28:42 +00003671 <li>First define a new I/O output allocator where the output don't close
3672 the file:
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003673 <pre>xmlOutputBufferPtr
3674xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) {
3675    xmlOutputBufferPtr ret;
3676    
3677    if (xmlOutputCallbackInitialized == 0)
3678        xmlRegisterDefaultOutputCallbacks();
3679
3680    if (file == NULL) return(NULL);
3681    ret = xmlAllocOutputBuffer(encoder);
3682    if (ret != NULL) {
3683        ret-&gt;context = file;
3684        ret-&gt;writecallback = xmlFileWrite;
3685        ret-&gt;closecallback = NULL; /* No close callback */
3686    }
Daniel Veillardf83a2c72003-04-08 13:48:40 +00003687    return(ret);
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003688} </pre>
3689 </li>
3690 <li>And then use it to save the document:
3691 <pre>FILE *f;
3692xmlOutputBufferPtr output;
3693xmlDocPtr doc;
3694int res;
3695
3696f = ...
3697doc = ....
3698
3699output = xmlOutputBufferCreateOwn(f, NULL);
3700res = xmlSaveFileTo(output, doc, NULL);
3701 </pre>
3702 </li>
3703</ol>
3704
3705<h2><a name="Catalog">Catalog support</a></h2>
3706
3707<p>Table of Content:</p>
3708<ol>
3709 <li><a href="General2">General overview</a></li>
3710 <li><a href="#definition">The definition</a></li>
3711 <li><a href="#Simple">Using catalogs</a></li>
3712 <li><a href="#Some">Some examples</a></li>
3713 <li><a href="#reference">How to tune catalog usage</a></li>
3714 <li><a href="#validate">How to debug catalog processing</a></li>
3715 <li><a href="#Declaring">How to create and maintain catalogs</a></li>
3716 <li><a href="#implemento">The implementor corner quick review of the
3717 API</a></li>
3718 <li><a href="#Other">Other resources</a></li>
3719</ol>
3720
3721<h3><a name="General2">General overview</a></h3>
3722
3723<p>What is a catalog? Basically it's a lookup mechanism used when an entity
3724(a file or a remote resource) references another entity. The catalog lookup
3725is inserted between the moment the reference is recognized by the software
3726(XML parser, stylesheet processing, or even images referenced for inclusion
3727in a rendering) and the time where loading that resource is actually
3728started.</p>
3729
3730<p>It is basically used for 3 things:</p>
3731<ul>
3732 <li>mapping from "logical" names, the public identifiers and a more
3733 concrete name usable for download (and URI). For example it can associate
3734 the logical name
3735 <p>"-//OASIS//DTD DocBook XML V4.1.2//EN"</p>
3736 <p>of the DocBook 4.1.2 XML DTD with the actual URL where it can be
3737 downloaded</p>
3738 <p>http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd</p>
3739 </li>
3740 <li>remapping from a given URL to another one, like an HTTP indirection
3741 saying that
3742 <p>"http://www.oasis-open.org/committes/tr.xsl"</p>
3743 <p>should really be looked at</p>
3744 <p>"http://www.oasis-open.org/committes/entity/stylesheets/base/tr.xsl"</p>
3745 </li>
3746 <li>providing a local cache mechanism allowing to load the entities
3747 associated to public identifiers or remote resources, this is a really
3748 important feature for any significant deployment of XML or SGML since it
3749 allows to avoid the aleas and delays associated to fetching remote
3750 resources.</li>
3751</ul>
3752
3753<h3><a name="definition">The definitions</a></h3>
3754
3755<p>Libxml, as of 2.4.3 implements 2 kind of catalogs:</p>
3756<ul>
3757 <li>the older SGML catalogs, the official spec is SGML Open Technical
3758 Resolution TR9401:1997, but is better understood by reading <a
3759 href="http://www.jclark.com/sp/catalog.htm">the SP Catalog page</a> from
3760 James Clark. This is relatively old and not the preferred mode of
3761 operation of libxml.</li>
3762 <li><a href="http://www.oasis-open.org/committees/entity/spec.html">XML
Daniel Veillardaf43f632002-03-08 15:05:20 +00003763 Catalogs</a> is far more flexible, more recent, uses an XML syntax and
3764 should scale quite better. This is the default option of libxml.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003765</ul>
3766
3767<p></p>
3768
3769<h3><a name="Simple">Using catalog</a></h3>
3770
Daniel Veillard8a469172003-06-12 16:05:07 +00003771<p>In a normal environment libxml2 will by default check the presence of a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003772catalog in /etc/xml/catalog, and assuming it has been correctly populated,
3773the processing is completely transparent to the document user. To take a
3774concrete example, suppose you are authoring a DocBook document, this one
3775starts with the following DOCTYPE definition:</p>
3776<pre>&lt;?xml version='1.0'?&gt;
3777&lt;!DOCTYPE book PUBLIC "-//Norman Walsh//DTD DocBk XML V3.1.4//EN"
3778 "http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd"&gt;</pre>
3779
3780<p>When validating the document with libxml, the catalog will be
3781automatically consulted to lookup the public identifier "-//Norman Walsh//DTD
3782DocBk XML V3.1.4//EN" and the system identifier
3783"http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd", and if these entities have
3784been installed on your system and the catalogs actually point to them, libxml
3785will fetch them from the local disk.</p>
3786
3787<p style="font-size: 10pt"><strong>Note</strong>: Really don't use this
3788DOCTYPE example it's a really old version, but is fine as an example.</p>
3789
Daniel Veillard8a469172003-06-12 16:05:07 +00003790<p>Libxml2 will check the catalog each time that it is requested to load an
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003791entity, this includes DTD, external parsed entities, stylesheets, etc ... If
3792your system is correctly configured all the authoring phase and processing
3793should use only local files, even if your document stays portable because it
3794uses the canonical public and system ID, referencing the remote document.</p>
3795
3796<h3><a name="Some">Some examples:</a></h3>
3797
Daniel Veillard8a469172003-06-12 16:05:07 +00003798<p>Here is a couple of fragments from XML Catalogs used in libxml2 early
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003799regression tests in <code>test/catalogs</code> :</p>
3800<pre>&lt;?xml version="1.0"?&gt;
3801&lt;!DOCTYPE catalog PUBLIC
3802 "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
3803 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3804&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"&gt;
3805 &lt;public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
3806 uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/&gt;
3807...</pre>
3808
3809<p>This is the beginning of a catalog for DocBook 4.1.2, XML Catalogs are
3810written in XML, there is a specific namespace for catalog elements
3811"urn:oasis:names:tc:entity:xmlns:xml:catalog". The first entry in this
3812catalog is a <code>public</code> mapping it allows to associate a Public
3813Identifier with an URI.</p>
3814<pre>...
3815 &lt;rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/"
3816 rewritePrefix="file:///usr/share/xml/docbook/"/&gt;
3817...</pre>
3818
3819<p>A <code>rewriteSystem</code> is a very powerful instruction, it says that
3820any URI starting with a given prefix should be looked at another URI
3821constructed by replacing the prefix with an new one. In effect this acts like
3822a cache system for a full area of the Web. In practice it is extremely useful
3823with a file prefix if you have installed a copy of those resources on your
3824local system.</p>
3825<pre>...
3826&lt;delegatePublic publicIdStartString="-//OASIS//DTD XML Catalog //"
3827 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3828&lt;delegatePublic publicIdStartString="-//OASIS//ENTITIES DocBook XML"
3829 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3830&lt;delegatePublic publicIdStartString="-//OASIS//DTD DocBook XML"
3831 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3832&lt;delegateSystem systemIdStartString="http://www.oasis-open.org/docbook/"
3833 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3834&lt;delegateURI uriStartString="http://www.oasis-open.org/docbook/"
3835 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3836...</pre>
3837
3838<p>Delegation is the core features which allows to build a tree of catalogs,
3839easier to maintain than a single catalog, based on Public Identifier, System
3840Identifier or URI prefixes it instructs the catalog software to look up
3841entries in another resource. This feature allow to build hierarchies of
3842catalogs, the set of entries presented should be sufficient to redirect the
3843resolution of all DocBook references to the specific catalog in
3844<code>/usr/share/xml/docbook.xml</code> this one in turn could delegate all
3845references for DocBook 4.2.1 to a specific catalog installed at the same time
3846as the DocBook resources on the local machine.</p>
3847
3848<h3><a name="reference">How to tune catalog usage:</a></h3>
3849
3850<p>The user can change the default catalog behaviour by redirecting queries
3851to its own set of catalogs, this can be done by setting the
3852<code>XML_CATALOG_FILES</code> environment variable to a list of catalogs, an
3853empty one should deactivate loading the default <code>/etc/xml/catalog</code>
3854default catalog</p>
3855
3856<h3><a name="validate">How to debug catalog processing:</a></h3>
3857
3858<p>Setting up the <code>XML_DEBUG_CATALOG</code> environment variable will
Daniel Veillard8a469172003-06-12 16:05:07 +00003859make libxml2 output debugging informations for each catalog operations, for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003860example:</p>
3861<pre>orchis:~/XML -&gt; xmllint --memory --noout test/ent2
3862warning: failed to load external entity "title.xml"
3863orchis:~/XML -&gt; export XML_DEBUG_CATALOG=
3864orchis:~/XML -&gt; xmllint --memory --noout test/ent2
3865Failed to parse catalog /etc/xml/catalog
3866Failed to parse catalog /etc/xml/catalog
3867warning: failed to load external entity "title.xml"
3868Catalogs cleanup
3869orchis:~/XML -&gt; </pre>
3870
3871<p>The test/ent2 references an entity, running the parser from memory makes
3872the base URI unavailable and the the "title.xml" entity cannot be loaded.
3873Setting up the debug environment variable allows to detect that an attempt is
3874made to load the <code>/etc/xml/catalog</code> but since it's not present the
3875resolution fails.</p>
3876
3877<p>But the most advanced way to debug XML catalog processing is to use the
3878<strong>xmlcatalog</strong> command shipped with libxml2, it allows to load
3879catalogs and make resolution queries to see what is going on. This is also
3880used for the regression tests:</p>
3881<pre>orchis:~/XML -&gt; ./xmlcatalog test/catalogs/docbook.xml \
3882 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3883http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3884orchis:~/XML -&gt; </pre>
3885
3886<p>For debugging what is going on, adding one -v flags increase the verbosity
3887level to indicate the processing done (adding a second flag also indicate
3888what elements are recognized at parsing):</p>
3889<pre>orchis:~/XML -&gt; ./xmlcatalog -v test/catalogs/docbook.xml \
3890 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3891Parsing catalog test/catalogs/docbook.xml's content
3892Found public match -//OASIS//DTD DocBook XML V4.1.2//EN
3893http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3894Catalogs cleanup
3895orchis:~/XML -&gt; </pre>
3896
3897<p>A shell interface is also available to debug and process multiple queries
3898(and for regression tests):</p>
3899<pre>orchis:~/XML -&gt; ./xmlcatalog -shell test/catalogs/docbook.xml \
3900 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3901&gt; help
3902Commands available:
3903public PublicID: make a PUBLIC identifier lookup
3904system SystemID: make a SYSTEM identifier lookup
3905resolve PublicID SystemID: do a full resolver lookup
3906add 'type' 'orig' 'replace' : add an entry
3907del 'values' : remove values
3908dump: print the current catalog state
3909debug: increase the verbosity level
3910quiet: decrease the verbosity level
3911exit: quit the shell
3912&gt; public "-//OASIS//DTD DocBook XML V4.1.2//EN"
3913http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3914&gt; quit
3915orchis:~/XML -&gt; </pre>
3916
3917<p>This should be sufficient for most debugging purpose, this was actually
3918used heavily to debug the XML Catalog implementation itself.</p>
3919
3920<h3><a name="Declaring">How to create and maintain</a> catalogs:</h3>
3921
3922<p>Basically XML Catalogs are XML files, you can either use XML tools to
3923manage them or use <strong>xmlcatalog</strong> for this. The basic step is
3924to create a catalog the -create option provide this facility:</p>
3925<pre>orchis:~/XML -&gt; ./xmlcatalog --create tst.xml
3926&lt;?xml version="1.0"?&gt;
3927&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
3928 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3929&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/&gt;
3930orchis:~/XML -&gt; </pre>
3931
3932<p>By default xmlcatalog does not overwrite the original catalog and save the
3933result on the standard output, this can be overridden using the -noout
3934option. The <code>-add</code> command allows to add entries in the
3935catalog:</p>
3936<pre>orchis:~/XML -&gt; ./xmlcatalog --noout --create --add "public" \
3937 "-//OASIS//DTD DocBook XML V4.1.2//EN" \
3938 http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd tst.xml
3939orchis:~/XML -&gt; cat tst.xml
3940&lt;?xml version="1.0"?&gt;
3941&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" \
3942 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3943&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"&gt;
3944&lt;public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
3945 uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/&gt;
3946&lt;/catalog&gt;
3947orchis:~/XML -&gt; </pre>
3948
3949<p>The <code>-add</code> option will always take 3 parameters even if some of
3950the XML Catalog constructs (like nextCatalog) will have only a single
3951argument, just pass a third empty string, it will be ignored.</p>
3952
3953<p>Similarly the <code>-del</code> option remove matching entries from the
3954catalog:</p>
3955<pre>orchis:~/XML -&gt; ./xmlcatalog --del \
3956 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" tst.xml
3957&lt;?xml version="1.0"?&gt;
3958&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
3959 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3960&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/&gt;
3961orchis:~/XML -&gt; </pre>
3962
3963<p>The catalog is now empty. Note that the matching of <code>-del</code> is
3964exact and would have worked in a similar fashion with the Public ID
3965string.</p>
3966
3967<p>This is rudimentary but should be sufficient to manage a not too complex
3968catalog tree of resources.</p>
3969
3970<h3><a name="implemento">The implementor corner quick review of the
3971API:</a></h3>
3972
3973<p>First, and like for every other module of libxml, there is an
3974automatically generated <a href="html/libxml-catalog.html">API page for
3975catalog support</a>.</p>
3976
3977<p>The header for the catalog interfaces should be included as:</p>
3978<pre>#include &lt;libxml/catalog.h&gt;</pre>
3979
3980<p>The API is voluntarily kept very simple. First it is not obvious that
3981applications really need access to it since it is the default behaviour of
Daniel Veillard560c2a42003-07-06 21:13:49 +00003982libxml2 (Note: it is possible to completely override libxml2 default catalog
3983by using <a href="html/libxml-parser.html">xmlSetExternalEntityLoader</a> to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003984plug an application specific resolver).</p>
3985
Daniel Veillard8a469172003-06-12 16:05:07 +00003986<p>Basically libxml2 support 2 catalog lists:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00003987<ul>
3988 <li>the default one, global shared by all the application</li>
3989 <li>a per-document catalog, this one is built if the document uses the
3990 <code>oasis-xml-catalog</code> PIs to specify its own catalog list, it is
3991 associated to the parser context and destroyed when the parsing context
3992 is destroyed.</li>
3993</ul>
3994
3995<p>the document one will be used first if it exists.</p>
3996
3997<h4>Initialization routines:</h4>
3998
3999<p>xmlInitializeCatalog(), xmlLoadCatalog() and xmlLoadCatalogs() should be
4000used at startup to initialize the catalog, if the catalog should be
4001initialized with specific values xmlLoadCatalog() or xmlLoadCatalogs()
4002should be called before xmlInitializeCatalog() which would otherwise do a
4003default initialization first.</p>
4004
4005<p>The xmlCatalogAddLocal() call is used by the parser to grow the document
4006own catalog list if needed.</p>
4007
4008<h4>Preferences setup:</h4>
4009
4010<p>The XML Catalog spec requires the possibility to select default
4011preferences between public and system delegation,
4012xmlCatalogSetDefaultPrefer() allows this, xmlCatalogSetDefaults() and
4013xmlCatalogGetDefaults() allow to control if XML Catalogs resolution should
4014be forbidden, allowed for global catalog, for document catalog or both, the
4015default is to allow both.</p>
4016
4017<p>And of course xmlCatalogSetDebug() allows to generate debug messages
4018(through the xmlGenericError() mechanism).</p>
4019
4020<h4>Querying routines:</h4>
4021
4022<p>xmlCatalogResolve(), xmlCatalogResolveSystem(), xmlCatalogResolvePublic()
4023and xmlCatalogResolveURI() are relatively explicit if you read the XML
4024Catalog specification they correspond to section 7 algorithms, they should
4025also work if you have loaded an SGML catalog with a simplified semantic.</p>
4026
4027<p>xmlCatalogLocalResolve() and xmlCatalogLocalResolveURI() are the same but
4028operate on the document catalog list</p>
4029
4030<h4>Cleanup and Miscellaneous:</h4>
4031
4032<p>xmlCatalogCleanup() free-up the global catalog, xmlCatalogFreeLocal() is
4033the per-document equivalent.</p>
4034
4035<p>xmlCatalogAdd() and xmlCatalogRemove() are used to dynamically modify the
4036first catalog in the global list, and xmlCatalogDump() allows to dump a
4037catalog state, those routines are primarily designed for xmlcatalog, I'm not
4038sure that exposing more complex interfaces (like navigation ones) would be
4039really useful.</p>
4040
4041<p>The xmlParseCatalogFile() is a function used to load XML Catalog files,
4042it's similar as xmlParseFile() except it bypass all catalog lookups, it's
4043provided because this functionality may be useful for client tools.</p>
4044
4045<h4>threaded environments:</h4>
4046
4047<p>Since the catalog tree is built progressively, some care has been taken to
4048try to avoid troubles in multithreaded environments. The code is now thread
Daniel Veillard8a469172003-06-12 16:05:07 +00004049safe assuming that the libxml2 library has been compiled with threads
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004050support.</p>
4051
4052<p></p>
4053
4054<h3><a name="Other">Other resources</a></h3>
4055
4056<p>The XML Catalog specification is relatively recent so there isn't much
4057literature to point at:</p>
4058<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +00004059 <li>You can find a good rant from Norm Walsh about <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004060 href="http://www.arbortext.com/Think_Tank/XML_Resources/Issue_Three/issue_three.html">the
4061 need for catalogs</a>, it provides a lot of context informations even if
Daniel Veillard93d3a472002-04-26 14:04:55 +00004062 I don't agree with everything presented. Norm also wrote a more recent
4063 article <a
4064 href="http://wwws.sun.com/software/xml/developers/resolver/article/">XML
4065 entities and URI resolvers</a> describing them.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004066 <li>An <a href="http://home.ccil.org/~cowan/XML/XCatalog.html">old XML
4067 catalog proposal</a> from John Cowan</li>
4068 <li>The <a href="http://www.rddl.org/">Resource Directory Description
4069 Language</a> (RDDL) another catalog system but more oriented toward
4070 providing metadata for XML namespaces.</li>
4071 <li>the page from the OASIS Technical <a
4072 href="http://www.oasis-open.org/committees/entity/">Committee on Entity
4073 Resolution</a> who maintains XML Catalog, you will find pointers to the
4074 specification update, some background and pointers to others tools
4075 providing XML Catalog support</li>
Daniel Veillardabfca612004-01-07 23:38:02 +00004076 <li>There is a <a href="buildDocBookCatalog">shell script</a> to generate
Daniel Veillard35e937a2002-01-19 22:21:54 +00004077 XML Catalogs for DocBook 4.1.2 . If it can write to the /etc/xml/
4078 directory, it will set-up /etc/xml/catalog and /etc/xml/docbook based on
4079 the resources found on the system. Otherwise it will just create
4080 ~/xmlcatalog and ~/dbkxmlcatalog and doing:
Daniel Veillard8594de92003-04-25 10:08:44 +00004081 <p><code>export XML_CATALOG_FILES=$HOME/xmlcatalog</code></p>
Daniel Veillard35e937a2002-01-19 22:21:54 +00004082 <p>should allow to process DocBook documentations without requiring
Daniel Veillard63d83142002-05-20 06:51:05 +00004083 network accesses for the DTD or stylesheets</p>
Daniel Veillard35e937a2002-01-19 22:21:54 +00004084 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004085 <li>I have uploaded <a href="ftp://xmlsoft.org/test/dbk412catalog.tar.gz">a
Daniel Veillard35e937a2002-01-19 22:21:54 +00004086 small tarball</a> containing XML Catalogs for DocBook 4.1.2 which seems
4087 to work fine for me too</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004088 <li>The <a href="http://www.xmlsoft.org/xmlcatalog_man.html">xmlcatalog
4089 manual page</a></li>
4090</ul>
4091
4092<p>If you have suggestions for corrections or additions, simply contact
4093me:</p>
4094
4095<h2><a name="library">The parser interfaces</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004096
4097<p>This section is directly intended to help programmers getting bootstrapped
Daniel Veillard8a469172003-06-12 16:05:07 +00004098using the XML tollkit from the C language. It is not intended to be
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004099extensive. I hope the automatically generated documents will provide the
4100completeness required, but as a separate set of documents. The interfaces of
Daniel Veillard560c2a42003-07-06 21:13:49 +00004101the XML parser are by principle low level, Those interested in a higher level
4102API should <a href="#DOM">look at DOM</a>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +00004103
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00004104<p>The <a href="html/libxml-parser.html">parser interfaces for XML</a> are
4105separated from the <a href="html/libxml-htmlparser.html">HTML parser
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004106interfaces</a>. Let's have a look at how the XML parser can be called:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +00004107
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004108<h3><a name="Invoking">Invoking the parser : the pull method</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004109
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004110<p>Usually, the first thing to do is to read an XML input. The parser accepts
4111documents either from in-memory strings or from files. The functions are
Daniel Veillardb05deb71999-08-10 19:04:08 +00004112defined in "parser.h":</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004113<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004114 <dt><code>xmlDocPtr xmlParseMemory(char *buffer, int size);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004115 <dd><p>Parse a null-terminated string containing the document.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004116 </dd>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004117</dl>
4118<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004119 <dt><code>xmlDocPtr xmlParseFile(const char *filename);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004120 <dd><p>Parse an XML document contained in a (possibly compressed)
4121 file.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004122 </dd>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004123</dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004124
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004125<p>The parser returns a pointer to the document structure (or NULL in case of
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004126failure).</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004127
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004128<h3 id="Invoking1">Invoking the parser: the push method</h3>
Daniel Veillard0142b842000-01-14 14:45:24 +00004129
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004130<p>In order for the application to keep the control when the document is
Daniel Veillard560c2a42003-07-06 21:13:49 +00004131being fetched (which is common for GUI based programs) libxml2 provides a
4132push interface, too, as of version 1.8.3. Here are the interface
4133functions:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +00004134<pre>xmlParserCtxtPtr xmlCreatePushParserCtxt(xmlSAXHandlerPtr sax,
4135 void *user_data,
4136 const char *chunk,
4137 int size,
4138 const char *filename);
4139int xmlParseChunk (xmlParserCtxtPtr ctxt,
4140 const char *chunk,
4141 int size,
4142 int terminate);</pre>
4143
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004144<p>and here is a simple example showing how to use the interface:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +00004145<pre> FILE *f;
4146
4147 f = fopen(filename, "r");
4148 if (f != NULL) {
4149 int res, size = 1024;
4150 char chars[1024];
4151 xmlParserCtxtPtr ctxt;
4152
4153 res = fread(chars, 1, 4, f);
Daniel Veillard60979bd2000-07-10 12:17:33 +00004154 if (res &gt; 0) {
Daniel Veillard0142b842000-01-14 14:45:24 +00004155 ctxt = xmlCreatePushParserCtxt(NULL, NULL,
4156 chars, res, filename);
Daniel Veillard60979bd2000-07-10 12:17:33 +00004157 while ((res = fread(chars, 1, size, f)) &gt; 0) {
Daniel Veillard0142b842000-01-14 14:45:24 +00004158 xmlParseChunk(ctxt, chars, res, 0);
4159 }
4160 xmlParseChunk(ctxt, chars, 0, 1);
Daniel Veillard60979bd2000-07-10 12:17:33 +00004161 doc = ctxt-&gt;myDoc;
Daniel Veillard0142b842000-01-14 14:45:24 +00004162 xmlFreeParserCtxt(ctxt);
4163 }
4164 }</pre>
4165
Daniel Veillard8a469172003-06-12 16:05:07 +00004166<p>The HTML parser embedded into libxml2 also has a push interface; the
Daniel Veillardec70e912001-02-26 20:10:45 +00004167functions are just prefixed by "html" rather than "xml".</p>
Daniel Veillard0142b842000-01-14 14:45:24 +00004168
4169<h3 id="Invoking2">Invoking the parser: the SAX interface</h3>
4170
Daniel Veillardec70e912001-02-26 20:10:45 +00004171<p>The tree-building interface makes the parser memory-hungry, first loading
4172the document in memory and then building the tree itself. Reading a document
4173without building the tree is possible using the SAX interfaces (see SAX.h and
4174<a href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">James
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004175Henstridge's documentation</a>). Note also that the push interface can be
Daniel Veillard91e9d582001-02-26 07:31:12 +00004176limited to SAX: just use the two first arguments of
Daniel Veillard0142b842000-01-14 14:45:24 +00004177<code>xmlCreatePushParserCtxt()</code>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +00004178
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004179<h3><a name="Building">Building a tree from scratch</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004180
4181<p>The other way to get an XML tree in memory is by building it. Basically
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004182there is a set of functions dedicated to building new elements. (These are
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004183also described in &lt;libxml/tree.h&gt;.) For example, here is a piece of
4184code that produces the XML document used in the previous examples:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004185<pre> #include &lt;libxml/tree.h&gt;
Daniel Veillard361d8452000-04-03 19:48:13 +00004186 xmlDocPtr doc;
Daniel Veillard25940b71998-10-29 05:51:30 +00004187 xmlNodePtr tree, subtree;
4188
4189 doc = xmlNewDoc("1.0");
Daniel Veillard60979bd2000-07-10 12:17:33 +00004190 doc-&gt;children = xmlNewDocNode(doc, NULL, "EXAMPLE", NULL);
4191 xmlSetProp(doc-&gt;children, "prop1", "gnome is great");
4192 xmlSetProp(doc-&gt;children, "prop2", "&amp; linux too");
4193 tree = xmlNewChild(doc-&gt;children, NULL, "head", NULL);
Daniel Veillard25940b71998-10-29 05:51:30 +00004194 subtree = xmlNewChild(tree, NULL, "title", "Welcome to Gnome");
Daniel Veillard60979bd2000-07-10 12:17:33 +00004195 tree = xmlNewChild(doc-&gt;children, NULL, "chapter", NULL);
Daniel Veillard25940b71998-10-29 05:51:30 +00004196 subtree = xmlNewChild(tree, NULL, "title", "The Linux adventure");
4197 subtree = xmlNewChild(tree, NULL, "p", "bla bla bla ...");
4198 subtree = xmlNewChild(tree, NULL, "image", NULL);
4199 xmlSetProp(subtree, "href", "linus.gif");</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004200
4201<p>Not really rocket science ...</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004202
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004203<h3><a name="Traversing">Traversing the tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004204
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00004205<p>Basically by <a href="html/libxml-tree.html">including "tree.h"</a> your
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004206code has access to the internal structure of all the elements of the tree.
4207The names should be somewhat simple like <strong>parent</strong>,
Daniel Veillard306be992000-07-03 12:38:45 +00004208<strong>children</strong>, <strong>next</strong>, <strong>prev</strong>,
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004209<strong>properties</strong>, etc... For example, still with the previous
Daniel Veillard0142b842000-01-14 14:45:24 +00004210example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004211<pre><code>doc-&gt;children-&gt;children-&gt;children</code></pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004212
4213<p>points to the title element,</p>
Daniel Veillard91e9d582001-02-26 07:31:12 +00004214<pre>doc-&gt;children-&gt;children-&gt;next-&gt;children-&gt;children</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004215
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004216<p>points to the text node containing the chapter title "The Linux
4217adventure".</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004218
Daniel Veillardb24054a1999-12-18 15:32:46 +00004219<p><strong>NOTE</strong>: XML allows <em>PI</em>s and <em>comments</em> to be
Daniel Veillard60979bd2000-07-10 12:17:33 +00004220present before the document root, so <code>doc-&gt;children</code> may point
Daniel Veillard91e9d582001-02-26 07:31:12 +00004221to an element which is not the document Root Element; a function
Daniel Veillard5cb5ab81999-12-21 15:35:29 +00004222<code>xmlDocGetRootElement()</code> was added for this purpose.</p>
Daniel Veillardb24054a1999-12-18 15:32:46 +00004223
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004224<h3><a name="Modifying">Modifying the tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004225
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004226<p>Functions are provided for reading and writing the document content. Here
Daniel Veillard9cb5ff42001-01-29 08:22:21 +00004227is an excerpt from the <a href="html/libxml-tree.html">tree API</a>:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004228<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004229 <dt><code>xmlAttrPtr xmlSetProp(xmlNodePtr node, const xmlChar *name, const
4230 xmlChar *value);</code></dt>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004231 <dd><p>This sets (or changes) an attribute carried by an ELEMENT node.
4232 The value can be NULL.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004233 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004234</dl>
4235<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004236 <dt><code>const xmlChar *xmlGetProp(xmlNodePtr node, const xmlChar
Daniel Veillardb05deb71999-08-10 19:04:08 +00004237 *name);</code></dt>
Daniel Veillardc92c3042000-09-29 02:42:04 +00004238 <dd><p>This function returns a pointer to new copy of the property
4239 content. Note that the user must deallocate the result.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004240 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004241</dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004242
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004243<p>Two functions are provided for reading and writing the text associated
4244with elements:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004245<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004246 <dt><code>xmlNodePtr xmlStringGetNodeList(xmlDocPtr doc, const xmlChar
Daniel Veillardb05deb71999-08-10 19:04:08 +00004247 *value);</code></dt>
Daniel Veillardec70e912001-02-26 20:10:45 +00004248 <dd><p>This function takes an "external" string and converts it to one
4249 text node or possibly to a list of entity and text nodes. All
4250 non-predefined entity references like &amp;Gnome; will be stored
4251 internally as entity nodes, hence the result of the function may not be
4252 a single node.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004253 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004254</dl>
4255<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004256 <dt><code>xmlChar *xmlNodeListGetString(xmlDocPtr doc, xmlNodePtr list, int
Daniel Veillardb05deb71999-08-10 19:04:08 +00004257 inLine);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004258 <dd><p>This function is the inverse of
4259 <code>xmlStringGetNodeList()</code>. It generates a new string
4260 containing the content of the text and entity nodes. Note the extra
4261 argument inLine. If this argument is set to 1, the function will expand
4262 entity references. For example, instead of returning the &amp;Gnome;
4263 XML encoding in the string, it will substitute it with its value (say,
Daniel Veillard91e9d582001-02-26 07:31:12 +00004264 "GNU Network Object Model Environment").</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004265 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004266</dl>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004267
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004268<h3><a name="Saving">Saving a tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004269
4270<p>Basically 3 options are possible:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004271<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +00004272 <dt><code>void xmlDocDumpMemory(xmlDocPtr cur, xmlChar**mem, int
Daniel Veillardb05deb71999-08-10 19:04:08 +00004273 *size);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004274 <dd><p>Returns a buffer into which the document has been saved.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004275 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004276</dl>
4277<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004278 <dt><code>extern void xmlDocDump(FILE *f, xmlDocPtr doc);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004279 <dd><p>Dumps a document to an open file descriptor.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004280 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004281</dl>
4282<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004283 <dt><code>int xmlSaveFile(const char *filename, xmlDocPtr cur);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004284 <dd><p>Saves the document to a file. In this case, the compression
4285 interface is triggered if it has been turned on.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004286 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004287</dl>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +00004288
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004289<h3><a name="Compressio">Compression</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004290
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004291<p>The library transparently handles compression when doing file-based
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004292accesses. The level of compression on saves can be turned on either globally
4293or individually for one file:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +00004294<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004295 <dt><code>int xmlGetDocCompressMode (xmlDocPtr doc);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004296 <dd><p>Gets the document compression ratio (0-9).</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004297 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004298</dl>
4299<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004300 <dt><code>void xmlSetDocCompressMode (xmlDocPtr doc, int mode);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004301 <dd><p>Sets the document compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004302 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004303</dl>
4304<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004305 <dt><code>int xmlGetCompressMode(void);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004306 <dd><p>Gets the default compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004307 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004308</dl>
4309<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004310 <dt><code>void xmlSetCompressMode(int mode);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004311 <dd><p>Sets the default compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004312 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +00004313</dl>
4314
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004315<h2><a name="Entities">Entities or no entities</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004316
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004317<p>Entities in principle are similar to simple C macros. An entity defines an
4318abbreviation for a given string that you can reuse many times throughout the
4319content of your document. Entities are especially useful when a given string
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004320may occur frequently within a document, or to confine the change needed to a
4321document to a restricted area in the internal subset of the document (at the
4322beginning). Example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004323<pre>1 &lt;?xml version="1.0"?&gt;
Daniel Veillardc8eab3a1999-09-04 18:27:23 +000043242 &lt;!DOCTYPE EXAMPLE SYSTEM "example.dtd" [
Daniel Veillard60979bd2000-07-10 12:17:33 +000043253 &lt;!ENTITY xml "Extensible Markup Language"&gt;
43264 ]&gt;
43275 &lt;EXAMPLE&gt;
Daniel Veillardc8eab3a1999-09-04 18:27:23 +000043286 &amp;xml;
Daniel Veillard60979bd2000-07-10 12:17:33 +000043297 &lt;/EXAMPLE&gt;</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004330
4331<p>Line 3 declares the xml entity. Line 6 uses the xml entity, by prefixing
Daniel Veillard91e9d582001-02-26 07:31:12 +00004332its name with '&amp;' and following it by ';' without any spaces added. There
Daniel Veillard8a469172003-06-12 16:05:07 +00004333are 5 predefined entities in libxml2 allowing you to escape characters with
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004334predefined meaning in some parts of the xml document content:
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004335<strong>&amp;lt;</strong> for the character '&lt;', <strong>&amp;gt;</strong>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004336for the character '&gt;', <strong>&amp;apos;</strong> for the character ''',
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004337<strong>&amp;quot;</strong> for the character '"', and
4338<strong>&amp;amp;</strong> for the character '&amp;'.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004339
4340<p>One of the problems related to entities is that you may want the parser to
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004341substitute an entity's content so that you can see the replacement text in
4342your application. Or you may prefer to keep entity references as such in the
4343content to be able to save the document back without losing this usually
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004344precious information (if the user went through the pain of explicitly
4345defining entities, he may have a a rather negative attitude if you blindly
Daniel Veillard63d83142002-05-20 06:51:05 +00004346substitute them as saving time). The <a
Daniel Veillard5373ea12003-07-24 13:09:13 +00004347href="html/libxml-parser.html#xmlSubstituteEntitiesDefault">xmlSubstituteEntitiesDefault()</a>
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004348function allows you to check and change the behaviour, which is to not
4349substitute entities by default.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004350
Daniel Veillard8a469172003-06-12 16:05:07 +00004351<p>Here is the DOM tree built by libxml2 for the previous document in the
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004352default case:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004353<pre>/gnome/src/gnome-xml -&gt; ./xmllint --debug test/ent1
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004354DOCUMENT
4355version=1.0
4356 ELEMENT EXAMPLE
4357 TEXT
4358 content=
4359 ENTITY_REF
4360 INTERNAL_GENERAL_ENTITY xml
4361 content=Extensible Markup Language
4362 TEXT
4363 content=</pre>
4364
4365<p>And here is the result when substituting entities:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004366<pre>/gnome/src/gnome-xml -&gt; ./tester --debug --noent test/ent1
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004367DOCUMENT
4368version=1.0
4369 ELEMENT EXAMPLE
4370 TEXT
4371 content= Extensible Markup Language</pre>
4372
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004373<p>So, entities or no entities? Basically, it depends on your use case. I
4374suggest that you keep the non-substituting default behaviour and avoid using
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004375entities in your XML document or data if you are not willing to handle the
4376entity references elements in the DOM tree.</p>
4377
Daniel Veillard8a469172003-06-12 16:05:07 +00004378<p>Note that at save time libxml2 enforces the conversion of the predefined
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004379entities where necessary to prevent well-formedness problems, and will also
Daniel Veillard91e9d582001-02-26 07:31:12 +00004380transparently replace those with chars (i.e. it will not generate entity
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004381reference elements in the DOM tree or call the reference() SAX callback when
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004382finding them in the input).</p>
4383
Daniel Veillard7b9c4b72000-08-25 16:26:50 +00004384<p><span style="background-color: #FF0000">WARNING</span>: handling entities
Daniel Veillard8a469172003-06-12 16:05:07 +00004385on top of the libxml2 SAX interface is difficult!!! If you plan to use
Daniel Veillard63d83142002-05-20 06:51:05 +00004386non-predefined entities in your documents, then the learning curve to handle
Daniel Veillard91e9d582001-02-26 07:31:12 +00004387then using the SAX API may be long. If you plan to use complex documents, I
Daniel Veillard7b9c4b72000-08-25 16:26:50 +00004388strongly suggest you consider using the DOM interface instead and let libxml
Daniel Veillard8c6d6af2000-08-25 17:14:13 +00004389deal with the complexity rather than trying to do it yourself.</p>
Daniel Veillard7b9c4b72000-08-25 16:26:50 +00004390
Daniel Veillard2f4dfc41999-09-24 14:03:48 +00004391<h2><a name="Namespaces">Namespaces</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004392
Daniel Veillard8a469172003-06-12 16:05:07 +00004393<p>The libxml2 library implements <a
Daniel Veillardec303412000-03-24 13:41:54 +00004394href="http://www.w3.org/TR/REC-xml-names/">XML namespaces</a> support by
Daniel Veillard63d83142002-05-20 06:51:05 +00004395recognizing namespace constructs in the input, and does namespace lookup
Daniel Veillardec303412000-03-24 13:41:54 +00004396automatically when building the DOM tree. A namespace declaration is
4397associated with an in-memory structure and all elements or attributes within
4398that namespace point to it. Hence testing the namespace is a simple and fast
4399equality operation at the user level.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004400
Daniel Veillard8a469172003-06-12 16:05:07 +00004401<p>I suggest that people using libxml2 use a namespace, and declare it in the
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004402root element of their document as the default namespace. Then they don't need
4403to use the prefix in the content but we will have a basis for future semantic
Daniel Veillard91e9d582001-02-26 07:31:12 +00004404refinement and merging of data from different sources. This doesn't increase
Daniel Veillardec70e912001-02-26 20:10:45 +00004405the size of the XML output significantly, but significantly increases its
4406value in the long-term. Example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004407<pre>&lt;mydoc xmlns="http://mydoc.example.org/schemas/"&gt;
4408 &lt;elem1&gt;...&lt;/elem1&gt;
4409 &lt;elem2&gt;...&lt;/elem2&gt;
4410&lt;/mydoc&gt;</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004411
Daniel Veillardec70e912001-02-26 20:10:45 +00004412<p>The namespace value has to be an absolute URL, but the URL doesn't have to
4413point to any existing resource on the Web. It will bind all the element and
Daniel Veillardc0801af2002-05-28 16:28:42 +00004414attributes with that URL. I suggest to use an URL within a domain you
4415control, and that the URL should contain some kind of version information if
4416possible. For example, <code>"http://www.gnome.org/gnumeric/1.0/"</code> is a
4417good namespace scheme.</p>
Daniel Veillardec303412000-03-24 13:41:54 +00004418
4419<p>Then when you load a file, make sure that a namespace carrying the
Daniel Veillard88f00ae2000-03-02 00:15:55 +00004420version-independent prefix is installed on the root element of your document,
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004421and if the version information don't match something you know, warn the user
4422and be liberal in what you accept as the input. Also do *not* try to base
Daniel Veillard60979bd2000-07-10 12:17:33 +00004423namespace checking on the prefix value. &lt;foo:text&gt; may be exactly the
Daniel Veillard91e9d582001-02-26 07:31:12 +00004424same as &lt;bar:text&gt; in another document. What really matters is the URI
Daniel Veillard60979bd2000-07-10 12:17:33 +00004425associated with the element or the attribute, not the prefix string (which is
Daniel Veillard91e9d582001-02-26 07:31:12 +00004426just a shortcut for the full URI). In libxml, element and attributes have an
Daniel Veillardec303412000-03-24 13:41:54 +00004427<code>ns</code> field pointing to an xmlNs structure detailing the namespace
Daniel Veillard91e9d582001-02-26 07:31:12 +00004428prefix and its URI.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004429
4430<p>@@Interfaces@@</p>
Daniel Veillard3e35f8e2003-10-21 00:05:38 +00004431<pre>xmlNodePtr node;
Daniel Veillardfc8dc352003-10-18 09:07:46 +00004432if(!strncmp(node-&gt;name,"mytag",5)
4433 &amp;&amp; node-&gt;ns
4434 &amp;&amp; !strcmp(node-&gt;ns-&gt;href,"http://www.mysite.com/myns/1.0")) {
4435 ...
Daniel Veillard3e35f8e2003-10-21 00:05:38 +00004436}</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004437
Daniel Veillard91e9d582001-02-26 07:31:12 +00004438<p>Usually people object to using namespaces together with validity checking.
4439I will try to make sure that using namespaces won't break validity checking,
4440so even if you plan to use or currently are using validation I strongly
Daniel Veillardf13e1ed2000-03-06 07:41:49 +00004441suggest adding namespaces to your document. A default namespace scheme
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004442<code>xmlns="http://...."</code> should not break validity even on less
Daniel Veillard91e9d582001-02-26 07:31:12 +00004443flexible parsers. Using namespaces to mix and differentiate content coming
Daniel Veillard3e35f8e2003-10-21 00:05:38 +00004444from multiple DTDs will certainly break current validation schemes. To check
4445such documents one needs to use schema-validation, which is supported in
4446libxml2 as well. See <a href="http://www.relaxng.org/">relagx-ng</a> and <a
4447href="http://www.w3c.org/XML/Schema">w3c-schema</a>.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004448
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004449<h2><a name="Upgrading">Upgrading 1.x code</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004450
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004451<p>Incompatible changes:</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004452
Daniel Veillard8a469172003-06-12 16:05:07 +00004453<p>Version 2 of libxml2 is the first version introducing serious backward
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004454incompatible changes. The main goals were:</p>
4455<ul>
4456 <li>a general cleanup. A number of mistakes inherited from the very early
4457 versions couldn't be changed due to compatibility constraints. Example
4458 the "childs" element in the nodes.</li>
4459 <li>Uniformization of the various nodes, at least for their header and link
4460 parts (doc, parent, children, prev, next), the goal is a simpler
4461 programming model and simplifying the task of the DOM implementors.</li>
4462 <li>better conformances to the XML specification, for example version 1.x
4463 had an heuristic to try to detect ignorable white spaces. As a result the
4464 SAX event generated were ignorableWhitespace() while the spec requires
4465 character() in that case. This also mean that a number of DOM node
4466 containing blank text may populate the DOM tree which were not present
4467 before.</li>
4468</ul>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004469
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004470<h3>How to fix libxml-1.x code:</h3>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004471
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004472<p>So client code of libxml designed to run with version 1.x may have to be
4473changed to compile against version 2.x of libxml. Here is a list of changes
4474that I have collected, they may not be sufficient, so in case you find other
Daniel Veillardfc8dc352003-10-18 09:07:46 +00004475change which are required, <a href="mailto:Daniel.Veillard@w3.org">drop me a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004476mail</a>:</p>
4477<ol>
4478 <li>The package name have changed from libxml to libxml2, the library name
4479 is now -lxml2 . There is a new xml2-config script which should be used to
4480 select the right parameters libxml2</li>
4481 <li>Node <strong>childs</strong> field has been renamed
4482 <strong>children</strong> so s/childs/children/g should be applied
Daniel Veillard63d83142002-05-20 06:51:05 +00004483 (probability of having "childs" anywhere else is close to 0+</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004484 <li>The document don't have anymore a <strong>root</strong> element it has
4485 been replaced by <strong>children</strong> and usually you will get a
4486 list of element here. For example a Dtd element for the internal subset
4487 and it's declaration may be found in that list, as well as processing
4488 instructions or comments found before or after the document root element.
4489 Use <strong>xmlDocGetRootElement(doc)</strong> to get the root element of
Daniel Veillard63d83142002-05-20 06:51:05 +00004490 a document. Alternatively if you are sure to not reference DTDs nor have
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004491 PIs or comments before or after the root element
4492 s/-&gt;root/-&gt;children/g will probably do it.</li>
4493 <li>The white space issue, this one is more complex, unless special case of
4494 validating parsing, the line breaks and spaces usually used for indenting
4495 and formatting the document content becomes significant. So they are
4496 reported by SAX and if your using the DOM tree, corresponding nodes are
4497 generated. Too approach can be taken:
4498 <ol>
4499 <li>lazy one, use the compatibility call
4500 <strong>xmlKeepBlanksDefault(0)</strong> but be aware that you are
4501 relying on a special (and possibly broken) set of heuristics of
4502 libxml to detect ignorable blanks. Don't complain if it breaks or
4503 make your application not 100% clean w.r.t. to it's input.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00004504 <li>the Right Way: change you code to accept possibly insignificant
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004505 blanks characters, or have your tree populated with weird blank text
Daniel Veillard63d83142002-05-20 06:51:05 +00004506 nodes. You can spot them using the commodity function
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004507 <strong>xmlIsBlankNode(node)</strong> returning 1 for such blank
4508 nodes.</li>
4509 </ol>
4510 <p>Note also that with the new default the output functions don't add any
4511 extra indentation when saving a tree in order to be able to round trip
4512 (read and save) without inflating the document with extra formatting
4513 chars.</p>
4514 </li>
4515 <li>The include path has changed to $prefix/libxml/ and the includes
4516 themselves uses this new prefix in includes instructions... If you are
4517 using (as expected) the
4518 <pre>xml2-config --cflags</pre>
4519 <p>output to generate you compile commands this will probably work out of
4520 the box</p>
4521 </li>
Daniel Veillard63d83142002-05-20 06:51:05 +00004522 <li>xmlDetectCharEncoding takes an extra argument indicating the length in
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004523 byte of the head of the document available for character detection.</li>
4524</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004525
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004526<h3>Ensuring both libxml-1.x and libxml-2.x compatibility</h3>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004527
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004528<p>Two new version of libxml (1.8.11) and libxml2 (2.3.4) have been released
Daniel Veillard63d83142002-05-20 06:51:05 +00004529to allow smooth upgrade of existing libxml v1code while retaining
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004530compatibility. They offers the following:</p>
4531<ol>
4532 <li>similar include naming, one should use
4533 <strong>#include&lt;libxml/...&gt;</strong> in both cases.</li>
4534 <li>similar identifiers defined via macros for the child and root fields:
4535 respectively <strong>xmlChildrenNode</strong> and
4536 <strong>xmlRootNode</strong></li>
4537 <li>a new macro <strong>LIBXML_TEST_VERSION</strong> which should be
4538 inserted once in the client code</li>
4539</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004540
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004541<p>So the roadmap to upgrade your existing libxml applications is the
4542following:</p>
4543<ol>
4544 <li>install the libxml-1.8.8 (and libxml-devel-1.8.8) packages</li>
Daniel Veillard63d83142002-05-20 06:51:05 +00004545 <li>find all occurrences where the xmlDoc <strong>root</strong> field is
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004546 used and change it to <strong>xmlRootNode</strong></li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00004547 <li>similarly find all occurrences where the xmlNode
4548 <strong>childs</strong> field is used and change it to
4549 <strong>xmlChildrenNode</strong></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004550 <li>add a <strong>LIBXML_TEST_VERSION</strong> macro somewhere in your
4551 <strong>main()</strong> or in the library init entry point</li>
4552 <li>Recompile, check compatibility, it should still work</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +00004553 <li>Change your configure script to look first for xml2-config and fall
4554 back using xml-config . Use the --cflags and --libs output of the command
4555 as the Include and Linking parameters needed to use libxml.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004556 <li>install libxml2-2.3.x and libxml2-devel-2.3.x (libxml-1.8.y and
4557 libxml-devel-1.8.y can be kept simultaneously)</li>
4558 <li>remove your config.cache, relaunch your configuration mechanism, and
4559 recompile, if steps 2 and 3 were done right it should compile as-is</li>
4560 <li>Test that your application is still running correctly, if not this may
4561 be due to extra empty nodes due to formating spaces being kept in libxml2
4562 contrary to libxml1, in that case insert xmlKeepBlanksDefault(1) in your
4563 code before calling the parser (next to
4564 <strong>LIBXML_TEST_VERSION</strong> is a fine place).</li>
4565</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004566
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004567<p>Following those steps should work. It worked for some of my own code.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004568
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004569<p>Let me put some emphasis on the fact that there is far more changes from
4570libxml 1.x to 2.x than the ones you may have to patch for. The overall code
4571has been considerably cleaned up and the conformance to the XML specification
4572has been drastically improved too. Don't take those changes as an excuse to
4573not upgrade, it may cost a lot on the long term ...</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004574
Daniel Veillard52dcab32001-10-30 12:51:17 +00004575<h2><a name="Thread">Thread safety</a></h2>
4576
Daniel Veillard8a469172003-06-12 16:05:07 +00004577<p>Starting with 2.4.7, libxml2 makes provisions to ensure that concurrent
Daniel Veillard52dcab32001-10-30 12:51:17 +00004578threads can safely work in parallel parsing different documents. There is
4579however a couple of things to do to ensure it:</p>
4580<ul>
4581 <li>configure the library accordingly using the --with-threads options</li>
4582 <li>call xmlInitParser() in the "main" thread before using any of the
Daniel Veillard8a469172003-06-12 16:05:07 +00004583 libxml2 API (except possibly selecting a different memory allocator)</li>
Daniel Veillard52dcab32001-10-30 12:51:17 +00004584</ul>
4585
4586<p>Note that the thread safety cannot be ensured for multiple threads sharing
4587the same document, the locking must be done at the application level, libxml
4588exports a basic mutex and reentrant mutexes API in &lt;libxml/threads.h&gt;.
4589The parts of the library checked for thread safety are:</p>
4590<ul>
4591 <li>concurrent loading</li>
4592 <li>file access resolution</li>
4593 <li>catalog access</li>
4594 <li>catalog building</li>
4595 <li>entities lookup/accesses</li>
4596 <li>validation</li>
4597 <li>global variables per-thread override</li>
4598 <li>memory handling</li>
4599</ul>
4600
4601<p>XPath is supposed to be thread safe now, but this wasn't tested
4602seriously.</p>
4603
Daniel Veillard35008381999-10-25 13:15:52 +00004604<h2><a name="DOM"></a><a name="Principles">DOM Principles</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004605
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004606<p><a href="http://www.w3.org/DOM/">DOM</a> stands for the <em>Document
4607Object Model</em>; this is an API for accessing XML or HTML structured
4608documents. Native support for DOM in Gnome is on the way (module gnome-dom),
4609and will be based on gnome-xml. This will be a far cleaner interface to
4610manipulate XML files within Gnome since it won't expose the internal
4611structure.</p>
Daniel Veillard14fff061999-06-22 21:49:07 +00004612
Daniel Veillard8a469172003-06-12 16:05:07 +00004613<p>The current DOM implementation on top of libxml2 is the <a
Daniel Veillarda47fb3d2001-03-25 17:23:49 +00004614href="http://cvs.gnome.org/lxr/source/gdome2/">gdome2 Gnome module</a>, this
4615is a full DOM interface, thanks to Paolo Casarini, check the <a
4616href="http://www.cs.unibo.it/~casarini/gdome2/">Gdome2 homepage</a> for more
4617informations.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004618
Daniel Veillard35008381999-10-25 13:15:52 +00004619<h2><a name="Example"></a><a name="real">A real example</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004620
4621<p>Here is a real size example, where the actual content of the application
4622data is not kept in the DOM tree but uses internal structures. It is based on
Daniel Veillard14fff061999-06-22 21:49:07 +00004623a proposal to keep a database of jobs related to Gnome, with an XML based
Daniel Veillardb05deb71999-08-10 19:04:08 +00004624storage structure. Here is an <a href="gjobs.xml">XML encoded jobs
4625base</a>:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004626<pre>&lt;?xml version="1.0"?&gt;
4627&lt;gjob:Helping xmlns:gjob="http://www.gnome.org/some-location"&gt;
4628 &lt;gjob:Jobs&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004629
Daniel Veillard60979bd2000-07-10 12:17:33 +00004630 &lt;gjob:Job&gt;
4631 &lt;gjob:Project ID="3"/&gt;
4632 &lt;gjob:Application&gt;GBackup&lt;/gjob:Application&gt;
4633 &lt;gjob:Category&gt;Development&lt;/gjob:Category&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004634
Daniel Veillard60979bd2000-07-10 12:17:33 +00004635 &lt;gjob:Update&gt;
4636 &lt;gjob:Status&gt;Open&lt;/gjob:Status&gt;
4637 &lt;gjob:Modified&gt;Mon, 07 Jun 1999 20:27:45 -0400 MET DST&lt;/gjob:Modified&gt;
4638 &lt;gjob:Salary&gt;USD 0.00&lt;/gjob:Salary&gt;
4639 &lt;/gjob:Update&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004640
Daniel Veillard60979bd2000-07-10 12:17:33 +00004641 &lt;gjob:Developers&gt;
4642 &lt;gjob:Developer&gt;
4643 &lt;/gjob:Developer&gt;
4644 &lt;/gjob:Developers&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004645
Daniel Veillard60979bd2000-07-10 12:17:33 +00004646 &lt;gjob:Contact&gt;
4647 &lt;gjob:Person&gt;Nathan Clemons&lt;/gjob:Person&gt;
4648 &lt;gjob:Email&gt;nathan@windsofstorm.net&lt;/gjob:Email&gt;
4649 &lt;gjob:Company&gt;
4650 &lt;/gjob:Company&gt;
4651 &lt;gjob:Organisation&gt;
4652 &lt;/gjob:Organisation&gt;
4653 &lt;gjob:Webpage&gt;
4654 &lt;/gjob:Webpage&gt;
4655 &lt;gjob:Snailmail&gt;
4656 &lt;/gjob:Snailmail&gt;
4657 &lt;gjob:Phone&gt;
4658 &lt;/gjob:Phone&gt;
4659 &lt;/gjob:Contact&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004660
Daniel Veillard60979bd2000-07-10 12:17:33 +00004661 &lt;gjob:Requirements&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004662 The program should be released as free software, under the GPL.
Daniel Veillard60979bd2000-07-10 12:17:33 +00004663 &lt;/gjob:Requirements&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004664
Daniel Veillard60979bd2000-07-10 12:17:33 +00004665 &lt;gjob:Skills&gt;
4666 &lt;/gjob:Skills&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004667
Daniel Veillard60979bd2000-07-10 12:17:33 +00004668 &lt;gjob:Details&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004669 A GNOME based system that will allow a superuser to configure
4670 compressed and uncompressed files and/or file systems to be backed
4671 up with a supported media in the system. This should be able to
4672 perform via find commands generating a list of files that are passed
4673 to tar, dd, cpio, cp, gzip, etc., to be directed to the tape machine
4674 or via operations performed on the filesystem itself. Email
4675 notification and GUI status display very important.
Daniel Veillard60979bd2000-07-10 12:17:33 +00004676 &lt;/gjob:Details&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004677
Daniel Veillard60979bd2000-07-10 12:17:33 +00004678 &lt;/gjob:Job&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +00004679
Daniel Veillard60979bd2000-07-10 12:17:33 +00004680 &lt;/gjob:Jobs&gt;
4681&lt;/gjob:Helping&gt;</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004682
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004683<p>While loading the XML file into an internal DOM tree is a matter of
Daniel Veillard63d83142002-05-20 06:51:05 +00004684calling only a couple of functions, browsing the tree to gather the data and
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004685generate the internal structures is harder, and more error prone.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004686
4687<p>The suggested principle is to be tolerant with respect to the input
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004688structure. For example, the ordering of the attributes is not significant,
4689the XML specification is clear about it. It's also usually a good idea not to
Daniel Veillardec70e912001-02-26 20:10:45 +00004690depend on the order of the children of a given node, unless it really makes
4691things harder. Here is some code to parse the information for a person:</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004692<pre>/*
Daniel Veillard14fff061999-06-22 21:49:07 +00004693 * A person record
4694 */
4695typedef struct person {
4696 char *name;
4697 char *email;
4698 char *company;
4699 char *organisation;
4700 char *smail;
4701 char *webPage;
4702 char *phone;
4703} person, *personPtr;
4704
4705/*
4706 * And the code needed to parse it
4707 */
4708personPtr parsePerson(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
4709 personPtr ret = NULL;
4710
4711DEBUG("parsePerson\n");
4712 /*
4713 * allocate the struct
4714 */
4715 ret = (personPtr) malloc(sizeof(person));
4716 if (ret == NULL) {
4717 fprintf(stderr,"out of memory\n");
Daniel Veillardb05deb71999-08-10 19:04:08 +00004718 return(NULL);
Daniel Veillard14fff061999-06-22 21:49:07 +00004719 }
4720 memset(ret, 0, sizeof(person));
4721
4722 /* We don't care what the top level element name is */
Daniel Veillard60979bd2000-07-10 12:17:33 +00004723 cur = cur-&gt;xmlChildrenNode;
Daniel Veillard14fff061999-06-22 21:49:07 +00004724 while (cur != NULL) {
Daniel Veillard60979bd2000-07-10 12:17:33 +00004725 if ((!strcmp(cur-&gt;name, "Person")) &amp;&amp; (cur-&gt;ns == ns))
4726 ret-&gt;name = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4727 if ((!strcmp(cur-&gt;name, "Email")) &amp;&amp; (cur-&gt;ns == ns))
4728 ret-&gt;email = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4729 cur = cur-&gt;next;
Daniel Veillard14fff061999-06-22 21:49:07 +00004730 }
4731
4732 return(ret);
Daniel Veillardb05deb71999-08-10 19:04:08 +00004733}</pre>
4734
Daniel Veillard91e9d582001-02-26 07:31:12 +00004735<p>Here are a couple of things to notice:</p>
Daniel Veillard14fff061999-06-22 21:49:07 +00004736<ul>
Daniel Veillard91e9d582001-02-26 07:31:12 +00004737 <li>Usually a recursive parsing style is the more convenient one: XML data
Daniel Veillard63d83142002-05-20 06:51:05 +00004738 is by nature subject to repetitive constructs and usually exhibits highly
4739 structured patterns.</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004740 <li>The two arguments of type <em>xmlDocPtr</em> and <em>xmlNsPtr</em>,
4741 i.e. the pointer to the global XML document and the namespace reserved to
4742 the application. Document wide information are needed for example to
4743 decode entities and it's a good coding practice to define a namespace for
4744 your application set of data and test that the element and attributes
4745 you're analyzing actually pertains to your application space. This is
4746 done by a simple equality test (cur-&gt;ns == ns).</li>
Daniel Veillardec70e912001-02-26 20:10:45 +00004747 <li>To retrieve text and attributes value, you can use the function
4748 <em>xmlNodeListGetString</em> to gather all the text and entity reference
4749 nodes generated by the DOM output and produce an single text string.</li>
Daniel Veillard14fff061999-06-22 21:49:07 +00004750</ul>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004751
4752<p>Here is another piece of code used to parse another level of the
4753structure:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +00004754<pre>#include &lt;libxml/tree.h&gt;
Daniel Veillard361d8452000-04-03 19:48:13 +00004755/*
Daniel Veillard14fff061999-06-22 21:49:07 +00004756 * a Description for a Job
4757 */
4758typedef struct job {
4759 char *projectID;
4760 char *application;
4761 char *category;
4762 personPtr contact;
4763 int nbDevelopers;
4764 personPtr developers[100]; /* using dynamic alloc is left as an exercise */
4765} job, *jobPtr;
4766
4767/*
4768 * And the code needed to parse it
4769 */
4770jobPtr parseJob(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
4771 jobPtr ret = NULL;
4772
4773DEBUG("parseJob\n");
4774 /*
4775 * allocate the struct
4776 */
4777 ret = (jobPtr) malloc(sizeof(job));
4778 if (ret == NULL) {
4779 fprintf(stderr,"out of memory\n");
Daniel Veillardb05deb71999-08-10 19:04:08 +00004780 return(NULL);
Daniel Veillard14fff061999-06-22 21:49:07 +00004781 }
4782 memset(ret, 0, sizeof(job));
4783
4784 /* We don't care what the top level element name is */
Daniel Veillard60979bd2000-07-10 12:17:33 +00004785 cur = cur-&gt;xmlChildrenNode;
Daniel Veillard14fff061999-06-22 21:49:07 +00004786 while (cur != NULL) {
4787
Daniel Veillard60979bd2000-07-10 12:17:33 +00004788 if ((!strcmp(cur-&gt;name, "Project")) &amp;&amp; (cur-&gt;ns == ns)) {
4789 ret-&gt;projectID = xmlGetProp(cur, "ID");
4790 if (ret-&gt;projectID == NULL) {
Daniel Veillardb05deb71999-08-10 19:04:08 +00004791 fprintf(stderr, "Project has no ID\n");
4792 }
4793 }
Daniel Veillard60979bd2000-07-10 12:17:33 +00004794 if ((!strcmp(cur-&gt;name, "Application")) &amp;&amp; (cur-&gt;ns == ns))
4795 ret-&gt;application = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4796 if ((!strcmp(cur-&gt;name, "Category")) &amp;&amp; (cur-&gt;ns == ns))
4797 ret-&gt;category = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4798 if ((!strcmp(cur-&gt;name, "Contact")) &amp;&amp; (cur-&gt;ns == ns))
4799 ret-&gt;contact = parsePerson(doc, ns, cur);
4800 cur = cur-&gt;next;
Daniel Veillard14fff061999-06-22 21:49:07 +00004801 }
4802
4803 return(ret);
Daniel Veillardb05deb71999-08-10 19:04:08 +00004804}</pre>
Daniel Veillard14fff061999-06-22 21:49:07 +00004805
Daniel Veillardec70e912001-02-26 20:10:45 +00004806<p>Once you are used to it, writing this kind of code is quite simple, but
Daniel Veillard63d83142002-05-20 06:51:05 +00004807boring. Ultimately, it could be possible to write stubbers taking either C
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +00004808data structure definitions, a set of XML examples or an XML DTD and produce
4809the code needed to import and export the content between C data and XML
4810storage. This is left as an exercise to the reader :-)</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004811
Daniel Veillard6f0adb52000-07-03 11:41:26 +00004812<p>Feel free to use <a href="example/gjobread.c">the code for the full C
4813parsing example</a> as a template, it is also available with Makefile in the
4814Gnome CVS base under gnome-xml/example</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +00004815
Daniel Veillardc310d562000-06-23 18:32:15 +00004816<h2><a name="Contributi">Contributions</a></h2>
4817<ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004818 <li>Bjorn Reese, William Brack and Thomas Broyer have provided a number of
4819 patches, Gary Pennington worked on the validation API, threading support
4820 and Solaris port.</li>
4821 <li>John Fleck helps maintaining the documentation and man pages.</li>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +00004822 <li><a href="mailto:igor@zlatkovic.com">Igor Zlatkovic</a> is now the
4823 maintainer of the Windows port, <a
4824 href="http://www.zlatkovic.com/projects/libxml/index.html">he provides
4825 binaries</a></li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00004826 <li><a href="mailto:Gary.Pennington@sun.com">Gary Pennington</a> provides
4827 <a href="http://garypennington.net/libxml2/">Solaris binaries</a></li>
Daniel Veillarde356c282001-03-10 12:32:04 +00004828 <li><a
4829 href="http://mail.gnome.org/archives/xml/2001-March/msg00014.html">Matt
Daniel Veillard63d83142002-05-20 06:51:05 +00004830 Sergeant</a> developed <a
4831 href="http://axkit.org/download/">XML::LibXSLT</a>, a Perl wrapper for
Daniel Veillardaf43f632002-03-08 15:05:20 +00004832 libxml2/libxslt as part of the <a href="http://axkit.com/">AxKit XML
4833 application server</a></li>
4834 <li><a href="mailto:fnatter@gmx.net">Felix Natter</a> and <a
4835 href="mailto:geertk@ai.rug.nl">Geert Kloosterman</a> provide <a
Daniel Veillardca989762001-06-23 17:39:29 +00004836 href="libxml-doc.el">an emacs module</a> to lookup libxml(2) functions
Daniel Veillard3f6f7f62000-06-30 17:58:25 +00004837 documentation</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +00004838 <li><a href="mailto:sherwin@nlm.nih.gov">Ziying Sherwin</a> provided <a
4839 href="http://xmlsoft.org/messages/0488.html">man pages</a></li>
Daniel Veillard5168dbf2001-07-07 00:18:23 +00004840 <li>there is a module for <a
4841 href="http://acs-misc.sourceforge.net/nsxml.html">libxml/libxslt support
4842 in OpenNSD/AOLServer</a></li>
Daniel Veillard2d347fa2002-03-17 10:34:11 +00004843 <li><a href="mailto:dkuhlman@cutter.rexx.com">Dave Kuhlman</a> provided the
4844 first version of libxml/libxslt <a
4845 href="http://www.rexx.com/~dkuhlman">wrappers for Python</a></li>
Daniel Veillard1aadc442001-11-28 13:10:32 +00004846 <li>Petr Kozelka provides <a
4847 href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
4848 libxml2</a> with Kylix and Delphi and other Pascal compilers</li>
Daniel Veillard2d347fa2002-03-17 10:34:11 +00004849 <li><a href="mailto:aleksey@aleksey.com">Aleksey Sanin</a> implemented the
4850 <a href="http://www.w3.org/Signature/">XML Canonicalization and XML
4851 Digital Signature</a> <a
4852 href="http://www.aleksey.com/xmlsec/">implementations for libxml2</a></li>
Daniel Veillardd49370e2005-04-11 23:28:16 +00004853 <li><a href="mailto:Steve.Ball@explain.com.au">Steve Ball</a>
4854 and contributors maintain <a
Daniel Veillard17bed982003-02-24 20:11:43 +00004855 href="http://tclxml.sourceforge.net/">tcl bindings for libxml2 and
4856 libxslt</a>, as well as <a
4857 href="http://tclxml.sf.net/tkxmllint.html">tkxmllint</a> a GUI for
4858 xmllint and <a href="http://tclxml.sf.net/tkxsltproc.html">tkxsltproc</a>
4859 a GUI for xsltproc.</li>
Daniel Veillardc310d562000-06-23 18:32:15 +00004860</ul>
4861
Daniel Veillardc8eab3a1999-09-04 18:27:23 +00004862<p></p>
Daniel Veillardccb09631998-10-27 06:21:04 +00004863</body>
4864</html>