Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / libxml2 / c480c4ea56bbb5aad5ac991dafef5702dabb6360 / . / doc / xml.html
blob: 63c99a267ef9830e848b900b3e0b4318bb8f0bfc [file] [log] [blame]
Daniel Veillard09ab7e12001-07-10 15:49:44 +0000[diff] [blame]1<!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 +0000[diff] [blame]3<html>
4<head>
Daniel Veillard598bec32003-07-06 10:02:03 +0000[diff] [blame]5 <title>The XML C parser and toolkit of Gnome</title>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]6 <meta name="GENERATOR" content="amaya 5.1">
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]7 <meta http-equiv="Content-Type" content="text/html">
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]8</head>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]9
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]10<body bgcolor="#ffffff">
Daniel Veillard598bec32003-07-06 10:02:03 +0000[diff] [blame]11<h1 align="center">The XML C parser and toolkit of Gnome</h1>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]12
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]13<h1>Note: this is the flat content of the <a href="index.html">web
14site</a></h1>
15
Daniel Veillardc9484202001-10-24 12:35:52 +0000[diff] [blame]16<h1 style="text-align: center">libxml, a.k.a. gnome-xml</h1>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]17
18<p></p>
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]19
Daniel Veillard598bec32003-07-06 10:02:03 +0000[diff] [blame]20<p>Libxml2 is the XML C parser and toolkit developed for the Gnome project
Daniel Veillard23a52c52003-08-18 10:01:18 +0000[diff] [blame]21(but usable outside of the Gnome platform), it is free software available
Daniel Veillardeec1ae92003-09-09 13:11:01 +0000[diff] [blame]22under the <a href="http://www.opensource.org/licenses/mit-license.html">MIT
23License</a>. XML itself is a metalanguage to design markup languages, i.e.
24text language where semantic and structure are added to the content using
25extra "markup" information enclosed between angle brackets. HTML is the most
26well-known markup language. Though the library is written in C <a
27href="python.html">a variety of language bindings</a> make it available in
28other environments.</p>
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]29
Daniel Veillard710823b2003-03-04 10:05:52 +0000[diff] [blame]30<p>Libxml2 is known to be very portable, the library should build and work
31without serious troubles on a variety of systems (Linux, Unix, Windows,
32CygWin, MacOS, MacOS X, RISC Os, OS/2, VMS, QNX, MVS, ...)</p>
33
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]34<p>Libxml2 implements a number of existing standards related to markup
35languages:</p>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]36<ul>
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]37 <li>the XML standard: <a
38 href="http://www.w3.org/TR/REC-xml">http://www.w3.org/TR/REC-xml</a></li>
39 <li>Namespaces in XML: <a
40 href="http://www.w3.org/TR/REC-xml-names/">http://www.w3.org/TR/REC-xml-names/</a></li>
41 <li>XML Base: <a
42 href="http://www.w3.org/TR/xmlbase/">http://www.w3.org/TR/xmlbase/</a></li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]43 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc2396.txt">RFC 2396</a> :
44 Uniform Resource Identifiers <a
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]45 href="http://www.ietf.org/rfc/rfc2396.txt">http://www.ietf.org/rfc/rfc2396.txt</a></li>
46 <li>XML Path Language (XPath) 1.0: <a
47 href="http://www.w3.org/TR/xpath">http://www.w3.org/TR/xpath</a></li>
48 <li>HTML4 parser: <a
49 href="http://www.w3.org/TR/html401/">http://www.w3.org/TR/html401/</a></li>
Daniel Veillard23a52c52003-08-18 10:01:18 +0000[diff] [blame]50 <li>XML Pointer Language (XPointer) Version 1.0: <a
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]51 href="http://www.w3.org/TR/xptr">http://www.w3.org/TR/xptr</a></li>
52 <li>XML Inclusions (XInclude) Version 1.0: <a
53 href="http://www.w3.org/TR/xinclude/">http://www.w3.org/TR/xinclude/</a></li>
Daniel Veillard23a52c52003-08-18 10:01:18 +0000[diff] [blame]54 <li>ISO-8859-x encodings, as well as <a
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]55 href="http://www.cis.ohio-state.edu/rfc/rfc2044.txt">rfc2044</a> [UTF-8]
56 and <a href="http://www.cis.ohio-state.edu/rfc/rfc2781.txt">rfc2781</a>
Daniel Veillard23a52c52003-08-18 10:01:18 +0000[diff] [blame]57 [UTF-16] Unicode encodings, and more if using iconv support</li>
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]58 <li>part of SGML Open Technical Resolution TR9401:1997</li>
59 <li>XML Catalogs Working Draft 06 August 2001: <a
60 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 +0000[diff] [blame]61 <li>Canonical XML Version 1.0: <a
62 href="http://www.w3.org/TR/xml-c14n">http://www.w3.org/TR/xml-c14n</a>
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000[diff] [blame]63 and the Exclusive XML Canonicalization CR draft <a
64 href="http://www.w3.org/TR/xml-exc-c14n">http://www.w3.org/TR/xml-exc-c14n</a></li>
Daniel Veillard17bed982003-02-24 20:11:43 +0000[diff] [blame]65 <li>Relax NG Committee Specification 3 December 2001 <a
66 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 +0000[diff] [blame]67 <li>W3C XML Schemas Part 2: Datatypes <a
68 href="http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/">REC 02 May
Daniel Veillard23a52c52003-08-18 10:01:18 +0000[diff] [blame]69 2001</a> except the base64Binary type</li>
Daniel Veillard96984452000-08-31 13:50:12 +0000[diff] [blame]70</ul>
71
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]72<p>In most cases libxml2 tries to implement the specifications in a
73relatively strictly compliant way. As of release 2.4.16, libxml2 passes all
741800+ tests from the <a
Daniel Veillarda5393562002-02-20 11:40:49 +0000[diff] [blame]75href="http://www.oasis-open.org/committees/xml-conformance/">OASIS XML Tests
76Suite</a>.</p>
Daniel Veillard5b16f582002-02-20 11:38:46 +0000[diff] [blame]77
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]78<p>To some extent libxml2 provides support for the following additional
79specifications but doesn't claim to implement them completely:</p>
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]80<ul>
81 <li>Document Object Model (DOM) <a
82 href="http://www.w3.org/TR/DOM-Level-2-Core/">http://www.w3.org/TR/DOM-Level-2-Core/</a>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]83 it doesn't implement the API itself, gdome2 does this on top of
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]84 libxml2</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]85 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc959.txt">RFC 959</a> :
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]86 libxml2 implements a basic FTP client code</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]87 <li><a href="http://www.cis.ohio-state.edu/rfc/rfc1945.txt">RFC 1945</a> :
88 HTTP/1.0, again a basic HTTP client code</li>
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]89 <li>SAX: a minimal SAX implementation compatible with early expat
90 versions</li>
91 <li>DocBook SGML v4: libxml2 includes a hackish parser to transition to
92 XML</li>
93</ul>
94
Daniel Veillardf83a2c72003-04-08 13:48:40 +0000[diff] [blame]95<p>A partial implementation of <a
96href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">XML Schemas Part
971: Structure</a> is being worked on but it would be far too early to make any
98conformance statement about it at the moment.</p>
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000[diff] [blame]99
Daniel Veillard96984452000-08-31 13:50:12 +0000[diff] [blame]100<p>Separate documents:</p>
101<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]102 <li><a href="http://xmlsoft.org/XSLT/">the libxslt page</a> providing an
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000[diff] [blame]103 implementation of XSLT 1.0 and common extensions like EXSLT for
104 libxml2</li>
Daniel Veillardc6271d22001-10-27 07:50:58 +0000[diff] [blame]105 <li><a href="http://www.cs.unibo.it/~casarini/gdome2/">the gdome2 page</a>
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000[diff] [blame]106 : a standard DOM2 implementation for libxml2</li>
107 <li><a href="http://www.aleksey.com/xmlsec/">the XMLSec page</a>: an
108 implementation of <a href="http://www.w3.org/TR/xmldsig-core/">W3C XML
109 Digital Signature</a> for libxml2</li>
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000[diff] [blame]110 <li>also check the related links section below for more related and active
111 projects.</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]112</ul>
113
Daniel Veillard806cada2003-03-19 21:58:59 +0000[diff] [blame]114<p>Results of the <a
115href="http://xmlbench.sourceforge.net/results/benchmark/index.html">xmlbench
116benchmark</a> on sourceforge 19 March 2003 (smaller is better):</p>
Daniel Veillardd8da01c2003-03-24 15:58:23 +0000[diff] [blame]117
118<p align="center"><img src="benchmark.gif"
119alt="benchmark results for Expat Xerces libxml2 Oracle and Sun toolkits"></p>
Daniel Veillard806cada2003-03-19 21:58:59 +0000[diff] [blame]120
Daniel Veillarde1662542002-08-28 11:50:59 +0000[diff] [blame]121<p>Logo designed by <a href="mailto:liyanage@access.ch">Marc Liyanage</a>.</p>
122
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]123<h2><a name="Introducti">Introduction</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]124
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]125<p>This document describes libxml, the <a
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]126href="http://www.w3.org/XML/">XML</a> C parser and toolkit developed for the
127<a href="http://www.gnome.org/">Gnome</a> project. <a
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000[diff] [blame]128href="http://www.w3.org/XML/">XML is a standard</a> for building tag-based
129structured documents/data.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]130
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]131<p>Here are some key points about libxml:</p>
132<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]133 <li>Libxml2 exports Push (progressive) and Pull (blocking) type parser
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000[diff] [blame]134 interfaces for both XML and HTML.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]135 <li>Libxml2 can do DTD validation at parse time, using a parsed document
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]136 instance, or with an arbitrary DTD.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]137 <li>Libxml2 includes complete <a
Daniel Veillard8c2ecaf2001-07-10 17:53:07 +0000[diff] [blame]138 href="http://www.w3.org/TR/xpath">XPath</a>, <a
139 href="http://www.w3.org/TR/xptr">XPointer</a> and <a
140 href="http://www.w3.org/TR/xinclude">XInclude</a> implementations.</li>
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000[diff] [blame]141 <li>It is written in plain C, making as few assumptions as possible, and
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame]142 sticking closely to ANSI C/POSIX for easy embedding. Works on
Daniel Veillardab8500d2000-10-15 21:06:19 +0000[diff] [blame]143 Linux/Unix/Windows, ported to a number of other platforms.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]144 <li>Basic support for HTTP and FTP client allowing applications to fetch
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]145 remote resources.</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]146 <li>The design is modular, most of the extensions can be compiled out.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]147 <li>The internal document representation is as close as possible to the <a
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]148 href="http://www.w3.org/DOM/">DOM</a> interfaces.</li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]149 <li>Libxml2 also has a <a
150 href="http://www.megginson.com/SAX/index.html">SAX like interface</a>;
151 the interface is designed to be compatible with <a
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]152 href="http://www.jclark.com/xml/expat.html">Expat</a>.</li>
Daniel Veillardc575b992002-02-08 13:28:40 +0000[diff] [blame]153 <li>This library is released under the <a
154 href="http://www.opensource.org/licenses/mit-license.html">MIT
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]155 License</a>. See the Copyright file in the distribution for the precise
Daniel Veillardc575b992002-02-08 13:28:40 +0000[diff] [blame]156 wording.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]157</ul>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]158
Daniel Veillarde0c1d722001-03-21 10:28:36 +0000[diff] [blame]159<p>Warning: unless you are forced to because your application links with a
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000[diff] [blame]160Gnome-1.X library requiring it, <strong><span
Daniel Veillarde0c1d722001-03-21 10:28:36 +0000[diff] [blame]161style="background-color: #FF0000">Do Not Use libxml1</span></strong>, use
162libxml2</p>
163
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]164<h2><a name="FAQ">FAQ</a></h2>
165
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]166<p>Table of Contents:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]167<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]168 <li><a href="FAQ.html#License">License(s)</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]169 <li><a href="FAQ.html#Installati">Installation</a></li>
170 <li><a href="FAQ.html#Compilatio">Compilation</a></li>
171 <li><a href="FAQ.html#Developer">Developer corner</a></li>
172</ul>
173
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]174<h3><a name="License">License</a>(s)</h3>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]175<ol>
176 <li><em>Licensing Terms for libxml</em>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]177 <p>libxml2 is released under the <a
Daniel Veillardc575b992002-02-08 13:28:40 +0000[diff] [blame]178 href="http://www.opensource.org/licenses/mit-license.html">MIT
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]179 License</a>; see the file Copyright in the distribution for the precise
Daniel Veillardc575b992002-02-08 13:28:40 +0000[diff] [blame]180 wording</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]181 </li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]182 <li><em>Can I embed libxml2 in a proprietary application ?</em>
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]183 <p>Yes. The MIT License allows you to keep proprietary the changes you
184 made to libxml, but it would be graceful to send-back bug fixes and
185 improvements as patches for possible incorporation in the main
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]186 development tree.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]187 </li>
188</ol>
189
190<h3><a name="Installati">Installation</a></h3>
191<ol>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]192 <li><strong><span style="background-color: #FF0000">Do Not Use
193 libxml1</span></strong>, use libxml2</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]194 <li><em>Where can I get libxml</em> ?
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]195 <p>The original distribution comes from <a
196 href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> or <a
Daniel Veillard6581e1b2003-02-09 22:21:43 +0000[diff] [blame]197 href="ftp://ftp.gnome.org/pub/GNOME/sources/libxml2/2.5/">gnome.org</a></p>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]198 <p>Most Linux and BSD distributions include libxml, this is probably the
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]199 safer way for end-users to use libxml.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]200 <p>David Doolin provides precompiled Windows versions at <a
201 href="http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/ ">http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/</a></p>
202 </li>
203 <li><em>I see libxml and libxml2 releases, which one should I install ?</em>
204 <ul>
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]205 <li>If you are not constrained by backward compatibility issues with
206 existing applications, install libxml2 only</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]207 <li>If you are not doing development, you can safely install both.
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]208 Usually the packages <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]209 href="http://rpmfind.net/linux/RPM/libxml.html">libxml</a> and <a
210 href="http://rpmfind.net/linux/RPM/libxml2.html">libxml2</a> are
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]211 compatible (this is not the case for development packages).</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]212 <li>If you are a developer and your system provides separate packaging
213 for shared libraries and the development components, it is possible
214 to install libxml and libxml2, and also <a
215 href="http://rpmfind.net/linux/RPM/libxml-devel.html">libxml-devel</a>
216 and <a
217 href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml2-devel</a>
218 too for libxml2 &gt;= 2.3.0</li>
219 <li>If you are developing a new application, please develop against
220 libxml2(-devel)</li>
221 </ul>
222 </li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]223 <li><em>I can't install the libxml package, it conflicts with libxml0</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]224 <p>You probably have an old libxml0 package used to provide the shared
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]225 library for libxml.so.0, you can probably safely remove it. The libxml
226 packages provided on <a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]227 href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> provide
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]228 libxml.so.0</p>
229 </li>
230 <li><em>I can't install the libxml(2) RPM package due to failed
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]231 dependencies</em>
232 <p>The most generic solution is to re-fetch the latest src.rpm , and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]233 rebuild it locally with</p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]234 <p><code>rpm --rebuild libxml(2)-xxx.src.rpm</code>.</p>
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]235 <p>If everything goes well it will generate two binary rpm packages (one
236 providing the shared libs and xmllint, and the other one, the -devel
237 package, providing includes, static libraries and scripts needed to build
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]238 applications with libxml(2)) that you can install locally.</p>
239 </li>
240</ol>
241
242<h3><a name="Compilatio">Compilation</a></h3>
243<ol>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]244 <li><em>What is the process to compile libxml2 ?</em>
245 <p>As most UNIX libraries libxml2 follows the "standard":</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]246 <p><code>gunzip -c xxx.tar.gz | tar xvf -</code></p>
247 <p><code>cd libxml-xxxx</code></p>
248 <p><code>./configure --help</code></p>
249 <p>to see the options, then the compilation/installation proper</p>
250 <p><code>./configure [possible options]</code></p>
251 <p><code>make</code></p>
252 <p><code>make install</code></p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]253 <p>At that point you may have to rerun ldconfig or a similar utility to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]254 update your list of installed shared libs.</p>
255 </li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]256 <li><em>What other libraries are needed to compile/install libxml2 ?</em>
257 <p>Libxml2 does not require any other library, the normal C ANSI API
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]258 should be sufficient (please report any violation to this rule you may
259 find).</p>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]260 <p>However if found at configuration time libxml2 will detect and use the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]261 following libs:</p>
262 <ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]263 <li><a href="http://www.info-zip.org/pub/infozip/zlib/">libz</a> : a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]264 highly portable and available widely compression library.</li>
265 <li>iconv: a powerful character encoding conversion library. It is
266 included by default in recent glibc libraries, so it doesn't need to
267 be installed specifically on Linux. It now seems a <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]268 href="http://www.opennc.org/onlinepubs/7908799/xsh/iconv.html">part
269 of the official UNIX</a> specification. Here is one <a
Daniel Veillarddad3f682002-11-17 16:47:27 +0000[diff] [blame]270 href="http://www.gnu.org/software/libiconv/">implementation of the
271 library</a> which source can be found <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]272 href="ftp://ftp.ilog.fr/pub/Users/haible/gnu/">here</a>.</li>
273 </ul>
274 </li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]275 <li><em>Make check fails on some platforms</em>
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]276 <p>Sometimes the regression tests' results don't completely match the
277 value produced by the parser, and the makefile uses diff to print the
278 delta. On some platforms the diff return breaks the compilation process;
279 if the diff is small this is probably not a serious problem.</p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]280 <p>Sometimes (especially on Solaris) make checks fail due to limitations
Daniel Veillarde46182c2002-02-12 14:29:11 +0000[diff] [blame]281 in make. Try using GNU-make instead.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]282 </li>
283 <li><em>I use the CVS version and there is no configure script</em>
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]284 <p>The configure script (and other Makefiles) are generated. Use the
285 autogen.sh script to regenerate the configure script and Makefiles,
286 like:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]287 <p><code>./autogen.sh --prefix=/usr --disable-shared</code></p>
288 </li>
289 <li><em>I have troubles when running make tests with gcc-3.0</em>
290 <p>It seems the initial release of gcc-3.0 has a problem with the
291 optimizer which miscompiles the URI module. Please use another
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]292 compiler.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]293 </li>
294</ol>
295
296<h3><a name="Developer">Developer</a> corner</h3>
297<ol>
Daniel Veillard93d95252003-04-29 20:25:40 +0000[diff] [blame]298 <li><em>Troubles compiling or linking programs using libxml2</em>
299 <p>Usually the problem comes from the fact that the compiler doesn't get
300 the right compilation or linking flags. There is a small shell script
301 <code>xml2-config</code> which is installed as part of libxml2 usual
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]302 install process which provides those flags. Use</p>
Daniel Veillard93d95252003-04-29 20:25:40 +0000[diff] [blame]303 <p><code>xml2-config --cflags</code></p>
304 <p>to get the compilation flags and</p>
305 <p><code>xml2-config --libs</code></p>
306 <p>to get the linker flags. Usually this is done directly from the
307 Makefile as:</p>
308 <p><code>CFLAGS=`xml2-config --cflags`</code></p>
309 <p><code>LIBS=`xml2-config --libs`</code></p>
310 </li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]311 <li><em>xmlDocDump() generates output on one line.</em>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]312 <p>Libxml2 will not <strong>invent</strong> spaces in the content of a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]313 document since <strong>all spaces in the content of a document are
314 significant</strong>. If you build a tree from the API and want
315 indentation:</p>
316 <ol>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]317 <li>the correct way is to generate those yourself too.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]318 <li>the dangerous way is to ask libxml2 to add those blanks to your
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]319 content <strong>modifying the content of your document in the
320 process</strong>. The result may not be what you expect. There is
321 <strong>NO</strong> way to guarantee that such a modification won't
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]322 affect other parts of the content of your document. See <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000[diff] [blame]323 href="http://xmlsoft.org/html/libxml-parser.html#xmlKeepBlanksDefault">xmlKeepBlanksDefault
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]324 ()</a> and <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000[diff] [blame]325 href="http://xmlsoft.org/html/libxml-tree.html#xmlSaveFormatFile">xmlSaveFormatFile
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]326 ()</a></li>
327 </ol>
328 </li>
329 <li>Extra nodes in the document:
330 <p><em>For a XML file as below:</em></p>
331 <pre>&lt;?xml version="1.0"?&gt;
332&lt;PLAN xmlns="http://www.argus.ca/autotest/1.0/"&gt;
333&lt;NODE CommFlag="0"/&gt;
334&lt;NODE CommFlag="1"/&gt;
335&lt;/PLAN&gt;</pre>
336 <p><em>after parsing it with the function
337 pxmlDoc=xmlParseFile(...);</em></p>
338 <p><em>I want to the get the content of the first node (node with the
339 CommFlag="0")</em></p>
340 <p><em>so I did it as following;</em></p>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]341 <pre>xmlNodePtr pnode;
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]342pnode=pxmlDoc-&gt;children-&gt;children;</pre>
343 <p><em>but it does not work. If I change it to</em></p>
344 <pre>pnode=pxmlDoc-&gt;children-&gt;children-&gt;next;</pre>
345 <p><em>then it works. Can someone explain it to me.</em></p>
346 <p></p>
347 <p>In XML all characters in the content of the document are significant
348 <strong>including blanks and formatting line breaks</strong>.</p>
349 <p>The extra nodes you are wondering about are just that, text nodes with
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]350 the formatting spaces which are part of the document but that people tend
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]351 to forget. There is a function <a
352 href="http://xmlsoft.org/html/libxml-parser.html">xmlKeepBlanksDefault
353 ()</a> to remove those at parse time, but that's an heuristic, and its
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]354 use should be limited to cases where you are certain there is no
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]355 mixed-content in the document.</p>
356 </li>
357 <li><em>I get compilation errors of existing code like when accessing
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]358 <strong>root</strong> or <strong>child fields</strong> of nodes.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]359 <p>You are compiling code developed for libxml version 1 and using a
360 libxml2 development environment. Either switch back to libxml v1 devel or
361 even better fix the code to compile with libxml2 (or both) by <a
362 href="upgrade.html">following the instructions</a>.</p>
363 </li>
364 <li><em>I get compilation errors about non existing
365 <strong>xmlRootNode</strong> or <strong>xmlChildrenNode</strong>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]366 fields.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]367 <p>The source code you are using has been <a
368 href="upgrade.html">upgraded</a> to be able to compile with both libxml
369 and libxml2, but you need to install a more recent version:
370 libxml(-devel) &gt;= 1.8.8 or libxml2(-devel) &gt;= 2.1.0</p>
371 </li>
372 <li><em>XPath implementation looks seriously broken</em>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]373 <p>XPath implementation prior to 2.3.0 was really incomplete. Upgrade to
374 a recent version, there are no known bugs in the current version.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]375 </li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]376 <li><em>The example provided in the web page does not compile.</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]377 <p>It's hard to maintain the documentation in sync with the code
378 &lt;grin/&gt; ...</p>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]379 <p>Check the previous points 1/ and 2/ raised before, and please send
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]380 patches.</p>
381 </li>
Daniel Veillard8d7b5c72003-11-15 18:24:36 +0000[diff] [blame]382 <li><em>Where can I get more examples and information than provided on the
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]383 web page?</em>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]384 <p>Ideally a libxml2 book would be nice. I have no such plan ... But you
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]385 can:</p>
386 <ul>
387 <li>check more deeply the <a href="html/libxml-lib.html">existing
388 generated doc</a></li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000[diff] [blame^]389 <li>have a look at <a href="examples/index.html">the set of
390 examples</a>.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]391 <li>look for examples of use for libxml2 function using the Gnome code.
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]392 For example the following will query the full Gnome CVS base for the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]393 use of the <strong>xmlAddChild()</strong> function:
394 <p><a
395 href="http://cvs.gnome.org/lxr/search?string=xmlAddChild">http://cvs.gnome.org/lxr/search?string=xmlAddChild</a></p>
396 <p>This may be slow, a large hardware donation to the gnome project
397 could cure this :-)</p>
398 </li>
399 <li><a
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000[diff] [blame^]400 href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gnome-xml">Browse
401 the libxml2 source</a> , I try to write code as clean and documented
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]402 as possible, so looking at it may be helpful. In particular the code
403 of xmllint.c and of the various testXXX.c test programs should
404 provide good examples of how to do things with the library.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]405 </ul>
406 </li>
407 <li>What about C++ ?
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]408 <p>libxml2 is written in pure C in order to allow easy reuse on a number
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]409 of platforms, including embedded systems. I don't intend to convert to
410 C++.</p>
Daniel Veillard91e69c52003-08-04 01:43:07 +0000[diff] [blame]411 <p>There is however a C++ wrapper which may fulfill your needs:</p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000[diff] [blame]412 <ul>
413 <li>by Ari Johnson &lt;ari@btigate.com&gt;:
414 <p>Website: <a
Daniel Veillard91e69c52003-08-04 01:43:07 +0000[diff] [blame]415 href="http://libxmlplusplus.sourceforge.net/">http://libxmlplusplus.sourceforge.net/</a></p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000[diff] [blame]416 <p>Download: <a
Daniel Veillard91e69c52003-08-04 01:43:07 +0000[diff] [blame]417 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 +0000[diff] [blame]418 </li>
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000[diff] [blame]419 <!-- Website is currently unavailable as of 2003-08-02
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000[diff] [blame]420 <li>by Peter Jones &lt;pjones@pmade.org&gt;
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000[diff] [blame]421 <p>Website: <a
422 href="http://pmade.org/pjones/software/xmlwrapp/">http://pmade.org/pjones/software/xmlwrapp/</a></p>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000[diff] [blame]423 </li>
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000[diff] [blame]424 -->
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000[diff] [blame]425 </ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]426 </li>
427 <li>How to validate a document a posteriori ?
428 <p>It is possible to validate documents which had not been validated at
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]429 initial parsing time or documents which have been built from scratch
430 using the API. Use the <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000[diff] [blame]431 href="http://xmlsoft.org/html/libxml-valid.html#xmlValidateDtd">xmlValidateDtd()</a>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]432 function. It is also possible to simply add a DTD to an existing
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]433 document:</p>
434 <pre>xmlDocPtr doc; /* your existing document */
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]435xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
436
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]437 dtd-&gt;name = xmlStrDup((xmlChar*)"root_name"); /* use the given root */
438
439 doc-&gt;intSubset = dtd;
440 if (doc-&gt;children == NULL) xmlAddChild((xmlNodePtr)doc, (xmlNodePtr)dtd);
441 else xmlAddPrevSibling(doc-&gt;children, (xmlNodePtr)dtd);
442 </pre>
443 </li>
Daniel Veillarddad3f682002-11-17 16:47:27 +0000[diff] [blame]444 <li>So what is this funky "xmlChar" used all the time?
445 <p>It is a null terminated sequence of utf-8 characters. And only utf-8!
446 You need to convert strings encoded in different ways to utf-8 before
447 passing them to the API. This can be accomplished with the iconv library
448 for instance.</p>
John Fleck61f6fb62002-10-31 15:23:29 +0000[diff] [blame]449 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]450 <li>etc ...</li>
451</ol>
452
453<p></p>
454
Daniel Veillard66f68e72003-08-18 16:39:51 +0000[diff] [blame]455<h2><a name="Documentat">Developer Menu</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]456
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]457<p>There are several on-line resources related to using libxml:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]458<ol>
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000[diff] [blame]459 <li>Use the <a href="search.php">search engine</a> to look up
460 information.</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]461 <li>Check the <a href="FAQ.html">FAQ.</a></li>
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]462 <li>Check the <a href="http://xmlsoft.org/html/libxml-lib.html">extensive
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000[diff] [blame]463 documentation</a> automatically extracted from code comments.</li>
Daniel Veillard8d869642000-07-14 12:12:59 +0000[diff] [blame]464 <li>Look at the documentation about <a href="encoding.html">libxml
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]465 internationalization support</a>.</li>
Daniel Veillardbc66f852002-01-14 09:49:20 +0000[diff] [blame]466 <li>This page provides a global overview and <a href="example.html">some
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]467 examples</a> on how to use libxml.</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000[diff] [blame^]468 <li><a href="examples/index.html">Code examples</a></li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]469 <li>John Fleck's libxml2 tutorial: <a href="tutorial/index.html">html</a>
470 or <a href="tutorial/xmltutorial.pdf">pdf</a>.</li>
Daniel Veillard1177ca42003-04-26 22:29:54 +0000[diff] [blame]471 <li>If you need to parse large files, check the <a
472 href="xmlreader.html">xmlReader</a> API tutorial</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]473 <li><a href="mailto:james@daa.com.au">James Henstridge</a> wrote <a
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]474 href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">some nice
475 documentation</a> explaining how to use the libxml SAX interface.</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000[diff] [blame^]476 <li>George Lebl wrote <a
MST 2003 John Fleck2b7142a2003-11-22 03:55:27 +0000[diff] [blame]477 href="http://www-106.ibm.com/developerworks/library/l-gnome3/">an article
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]478 for IBM developerWorks</a> about using libxml.</li>
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]479 <li>Check <a href="http://cvs.gnome.org/lxr/source/gnome-xml/TODO">the TODO
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]480 file</a>.</li>
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]481 <li>Read the <a href="upgrade.html">1.x to 2.x upgrade path</a>
482 description. If you are starting a new project using libxml you should
483 really use the 2.x version.</li>
Daniel Veillard845cce42002-01-09 11:51:37 +0000[diff] [blame]484 <li>And don't forget to look at the <a
485 href="http://mail.gnome.org/archives/xml/">mailing-list archive</a>.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]486</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]487
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]488<h2><a name="Reporting">Reporting bugs and getting help</a></h2>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]489
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]490<p>Well, bugs or missing features are always possible, and I will make a
491point of fixing them in a timely fashion. The best way to report a bug is to
Daniel Veillardccf996f2003-08-14 10:48:38 +0000[diff] [blame]492use the <a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]493bug tracking database</a> (make sure to use the "libxml2" module name). I
494look at reports there regularly and it's good to have a reminder when a bug
495is still open. Be sure to specify that the bug is for the package libxml2.</p>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]496
Daniel Veillard4ac494b2003-09-18 15:08:00 +0000[diff] [blame]497<p>For small problems you can try to get help on IRC, the #xml channel on
498irc.gnome.org (port 6667) usually have a few person subscribed which may help
499(but there is no garantee and if a real issue is raised it should go on the
500mailing-list for archival).</p>
Daniel Veillard9582d6c2003-09-16 11:40:04 +0000[diff] [blame]501
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]502<p>There is also a mailing-list <a
Daniel Veillard3197f162001-04-04 00:40:08 +0000[diff] [blame]503href="mailto:xml@gnome.org">xml@gnome.org</a> for libxml, with an <a
504href="http://mail.gnome.org/archives/xml/">on-line archive</a> (<a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]505href="http://xmlsoft.org/messages">old</a>). To subscribe to this list,
506please visit the <a
507href="http://mail.gnome.org/mailman/listinfo/xml">associated Web</a> page and
508follow the instructions. <strong>Do not send code, I won't debug it</strong>
509(but patches are really appreciated!).</p>
Daniel Veillard234547b2001-07-05 09:46:10 +0000[diff] [blame]510
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]511<p>Check the following <strong><span style="color: #FF0000">before
512posting</span></strong>:</p>
Daniel Veillard234547b2001-07-05 09:46:10 +0000[diff] [blame]513<ul>
Daniel Veillard321be0c2002-10-08 21:26:42 +0000[diff] [blame]514 <li>Read the <a href="FAQ.html">FAQ</a> and <a href="search.php">use the
Daniel Veillarda37aab82003-06-09 09:10:36 +0000[diff] [blame]515 search engine</a> to get information related to your problem.</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]516 <li>Make sure you are <a href="ftp://xmlsoft.org/">using a recent
517 version</a>, and that the problem still shows up in a recent version.</li>
518 <li>Check the <a href="http://mail.gnome.org/archives/xml/">list
519 archives</a> to see if the problem was reported already. In this case
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]520 there is probably a fix available, similarly check the <a
Daniel Veillardccf996f2003-08-14 10:48:38 +0000[diff] [blame]521 href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">registered
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]522 open bugs</a>.</li>
523 <li>Make sure you can reproduce the bug with xmllint or one of the test
524 programs found in source in the distribution.</li>
Daniel Veillard234547b2001-07-05 09:46:10 +0000[diff] [blame]525 <li>Please send the command showing the error as well as the input (as an
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]526 attachment)</li>
Daniel Veillard234547b2001-07-05 09:46:10 +0000[diff] [blame]527</ul>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]528
Daniel Veillarda37aab82003-06-09 09:10:36 +0000[diff] [blame]529<p>Then send the bug with associated information to reproduce it to the <a
Daniel Veillard33a67802001-03-07 09:44:02 +0000[diff] [blame]530href="mailto:xml@gnome.org">xml@gnome.org</a> list; if it's really libxml
Daniel Veillard98d071d2003-01-10 09:22:44 +0000[diff] [blame]531related I will approve it. Please do not send mail to me directly, it makes
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]532things really hard to track and in some cases I am not the best person to
Daniel Veillard98d071d2003-01-10 09:22:44 +0000[diff] [blame]533answer a given question, ask on the list.</p>
534
535<p>To <span style="color: #E50000">be really clear about support</span>:</p>
536<ul>
Daniel Veillarda37aab82003-06-09 09:10:36 +0000[diff] [blame]537 <li>Support or help <span style="color: #E50000">requests MUST be sent to
Daniel Veillard98d071d2003-01-10 09:22:44 +0000[diff] [blame]538 the list or on bugzilla</span> in case of problems, so that the Question
539 and Answers can be shared publicly. Failing to do so carries the implicit
540 message "I want free support but I don't want to share the benefits with
Daniel Veillard831e8fd2003-01-25 11:45:34 +0000[diff] [blame]541 others" and is not welcome. I will automatically Carbon-Copy the
542 xml@gnome.org mailing list for any technical reply made about libxml2 or
543 libxslt.</li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]544 <li>There is <span style="color: #E50000">no garantee of support</span>, if
545 your question remains unanswered after a week, repost it, making sure you
546 gave all the detail needed and the information requested.</li>
Daniel Veillarda37aab82003-06-09 09:10:36 +0000[diff] [blame]547 <li>Failing to provide information as requested or double checking first
Daniel Veillard98d071d2003-01-10 09:22:44 +0000[diff] [blame]548 for prior feedback also carries the implicit message "the time of the
549 library maintainers is less valuable than my time" and might not be
550 welcome.</li>
551</ul>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]552
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]553<p>Of course, bugs reported with a suggested patch for fixing them will
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]554probably be processed faster than those without.</p>
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]555
556<p>If you're looking for help, a quick look at <a
Daniel Veillardf7ed3362001-08-17 12:01:21 +0000[diff] [blame]557href="http://mail.gnome.org/archives/xml/">the list archive</a> may actually
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]558provide the answer. I usually send source samples when answering libxml2
559usage questions. The <a
560href="http://xmlsoft.org/html/book1.html">auto-generated documentation</a> is
561not as polished as I would like (i need to learn more about DocBook), but
562it's a good starting point.</p>
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]563
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]564<h2><a name="help">How to help</a></h2>
565
566<p>You can help the project in various ways, the best thing to do first is to
567subscribe to the mailing-list as explained before, check the <a
Daniel Veillardf7ed3362001-08-17 12:01:21 +0000[diff] [blame]568href="http://mail.gnome.org/archives/xml/">archives </a>and the <a
Daniel Veillardccf996f2003-08-14 10:48:38 +0000[diff] [blame]569href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome bug
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]570database</a>:</p>
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]571<ol>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]572 <li>Provide patches when you find problems.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]573 <li>Provide the diffs when you port libxml2 to a new platform. They may not
Daniel Veillardab8500d2000-10-15 21:06:19 +0000[diff] [blame]574 be integrated in all cases but help pinpointing portability problems
575 and</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]576 <li>Provide documentation fixes (either as patches to the code comments or
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]577 as HTML diffs).</li>
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]578 <li>Provide new documentations pieces (translations, examples, etc
579 ...).</li>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]580 <li>Check the TODO file and try to close one of the items.</li>
581 <li>Take one of the points raised in the archive or the bug database and
Daniel Veillarde7ead2d2001-08-22 23:44:09 +0000[diff] [blame]582 provide a fix. <a href="mailto:daniel@veillard.com">Get in touch with me
583 </a>before to avoid synchronization problems and check that the suggested
584 fix will fit in nicely :-)</li>
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]585</ol>
586
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]587<h2><a name="Downloads">Downloads</a></h2>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]588
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]589<p>The latest versions of libxml2 can be found on <a
Daniel Veillard20c8cf22001-06-26 22:47:36 +0000[diff] [blame]590href="ftp://xmlsoft.org/">xmlsoft.org</a> (<a
591href="ftp://speakeasy.rpmfind.net/pub/libxml/">Seattle</a>, <a
592href="ftp://fr.rpmfind.net/pub/libxml/">France</a>) or on the <a
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]593href="ftp://ftp.gnome.org/pub/GNOME/MIRRORS.html">Gnome FTP server</a> either
Daniel Veillard6581e1b2003-02-09 22:21:43 +0000[diff] [blame]594as a <a href="ftp://ftp.gnome.org/pub/GNOME/sources/libxml2/2.5/">source
MDT 2002 John Fleck30c70542002-09-24 14:24:54 +0000[diff] [blame]595archive</a><!-- commenting this out because they seem to have disappeared or <a
Daniel Veillarda41123c2001-04-22 19:31:20 +0000[diff] [blame]596href="ftp://ftp.gnome.org/pub/GNOME/stable/redhat/i386/libxml/">RPM
Daniel Veillarde16b5742002-09-26 17:50:03 +0000[diff] [blame]597packages</a> -->
Daniel Veillard321be0c2002-10-08 21:26:42 +0000[diff] [blame]598 , Antonin Sprinzl also provide <a href="ftp://gd.tuwien.ac.at/pub/libxml/">a
Daniel Veillarde16b5742002-09-26 17:50:03 +0000[diff] [blame]599mirror in Austria</a>. (NOTE that you need both the <a
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]600href="http://rpmfind.net/linux/RPM/libxml2.html">libxml(2)</a> and <a
601href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml(2)-devel</a>
Daniel Veillardb46a5732003-04-08 13:35:48 +0000[diff] [blame]602packages installed to compile applications using libxml.)</p>
603
604<p>Binary ports:</p>
605<ul>
606 <li>Red Hat RPMs for i386 are available directly on <a
607 href="ftp://xmlsoft.org/">xmlsoft.org</a>, the source RPM will compile on
608 any architecture supported by Red Hat.</li>
Daniel Veillardf83a2c72003-04-08 13:48:40 +0000[diff] [blame]609 <li><p><a href="mailto:igor@zlatkovic.com">Igor Zlatkovic</a></p>
Daniel Veillardce192eb2003-04-16 15:58:05 +0000[diff] [blame]610 is now the maintainer of the Windows port, <a
Daniel Veillardb46a5732003-04-08 13:35:48 +0000[diff] [blame]611 href="http://www.zlatkovic.com/projects/libxml/index.html">he provides
612 binaries</a>.</li>
613 <li><a href="mailto:Gary.Pennington@sun.com">Gary Pennington</a> provides
614 <a href="http://garypennington.net/libxml2/">Solaris binaries</a>.</li>
615 <li><a href="mailto:Steve.Ball@zveno.com">Steve Ball</a> provides <a
616 href="http://www.zveno.com/open_source/libxml2xslt.html">Mac Os X
617 binaries</a>.</li>
618 <li>The HP-UX porting center provides <a
619 href="http://hpux.connect.org.uk/hppd/hpux/Gnome/">HP-UX binaries</a></li>
620</ul>
621
622<p>If you know other supported binary ports, please <a
623href="http://veillard.com/">contact me</a>.</p>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]624
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]625<p><a name="Snapshot">Snapshot:</a></p>
626<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]627 <li>Code from the W3C cvs base gnome-xml <a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]628 href="ftp://xmlsoft.org/cvs-snapshot.tar.gz">cvs-snapshot.tar.gz</a>.</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]629 <li>Docs, content of the web site, the list archive included <a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]630 href="ftp://xmlsoft.org/libxml-docs.tar.gz">libxml-docs.tar.gz</a>.</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]631</ul>
632
Daniel Veillardc6271d22001-10-27 07:50:58 +0000[diff] [blame]633<p><a name="Contribs">Contributions:</a></p>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]634
635<p>I do accept external contributions, especially if compiling on another
Daniel Veillardc6271d22001-10-27 07:50:58 +0000[diff] [blame]636platform, get in touch with me to upload the package, wrappers for various
Daniel Veillard51095312001-10-28 18:51:57 +0000[diff] [blame]637languages have been provided, and can be found in the <a
638href="contribs.html">contrib section</a></p>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]639
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]640<p>Libxml2 is also available from CVS:</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]641<ul>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]642 <li><p>The <a
643 href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gnome-xml">Gnome
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]644 CVS base</a>. Check the <a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]645 href="http://developer.gnome.org/tools/cvs.html">Gnome CVS Tools</a>
646 page; the CVS module is <b>gnome-xml</b>.</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]647 </li>
Daniel Veillard82687162001-01-22 15:32:01 +0000[diff] [blame]648 <li>The <strong>libxslt</strong> module is also present there</li>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]649</ul>
650
651<h2><a name="News">News</a></h2>
652
Daniel Veillard944b5ff1999-12-15 19:08:24 +0000[diff] [blame]653<h3>CVS only : check the <a
654href="http://cvs.gnome.org/lxr/source/gnome-xml/ChangeLog">Changelog</a> file
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame]655for a really accurate description</h3>
Daniel Veillardab8500d2000-10-15 21:06:19 +0000[diff] [blame]656
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000[diff] [blame]657<p>Items not finished and worked on, get in touch with the list if you want
658to test those</p>
Daniel Veillardab8500d2000-10-15 21:06:19 +0000[diff] [blame]659<ul>
Daniel Veillard72fef162003-02-05 14:31:19 +0000[diff] [blame]660 <li>More testing on RelaxNG</li>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +0000[diff] [blame]661 <li>Finishing up <a href="http://www.w3.org/TR/xmlschema-1/">XML
Daniel Veillard72fef162003-02-05 14:31:19 +0000[diff] [blame]662 Schemas</a></li>
663</ul>
664
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000[diff] [blame^]665<h3>2.6.3: Dec 10 2003</h3>
666<ul>
667 <li>documentation updates and cleanup (DV, William Brack, John Fleck)</li>
668 <li>added a repository of examples, examples from Aleksey Sanin, Dodji
669 Seketeli, Alfred Mickautsch </li>
670 <li>Windows updates: Mark Vakoc, Igor Zlatkovic, Eric Zurcher, Mingw
671 (Kenneth Haley)</li>
672 <li>Unicode range checking (William Brack)</li>
673 <li>code cleanup (William Brack)</li>
674 <li>Python bindings: doc (John Fleck), bug fixes</li>
675 <li>UTF-16 cleanup and BOM issues (William Brack)</li>
676 <li>bug fixes: ID and xmlReader validation, XPath (William Brack),
677 xmlWriter (Alfred Mickautsch), hash.h inclusion problem, HTML parser
678 (James Bursa), attribute defaulting and validation, some serialization
679 cleanups, XML_GET_LINE macro, memory debug when using threads (William
680 Brack), serialization of attributes and entities content, xmlWriter
681 (Daniel Schulman)</li>
682 <li>XInclude bugfix, new APIs and update to the last version including the
683 namespace change.</li>
684 <li>XML Schemas improvements: include (Robert Stepanek), import and
685 namespace handling, fixed the regression tests troubles, added examples
686 based on Eric van der Vlist book, regexp fixes </li>
687 <li>preliminary pattern support for streaming (needed for schemas
688 constraints), added xmlTextReaderPreservePattern() to collect subdocument
689 when streaming.</li>
690 <li>various fixes in the structured error handling</li>
691</ul>
692
Daniel Veillard6d373a22003-11-04 10:26:43 +0000[diff] [blame]693<h3>2.6.2: Nov 4 2003</h3>
694<ul>
695 <li>XPath context unregistration fixes</li>
696 <li>text node coalescing fixes (Mark Lilback)</li>
697 <li>API to screate a W3C Schemas from an existing document (Steve Ball)</li>
698 <li>BeOS patches (Marcin 'Shard' Konicki)</li>
699 <li>xmlStrVPrintf function added (Aleksey Sanin)</li>
700 <li>compilation fixes (Mark Vakoc)</li>
701 <li>stdin parsing fix (William Brack)</li>
702 <li>a posteriori DTD validation fixes</li>
Daniel Veillardc480c4e2003-12-10 13:24:38 +0000[diff] [blame^]703 <li>xmlReader bug fixes: Walker fixes, python bindings</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +0000[diff] [blame]704 <li>fixed xmlStopParser() to really stop the parser and errors</li>
705 <li>always generate line numbers when using the new xmlReadxxx
706 functions</li>
707 <li>added XInclude support to the xmlReader interface</li>
708 <li>implemented XML_PARSE_NONET parser option</li>
709 <li>DocBook XSLT processing bug fixed</li>
710 <li>HTML serialization for &lt;p&gt; elements (William Brack and me)</li>
711 <li>XPointer failure in XInclude are now handled as resource errors</li>
712 <li>fixed xmllint --html to use the HTML serializer on output (added
713 --xmlout to implement the previous behaviour of saving it using the XML
714 serializer)</li>
715</ul>
716
Daniel Veillarde4e3f5d2003-10-28 23:06:32 +0000[diff] [blame]717<h3>2.6.1: Oct 28 2003</h3>
718<ul>
719 <li>Mostly bugfixes after the big 2.6.0 changes</li>
720 <li>Unix compilation patches: libxml.m4 (Patrick Welche), warnings cleanup
721 (William Brack)</li>
722 <li>Windows compilation patches (Joachim Bauch, Stephane Bidoul, Igor
723 Zlatkovic)</li>
724 <li>xmlWriter bugfix (Alfred Mickautsch)</li>
725 <li>chvalid.[ch]: couple of fixes from Stephane Bidoul</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +0000[diff] [blame]726 <li>context reset: error state reset, push parser reset (Graham
727 Bennett)</li>
Daniel Veillarde4e3f5d2003-10-28 23:06:32 +0000[diff] [blame]728 <li>context reuse: generate errors if file is not readable</li>
729 <li>defaulted attributes for element coming from internal entities
730 (Stephane Bidoul)</li>
731 <li>Python: tab and spaces mix (William Brack)</li>
732 <li>Error handler could crash in DTD validation in 2.6.0</li>
733 <li>xmlReader: do not use the document or element _private field</li>
734 <li>testSAX.c: avoid a problem with some PIs (Massimo Morara)</li>
735 <li>general bug fixes: mandatory encoding in text decl, serializing
736 Document Fragment nodes, xmlSearchNs 2.6.0 problem (Kasimier Buchcik),
737 XPath errors not reported, slow HTML parsing of large documents.</li>
738</ul>
739
Daniel Veillard3e35f8e2003-10-21 00:05:38 +0000[diff] [blame]740<h3>2.6.0: Oct 20 2003</h3>
741<ul>
742 <li>Major revision release: should be API and ABI compatible but got a lot
743 of change</li>
744 <li>Increased the library modularity, far more options can be stripped out,
745 a --with-minimum configuration will weight around 160KBytes</li>
746 <li>Use per parser and per document dictionnary, allocate names and small
747 text nodes from the dictionnary</li>
748 <li>Switch to a SAX2 like parser rewrote most of the XML parser core,
749 provides namespace resolution and defaulted attributes, minimize memory
750 allocations and copies, namespace checking and specific error handling,
751 immutable buffers, make predefined entities static structures, etc...</li>
752 <li>rewrote all the error handling in the library, all errors can be
753 intercepted at a structured level, with precise information
754 available.</li>
755 <li>New simpler and more generic XML and HTML parser APIs, allowing to
756 easilly modify the parsing options and reuse parser context for multiple
757 consecutive documents.</li>
758 <li>Similar new APIs for the xmlReader, for options and reuse, provided new
759 functions to access content as const strings, use them for Python
760 bindings</li>
761 <li>a lot of other smaller API improvements: xmlStrPrintf (Aleksey Sanin),
762 Walker i.e. reader on a document tree based on Alfred Mickautsch code,
763 make room in nodes for line numbers, reference counting and future PSVI
764 extensions, generation of character ranges to be checked with faster
765 algorithm (William), xmlParserMaxDepth (Crutcher Dunnavant), buffer
766 access</li>
767 <li>New xmlWriter API provided by Alfred Mickautsch</li>
768 <li>Schemas: base64 support by Anthony Carrico</li>
769 <li>Parser&lt;-&gt;HTTP integration fix, proper processing of the Mime-Type
770 and charset informations if available.</li>
771 <li>Relax-NG: bug fixes including the one reported by Martijn Faassen and
772 zeroOrMore, better error reporting.</li>
773 <li>Python bindings (Stéphane Bidoul), never use stdout for errors
774 output</li>
775 <li>Portability: all the headers have macros for export and calling
776 convention definitions (Igor Zlatkovic), VMS update (Craig A. Berry),
777 Windows: threads (Jesse Pelton), Borland compiler (Eric Zurcher, Igor),
778 Mingw (Igor), typos (Mark Vakoc), beta version (Stephane Bidoul),
779 warning cleanups on AIX and MIPS compilers (William Brack), BeOS (Marcin
780 'Shard' Konicki)</li>
781 <li>Documentation fixes and README (William Brack), search fix (William),
782 tutorial updates (John Fleck), namespace docs (Stefan Kost)</li>
783 <li>Bug fixes: xmlCleanupParser (Dave Beckett), threading uninitialized
784 mutexes, HTML doctype lowercase, SAX/IO (William), compression detection
785 and restore (William), attribute declaration in DTDs (William), namespace
786 on attribute in HTML output (William), input filename (Rob Richards),
787 namespace DTD validation, xmlReplaceNode (Chris Ryland), I/O callbacks
788 (Markus Keim), CDATA serialization (Shaun McCance), xmlReader (Peter
789 Derr), high codepoint charref like &amp;#x10FFFF;, buffer access in push
790 mode (Justin Fletcher), TLS threads on Windows (Jesse Pelton), XPath bug
791 (William), xmlCleanupParser (Marc Liyanage), CDATA output (William), HTTP
792 error handling.</li>
793 <li>xmllint options: --dtdvalidfpi for Tobias Reif, --sax1 for compat
794 testing, --nodict for building without tree dictionnary, --nocdata to
795 replace CDATA by text, --nsclean to remove surperfluous namespace
796 declarations</li>
797 <li>added xml2-config --libtool-libs option from Kevin P. Fleming</li>
798 <li>a lot of profiling and tuning of the code, speedup patch for
799 xmlSearchNs() by Luca Padovani. The xmlReader should do far less
800 allocation and it speed should get closer to SAX. Chris Anderson worked
801 on speeding and cleaning up repetitive checking code.</li>
802 <li>cleanup of "make tests"</li>
803 <li>libxml-2.0-uninstalled.pc from Malcolm Tredinnick</li>
804 <li>deactivated the broken docBook SGML parser code and plugged the XML
805 parser instead.</li>
806</ul>
807
Daniel Veillardeec1ae92003-09-09 13:11:01 +0000[diff] [blame]808<h3>2.5.11: Sep 9 2003</h3>
809
810<p>A bugfix only release:</p>
811<ul>
812 <li>risk of crash in Relax-NG</li>
813 <li>risk of crash when using multithreaded programs</li>
814</ul>
815
Daniel Veillardcfba2fe2003-08-15 00:33:43 +0000[diff] [blame]816<h3>2.5.10: Aug 15 2003</h3>
817
818<p>A bugfixes only release</p>
819<ul>
820 <li>Windows Makefiles (William Brack)</li>
821 <li>UTF-16 support fixes (Mark Itzcovitz)</li>
822 <li>Makefile and portability (William Brack) automake, Linux alpha, Mingw
Daniel Veillardeec1ae92003-09-09 13:11:01 +0000[diff] [blame]823 on Windows (Mikhail Grushinskiy)</li>
Daniel Veillardcfba2fe2003-08-15 00:33:43 +0000[diff] [blame]824 <li>HTML parser (Oliver Stoeneberg)</li>
825 <li>XInclude performance problem reported by Kevin Ruscoe</li>
826 <li>XML parser performance problem reported by Grant Goodale</li>
827 <li>xmlSAXParseDTD() bug fix from Malcolm Tredinnick</li>
Daniel Veillardeec1ae92003-09-09 13:11:01 +0000[diff] [blame]828 <li>and a couple other cleanup</li>
Daniel Veillardcfba2fe2003-08-15 00:33:43 +0000[diff] [blame]829</ul>
830
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000[diff] [blame]831<h3>2.5.9: Aug 9 2003</h3>
832<ul>
833 <li>bugfixes: IPv6 portability, xmlHasNsProp (Markus Keim), Windows build
834 (Wiliam Brake, Jesse Pelton, Igor), Schemas (Peter Sobisch), threading
835 (Rob Richards), hexBinary type (), UTF-16 BOM (Dodji Seketeli),
836 xmlReader, Relax-NG schemas compilation, namespace handling, EXSLT (Sean
837 Griffin), HTML parsing problem (William Brack), DTD validation for mixed
838 content + namespaces, HTML serialization, library initialization,
839 progressive HTML parser</li>
840 <li>better interfaces for Relax-NG error handling (Joachim Bauch, )</li>
841 <li>adding xmlXIncludeProcessTree() for XInclud'ing in a subtree</li>
842 <li>doc fixes and improvements (John Fleck)</li>
843 <li>configure flag for -with-fexceptions when embedding in C++</li>
844 <li>couple of new UTF-8 helper functions (William Brack)</li>
845 <li>general encoding cleanup + ISO-8859-x without iconv (Peter Jacobi)</li>
846 <li>xmlTextReader cleanup + enum for node types (Bjorn Reese)</li>
847 <li>general compilation/warning cleanup Solaris/HP-UX/... (William
848 Brack)</li>
849</ul>
850
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]851<h3>2.5.8: Jul 6 2003</h3>
852<ul>
853 <li>bugfixes: XPath, XInclude, file/URI mapping, UTF-16 save (Mark
854 Itzcovitz), UTF-8 checking, URI saving, error printing (William Brack),
855 PI related memleak, compilation without schemas or without xpath (Joerg
856 Schmitz-Linneweber/Garry Pennington), xmlUnlinkNode problem with DTDs,
857 rpm problem on , i86_64, removed a few compilation problems from 2.5.7,
858 xmlIOParseDTD, and xmlSAXParseDTD (Malcolm Tredinnick)</li>
859 <li>portability: DJGPP (MsDos) , OpenVMS (Craig A. Berry)</li>
860 <li>William Brack fixed multithreading lock problems</li>
861 <li>IPv6 patch for FTP and HTTP accesses (Archana Shah/Wipro)</li>
862 <li>Windows fixes (Igor Zlatkovic, Eric Zurcher), threading (Stéphane
863 Bidoul)</li>
864 <li>A few W3C Schemas Structure improvements</li>
865 <li>W3C Schemas Datatype improvements (Charlie Bozeman)</li>
866 <li>Python bindings for thread globals (Stéphane Bidoul), and method/class
Daniel Veillard83ee40d2003-08-09 22:24:09 +0000[diff] [blame]867 generator</li>
868 <li>added --nonet option to xmllint</li>
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]869 <li>documentation improvements (John Fleck)</li>
870</ul>
871
Daniel Veillard92fc02c2003-04-24 23:12:35 +0000[diff] [blame]872<h3>2.5.7: Apr 25 2003</h3>
873<ul>
874 <li>Relax-NG: Compiling to regexp and streaming validation on top of the
875 xmlReader interface, added to xmllint --stream</li>
876 <li>xmlReader: Expand(), Next() and DOM access glue, bug fixes</li>
877 <li>Support for large files: RGN validated a 4.5GB instance</li>
878 <li>Thread support is now configured in by default</li>
879 <li>Fixes: update of the Trio code (Bjorn), WXS Date and Duration fixes
880 (Charles Bozeman), DTD and namespaces (Brent Hendricks), HTML push parser
881 and zero bytes handling, some missing Windows file path conversions,
882 behaviour of the parser and validator in the presence of "out of memory"
Daniel Veillard93d95252003-04-29 20:25:40 +0000[diff] [blame]883 error conditions</li>
Daniel Veillard92fc02c2003-04-24 23:12:35 +0000[diff] [blame]884 <li>extended the API to be able to plug a garbage collecting memory
885 allocator, added xmlMallocAtomic() and modified the allocations
886 accordingly.</li>
887 <li>Performances: removed excessive malloc() calls, speedup of the push and
888 xmlReader interfaces, removed excessive thread locking</li>
889 <li>Documentation: man page (John Fleck), xmlReader documentation</li>
890 <li>Python: adding binding for xmlCatalogAddLocal (Brent M Hendricks)</li>
891</ul>
892
Daniel Veillardc2d4a932003-04-01 11:13:05 +0000[diff] [blame]893<h3>2.5.6: Apr 1 2003</h3>
894<ul>
895 <li>Fixed W3C XML Schemas datatype, should be compliant now except for
896 binHex and base64 which are not supported yet.</li>
897 <li>bug fixes: non-ASCII IDs, HTML output, XInclude on large docs and
898 XInclude entities handling, encoding detection on external subsets, XML
899 Schemas bugs and memory leaks, HTML parser (James Bursa)</li>
900 <li>portability: python/trio (Albert Chin), Sun compiler warnings</li>
901 <li>documentation: added --relaxng option to xmllint man page (John)</li>
902 <li>improved error reporting: xml:space, start/end tag mismatches, Relax NG
903 errors</li>
904</ul>
905
906<h3>2.5.5: Mar 24 2003</h3>
Daniel Veillardd8da01c2003-03-24 15:58:23 +0000[diff] [blame]907<ul>
908 <li>Lot of fixes on the Relax NG implementation. More testing including
909 DocBook and TEI examples.</li>
910 <li>Increased the support for W3C XML Schemas datatype</li>
911 <li>Several bug fixes in the URI handling layer</li>
912 <li>Bug fixes: HTML parser, xmlReader, DTD validation, XPath, encoding
913 conversion, line counting in the parser.</li>
914 <li>Added support for $XMLLINT_INDENT environment variable, FTP delete</li>
915 <li>Fixed the RPM spec file name</li>
916</ul>
917
Daniel Veillard17bed982003-02-24 20:11:43 +0000[diff] [blame]918<h3>2.5.4: Feb 20 2003</h3>
919<ul>
920 <li>Conformance testing and lot of fixes on Relax NG and XInclude
921 implementation</li>
922 <li>Implementation of XPointer element() scheme</li>
923 <li>Bug fixes: XML parser, XInclude entities merge, validity checking on
924 namespaces,
925 <p>2 serialization bugs, node info generation problems, a DTD regexp
926 generation problem.</p>
927 </li>
928 <li>Portability: windows updates and path canonicalization (Igor)</li>
929 <li>A few typo fixes (Kjartan Maraas)</li>
930 <li>Python bindings generator fixes (Stephane Bidoul)</li>
931</ul>
932
Daniel Veillard1d788d22003-02-10 16:21:58 +0000[diff] [blame]933<h3>2.5.3: Feb 10 2003</h3>
934<ul>
935 <li>RelaxNG and XML Schemas datatypes improvements, and added a first
936 version of RelaxNG Python bindings</li>
937 <li>Fixes: XLink (Sean Chittenden), XInclude (Sean Chittenden), API fix for
938 serializing namespace nodes, encoding conversion bug, XHTML1
939 serialization</li>
940 <li>Portability fixes: Windows (Igor), AMD 64bits RPM spec file</li>
941</ul>
942
Daniel Veillard72fef162003-02-05 14:31:19 +0000[diff] [blame]943<h3>2.5.2: Feb 5 2003</h3>
944<ul>
945 <li>First implementation of RelaxNG, added --relaxng flag to xmllint</li>
946 <li>Schemas support now compiled in by default.</li>
947 <li>Bug fixes: DTD validation, namespace checking, XInclude and entities,
948 delegateURI in XML Catalogs, HTML parser, XML reader (Stéphane Bidoul),
949 XPath parser and evaluation, UTF8ToUTF8 serialization, XML reader memory
950 consumption, HTML parser, HTML serialization in the presence of
951 namespaces</li>
952 <li>added an HTML API to check elements and attributes.</li>
953 <li>Documentation improvement, PDF for the tutorial (John Fleck), doc
954 patches (Stefan Kost)</li>
955 <li>Portability fixes: NetBSD (Julio Merino), Windows (Igor Zlatkovic)</li>
956 <li>Added python bindings for XPointer, contextual error reporting
957 (Stéphane Bidoul)</li>
958 <li>URI/file escaping problems (Stefano Zacchiroli)</li>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +0000[diff] [blame]959</ul>
960
Daniel Veillarde2830f12003-01-08 17:47:49 +0000[diff] [blame]961<h3>2.5.1: Jan 8 2003</h3>
962<ul>
963 <li>Fixes a memory leak and configuration/compilation problems in 2.5.0</li>
964 <li>documentation updates (John)</li>
965 <li>a couple of XmlTextReader fixes</li>
966</ul>
967
Daniel Veillard7b4b2f92003-01-06 13:11:20 +0000[diff] [blame]968<h3>2.5.0: Jan 6 2003</h3>
969<ul>
970 <li>New <a href="xmlreader.html">XmltextReader interface</a> based on C#
971 API (with help of Stéphane Bidoul)</li>
972 <li>Windows: more exports, including the new API (Igor)</li>
973 <li>XInclude fallback fix</li>
974 <li>Python: bindings for the new API, packaging (Stéphane Bidoul),
975 drv_libxml2.py Python xml.sax driver (Stéphane Bidoul), fixes, speedup
976 and iterators for Python-2.2 (Hannu Krosing)</li>
977 <li>Tutorial fixes (john Fleck and Niraj Tolia) xmllint man update
978 (John)</li>
979 <li>Fix an XML parser bug raised by Vyacheslav Pindyura</li>
980 <li>Fix for VMS serialization (Nigel Hall) and config (Craig A. Berry)</li>
981 <li>Entities handling fixes</li>
982 <li>new API to optionally track node creation and deletion (Lukas
983 Schroeder)</li>
984 <li>Added documentation for the XmltextReader interface and some <a
985 href="guidelines.html">XML guidelines</a></li>
986</ul>
987
Daniel Veillardc1eed322002-12-12 11:01:32 +0000[diff] [blame]988<h3>2.4.30: Dec 12 2002</h3>
989<ul>
990 <li>2.4.29 broke the python bindings, rereleasing</li>
991 <li>Improvement/fixes of the XML API generator, and couple of minor code
992 fixes.</li>
993</ul>
994
Daniel Veillard9b4bb4d2002-12-11 19:28:47 +0000[diff] [blame]995<h3>2.4.29: Dec 11 2002</h3>
996<ul>
997 <li>Windows fixes (Igor): Windows CE port, pthread linking, python bindings
998 (Stéphane Bidoul), Mingw (Magnus Henoch), and export list updates</li>
999 <li>Fix for prev in python bindings (ERDI Gergo)</li>
1000 <li>Fix for entities handling (Marcus Clarke)</li>
1001 <li>Refactored the XML and HTML dumps to a single code path, fixed XHTML1
1002 dump</li>
1003 <li>Fix for URI parsing when handling URNs with fragment identifiers</li>
1004 <li>Fix for HTTP URL escaping problem</li>
1005 <li>added an TextXmlReader (C#) like API (work in progress)</li>
1006 <li>Rewrote the API in XML generation script, includes a C parser and saves
1007 more informations needed for C# bindings</li>
1008</ul>
1009
Daniel Veillardf9c4cad2002-11-22 15:57:07 +0000[diff] [blame]1010<h3>2.4.28: Nov 22 2002</h3>
1011<ul>
1012 <li>a couple of python binding fixes</li>
1013 <li>2 bug fixes in the XML push parser</li>
1014 <li>potential memory leak removed (Martin Stoilov)</li>
1015 <li>fix to the configure script for Unix (Dimitri Papadopoulos)</li>
1016 <li>added encoding support for XInclude parse="text"</li>
1017 <li>autodetection of XHTML1 and specific serialization rules added</li>
Daniel Veillard9b4bb4d2002-12-11 19:28:47 +0000[diff] [blame]1018 <li>nasty threading bug fixed (William Brack)</li>
Daniel Veillardf9c4cad2002-11-22 15:57:07 +0000[diff] [blame]1019</ul>
1020
Daniel Veillarddad3f682002-11-17 16:47:27 +0000[diff] [blame]1021<h3>2.4.27: Nov 17 2002</h3>
1022<ul>
1023 <li>fixes for the Python bindings</li>
1024 <li>a number of bug fixes: SGML catalogs, xmlParseBalancedChunkMemory(),
1025 HTML parser, Schemas (Charles Bozeman), document fragment support
1026 (Christian Glahn), xmlReconciliateNs (Brian Stafford), XPointer,
1027 xmlFreeNode(), xmlSAXParseMemory (Peter Jones), xmlGetNodePath (Petr
1028 Pajas), entities processing</li>
1029 <li>added grep to xmllint --shell</li>
1030 <li>VMS update patch from Craig A. Berry</li>
1031 <li>cleanup of the Windows build with support for more compilers (Igor),
1032 better thread support on Windows</li>
1033 <li>cleanup of Unix Makefiles and spec file</li>
1034 <li>Improvements to the documentation (John Fleck)</li>
1035</ul>
1036
Daniel Veillard48267432002-10-18 11:21:38 +0000[diff] [blame]1037<h3>2.4.26: Oct 18 2002</h3>
1038<ul>
1039 <li>Patches for Windows CE port, improvements on Windows paths handling</li>
1040 <li>Fixes to the validation code (DTD and Schemas), xmlNodeGetPath() ,
1041 HTML serialization, Namespace compliance, and a number of small
1042 problems</li>
1043</ul>
1044
Daniel Veillarde16b5742002-09-26 17:50:03 +0000[diff] [blame]1045<h3>2.4.25: Sep 26 2002</h3>
1046<ul>
1047 <li>A number of bug fixes: XPath, validation, Python bindings, DOM and
1048 tree, xmlI/O, Html</li>
1049 <li>Serious rewrite of XInclude</li>
1050 <li>Made XML Schemas regexp part of the default build and APIs, small fix
1051 and improvement of the regexp core</li>
1052 <li>Changed the validation code to reuse XML Schemas regexp APIs</li>
1053 <li>Better handling of Windows file paths, improvement of Makefiles (Igor,
1054 Daniel Gehriger, Mark Vakoc)</li>
1055 <li>Improved the python I/O bindings, the tests, added resolver and regexp
Daniel Veillard321be0c2002-10-08 21:26:42 +0000[diff] [blame]1056 APIs</li>
Daniel Veillarde16b5742002-09-26 17:50:03 +0000[diff] [blame]1057 <li>New logos from Marc Liyanage</li>
1058 <li>Tutorial improvements: John Fleck, Christopher Harris</li>
1059 <li>Makefile: Fixes for AMD x86_64 (Mandrake), DESTDIR (Christophe
1060 Merlet)</li>
1061 <li>removal of all stderr/perror use for error reporting</li>
1062 <li>Better error reporting: XPath and DTD validation</li>
1063 <li>update of the trio portability layer (Bjorn Reese)</li>
1064</ul>
1065
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]1066<p><strong>2.4.24: Aug 22 2002</strong></p>
1067<ul>
1068 <li>XPath fixes (William), xf:escape-uri() (Wesley Terpstra)</li>
1069 <li>Python binding fixes: makefiles (William), generator, rpm build, x86-64
1070 (fcrozat)</li>
1071 <li>HTML &lt;style&gt; and boolean attributes serializer fixes</li>
1072 <li>C14N improvements by Aleksey</li>
Daniel Veillarde1662542002-08-28 11:50:59 +0000[diff] [blame]1073 <li>doc cleanups: Rick Jones</li>
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]1074 <li>Windows compiler makefile updates: Igor and Elizabeth Barham</li>
1075 <li>XInclude: implementation of fallback and xml:base fixup added</li>
1076</ul>
1077
Daniel Veillard782afda2002-07-08 15:12:49 +0000[diff] [blame]1078<h3>2.4.23: July 6 2002</h3>
1079<ul>
1080 <li>performances patches: Peter Jacobi</li>
1081 <li>c14n fixes, testsuite and performances: Aleksey Sanin</li>
1082 <li>added xmlDocFormatDump: Chema Celorio</li>
1083 <li>new tutorial: John Fleck</li>
1084 <li>new hash functions and performances: Sander Vesik, portability fix from
1085 Peter Jacobi</li>
1086 <li>a number of bug fixes: XPath (William Brack, Richard Jinks), XML and
1087 HTML parsers, ID lookup function</li>
1088 <li>removal of all remaining sprintf: Aleksey Sanin</li>
1089</ul>
1090
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]1091<h3>2.4.22: May 27 2002</h3>
1092<ul>
1093 <li>a number of bug fixes: configure scripts, base handling, parser, memory
1094 usage, HTML parser, XPath, documentation (Christian Cornelssen),
Daniel Veillard21473672002-06-17 07:29:22 +0000[diff] [blame]1095 indentation, URI parsing</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]1096 <li>Optimizations for XMLSec, fixing and making public some of the network
1097 protocol handlers (Aleksey)</li>
1098 <li>performance patch from Gary Pennington</li>
1099 <li>Charles Bozeman provided date and time support for XML Schemas
1100 datatypes</li>
1101</ul>
1102
Daniel Veillardcf27f7c2002-04-30 07:12:39 +0000[diff] [blame]1103<h3>2.4.21: Apr 29 2002</h3>
1104
1105<p>This release is both a bug fix release and also contains the early XML
1106Schemas <a href="http://www.w3.org/TR/xmlschema-1/">structures</a> and <a
1107href="http://www.w3.org/TR/xmlschema-2/">datatypes</a> code, beware, all
1108interfaces are likely to change, there is huge holes, it is clearly a work in
1109progress and don't even think of putting this code in a production system,
Daniel Veillarde6d8e202002-05-02 06:11:10 +0000[diff] [blame]1110it's actually not compiled in by default. The real fixes are:</p>
Daniel Veillardcf27f7c2002-04-30 07:12:39 +0000[diff] [blame]1111<ul>
1112 <li>a couple of bugs or limitations introduced in 2.4.20</li>
1113 <li>patches for Borland C++ and MSC by Igor</li>
1114 <li>some fixes on XPath strings and conformance patches by Richard
1115 Jinks</li>
1116 <li>patch from Aleksey for the ExcC14N specification</li>
1117 <li>OSF/1 bug fix by Bjorn</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1118</ul>
1119
Daniel Veillarda7084cd2002-04-15 17:12:47 +0000[diff] [blame]1120<h3>2.4.20: Apr 15 2002</h3>
1121<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1122 <li>bug fixes: file descriptor leak, XPath, HTML output, DTD validation</li>
Daniel Veillarda7084cd2002-04-15 17:12:47 +0000[diff] [blame]1123 <li>XPath conformance testing by Richard Jinks</li>
1124 <li>Portability fixes: Solaris, MPE/iX, Windows, OSF/1, python bindings,
1125 libxml.m4</li>
1126</ul>
1127
Daniel Veillard19274092002-03-25 16:48:03 +0000[diff] [blame]1128<h3>2.4.19: Mar 25 2002</h3>
1129<ul>
1130 <li>bug fixes: half a dozen XPath bugs, Validation, ISO-Latin to UTF8
1131 encoder</li>
1132 <li>portability fixes in the HTTP code</li>
Daniel Veillardb2fb8ed2002-04-01 09:33:12 +0000[diff] [blame]1133 <li>memory allocation checks using valgrind, and profiling tests</li>
Daniel Veillard19274092002-03-25 16:48:03 +0000[diff] [blame]1134 <li>revamp of the Windows build and Makefiles</li>
1135</ul>
1136
Daniel Veillard34ce8be2002-03-18 19:37:11 +0000[diff] [blame]1137<h3>2.4.18: Mar 18 2002</h3>
1138<ul>
1139 <li>bug fixes: tree, SAX, canonicalization, validation, portability,
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1140 XPath</li>
Daniel Veillard34ce8be2002-03-18 19:37:11 +0000[diff] [blame]1141 <li>removed the --with-buffer option it was becoming unmaintainable</li>
1142 <li>serious cleanup of the Python makefiles</li>
1143 <li>speedup patch to XPath very effective for DocBook stylesheets</li>
1144 <li>Fixes for Windows build, cleanup of the documentation</li>
1145</ul>
1146
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1147<h3>2.4.17: Mar 8 2002</h3>
1148<ul>
1149 <li>a lot of bug fixes, including "namespace nodes have no parents in
1150 XPath"</li>
1151 <li>fixed/improved the Python wrappers, added more examples and more
1152 regression tests, XPath extension functions can now return node-sets</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1153 <li>added the XML Canonicalization support from Aleksey Sanin</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1154</ul>
1155
Daniel Veillard5f4b5992002-02-20 10:22:49 +0000[diff] [blame]1156<h3>2.4.16: Feb 20 2002</h3>
1157<ul>
1158 <li>a lot of bug fixes, most of them were triggered by the XML Testsuite
1159 from OASIS and W3C. Compliance has been significantly improved.</li>
1160 <li>a couple of portability fixes too.</li>
1161</ul>
1162
Daniel Veillard397ff112002-02-11 18:27:20 +0000[diff] [blame]1163<h3>2.4.15: Feb 11 2002</h3>
1164<ul>
1165 <li>Fixed the Makefiles, especially the python module ones</li>
1166 <li>A few bug fixes and cleanup</li>
1167 <li>Includes cleanup</li>
1168</ul>
1169
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +0000[diff] [blame]1170<h3>2.4.14: Feb 8 2002</h3>
1171<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1172 <li>Change of License to the <a
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +0000[diff] [blame]1173 href="http://www.opensource.org/licenses/mit-license.html">MIT
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1174 License</a> basically for integration in XFree86 codebase, and removing
1175 confusion around the previous dual-licensing</li>
Daniel Veillardb6c1e2f2002-02-08 14:52:52 +0000[diff] [blame]1176 <li>added Python bindings, beta software but should already be quite
1177 complete</li>
1178 <li>a large number of fixes and cleanups, especially for all tree
1179 manipulations</li>
1180 <li>cleanup of the headers, generation of a reference API definition in
1181 XML</li>
1182</ul>
1183
1184<h3>2.4.13: Jan 14 2002</h3>
Daniel Veillard744683d2002-01-14 17:30:20 +0000[diff] [blame]1185<ul>
1186 <li>update of the documentation: John Fleck and Charlie Bozeman</li>
1187 <li>cleanup of timing code from Justin Fletcher</li>
1188 <li>fixes for Windows and initial thread support on Win32: Igor and Serguei
1189 Narojnyi</li>
1190 <li>Cygwin patch from Robert Collins</li>
1191 <li>added xmlSetEntityReferenceFunc() for Keith Isdale work on xsldbg</li>
1192</ul>
1193
Daniel Veillardef90ba72001-12-07 14:24:22 +0000[diff] [blame]1194<h3>2.4.12: Dec 7 2001</h3>
1195<ul>
1196 <li>a few bug fixes: thread (Gary Pennington), xmllint (Geert Kloosterman),
1197 XML parser (Robin Berjon), XPointer (Danny Jamshy), I/O cleanups
1198 (robert)</li>
1199 <li>Eric Lavigne contributed project files for MacOS</li>
1200 <li>some makefiles cleanups</li>
1201</ul>
1202
Daniel Veillarda4871052001-11-26 13:19:48 +0000[diff] [blame]1203<h3>2.4.11: Nov 26 2001</h3>
1204<ul>
1205 <li>fixed a couple of errors in the includes, fixed a few bugs, some code
1206 cleanups</li>
1207 <li>xmllint man pages improvement by Heiko Rupp</li>
1208 <li>updated VMS build instructions from John A Fotheringham</li>
1209 <li>Windows Makefiles updates from Igor</li>
1210</ul>
1211
Daniel Veillard43d3f612001-11-10 11:57:23 +0000[diff] [blame]1212<h3>2.4.10: Nov 10 2001</h3>
1213<ul>
1214 <li>URI escaping fix (Joel Young)</li>
1215 <li>added xmlGetNodePath() (for paths or XPointers generation)</li>
1216 <li>Fixes namespace handling problems when using DTD and validation</li>
1217 <li>improvements on xmllint: Morus Walter patches for --format and
1218 --encode, Stefan Kost and Heiko Rupp improvements on the --shell</li>
1219 <li>fixes for xmlcatalog linking pointed by Weiqi Gao</li>
1220 <li>fixes to the HTML parser</li>
1221</ul>
1222
1223<h3>2.4.9: Nov 6 2001</h3>
1224<ul>
1225 <li>fixes more catalog bugs</li>
1226 <li>avoid a compilation problem, improve xmlGetLineNo()</li>
1227</ul>
1228
Daniel Veillarded421aa2001-11-04 21:22:45 +0000[diff] [blame]1229<h3>2.4.8: Nov 4 2001</h3>
1230<ul>
1231 <li>fixed SGML catalogs broken in previous release, updated xmlcatalog
1232 tool</li>
1233 <li>fixed a compile errors and some includes troubles.</li>
1234</ul>
1235
Daniel Veillard52dcab32001-10-30 12:51:17 +0000[diff] [blame]1236<h3>2.4.7: Oct 30 2001</h3>
1237<ul>
1238 <li>exported some debugging interfaces</li>
1239 <li>serious rewrite of the catalog code</li>
1240 <li>integrated Gary Pennington thread safety patch, added configure option
1241 and regression tests</li>
1242 <li>removed an HTML parser bug</li>
1243 <li>fixed a couple of potentially serious validation bugs</li>
1244 <li>integrated the SGML DocBook support in xmllint</li>
1245 <li>changed the nanoftp anonymous login passwd</li>
1246 <li>some I/O cleanup and a couple of interfaces for Perl wrapper</li>
1247 <li>general bug fixes</li>
1248 <li>updated xmllint man page by John Fleck</li>
1249 <li>some VMS and Windows updates</li>
1250</ul>
1251
Daniel Veillard60087f32001-10-10 09:45:09 +0000[diff] [blame]1252<h3>2.4.6: Oct 10 2001</h3>
1253<ul>
Daniel Veillard52dcab32001-10-30 12:51:17 +0000[diff] [blame]1254 <li>added an updated man pages by John Fleck</li>
Daniel Veillard60087f32001-10-10 09:45:09 +0000[diff] [blame]1255 <li>portability and configure fixes</li>
1256 <li>an infinite loop on the HTML parser was removed (William)</li>
1257 <li>Windows makefile patches from Igor</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1258 <li>fixed half a dozen bugs reported for libxml or libxslt</li>
Daniel Veillard60087f32001-10-10 09:45:09 +0000[diff] [blame]1259 <li>updated xmlcatalog to be able to modify SGML super catalogs</li>
1260</ul>
1261
Daniel Veillarddadd0872001-09-15 09:21:44 +0000[diff] [blame]1262<h3>2.4.5: Sep 14 2001</h3>
1263<ul>
1264 <li>Remove a few annoying bugs in 2.4.4</li>
1265 <li>forces the HTML serializer to output decimal charrefs since some
1266 version of Netscape can't handle hexadecimal ones</li>
1267</ul>
1268
1269<h3>1.8.16: Sep 14 2001</h3>
1270<ul>
1271 <li>maintenance release of the old libxml1 branch, couple of bug and
1272 portability fixes</li>
1273</ul>
1274
Daniel Veillard04382ae2001-09-12 18:51:30 +0000[diff] [blame]1275<h3>2.4.4: Sep 12 2001</h3>
1276<ul>
1277 <li>added --convert to xmlcatalog, bug fixes and cleanups of XML
1278 Catalog</li>
1279 <li>a few bug fixes and some portability changes</li>
1280 <li>some documentation cleanups</li>
1281</ul>
1282
Daniel Veillard39936902001-08-24 00:49:01 +0000[diff] [blame]1283<h3>2.4.3: Aug 23 2001</h3>
1284<ul>
1285 <li>XML Catalog support see the doc</li>
1286 <li>New NaN/Infinity floating point code</li>
1287 <li>A few bug fixes</li>
1288</ul>
1289
1290<h3>2.4.2: Aug 15 2001</h3>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1291<ul>
1292 <li>adds xmlLineNumbersDefault() to control line number generation</li>
1293 <li>lot of bug fixes</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1294 <li>the Microsoft MSC projects files should now be up to date</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1295 <li>inheritance of namespaces from DTD defaulted attributes</li>
1296 <li>fixes a serious potential security bug</li>
1297 <li>added a --format option to xmllint</li>
1298</ul>
1299
1300<h3>2.4.1: July 24 2001</h3>
1301<ul>
1302 <li>possibility to keep line numbers in the tree</li>
1303 <li>some computation NaN fixes</li>
1304 <li>extension of the XPath API</li>
1305 <li>cleanup for alpha and ia64 targets</li>
1306 <li>patch to allow saving through HTTP PUT or POST</li>
Daniel Veillard09ab7e12001-07-10 15:49:44 +0000[diff] [blame]1307</ul>
1308
1309<h3>2.4.0: July 10 2001</h3>
1310<ul>
1311 <li>Fixed a few bugs in XPath, validation, and tree handling.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1312 <li>Fixed XML Base implementation, added a couple of examples to the
Daniel Veillard09ab7e12001-07-10 15:49:44 +0000[diff] [blame]1313 regression tests</li>
1314 <li>A bit of cleanup</li>
Daniel Veillardab8500d2000-10-15 21:06:19 +0000[diff] [blame]1315</ul>
1316
Daniel Veillard5b43fde2001-07-05 23:31:40 +0000[diff] [blame]1317<h3>2.3.14: July 5 2001</h3>
1318<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1319 <li>fixed some entities problems and reduce memory requirement when
1320 substituting them</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +0000[diff] [blame]1321 <li>lots of improvements in the XPath queries interpreter can be
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1322 substantially faster</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +0000[diff] [blame]1323 <li>Makefiles and configure cleanups</li>
1324 <li>Fixes to XPath variable eval, and compare on empty node set</li>
1325 <li>HTML tag closing bug fixed</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1326 <li>Fixed an URI reference computation problem when validating</li>
Daniel Veillard5b43fde2001-07-05 23:31:40 +0000[diff] [blame]1327</ul>
1328
Daniel Veillard2adbb512001-06-28 16:20:36 +0000[diff] [blame]1329<h3>2.3.13: June 28 2001</h3>
1330<ul>
1331 <li>2.3.12 configure.in was broken as well as the push mode XML parser</li>
1332 <li>a few more fixes for compilation on Windows MSC by Yon Derek</li>
1333</ul>
1334
1335<h3>1.8.14: June 28 2001</h3>
1336<ul>
1337 <li>Zbigniew Chyla gave a patch to use the old XML parser in push mode</li>
1338 <li>Small Makefile fix</li>
1339</ul>
1340
Daniel Veillard11648102001-06-26 16:08:24 +0000[diff] [blame]1341<h3>2.3.12: June 26 2001</h3>
1342<ul>
1343 <li>lots of cleanup</li>
1344 <li>a couple of validation fix</li>
1345 <li>fixed line number counting</li>
1346 <li>fixed serious problems in the XInclude processing</li>
1347 <li>added support for UTF8 BOM at beginning of entities</li>
1348 <li>fixed a strange gcc optimizer bugs in xpath handling of float, gcc-3.0
1349 miscompile uri.c (William), Thomas Leitner provided a fix for the
1350 optimizer on Tru64</li>
1351 <li>incorporated Yon Derek and Igor Zlatkovic fixes and improvements for
1352 compilation on Windows MSC</li>
1353 <li>update of libxml-doc.el (Felix Natter)</li>
1354 <li>fixed 2 bugs in URI normalization code</li>
1355</ul>
1356
Daniel Veillarde3c81b52001-06-17 14:50:34 +0000[diff] [blame]1357<h3>2.3.11: June 17 2001</h3>
1358<ul>
1359 <li>updates to trio, Makefiles and configure should fix some portability
1360 problems (alpha)</li>
1361 <li>fixed some HTML serialization problems (pre, script, and block/inline
1362 handling), added encoding aware APIs, cleanup of this code</li>
1363 <li>added xmlHasNsProp()</li>
1364 <li>implemented a specific PI for encoding support in the DocBook SGML
1365 parser</li>
1366 <li>some XPath fixes (-Infinity, / as a function parameter and namespaces
1367 node selection)</li>
1368 <li>fixed a performance problem and an error in the validation code</li>
1369 <li>fixed XInclude routine to implement the recursive behaviour</li>
1370 <li>fixed xmlFreeNode problem when libxml is included statically twice</li>
1371 <li>added --version to xmllint for bug reports</li>
1372</ul>
1373
Daniel Veillard2e4f1882001-06-01 10:11:57 +0000[diff] [blame]1374<h3>2.3.10: June 1 2001</h3>
1375<ul>
1376 <li>fixed the SGML catalog support</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1377 <li>a number of reported bugs got fixed, in XPath, iconv detection,
1378 XInclude processing</li>
Daniel Veillard2e4f1882001-06-01 10:11:57 +0000[diff] [blame]1379 <li>XPath string function should now handle unicode correctly</li>
1380</ul>
1381
Daniel Veillard4623acd2001-05-19 15:13:15 +0000[diff] [blame]1382<h3>2.3.9: May 19 2001</h3>
1383
1384<p>Lots of bugfixes, and added a basic SGML catalog support:</p>
1385<ul>
1386 <li>HTML push bugfix #54891 and another patch from Jonas Borgström</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1387 <li>some serious speed optimization again</li>
Daniel Veillard4623acd2001-05-19 15:13:15 +0000[diff] [blame]1388 <li>some documentation cleanups</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1389 <li>trying to get better linking on Solaris (-R)</li>
Daniel Veillard4623acd2001-05-19 15:13:15 +0000[diff] [blame]1390 <li>XPath API cleanup from Thomas Broyer</li>
1391 <li>Validation bug fixed #54631, added a patch from Gary Pennington, fixed
1392 xmlValidGetValidElements()</li>
1393 <li>Added an INSTALL file</li>
1394 <li>Attribute removal added to API: #54433</li>
1395 <li>added a basic support for SGML catalogs</li>
1396 <li>fixed xmlKeepBlanksDefault(0) API</li>
1397 <li>bugfix in xmlNodeGetLang()</li>
1398 <li>fixed a small configure portability problem</li>
1399 <li>fixed an inversion of SYSTEM and PUBLIC identifier in HTML document</li>
1400</ul>
1401
Daniel Veillarda265af72001-05-14 11:13:58 +0000[diff] [blame]1402<h3>1.8.13: May 14 2001</h3>
1403<ul>
1404 <li>bugfixes release of the old libxml1 branch used by Gnome</li>
1405</ul>
1406
Daniel Veillard3bbbe6f2001-05-03 11:15:37 +0000[diff] [blame]1407<h3>2.3.8: May 3 2001</h3>
1408<ul>
1409 <li>Integrated an SGML DocBook parser for the Gnome project</li>
1410 <li>Fixed a few things in the HTML parser</li>
1411 <li>Fixed some XPath bugs raised by XSLT use, tried to fix the floating
1412 point portability issue</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1413 <li>Speed improvement (8M/s for SAX, 3M/s for DOM, 1.5M/s for
1414 DOM+validation using the XML REC as input and a 700MHz celeron).</li>
Daniel Veillard3bbbe6f2001-05-03 11:15:37 +0000[diff] [blame]1415 <li>incorporated more Windows cleanup</li>
1416 <li>added xmlSaveFormatFile()</li>
1417 <li>fixed problems in copying nodes with entities references (gdome)</li>
1418 <li>removed some troubles surrounding the new validation module</li>
1419</ul>
1420
Daniel Veillarda41123c2001-04-22 19:31:20 +0000[diff] [blame]1421<h3>2.3.7: April 22 2001</h3>
1422<ul>
1423 <li>lots of small bug fixes, corrected XPointer</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1424 <li>Non deterministic content model validation support</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +0000[diff] [blame]1425 <li>added xmlDocCopyNode for gdome2</li>
1426 <li>revamped the way the HTML parser handles end of tags</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1427 <li>XPath: corrections of namespaces support and number formatting</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +0000[diff] [blame]1428 <li>Windows: Igor Zlatkovic patches for MSC compilation</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1429 <li>HTML output fixes from P C Chow and William M. Brack</li>
Daniel Veillarda41123c2001-04-22 19:31:20 +0000[diff] [blame]1430 <li>Improved validation speed sensible for DocBook</li>
1431 <li>fixed a big bug with ID declared in external parsed entities</li>
1432 <li>portability fixes, update of Trio from Bjorn Reese</li>
1433</ul>
1434
Daniel Veillardafc73112001-04-11 11:51:41 +0000[diff] [blame]1435<h3>2.3.6: April 8 2001</h3>
1436<ul>
1437 <li>Code cleanup using extreme gcc compiler warning options, found and
1438 cleared half a dozen potential problem</li>
1439 <li>the Eazel team found an XML parser bug</li>
1440 <li>cleaned up the user of some of the string formatting function. used the
1441 trio library code to provide the one needed when the platform is missing
1442 them</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1443 <li>xpath: removed a memory leak and fixed the predicate evaluation
1444 problem, extended the testsuite and cleaned up the result. XPointer seems
1445 broken ...</li>
Daniel Veillardafc73112001-04-11 11:51:41 +0000[diff] [blame]1446</ul>
1447
Daniel Veillard56a4cb82001-03-24 17:00:36 +0000[diff] [blame]1448<h3>2.3.5: Mar 23 2001</h3>
1449<ul>
1450 <li>Biggest change is separate parsing and evaluation of XPath expressions,
1451 there is some new APIs for this too</li>
1452 <li>included a number of bug fixes(XML push parser, 51876, notations,
1453 52299)</li>
1454 <li>Fixed some portability issues</li>
1455</ul>
1456
Daniel Veillarde356c282001-03-10 12:32:04 +0000[diff] [blame]1457<h3>2.3.4: Mar 10 2001</h3>
1458<ul>
1459 <li>Fixed bugs #51860 and #51861</li>
1460 <li>Added a global variable xmlDefaultBufferSize to allow default buffer
1461 size to be application tunable.</li>
1462 <li>Some cleanup in the validation code, still a bug left and this part
1463 should probably be rewritten to support ambiguous content model :-\</li>
1464 <li>Fix a couple of serious bugs introduced or raised by changes in 2.3.3
1465 parser</li>
1466 <li>Fixed another bug in xmlNodeGetContent()</li>
1467 <li>Bjorn fixed XPath node collection and Number formatting</li>
1468 <li>Fixed a loop reported in the HTML parsing</li>
1469 <li>blank space are reported even if the Dtd content model proves that they
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1470 are formatting spaces, this is for XML conformance</li>
Daniel Veillarde356c282001-03-10 12:32:04 +0000[diff] [blame]1471</ul>
1472
Daniel Veillardb402c072001-03-01 17:28:58 +0000[diff] [blame]1473<h3>2.3.3: Mar 1 2001</h3>
1474<ul>
1475 <li>small change in XPath for XSLT</li>
1476 <li>documentation cleanups</li>
1477 <li>fix in validation by Gary Pennington</li>
1478 <li>serious parsing performances improvements</li>
1479</ul>
1480
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]1481<h3>2.3.2: Feb 24 2001</h3>
Daniel Veillard71681102001-02-24 17:48:53 +0000[diff] [blame]1482<ul>
1483 <li>chasing XPath bugs, found a bunch, completed some TODO</li>
1484 <li>fixed a Dtd parsing bug</li>
1485 <li>fixed a bug in xmlNodeGetContent</li>
1486 <li>ID/IDREF support partly rewritten by Gary Pennington</li>
1487</ul>
1488
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]1489<h3>2.3.1: Feb 15 2001</h3>
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +0000[diff] [blame]1490<ul>
1491 <li>some XPath and HTML bug fixes for XSLT</li>
1492 <li>small extension of the hash table interfaces for DOM gdome2
1493 implementation</li>
1494 <li>A few bug fixes</li>
1495</ul>
1496
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]1497<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 +0000[diff] [blame]1498<ul>
1499 <li>Lots of XPath bug fixes</li>
1500 <li>Add a mode with Dtd lookup but without validation error reporting for
1501 XSLT</li>
1502 <li>Add support for text node without escaping (XSLT)</li>
1503 <li>bug fixes for xmlCheckFilename</li>
1504 <li>validation code bug fixes from Gary Pennington</li>
1505 <li>Patch from Paul D. Smith correcting URI path normalization</li>
1506 <li>Patch to allow simultaneous install of libxml-devel and
1507 libxml2-devel</li>
1508 <li>the example Makefile is now fixed</li>
1509 <li>added HTML to the RPM packages</li>
1510 <li>tree copying bugfixes</li>
1511 <li>updates to Windows makefiles</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1512 <li>optimization patch from Bjorn Reese</li>
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +0000[diff] [blame]1513</ul>
1514
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]1515<h3>2.2.11: Jan 4 2001</h3>
Daniel Veillard503b8932001-01-05 06:36:31 +0000[diff] [blame]1516<ul>
1517 <li>bunch of bug fixes (memory I/O, xpath, ftp/http, ...)</li>
1518 <li>added htmlHandleOmittedElem()</li>
1519 <li>Applied Bjorn Reese's IPV6 first patch</li>
1520 <li>Applied Paul D. Smith patches for validation of XInclude results</li>
Daniel Veillard82687162001-01-22 15:32:01 +0000[diff] [blame]1521 <li>added XPointer xmlns() new scheme support</li>
Daniel Veillard503b8932001-01-05 06:36:31 +0000[diff] [blame]1522</ul>
1523
Daniel Veillard2ddd23d2000-11-25 10:42:19 +0000[diff] [blame]1524<h3>2.2.10: Nov 25 2000</h3>
Daniel Veillard9d343c42000-11-25 10:12:43 +0000[diff] [blame]1525<ul>
1526 <li>Fix the Windows problems of 2.2.8</li>
1527 <li>integrate OpenVMS patches</li>
1528 <li>better handling of some nasty HTML input</li>
1529 <li>Improved the XPointer implementation</li>
1530 <li>integrate a number of provided patches</li>
1531</ul>
1532
Daniel Veillard2ddd23d2000-11-25 10:42:19 +0000[diff] [blame]1533<h3>2.2.9: Nov 25 2000</h3>
1534<ul>
1535 <li>erroneous release :-(</li>
1536</ul>
1537
Daniel Veillard28929b22000-11-13 18:22:49 +0000[diff] [blame]1538<h3>2.2.8: Nov 13 2000</h3>
1539<ul>
1540 <li>First version of <a href="http://www.w3.org/TR/xinclude">XInclude</a>
1541 support</li>
1542 <li>Patch in conditional section handling</li>
1543 <li>updated MS compiler project</li>
1544 <li>fixed some XPath problems</li>
1545 <li>added an URI escaping function</li>
1546 <li>some other bug fixes</li>
1547</ul>
1548
1549<h3>2.2.7: Oct 31 2000</h3>
1550<ul>
1551 <li>added message redirection</li>
1552 <li>XPath improvements (thanks TOM !)</li>
1553 <li>xmlIOParseDTD() added</li>
1554 <li>various small fixes in the HTML, URI, HTTP and XPointer support</li>
1555 <li>some cleanup of the Makefile, autoconf and the distribution content</li>
1556</ul>
1557
Daniel Veillard29a11cc2000-10-25 13:32:39 +0000[diff] [blame]1558<h3>2.2.6: Oct 25 2000:</h3>
1559<ul>
1560 <li>Added an hash table module, migrated a number of internal structure to
1561 those</li>
1562 <li>Fixed a posteriori validation problems</li>
1563 <li>HTTP module cleanups</li>
1564 <li>HTML parser improvements (tag errors, script/style handling, attribute
1565 normalization)</li>
1566 <li>coalescing of adjacent text nodes</li>
1567 <li>couple of XPath bug fixes, exported the internal API</li>
1568</ul>
1569
Daniel Veillardab8500d2000-10-15 21:06:19 +0000[diff] [blame]1570<h3>2.2.5: Oct 15 2000:</h3>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]1571<ul>
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame]1572 <li>XPointer implementation and testsuite</li>
1573 <li>Lot of XPath fixes, added variable and functions registration, more
1574 tests</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1575 <li>Portability fixes, lots of enhancements toward an easy Windows build
1576 and release</li>
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame]1577 <li>Late validation fixes</li>
1578 <li>Integrated a lot of contributed patches</li>
1579 <li>added memory management docs</li>
Daniel Veillardab8500d2000-10-15 21:06:19 +0000[diff] [blame]1580 <li>a performance problem when using large buffer seems fixed</li>
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame]1581</ul>
1582
1583<h3>2.2.4: Oct 1 2000:</h3>
1584<ul>
1585 <li>main XPath problem fixed</li>
1586 <li>Integrated portability patches for Windows</li>
1587 <li>Serious bug fixes on the URI and HTML code</li>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]1588</ul>
1589
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]1590<h3>2.2.3: Sep 17 2000</h3>
1591<ul>
1592 <li>bug fixes</li>
1593 <li>cleanup of entity handling code</li>
1594 <li>overall review of all loops in the parsers, all sprintf usage has been
1595 checked too</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1596 <li>Far better handling of larges Dtd. Validating against DocBook XML Dtd
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]1597 works smoothly now.</li>
1598</ul>
1599
1600<h3>1.8.10: Sep 6 2000</h3>
1601<ul>
1602 <li>bug fix release for some Gnome projects</li>
1603</ul>
1604
1605<h3>2.2.2: August 12 2000</h3>
Daniel Veillard786d7c82000-08-12 23:38:57 +0000[diff] [blame]1606<ul>
1607 <li>mostly bug fixes</li>
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000[diff] [blame]1608 <li>started adding routines to access xml parser context options</li>
Daniel Veillard786d7c82000-08-12 23:38:57 +0000[diff] [blame]1609</ul>
1610
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]1611<h3>2.2.1: July 21 2000</h3>
Daniel Veillarda2679fa2000-07-22 02:38:15 +0000[diff] [blame]1612<ul>
1613 <li>a purely bug fixes release</li>
1614 <li>fixed an encoding support problem when parsing from a memory block</li>
1615 <li>fixed a DOCTYPE parsing problem</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1616 <li>removed a bug in the function allowing to override the memory
1617 allocation routines</li>
Daniel Veillarda2679fa2000-07-22 02:38:15 +0000[diff] [blame]1618</ul>
1619
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]1620<h3>2.2.0: July 14 2000</h3>
Daniel Veillard94e90602000-07-17 14:38:19 +0000[diff] [blame]1621<ul>
1622 <li>applied a lot of portability fixes</li>
1623 <li>better encoding support/cleanup and saving (content is now always
1624 encoded in UTF-8)</li>
1625 <li>the HTML parser now correctly handles encodings</li>
1626 <li>added xmlHasProp()</li>
1627 <li>fixed a serious problem with &amp;#38;</li>
1628 <li>propagated the fix to FTP client</li>
1629 <li>cleanup, bugfixes, etc ...</li>
1630 <li>Added a page about <a href="encoding.html">libxml Internationalization
1631 support</a></li>
1632</ul>
1633
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1634<h3>1.8.9: July 9 2000</h3>
1635<ul>
1636 <li>fixed the spec the RPMs should be better</li>
1637 <li>fixed a serious bug in the FTP implementation, released 1.8.9 to solve
1638 rpmfind users problem</li>
1639</ul>
1640
Daniel Veillard6388e172000-07-03 16:07:19 +0000[diff] [blame]1641<h3>2.1.1: July 1 2000</h3>
1642<ul>
1643 <li>fixes a couple of bugs in the 2.1.0 packaging</li>
1644 <li>improvements on the HTML parser</li>
1645</ul>
1646
Daniel Veillard3f6f7f62000-06-30 17:58:25 +0000[diff] [blame]1647<h3>2.1.0 and 1.8.8: June 29 2000</h3>
1648<ul>
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]1649 <li>1.8.8 is mostly a commodity package for upgrading to libxml2 according
1650 to <a href="upgrade.html">new instructions</a>. It fixes a nasty problem
Daniel Veillard3f6f7f62000-06-30 17:58:25 +0000[diff] [blame]1651 about &amp;#38; charref parsing</li>
1652 <li>2.1.0 also ease the upgrade from libxml v1 to the recent version. it
1653 also contains numerous fixes and enhancements:
1654 <ul>
1655 <li>added xmlStopParser() to stop parsing</li>
1656 <li>improved a lot parsing speed when there is large CDATA blocs</li>
1657 <li>includes XPath patches provided by Picdar Technology</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1658 <li>tried to fix as much as possible DTD validation and namespace
Daniel Veillard3f6f7f62000-06-30 17:58:25 +0000[diff] [blame]1659 related problems</li>
1660 <li>output to a given encoding has been added/tested</li>
1661 <li>lot of various fixes</li>
1662 </ul>
1663 </li>
1664</ul>
1665
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]1666<h3>2.0.0: Apr 12 2000</h3>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]1667<ul>
1668 <li>First public release of libxml2. If you are using libxml, it's a good
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1669 idea to check the 1.x to 2.x upgrade instructions. NOTE: while initially
1670 scheduled for Apr 3 the release occurred only on Apr 12 due to massive
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]1671 workload.</li>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]1672 <li>The include are now located under $prefix/include/libxml (instead of
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]1673 $prefix/include/gnome-xml), they also are referenced by
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1674 <pre>#include &lt;libxml/xxx.h&gt;</pre>
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]1675 <p>instead of</p>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]1676 <pre>#include "xxx.h"</pre>
1677 </li>
Daniel Veillard8f621982000-03-20 13:07:15 +0000[diff] [blame]1678 <li>a new URI module for parsing URIs and following strictly RFC 2396</li>
1679 <li>the memory allocation routines used by libxml can now be overloaded
1680 dynamically by using xmlMemSetup()</li>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]1681 <li>The previously CVS only tool tester has been renamed
1682 <strong>xmllint</strong> and is now installed as part of the libxml2
1683 package</li>
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]1684 <li>The I/O interface has been revamped. There is now ways to plug in
1685 specific I/O modules, either at the URI scheme detection level using
1686 xmlRegisterInputCallbacks() or by passing I/O functions when creating a
1687 parser context using xmlCreateIOParserCtxt()</li>
1688 <li>there is a C preprocessor macro LIBXML_VERSION providing the version
1689 number of the libxml module in use</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1690 <li>a number of optional features of libxml can now be excluded at
1691 configure time (FTP/HTTP/HTML/XPath/Debug)</li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]1692</ul>
1693
1694<h3>2.0.0beta: Mar 14 2000</h3>
1695<ul>
1696 <li>This is a first Beta release of libxml version 2</li>
Daniel Veillarde356c282001-03-10 12:32:04 +0000[diff] [blame]1697 <li>It's available only from<a href="ftp://xmlsoft.org/">xmlsoft.org
1698 FTP</a>, it's packaged as libxml2-2.0.0beta and available as tar and
1699 RPMs</li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]1700 <li>This version is now the head in the Gnome CVS base, the old one is
1701 available under the tag LIB_XML_1_X</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]1702 <li>This includes a very large set of changes. From a programmatic point
1703 of view applications should not have to be modified too much, check the
1704 <a href="upgrade.html">upgrade page</a></li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]1705 <li>Some interfaces may changes (especially a bit about encoding).</li>
1706 <li>the updates includes:
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]1707 <ul>
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]1708 <li>fix I18N support. ISO-Latin-x/UTF-8/UTF-16 (nearly) seems correctly
1709 handled now</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1710 <li>Better handling of entities, especially well-formedness checking
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1711 and proper PEref extensions in external subsets</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]1712 <li>DTD conditional sections</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1713 <li>Validation now correctly handle entities content</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]1714 <li><a href="http://rpmfind.net/tools/gdome/messages/0039.html">change
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1715 structures to accommodate DOM</a></li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]1716 </ul>
1717 </li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]1718 <li>Serious progress were made toward compliance, <a
1719 href="conf/result.html">here are the result of the test</a> against the
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1720 OASIS testsuite (except the Japanese tests since I don't support that
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]1721 encoding yet). This URL is rebuilt every couple of hours using the CVS
1722 head version.</li>
Daniel Veillarde41f2b72000-01-30 20:00:07 +0000[diff] [blame]1723</ul>
1724
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]1725<h3>1.8.7: Mar 6 2000</h3>
1726<ul>
1727 <li>This is a bug fix release:</li>
1728 <li>It is possible to disable the ignorable blanks heuristic used by
1729 libxml-1.x, a new function xmlKeepBlanksDefault(0) will allow this. Note
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1730 that for adherence to XML spec, this behaviour will be disabled by
1731 default in 2.x . The same function will allow to keep compatibility for
1732 old code.</li>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1733 <li>Blanks in &lt;a&gt; &lt;/a&gt; constructs are not ignored anymore,
1734 avoiding heuristic is really the Right Way :-\</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]1735 <li>The unchecked use of snprintf which was breaking libxml-1.8.6
1736 compilation on some platforms has been fixed</li>
1737 <li>nanoftp.c nanohttp.c: Fixed '#' and '?' stripping when processing
1738 URIs</li>
1739</ul>
1740
Daniel Veillarde41f2b72000-01-30 20:00:07 +0000[diff] [blame]1741<h3>1.8.6: Jan 31 2000</h3>
1742<ul>
1743 <li>added a nanoFTP transport module, debugged until the new version of <a
1744 href="http://rpmfind.net/linux/rpm2html/rpmfind.html">rpmfind</a> can use
1745 it without troubles</li>
Daniel Veillardda07c342000-01-25 18:31:22 +0000[diff] [blame]1746</ul>
1747
1748<h3>1.8.5: Jan 21 2000</h3>
1749<ul>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]1750 <li>adding APIs to parse a well balanced chunk of XML (production <a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1751 href="http://www.w3.org/TR/REC-xml#NT-content">[43] content</a> of the
1752 XML spec)</li>
Daniel Veillard461a66c2000-01-18 18:01:01 +0000[diff] [blame]1753 <li>fixed a hideous bug in xmlGetProp pointed by Rune.Djurhuus@fast.no</li>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1754 <li>Jody Goldberg &lt;jgoldberg@home.com&gt; provided another patch trying
1755 to solve the zlib checks problems</li>
Daniel Veillard461a66c2000-01-18 18:01:01 +0000[diff] [blame]1756 <li>The current state in gnome CVS base is expected to ship as 1.8.5 with
1757 gnumeric soon</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]1758</ul>
1759
1760<h3>1.8.4: Jan 13 2000</h3>
1761<ul>
1762 <li>bug fixes, reintroduced xmlNewGlobalNs(), fixed xmlNewNs()</li>
1763 <li>all exit() call should have been removed from libxml</li>
1764 <li>fixed a problem with INCLUDE_WINSOCK on WIN32 platform</li>
1765 <li>added newDocFragment()</li>
Daniel Veillardf84f71f2000-01-05 19:54:23 +0000[diff] [blame]1766</ul>
1767
1768<h3>1.8.3: Jan 5 2000</h3>
1769<ul>
1770 <li>a Push interface for the XML and HTML parsers</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]1771 <li>a shell-like interface to the document tree (try tester --shell :-)</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1772 <li>lots of bug fixes and improvement added over XMas holidays</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +0000[diff] [blame]1773 <li>fixed the DTD parsing code to work with the xhtml DTD</li>
Daniel Veillardf84f71f2000-01-05 19:54:23 +0000[diff] [blame]1774 <li>added xmlRemoveProp(), xmlRemoveID() and xmlRemoveRef()</li>
1775 <li>Fixed bugs in xmlNewNs()</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +0000[diff] [blame]1776 <li>External entity loading code has been revamped, now it uses
Daniel Veillardf84f71f2000-01-05 19:54:23 +0000[diff] [blame]1777 xmlLoadExternalEntity(), some fix on entities processing were added</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +0000[diff] [blame]1778 <li>cleaned up WIN32 includes of socket stuff</li>
Daniel Veillard5cb5ab81999-12-21 15:35:29 +0000[diff] [blame]1779</ul>
1780
1781<h3>1.8.2: Dec 21 1999</h3>
1782<ul>
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]1783 <li>I got another problem with includes and C++, I hope this issue is fixed
1784 for good this time</li>
Daniel Veillard5cb5ab81999-12-21 15:35:29 +0000[diff] [blame]1785 <li>Added a few tree modification functions: xmlReplaceNode,
1786 xmlAddPrevSibling, xmlAddNextSibling, xmlNodeSetName and
1787 xmlDocSetRootElement</li>
1788 <li>Tried to improve the HTML output with help from <a
1789 href="mailto:clahey@umich.edu">Chris Lahey</a></li>
Daniel Veillarde4e51311999-12-18 15:32:46 +0000[diff] [blame]1790</ul>
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]1791
Daniel Veillarde4e51311999-12-18 15:32:46 +0000[diff] [blame]1792<h3>1.8.1: Dec 18 1999</h3>
1793<ul>
1794 <li>various patches to avoid troubles when using libxml with C++ compilers
1795 the "namespace" keyword and C escaping in include files</li>
1796 <li>a problem in one of the core macros IS_CHAR was corrected</li>
1797 <li>fixed a bug introduced in 1.8.0 breaking default namespace processing,
1798 and more specifically the Dia application</li>
Daniel Veillard944b5ff1999-12-15 19:08:24 +0000[diff] [blame]1799 <li>fixed a posteriori validation (validation after parsing, or by using a
1800 Dtd not specified in the original document)</li>
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]1801 <li>fixed a bug in</li>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]1802</ul>
1803
1804<h3>1.8.0: Dec 12 1999</h3>
1805<ul>
1806 <li>cleanup, especially memory wise</li>
1807 <li>the parser should be more reliable, especially the HTML one, it should
1808 not crash, whatever the input !</li>
1809 <li>Integrated various patches, especially a speedup improvement for large
1810 dataset from <a href="mailto:cnygard@bellatlantic.net">Carl Nygard</a>,
1811 configure with --with-buffers to enable them.</li>
1812 <li>attribute normalization, oops should have been added long ago !</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1813 <li>attributes defaulted from DTDs should be available, xmlSetProp() now
1814 does entities escaping by default.</li>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]1815</ul>
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]1816
1817<h3>1.7.4: Oct 25 1999</h3>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]1818<ul>
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]1819 <li>Lots of HTML improvement</li>
1820 <li>Fixed some errors when saving both XML and HTML</li>
1821 <li>More examples, the regression tests should now look clean</li>
1822 <li>Fixed a bug with contiguous charref</li>
1823</ul>
1824
1825<h3>1.7.3: Sep 29 1999</h3>
1826<ul>
1827 <li>portability problems fixed</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1828 <li>snprintf was used unconditionally, leading to link problems on system
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]1829 were it's not available, fixed</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]1830</ul>
1831
1832<h3>1.7.1: Sep 24 1999</h3>
1833<ul>
1834 <li>The basic type for strings manipulated by libxml has been renamed in
1835 1.7.1 from <strong>CHAR</strong> to <strong>xmlChar</strong>. The reason
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1836 is that CHAR was conflicting with a predefined type on Windows. However
1837 on non WIN32 environment, compatibility is provided by the way of a
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]1838 <strong>#define </strong>.</li>
1839 <li>Changed another error : the use of a structure field called errno, and
1840 leading to troubles on platforms where it's a macro</li>
1841</ul>
1842
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1843<h3>1.7.0: Sep 23 1999</h3>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]1844<ul>
1845 <li>Added the ability to fetch remote DTD or parsed entities, see the <a
Daniel Veillard9cb5ff42001-01-29 08:22:21 +0000[diff] [blame]1846 href="html/libxml-nanohttp.html">nanohttp</a> module.</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]1847 <li>Added an errno to report errors by another mean than a simple printf
1848 like callback</li>
1849 <li>Finished ID/IDREF support and checking when validation</li>
1850 <li>Serious memory leaks fixed (there is now a <a
Daniel Veillard9cb5ff42001-01-29 08:22:21 +0000[diff] [blame]1851 href="html/libxml-xmlmemory.html">memory wrapper</a> module)</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]1852 <li>Improvement of <a href="http://www.w3.org/TR/xpath">XPath</a>
1853 implementation</li>
1854 <li>Added an HTML parser front-end</li>
1855</ul>
1856
1857<h2><a name="XML">XML</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1858
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]1859<p><a href="http://www.w3.org/TR/REC-xml">XML is a standard</a> for
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]1860markup-based structured documents. Here is <a name="example">an example XML
1861document</a>:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1862<pre>&lt;?xml version="1.0"?&gt;
1863&lt;EXAMPLE prop1="gnome is great" prop2="&amp;amp; linux too"&gt;
1864 &lt;head&gt;
1865 &lt;title&gt;Welcome to Gnome&lt;/title&gt;
1866 &lt;/head&gt;
1867 &lt;chapter&gt;
1868 &lt;title&gt;The Linux adventure&lt;/title&gt;
1869 &lt;p&gt;bla bla bla ...&lt;/p&gt;
1870 &lt;image href="linus.gif"/&gt;
1871 &lt;p&gt;...&lt;/p&gt;
1872 &lt;/chapter&gt;
1873&lt;/EXAMPLE&gt;</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1874
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1875<p>The first line specifies that it is an XML document and gives useful
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]1876information about its encoding. Then the rest of the document is a text
1877format whose structure is specified by tags between brackets. <strong>Each
1878tag opened has to be closed</strong>. XML is pedantic about this. However, if
1879a tag is empty (no content), a single tag can serve as both the opening and
1880closing tag if it ends with <code>/&gt;</code> rather than with
1881<code>&gt;</code>. Note that, for example, the image tag has no content (just
1882an attribute) and is closed by ending the tag with <code>/&gt;</code>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]1883
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]1884<p>XML can be applied successfully to a wide range of tasks, ranging from
1885long term structured document maintenance (where it follows the steps of
1886SGML) to simple data encoding mechanisms like configuration file formatting
1887(glade), spreadsheets (gnumeric), or even shorter lived documents such as
1888WebDAV where it is used to encode remote calls between a client and a
1889server.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1890
Daniel Veillard82687162001-01-22 15:32:01 +0000[diff] [blame]1891<h2><a name="XSLT">XSLT</a></h2>
1892
Daniel Veillard6e6a6cc2001-02-15 15:55:44 +0000[diff] [blame]1893<p>Check <a href="http://xmlsoft.org/XSLT">the separate libxslt page</a></p>
1894
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1895<p><a href="http://www.w3.org/TR/xslt">XSL Transformations</a>, is a
1896language for transforming XML documents into other XML documents (or
1897HTML/textual output).</p>
Daniel Veillard82687162001-01-22 15:32:01 +0000[diff] [blame]1898
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]1899<p>A separate library called libxslt is available implementing XSLT-1.0 for
1900libxml2. This module "libxslt" too can be found in the Gnome CVS base.</p>
Daniel Veillard82687162001-01-22 15:32:01 +0000[diff] [blame]1901
Daniel Veillard383b1472001-01-23 11:39:52 +0000[diff] [blame]1902<p>You can check the <a
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]1903href="http://cvs.gnome.org/lxr/source/libxslt/FEATURES">features</a>
1904supported and the progresses on the <a
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1905href="http://cvs.gnome.org/lxr/source/libxslt/ChangeLog"
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1906name="Changelog">Changelog</a>.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1907
1908<h2><a name="Python">Python and bindings</a></h2>
1909
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]1910<p>There are a number of language bindings and wrappers available for
1911libxml2, the list below is not exhaustive. Please contact the <a
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1912href="http://mail.gnome.org/mailman/listinfo/xml-bindings">xml-bindings@gnome.org</a>
1913(<a href="http://mail.gnome.org/archives/xml-bindings/">archives</a>) in
1914order to get updates to this list or to discuss the specific topic of libxml2
1915or libxslt wrappers or bindings:</p>
1916<ul>
Daniel Veillardc14401e2002-11-20 14:28:17 +0000[diff] [blame]1917 <li><a href="http://libxmlplusplus.sourceforge.net/">Libxml++</a> seems the
1918 most up-to-date C++ bindings for libxml2, check the <a
1919 href="http://libxmlplusplus.sourceforge.net/reference/html/hierarchy.html">documentation</a>
1920 and the <a
1921 href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/libxmlplusplus/libxml%2b%2b/examples/">examples</a>.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1922 <li>There is another <a href="http://libgdome-cpp.berlios.de/">C++ wrapper
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1923 based on the gdome2 bindings</a> maintained by Tobias Peters.</li>
Daniel Veillard9b6fd302002-05-13 12:06:47 +0000[diff] [blame]1924 <li>and a third C++ wrapper by Peter Jones &lt;pjones@pmade.org&gt;
1925 <p>Website: <a
1926 href="http://pmade.org/pjones/software/xmlwrapp/">http://pmade.org/pjones/software/xmlwrapp/</a></p>
1927 </li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1928 <li><a
1929 href="http://mail.gnome.org/archives/xml/2001-March/msg00014.html">Matt
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]1930 Sergeant</a> developed <a
1931 href="http://axkit.org/download/">XML::LibXSLT</a>, a Perl wrapper for
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1932 libxml2/libxslt as part of the <a href="http://axkit.com/">AxKit XML
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1933 application server</a>.</li>
Daniel Veillard4ac494b2003-09-18 15:08:00 +0000[diff] [blame]1934 <li>If you're interested into scripting XML processing, have a look at <a
1935 href="http://xsh.sourceforge.net/">XSH</a> an XML editing shell based on
1936 Libxml2 Perl bindings.</li>
Daniel Veillard21473672002-06-17 07:29:22 +0000[diff] [blame]1937 <li><a href="mailto:dkuhlman@cutter.rexx.com">Dave Kuhlman</a> provides an
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1938 earlier version of the libxml/libxslt <a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1939 href="http://www.rexx.com/~dkuhlman">wrappers for Python</a>.</li>
Daniel Veillard21473672002-06-17 07:29:22 +0000[diff] [blame]1940 <li>Gopal.V and Peter Minten develop <a
1941 href="http://savannah.gnu.org/projects/libxmlsharp">libxml#</a>, a set of
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1942 C# libxml2 bindings.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1943 <li>Petr Kozelka provides <a
1944 href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1945 libxml2</a> with Kylix, Delphi and other Pascal compilers.</li>
Daniel Veillardb2fb8ed2002-04-01 09:33:12 +0000[diff] [blame]1946 <li>Uwe Fechner also provides <a
1947 href="http://sourceforge.net/projects/idom2-pas/">idom2</a>, a DOM2
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1948 implementation for Kylix2/D5/D6 from Borland.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1949 <li>Wai-Sun "Squidster" Chia provides <a
1950 href="http://www.rubycolor.org/arc/redist/">bindings for Ruby</a> and
1951 libxml2 bindings are also available in Ruby through the <a
1952 href="http://libgdome-ruby.berlios.de/">libgdome-ruby</a> module
1953 maintained by Tobias Peters.</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1954 <li>Steve Ball and contributors maintains <a
1955 href="http://tclxml.sourceforge.net/">libxml2 and libxslt bindings for
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1956 Tcl</a>.</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1957 <li>There is support for libxml2 in the DOM module of PHP.</li>
Daniel Veillard41b01a82003-02-27 11:09:06 +0000[diff] [blame]1958 <li><a href="http://savannah.gnu.org/projects/classpathx/">LibxmlJ</a> is
Daniel Veillard806cada2003-03-19 21:58:59 +0000[diff] [blame]1959 an effort to create a 100% JAXP-compatible Java wrapper for libxml2 and
1960 libxslt as part of GNU ClasspathX project.</li>
Daniel Veillard6d373a22003-11-04 10:26:43 +0000[diff] [blame]1961 <li>Patrick McPhee provides Rexx bindings fof libxml2 and libxslt, look for
1962 <a href="http://www.interlog.com/~ptjm/software.html">RexxXML</a>.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1963</ul>
1964
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]1965<p>The distribution includes a set of Python bindings, which are guaranteed
1966to be maintained as part of the library in the future, though the Python
Daniel Veillard41b01a82003-02-27 11:09:06 +0000[diff] [blame]1967interface have not yet reached the completeness of the C API.</p>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +0000[diff] [blame]1968
Daniel Veillard27907c72002-12-16 16:05:58 +0000[diff] [blame]1969<p><a href="mailto:stephane.bidoul@softwareag.com">Stéphane Bidoul</a>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +0000[diff] [blame]1970maintains <a href="http://users.skynet.be/sbi/libxml-python/">a Windows port
1971of the Python bindings</a>.</p>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1972
Daniel Veillard7ef0fcb2002-12-14 10:38:55 +0000[diff] [blame]1973<p>Note to people interested in building bindings, the API is formalized as
1974<a href="libxml2-api.xml">an XML API description file</a> which allows to
1975automate a large part of the Python bindings, this includes function
Daniel Veillard7b4b2f92003-01-06 13:11:20 +0000[diff] [blame]1976descriptions, enums, structures, typedefs, etc... The Python script used to
1977build the bindings is python/generator.py in the source distribution.</p>
Daniel Veillard7ef0fcb2002-12-14 10:38:55 +0000[diff] [blame]1978
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1979<p>To install the Python bindings there are 2 options:</p>
Daniel Veillard0b79dfe2002-02-23 13:02:31 +0000[diff] [blame]1980<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1981 <li>If you use an RPM based distribution, simply install the <a
1982 href="http://rpmfind.net/linux/rpm2html/search.php?query=libxml2-python">libxml2-python
1983 RPM</a> (and if needed the <a
1984 href="http://rpmfind.net/linux/rpm2html/search.php?query=libxslt-python">libxslt-python
1985 RPM</a>).</li>
1986 <li>Otherwise use the <a href="ftp://xmlsoft.org/python/">libxml2-python
1987 module distribution</a> corresponding to your installed version of
1988 libxml2 and libxslt. Note that to install it you will need both libxml2
1989 and libxslt installed and run "python setup.py build install" in the
1990 module tree.</li>
Daniel Veillard0b79dfe2002-02-23 13:02:31 +0000[diff] [blame]1991</ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]1992
1993<p>The distribution includes a set of examples and regression tests for the
1994python bindings in the <code>python/tests</code> directory. Here are some
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]1995excerpts from those tests:</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]1996
1997<h3>tst.py:</h3>
1998
1999<p>This is a basic test of the file interface and DOM navigation:</p>
MST 2003 John Fleck2dffb762003-11-29 04:41:24 +0000[diff] [blame]2000<pre>import libxml2, sys
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2001
2002doc = libxml2.parseFile("tst.xml")
2003if doc.name != "tst.xml":
2004 print "doc.name failed"
2005 sys.exit(1)
2006root = doc.children
2007if root.name != "doc":
2008 print "root.name failed"
2009 sys.exit(1)
2010child = root.children
2011if child.name != "foo":
2012 print "child.name failed"
2013 sys.exit(1)
2014doc.freeDoc()</pre>
2015
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2016<p>The Python module is called libxml2; parseFile is the equivalent of
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2017xmlParseFile (most of the bindings are automatically generated, and the xml
2018prefix is removed and the casing convention are kept). All node seen at the
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2019binding level share the same subset of accessors:</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2020<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2021 <li><code>name</code> : returns the node name</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]2022 <li><code>type</code> : returns a string indicating the node type</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2023 <li><code>content</code> : returns the content of the node, it is based on
2024 xmlNodeGetContent() and hence is recursive.</li>
2025 <li><code>parent</code> , <code>children</code>, <code>last</code>,
2026 <code>next</code>, <code>prev</code>, <code>doc</code>,
2027 <code>properties</code>: pointing to the associated element in the tree,
2028 those may return None in case no such link exists.</li>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2029</ul>
2030
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2031<p>Also note the need to explicitly deallocate documents with freeDoc() .
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2032Reference counting for libxml2 trees would need quite a lot of work to
2033function properly, and rather than risk memory leaks if not implemented
2034correctly it sounds safer to have an explicit function to free a tree. The
2035wrapper python objects like doc, root or child are them automatically garbage
2036collected.</p>
2037
2038<h3>validate.py:</h3>
2039
2040<p>This test check the validation interfaces and redirection of error
2041messages:</p>
2042<pre>import libxml2
2043
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2044#deactivate error messages from the validation
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2045def noerr(ctx, str):
2046 pass
2047
2048libxml2.registerErrorHandler(noerr, None)
2049
2050ctxt = libxml2.createFileParserCtxt("invalid.xml")
2051ctxt.validate(1)
2052ctxt.parseDocument()
2053doc = ctxt.doc()
2054valid = ctxt.isValid()
2055doc.freeDoc()
2056if valid != 0:
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2057 print "validity check failed"</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2058
2059<p>The first thing to notice is the call to registerErrorHandler(), it
2060defines a new error handler global to the library. It is used to avoid seeing
2061the error messages when trying to validate the invalid document.</p>
2062
2063<p>The main interest of that test is the creation of a parser context with
2064createFileParserCtxt() and how the behaviour can be changed before calling
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2065parseDocument() . Similarly the informations resulting from the parsing phase
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2066are also available using context methods.</p>
2067
2068<p>Contexts like nodes are defined as class and the libxml2 wrappers maps the
2069C function interfaces in terms of objects method as much as possible. The
2070best to get a complete view of what methods are supported is to look at the
2071libxml2.py module containing all the wrappers.</p>
2072
2073<h3>push.py:</h3>
2074
2075<p>This test show how to activate the push parser interface:</p>
2076<pre>import libxml2
2077
2078ctxt = libxml2.createPushParser(None, "&lt;foo", 4, "test.xml")
2079ctxt.parseChunk("/&gt;", 2, 1)
2080doc = ctxt.doc()
2081
2082doc.freeDoc()</pre>
2083
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2084<p>The context is created with a special call based on the
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2085xmlCreatePushParser() from the C library. The first argument is an optional
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2086SAX callback object, then the initial set of data, the length and the name of
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2087the resource in case URI-References need to be computed by the parser.</p>
2088
2089<p>Then the data are pushed using the parseChunk() method, the last call
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2090setting the third argument terminate to 1.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2091
2092<h3>pushSAX.py:</h3>
2093
2094<p>this test show the use of the event based parsing interfaces. In this case
2095the parser does not build a document, but provides callback information as
2096the parser makes progresses analyzing the data being provided:</p>
2097<pre>import libxml2
2098log = ""
2099
2100class callback:
2101 def startDocument(self):
2102 global log
2103 log = log + "startDocument:"
2104
2105 def endDocument(self):
2106 global log
2107 log = log + "endDocument:"
2108
2109 def startElement(self, tag, attrs):
2110 global log
2111 log = log + "startElement %s %s:" % (tag, attrs)
2112
2113 def endElement(self, tag):
2114 global log
2115 log = log + "endElement %s:" % (tag)
2116
2117 def characters(self, data):
2118 global log
2119 log = log + "characters: %s:" % (data)
2120
2121 def warning(self, msg):
2122 global log
2123 log = log + "warning: %s:" % (msg)
2124
2125 def error(self, msg):
2126 global log
2127 log = log + "error: %s:" % (msg)
2128
2129 def fatalError(self, msg):
2130 global log
2131 log = log + "fatalError: %s:" % (msg)
2132
2133handler = callback()
2134
2135ctxt = libxml2.createPushParser(handler, "&lt;foo", 4, "test.xml")
2136chunk = " url='tst'&gt;b"
2137ctxt.parseChunk(chunk, len(chunk), 0)
2138chunk = "ar&lt;/foo&gt;"
2139ctxt.parseChunk(chunk, len(chunk), 1)
2140
Daniel Veillardfcbfa2d2002-02-21 17:54:27 +0000[diff] [blame]2141reference = "startDocument:startElement foo {'url': 'tst'}:" + \
2142 "characters: bar:endElement foo:endDocument:"
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2143if log != reference:
2144 print "Error got: %s" % log
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2145 print "Expected: %s" % reference</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2146
2147<p>The key object in that test is the handler, it provides a number of entry
2148points which can be called by the parser as it makes progresses to indicate
2149the information set obtained. The full set of callback is larger than what
2150the callback class in that specific example implements (see the SAX
2151definition for a complete list). The wrapper will only call those supplied by
2152the object when activated. The startElement receives the names of the element
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2153and a dictionary containing the attributes carried by this element.</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2154
2155<p>Also note that the reference string generated from the callback shows a
2156single character call even though the string "bar" is passed to the parser
2157from 2 different call to parseChunk()</p>
2158
2159<h3>xpath.py:</h3>
2160
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2161<p>This is a basic test of XPath wrappers support</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2162<pre>import libxml2
2163
2164doc = libxml2.parseFile("tst.xml")
2165ctxt = doc.xpathNewContext()
2166res = ctxt.xpathEval("//*")
2167if len(res) != 2:
2168 print "xpath query: wrong node set size"
2169 sys.exit(1)
2170if res[0].name != "doc" or res[1].name != "foo":
2171 print "xpath query: wrong node set value"
2172 sys.exit(1)
2173doc.freeDoc()
2174ctxt.xpathFreeContext()</pre>
2175
2176<p>This test parses a file, then create an XPath context to evaluate XPath
2177expression on it. The xpathEval() method execute an XPath query and returns
2178the result mapped in a Python way. String and numbers are natively converted,
2179and node sets are returned as a tuple of libxml2 Python nodes wrappers. Like
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2180the document, the XPath context need to be freed explicitly, also not that
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2181the result of the XPath query may point back to the document tree and hence
2182the document must be freed after the result of the query is used.</p>
2183
2184<h3>xpathext.py:</h3>
2185
2186<p>This test shows how to extend the XPath engine with functions written in
2187python:</p>
2188<pre>import libxml2
2189
2190def foo(ctx, x):
2191 return x + 1
2192
2193doc = libxml2.parseFile("tst.xml")
2194ctxt = doc.xpathNewContext()
2195libxml2.registerXPathFunction(ctxt._o, "foo", None, foo)
2196res = ctxt.xpathEval("foo(1)")
2197if res != 2:
2198 print "xpath extension failure"
2199doc.freeDoc()
2200ctxt.xpathFreeContext()</pre>
2201
2202<p>Note how the extension function is registered with the context (but that
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2203part is not yet finalized, this may change slightly in the future).</p>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2204
2205<h3>tstxpath.py:</h3>
2206
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2207<p>This test is similar to the previous one but shows how the extension
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2208function can access the XPath evaluation context:</p>
2209<pre>def foo(ctx, x):
2210 global called
2211
2212 #
2213 # test that access to the XPath evaluation contexts
2214 #
2215 pctxt = libxml2.xpathParserContext(_obj=ctx)
2216 ctxt = pctxt.context()
2217 called = ctxt.function()
2218 return x + 1</pre>
2219
2220<p>All the interfaces around the XPath parser(or rather evaluation) context
2221are not finalized, but it should be sufficient to do contextual work at the
2222evaluation point.</p>
2223
2224<h3>Memory debugging:</h3>
2225
2226<p>last but not least, all tests starts with the following prologue:</p>
2227<pre>#memory debug specific
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2228libxml2.debugMemory(1)</pre>
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2229
2230<p>and ends with the following epilogue:</p>
2231<pre>#memory debug specific
2232libxml2.cleanupParser()
2233if libxml2.debugMemory(1) == 0:
2234 print "OK"
2235else:
2236 print "Memory leak %d bytes" % (libxml2.debugMemory(1))
2237 libxml2.dumpMemory()</pre>
2238
2239<p>Those activate the memory debugging interface of libxml2 where all
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2240allocated block in the library are tracked. The prologue then cleans up the
Daniel Veillard6dbcaf82002-02-20 14:37:47 +0000[diff] [blame]2241library state and checks that all allocated memory has been freed. If not it
2242calls dumpMemory() which saves that list in a <code>.memdump</code> file.</p>
Daniel Veillard82687162001-01-22 15:32:01 +0000[diff] [blame]2243
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2244<h2><a name="architecture">libxml2 architecture</a></h2>
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]2245
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]2246<p>Libxml2 is made of multiple components; some of them are optional, and
2247most of the block interfaces are public. The main components are:</p>
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]2248<ul>
2249 <li>an Input/Output layer</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]2250 <li>FTP and HTTP client layers (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]2251 <li>an Internationalization layer managing the encodings support</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]2252 <li>a URI module</li>
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]2253 <li>the XML parser and its basic SAX interface</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]2254 <li>an HTML parser using the same SAX interface (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]2255 <li>a SAX tree module to build an in-memory DOM representation</li>
2256 <li>a tree module to manipulate the DOM representation</li>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]2257 <li>a validation module using the DOM representation (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]2258 <li>an XPath module for global lookup in a DOM representation
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]2259 (optional)</li>
2260 <li>a debug module (optional)</li>
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]2261</ul>
2262
2263<p>Graphically this gives the following:</p>
2264
2265<p><img src="libxml.gif" alt="a graphical view of the various"></p>
2266
2267<p></p>
2268
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]2269<h2><a name="tree">The tree output</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]2270
2271<p>The parser returns a tree built during the document analysis. The value
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]2272returned is an <strong>xmlDocPtr</strong> (i.e., a pointer to an
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]2273<strong>xmlDoc</strong> structure). This structure contains information such
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]2274as the file name, the document type, and a <strong>children</strong> pointer
2275which is the root of the document (or more exactly the first child under the
2276root which is the document). The tree is made of <strong>xmlNode</strong>s,
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]2277chained in double-linked lists of siblings and with a children&lt;-&gt;parent
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]2278relationship. An xmlNode can also carry properties (a chain of xmlAttr
2279structures). An attribute may have a value which is a list of TEXT or
2280ENTITY_REF nodes.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]2281
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]2282<p>Here is an example (erroneous with respect to the XML spec since there
2283should be only one ELEMENT under the root):</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]2284
2285<p><img src="structure.gif" alt=" structure.gif "></p>
2286
2287<p>In the source package there is a small program (not installed by default)
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]2288called <strong>xmllint</strong> which parses XML files given as argument and
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]2289prints them back as parsed. This is useful for detecting errors both in XML
2290code and in the XML parser itself. It has an option <strong>--debug</strong>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]2291which prints the actual in-memory structure of the document; here is the
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]2292result with the <a href="#example">example</a> given before:</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]2293<pre>DOCUMENT
2294version=1.0
2295standalone=true
2296 ELEMENT EXAMPLE
2297 ATTRIBUTE prop1
2298 TEXT
2299 content=gnome is great
2300 ATTRIBUTE prop2
2301 ENTITY_REF
2302 TEXT
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]2303 content= linux too
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]2304 ELEMENT head
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]2305 ELEMENT title
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]2306 TEXT
2307 content=Welcome to Gnome
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]2308 ELEMENT chapter
2309 ELEMENT title
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]2310 TEXT
2311 content=The Linux adventure
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]2312 ELEMENT p
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]2313 TEXT
2314 content=bla bla bla ...
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]2315 ELEMENT image
2316 ATTRIBUTE href
2317 TEXT
2318 content=linus.gif
2319 ELEMENT p
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]2320 TEXT
2321 content=...</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]2322
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]2323<p>This should be useful for learning the internal representation model.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]2324
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]2325<h2><a name="interface">The SAX interface</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]2326
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]2327<p>Sometimes the DOM tree output is just too large to fit reasonably into
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]2328memory. In that case (and if you don't expect to save back the XML document
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]2329loaded using libxml), it's better to use the SAX interface of libxml. SAX is
2330a <strong>callback-based interface</strong> to the parser. Before parsing,
2331the application layer registers a customized set of callbacks which are
2332called by the library as it progresses through the XML input.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]2333
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]2334<p>To get more detailed step-by-step guidance on using the SAX interface of
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]2335libxml, see the <a
2336href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">nice
2337documentation</a>.written by <a href="mailto:james@daa.com.au">James
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]2338Henstridge</a>.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]2339
2340<p>You can debug the SAX behaviour by using the <strong>testSAX</strong>
2341program located in the gnome-xml module (it's usually not shipped in the
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]2342binary packages of libxml, but you can find it in the tar source
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]2343distribution). Here is the sequence of callbacks that would be reported by
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]2344testSAX when parsing the example XML document shown earlier:</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]2345<pre>SAX.setDocumentLocator()
2346SAX.startDocument()
2347SAX.getEntity(amp)
2348SAX.startElement(EXAMPLE, prop1='gnome is great', prop2='&amp;amp; linux too')
2349SAX.characters( , 3)
2350SAX.startElement(head)
2351SAX.characters( , 4)
2352SAX.startElement(title)
2353SAX.characters(Welcome to Gnome, 16)
2354SAX.endElement(title)
2355SAX.characters( , 3)
2356SAX.endElement(head)
2357SAX.characters( , 3)
2358SAX.startElement(chapter)
2359SAX.characters( , 4)
2360SAX.startElement(title)
2361SAX.characters(The Linux adventure, 19)
2362SAX.endElement(title)
2363SAX.characters( , 4)
2364SAX.startElement(p)
2365SAX.characters(bla bla bla ..., 15)
2366SAX.endElement(p)
2367SAX.characters( , 4)
2368SAX.startElement(image, href='linus.gif')
2369SAX.endElement(image)
2370SAX.characters( , 4)
2371SAX.startElement(p)
2372SAX.characters(..., 3)
2373SAX.endElement(p)
2374SAX.characters( , 3)
2375SAX.endElement(chapter)
2376SAX.characters( , 1)
2377SAX.endElement(EXAMPLE)
2378SAX.endDocument()</pre>
2379
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2380<p>Most of the other interfaces of libxml2 are based on the DOM tree-building
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]2381facility, so nearly everything up to the end of this document presupposes the
2382use of the standard DOM tree build. Note that the DOM tree itself is built by
2383a set of registered default callbacks, without internal specific
2384interface.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]2385
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2386<h2><a name="Validation">Validation &amp; DTDs</a></h2>
2387
2388<p>Table of Content:</p>
2389<ol>
2390 <li><a href="#General5">General overview</a></li>
2391 <li><a href="#definition">The definition</a></li>
2392 <li><a href="#Simple">Simple rules</a>
2393 <ol>
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]2394 <li><a href="#reference">How to reference a DTD from a document</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2395 <li><a href="#Declaring">Declaring elements</a></li>
2396 <li><a href="#Declaring1">Declaring attributes</a></li>
2397 </ol>
2398 </li>
2399 <li><a href="#Some">Some examples</a></li>
2400 <li><a href="#validate">How to validate</a></li>
2401 <li><a href="#Other">Other resources</a></li>
2402</ol>
2403
2404<h3><a name="General5">General overview</a></h3>
2405
2406<p>Well what is validation and what is a DTD ?</p>
2407
2408<p>DTD is the acronym for Document Type Definition. This is a description of
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2409the content for a family of XML files. This is part of the XML 1.0
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2410specification, and allows one to describe and verify that a given document
2411instance conforms to the set of rules detailing its structure and content.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2412
2413<p>Validation is the process of checking a document against a DTD (more
2414generally against a set of construction rules).</p>
2415
2416<p>The validation process and building DTDs are the two most difficult parts
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2417of the XML life cycle. Briefly a DTD defines all the possible elements to be
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2418found within your document, what is the formal shape of your document tree
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2419(by defining the allowed content of an element; either text, a regular
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2420expression for the allowed list of children, or mixed content i.e. both text
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]2421and children). The DTD also defines the valid attributes for all elements and
2422the types of those attributes.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2423
2424<h3><a name="definition1">The definition</a></h3>
2425
2426<p>The <a href="http://www.w3.org/TR/REC-xml">W3C XML Recommendation</a> (<a
2427href="http://www.xml.com/axml/axml.html">Tim Bray's annotated version of
2428Rev1</a>):</p>
2429<ul>
2430 <li><a href="http://www.w3.org/TR/REC-xml#elemdecls">Declaring
2431 elements</a></li>
2432 <li><a href="http://www.w3.org/TR/REC-xml#attdecls">Declaring
2433 attributes</a></li>
2434</ul>
2435
2436<p>(unfortunately) all this is inherited from the SGML world, the syntax is
2437ancient...</p>
2438
2439<h3><a name="Simple1">Simple rules</a></h3>
2440
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]2441<p>Writing DTDs can be done in many ways. The rules to build them if you need
2442something permanent or something which can evolve over time can be radically
2443different. Really complex DTDs like DocBook ones are flexible but quite
2444harder to design. I will just focus on DTDs for a formats with a fixed simple
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2445structure. It is just a set of basic rules, and definitely not exhaustive nor
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2446usable for complex DTD design.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2447
2448<h4><a name="reference1">How to reference a DTD from a document</a>:</h4>
2449
2450<p>Assuming the top element of the document is <code>spec</code> and the dtd
2451is placed in the file <code>mydtd</code> in the subdirectory
2452<code>dtds</code> of the directory from where the document were loaded:</p>
2453
2454<p><code>&lt;!DOCTYPE spec SYSTEM "dtds/mydtd"&gt;</code></p>
2455
2456<p>Notes:</p>
2457<ul>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2458 <li>The system string is actually an URI-Reference (as defined in <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2459 href="http://www.ietf.org/rfc/rfc2396.txt">RFC 2396</a>) so you can use a
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2460 full URL string indicating the location of your DTD on the Web. This is a
2461 really good thing to do if you want others to validate your document.</li>
2462 <li>It is also possible to associate a <code>PUBLIC</code> identifier (a
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2463 magic string) so that the DTD is looked up in catalogs on the client side
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2464 without having to locate it on the web.</li>
2465 <li>A DTD contains a set of element and attribute declarations, but they
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2466 don't define what the root of the document should be. This is explicitly
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2467 told to the parser/validator as the first element of the
2468 <code>DOCTYPE</code> declaration.</li>
2469</ul>
2470
2471<h4><a name="Declaring2">Declaring elements</a>:</h4>
2472
2473<p>The following declares an element <code>spec</code>:</p>
2474
2475<p><code>&lt;!ELEMENT spec (front, body, back?)&gt;</code></p>
2476
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2477<p>It also expresses that the spec element contains one <code>front</code>,
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]2478one <code>body</code> and one optional <code>back</code> children elements in
2479this order. The declaration of one element of the structure and its content
2480are done in a single declaration. Similarly the following declares
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2481<code>div1</code> elements:</p>
2482
Daniel Veillard51737272002-01-23 23:10:38 +0000[diff] [blame]2483<p><code>&lt;!ELEMENT div1 (head, (p | list | note)*, div2?)&gt;</code></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2484
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2485<p>which means div1 contains one <code>head</code> then a series of optional
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2486<code>p</code>, <code>list</code>s and <code>note</code>s and then an
2487optional <code>div2</code>. And last but not least an element can contain
2488text:</p>
2489
2490<p><code>&lt;!ELEMENT b (#PCDATA)&gt;</code></p>
2491
2492<p><code>b</code> contains text or being of mixed content (text and elements
2493in no particular order):</p>
2494
2495<p><code>&lt;!ELEMENT p (#PCDATA|a|ul|b|i|em)*&gt;</code></p>
2496
2497<p><code>p </code>can contain text or <code>a</code>, <code>ul</code>,
2498<code>b</code>, <code>i </code>or <code>em</code> elements in no particular
2499order.</p>
2500
2501<h4><a name="Declaring1">Declaring attributes</a>:</h4>
2502
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2503<p>Again the attributes declaration includes their content definition:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2504
2505<p><code>&lt;!ATTLIST termdef name CDATA #IMPLIED&gt;</code></p>
2506
2507<p>means that the element <code>termdef</code> can have a <code>name</code>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2508attribute containing text (<code>CDATA</code>) and which is optional
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2509(<code>#IMPLIED</code>). The attribute value can also be defined within a
2510set:</p>
2511
2512<p><code>&lt;!ATTLIST list type (bullets|ordered|glossary)
2513"ordered"&gt;</code></p>
2514
2515<p>means <code>list</code> element have a <code>type</code> attribute with 3
2516allowed values "bullets", "ordered" or "glossary" and which default to
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2517"ordered" if the attribute is not explicitly specified.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2518
2519<p>The content type of an attribute can be text (<code>CDATA</code>),
2520anchor/reference/references
2521(<code>ID</code>/<code>IDREF</code>/<code>IDREFS</code>), entity(ies)
2522(<code>ENTITY</code>/<code>ENTITIES</code>) or name(s)
2523(<code>NMTOKEN</code>/<code>NMTOKENS</code>). The following defines that a
2524<code>chapter</code> element can have an optional <code>id</code> attribute
2525of type <code>ID</code>, usable for reference from attribute of type
2526IDREF:</p>
2527
2528<p><code>&lt;!ATTLIST chapter id ID #IMPLIED&gt;</code></p>
2529
2530<p>The last value of an attribute definition can be <code>#REQUIRED
2531</code>meaning that the attribute has to be given, <code>#IMPLIED</code>
2532meaning that it is optional, or the default value (possibly prefixed by
2533<code>#FIXED</code> if it is the only allowed).</p>
2534
2535<p>Notes:</p>
2536<ul>
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2537 <li>Usually the attributes pertaining to a given element are declared in a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2538 single expression, but it is just a convention adopted by a lot of DTD
2539 writers:
2540 <pre>&lt;!ATTLIST termdef
2541 id ID #REQUIRED
2542 name CDATA #IMPLIED&gt;</pre>
2543 <p>The previous construct defines both <code>id</code> and
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2544 <code>name</code> attributes for the element <code>termdef</code>.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2545 </li>
2546</ul>
2547
2548<h3><a name="Some1">Some examples</a></h3>
2549
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2550<p>The directory <code>test/valid/dtds/</code> in the libxml2 distribution
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]2551contains some complex DTD examples. The example in the file
2552<code>test/valid/dia.xml</code> shows an XML file where the simple DTD is
2553directly included within the document.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2554
2555<h3><a name="validate1">How to validate</a></h3>
2556
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2557<p>The simplest way is to use the xmllint program included with libxml. The
2558<code>--valid</code> option turns-on validation of the files given as input.
2559For example the following validates a copy of the first revision of the XML
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]25601.0 specification:</p>
2561
2562<p><code>xmllint --valid --noout test/valid/REC-xml-19980210.xml</code></p>
2563
Daniel Veillard0b28e882002-07-24 23:47:05 +0000[diff] [blame]2564<p>the -- noout is used to disable output of the resulting tree.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2565
Daniel Veillard42766c02002-08-22 20:52:17 +0000[diff] [blame]2566<p>The <code>--dtdvalid dtd</code> allows validation of the document(s)
2567against a given DTD.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2568
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2569<p>Libxml2 exports an API to handle DTDs and validation, check the <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2570href="http://xmlsoft.org/html/libxml-valid.html">associated
2571description</a>.</p>
2572
2573<h3><a name="Other1">Other resources</a></h3>
2574
2575<p>DTDs are as old as SGML. So there may be a number of examples on-line, I
2576will just list one for now, others pointers welcome:</p>
2577<ul>
2578 <li><a href="http://www.xml101.com:8081/dtd/">XML-101 DTD</a></li>
2579</ul>
2580
2581<p>I suggest looking at the examples found under test/valid/dtd and any of
2582the large number of books available on XML. The dia example in test/valid
2583should be both simple and complete enough to allow you to build your own.</p>
2584
2585<p></p>
2586
2587<h2><a name="Memory">Memory Management</a></h2>
2588
2589<p>Table of Content:</p>
2590<ol>
2591 <li><a href="#General3">General overview</a></li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2592 <li><a href="#setting">Setting libxml2 set of memory routines</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2593 <li><a href="#cleanup">Cleaning up after parsing</a></li>
2594 <li><a href="#Debugging">Debugging routines</a></li>
2595 <li><a href="#General4">General memory requirements</a></li>
2596</ol>
2597
2598<h3><a name="General3">General overview</a></h3>
2599
2600<p>The module <code><a
2601href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlmemory.h</a></code>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2602provides the interfaces to the libxml2 memory system:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2603<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2604 <li>libxml2 does not use the libc memory allocator directly but xmlFree(),
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2605 xmlMalloc() and xmlRealloc()</li>
2606 <li>those routines can be reallocated to a specific set of routine, by
2607 default the libc ones i.e. free(), malloc() and realloc()</li>
2608 <li>the xmlmemory.c module includes a set of debugging routine</li>
2609</ul>
2610
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2611<h3><a name="setting">Setting libxml2 set of memory routines</a></h3>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2612
2613<p>It is sometimes useful to not use the default memory allocator, either for
2614debugging, analysis or to implement a specific behaviour on memory management
2615(like on embedded systems). Two function calls are available to do so:</p>
2616<ul>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2617 <li><a href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemGet
2618 ()</a> which return the current set of functions in use by the parser</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2619 <li><a
2620 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemSetup()</a>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2621 which allow to set up a new set of memory allocation functions</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2622</ul>
2623
2624<p>Of course a call to xmlMemSetup() should probably be done before calling
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2625any other libxml2 routines (unless you are sure your allocations routines are
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2626compatibles).</p>
2627
2628<h3><a name="cleanup">Cleaning up after parsing</a></h3>
2629
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2630<p>Libxml2 is not stateless, there is a few set of memory structures needing
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2631allocation before the parser is fully functional (some encoding structures
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2632for example). This also mean that once parsing is finished there is a tiny
2633amount of memory (a few hundred bytes) which can be recollected if you don't
2634reuse the parser immediately:</p>
2635<ul>
2636 <li><a href="http://xmlsoft.org/html/libxml-parser.html">xmlCleanupParser
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2637 ()</a> is a centralized routine to free the parsing states. Note that it
2638 won't deallocate any produced tree if any (use the xmlFreeDoc() and
2639 related routines for this).</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2640 <li><a href="http://xmlsoft.org/html/libxml-parser.html">xmlInitParser
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2641 ()</a> is the dual routine allowing to preallocate the parsing state
2642 which can be useful for example to avoid initialization reentrancy
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2643 problems when using libxml2 in multithreaded applications</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2644</ul>
2645
2646<p>Generally xmlCleanupParser() is safe, if needed the state will be rebuild
2647at the next invocation of parser routines, but be careful of the consequences
2648in multithreaded applications.</p>
2649
2650<h3><a name="Debugging">Debugging routines</a></h3>
2651
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2652<p>When configured using --with-mem-debug flag (off by default), libxml2 uses
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2653a set of memory allocation debugging routines keeping track of all allocated
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2654blocks and the location in the code where the routine was called. A couple of
2655other debugging routines allow to dump the memory allocated infos to a file
2656or call a specific routine when a given block number is allocated:</p>
2657<ul>
2658 <li><a
2659 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMallocLoc()</a>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2660 <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2661 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlReallocLoc()</a>
2662 and <a
2663 href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemStrdupLoc()</a>
2664 are the memory debugging replacement allocation routines</li>
2665 <li><a href="http://xmlsoft.org/html/libxml-xmlmemory.html">xmlMemoryDump
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]2666 ()</a> dumps all the informations about the allocated memory block lefts
2667 in the <code>.memdump</code> file</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2668</ul>
2669
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2670<p>When developing libxml2 memory debug is enabled, the tests programs call
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2671xmlMemoryDump () and the "make test" regression tests will check for any
2672memory leak during the full regression test sequence, this helps a lot
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2673ensuring that libxml2 does not leak memory and bullet proof memory
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2674allocations use (some libc implementations are known to be far too permissive
2675resulting in major portability problems!).</p>
2676
2677<p>If the .memdump reports a leak, it displays the allocation function and
2678also tries to give some informations about the content and structure of the
2679allocated blocks left. This is sufficient in most cases to find the culprit,
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2680but not always. Assuming the allocation problem is reproducible, it is
2681possible to find more easily:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2682<ol>
2683 <li>write down the block number xxxx not allocated</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2684 <li>export the environment variable XML_MEM_BREAKPOINT=xxxx , the easiest
Daniel Veillard75794822002-04-11 16:24:32 +0000[diff] [blame]2685 when using GDB is to simply give the command
2686 <p><code>set environment XML_MEM_BREAKPOINT xxxx</code></p>
2687 <p>before running the program.</p>
2688 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2689 <li>run the program under a debugger and set a breakpoint on
2690 xmlMallocBreakpoint() a specific function called when this precise block
2691 is allocated</li>
2692 <li>when the breakpoint is reached you can then do a fine analysis of the
2693 allocation an step to see the condition resulting in the missing
2694 deallocation.</li>
2695</ol>
2696
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2697<p>I used to use a commercial tool to debug libxml2 memory problems but after
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2698noticing that it was not detecting memory leaks that simple mechanism was
Daniel Veillard75794822002-04-11 16:24:32 +0000[diff] [blame]2699used and proved extremely efficient until now. Lately I have also used <a
2700href="http://developer.kde.org/~sewardj/">valgrind</a> with quite some
2701success, it is tied to the i386 architecture since it works by emulating the
2702processor and instruction set, it is slow but extremely efficient, i.e. it
2703spot memory usage errors in a very precise way.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2704
2705<h3><a name="General4">General memory requirements</a></h3>
2706
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2707<p>How much libxml2 memory require ? It's hard to tell in average it depends
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2708of a number of things:</p>
2709<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2710 <li>the parser itself should work in a fixed amount of memory, except for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2711 information maintained about the stacks of names and entities locations.
2712 The I/O and encoding handlers will probably account for a few KBytes.
2713 This is true for both the XML and HTML parser (though the HTML parser
2714 need more state).</li>
2715 <li>If you are generating the DOM tree then memory requirements will grow
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2716 nearly linear with the size of the data. In general for a balanced
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2717 textual document the internal memory requirement is about 4 times the
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2718 size of the UTF8 serialization of this document (example the XML-1.0
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2719 recommendation is a bit more of 150KBytes and takes 650KBytes of main
2720 memory when parsed). Validation will add a amount of memory required for
2721 maintaining the external Dtd state which should be linear with the
2722 complexity of the content model defined by the Dtd</li>
Daniel Veillardce192eb2003-04-16 15:58:05 +0000[diff] [blame]2723 <li>If you need to work with fixed memory requirements or don't need the
2724 full DOM tree then using the <a href="xmlreader.html">xmlReader
2725 interface</a> is probably the best way to proceed, it still allows to
2726 validate or operate on subset of the tree if needed.</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2727 <li>If you don't care about the advanced features of libxml2 like
Daniel Veillardce192eb2003-04-16 15:58:05 +0000[diff] [blame]2728 validation, DOM, XPath or XPointer, don't use entities, need to work with
2729 fixed memory requirements, and try to get the fastest parsing possible
2730 then the SAX interface should be used, but it has known restrictions.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2731</ul>
2732
2733<p></p>
2734
2735<h2><a name="Encodings">Encodings support</a></h2>
2736
2737<p>Table of Content:</p>
2738<ol>
2739 <li><a href="encoding.html#What">What does internationalization support
2740 mean ?</a></li>
2741 <li><a href="encoding.html#internal">The internal encoding, how and
2742 why</a></li>
2743 <li><a href="encoding.html#implemente">How is it implemented ?</a></li>
2744 <li><a href="encoding.html#Default">Default supported encodings</a></li>
2745 <li><a href="encoding.html#extend">How to extend the existing
2746 support</a></li>
2747</ol>
2748
2749<h3><a name="What">What does internationalization support mean ?</a></h3>
2750
Daniel Veillard238836e2003-04-07 22:57:29 +0000[diff] [blame]2751<p>If you are not really familiar with Internationalization (usual shorcut is
2752I18N) , Unicode, characters and glyphs, I suggest you read a <a
2753href="http://www.tbray.org/ongoing/When/200x/2003/04/06/Unicode">presentation</a>
2754by Tim Bray on Unicode and why you should care about it.</p>
2755
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2756<p>XML was designed from the start to allow the support of any character set
2757by using Unicode. Any conformant XML parser has to support the UTF-8 and
2758UTF-16 default encodings which can both express the full unicode ranges. UTF8
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2759is a variable length encoding whose greatest points are to reuse the same
2760encoding for ASCII and to save space for Western encodings, but it is a bit
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2761more complex to handle in practice. UTF-16 use 2 bytes per characters (and
2762sometimes combines two pairs), it makes implementation easier, but looks a
2763bit overkill for Western languages encoding. Moreover the XML specification
2764allows document to be encoded in other encodings at the condition that they
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2765are clearly labeled as such. For example the following is a wellformed XML
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2766document encoded in ISO-8859 1 and using accentuated letter that we French
2767likes for both markup and content:</p>
2768<pre>&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
2769&lt;très&gt;là&lt;/très&gt;</pre>
2770
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2771<p>Having internationalization support in libxml2 means the following:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2772<ul>
2773 <li>the document is properly parsed</li>
2774 <li>informations about it's encoding are saved</li>
2775 <li>it can be modified</li>
2776 <li>it can be saved in its original encoding</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2777 <li>it can also be saved in another encoding supported by libxml2 (for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2778 example straight UTF8 or even an ASCII form)</li>
2779</ul>
2780
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2781<p>Another very important point is that the whole libxml2 API, with the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2782exception of a few routines to read with a specific encoding or save to a
2783specific encoding, is completely agnostic about the original encoding of the
2784document.</p>
2785
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2786<p>It should be noted too that the HTML parser embedded in libxml2 now obey
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2787the same rules too, the following document will be (as of 2.2.2) handled in
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2788an internationalized fashion by libxml2 too:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2789<pre>&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
2790 "http://www.w3.org/TR/REC-html40/loose.dtd"&gt;
2791&lt;html lang="fr"&gt;
2792&lt;head&gt;
2793 &lt;META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"&gt;
2794&lt;/head&gt;
2795&lt;body&gt;
2796&lt;p&gt;W3C crée des standards pour le Web.&lt;/body&gt;
2797&lt;/html&gt;</pre>
2798
2799<h3><a name="internal">The internal encoding, how and why</a></h3>
2800
2801<p>One of the core decision was to force all documents to be converted to a
2802default internal encoding, and that encoding to be UTF-8, here are the
2803rationale for those choices:</p>
2804<ul>
2805 <li>keeping the native encoding in the internal form would force the libxml
2806 users (or the code associated) to be fully aware of the encoding of the
2807 original document, for examples when adding a text node to a document,
2808 the content would have to be provided in the document encoding, i.e. the
2809 client code would have to check it before hand, make sure it's conformant
2810 to the encoding, etc ... Very hard in practice, though in some specific
2811 cases this may make sense.</li>
2812 <li>the second decision was which encoding. From the XML spec only UTF8 and
2813 UTF16 really makes sense as being the two only encodings for which there
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2814 is mandatory support. UCS-4 (32 bits fixed size encoding) could be
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2815 considered an intelligent choice too since it's a direct Unicode mapping
2816 support. I selected UTF-8 on the basis of efficiency and compatibility
2817 with surrounding software:
2818 <ul>
2819 <li>UTF-8 while a bit more complex to convert from/to (i.e. slightly
2820 more costly to import and export CPU wise) is also far more compact
2821 than UTF-16 (and UCS-4) for a majority of the documents I see it used
2822 for right now (RPM RDF catalogs, advogato data, various configuration
2823 file formats, etc.) and the key point for today's computer
2824 architecture is efficient uses of caches. If one nearly double the
2825 memory requirement to store the same amount of data, this will trash
2826 caches (main memory/external caches/internal caches) and my take is
2827 that this harms the system far more than the CPU requirements needed
2828 for the conversion to UTF-8</li>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2829 <li>Most of libxml2 version 1 users were using it with straight ASCII
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2830 most of the time, doing the conversion with an internal encoding
2831 requiring all their code to be rewritten was a serious show-stopper
2832 for using UTF-16 or UCS-4.</li>
2833 <li>UTF-8 is being used as the de-facto internal encoding standard for
2834 related code like the <a href="http://www.pango.org/">pango</a>
2835 upcoming Gnome text widget, and a lot of Unix code (yep another place
2836 where Unix programmer base takes a different approach from Microsoft
2837 - they are using UTF-16)</li>
2838 </ul>
2839 </li>
2840</ul>
2841
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2842<p>What does this mean in practice for the libxml2 user:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2843<ul>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2844 <li>xmlChar, the libxml2 data type is a byte, those bytes must be assembled
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2845 as UTF-8 valid strings. The proper way to terminate an xmlChar * string
2846 is simply to append 0 byte, as usual.</li>
2847 <li>One just need to make sure that when using chars outside the ASCII set,
2848 the values has been properly converted to UTF-8</li>
2849</ul>
2850
2851<h3><a name="implemente">How is it implemented ?</a></h3>
2852
2853<p>Let's describe how all this works within libxml, basically the I18N
2854(internationalization) support get triggered only during I/O operation, i.e.
2855when reading a document or saving one. Let's look first at the reading
2856sequence:</p>
2857<ol>
2858 <li>when a document is processed, we usually don't know the encoding, a
Daniel Veillard7b68df92003-08-03 22:58:54 +0000[diff] [blame]2859 simple heuristic allows to detect UTF-16 and UCS-4 from whose where the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2860 ASCII range (0-0x7F) maps with ASCII</li>
2861 <li>the xml declaration if available is parsed, including the encoding
2862 declaration. At that point, if the autodetected encoding is different
2863 from the one declared a call to xmlSwitchEncoding() is issued.</li>
2864 <li>If there is no encoding declaration, then the input has to be in either
2865 UTF-8 or UTF-16, if it is not then at some point when processing the
2866 input, the converter/checker of UTF-8 form will raise an encoding error.
2867 You may end-up with a garbled document, or no document at all ! Example:
2868 <pre>~/XML -&gt; ./xmllint err.xml
2869err.xml:1: error: Input is not proper UTF-8, indicate encoding !
2870&lt;très&gt;là&lt;/très&gt;
2871 ^
2872err.xml:1: error: Bytes: 0xE8 0x73 0x3E 0x6C
2873&lt;très&gt;là&lt;/très&gt;
2874 ^</pre>
2875 </li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2876 <li>xmlSwitchEncoding() does an encoding name lookup, canonicalize it, and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2877 then search the default registered encoding converters for that encoding.
2878 If it's not within the default set and iconv() support has been compiled
2879 it, it will ask iconv for such an encoder. If this fails then the parser
2880 will report an error and stops processing:
2881 <pre>~/XML -&gt; ./xmllint err2.xml
2882err2.xml:1: error: Unsupported encoding UnsupportedEnc
2883&lt;?xml version="1.0" encoding="UnsupportedEnc"?&gt;
2884 ^</pre>
2885 </li>
Daniel Veillard46c5c1d2002-05-20 07:15:54 +0000[diff] [blame]2886 <li>From that point the encoder processes progressively the input (it is
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2887 plugged as a front-end to the I/O module) for that entity. It captures
2888 and convert on-the-fly the document to be parsed to UTF-8. The parser
2889 itself just does UTF-8 checking of this input and process it
2890 transparently. The only difference is that the encoding information has
2891 been added to the parsing context (more precisely to the input
2892 corresponding to this entity).</li>
2893 <li>The result (when using DOM) is an internal form completely in UTF-8
2894 with just an encoding information on the document node.</li>
2895</ol>
2896
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2897<p>Ok then what happens when saving the document (assuming you
2898collected/built an xmlDoc DOM like structure) ? It depends on the function
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2899called, xmlSaveFile() will just try to save in the original encoding, while
2900xmlSaveFileTo() and xmlSaveFileEnc() can optionally save to a given
2901encoding:</p>
2902<ol>
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2903 <li>if no encoding is given, libxml2 will look for an encoding value
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2904 associated to the document and if it exists will try to save to that
2905 encoding,
2906 <p>otherwise everything is written in the internal form, i.e. UTF-8</p>
2907 </li>
2908 <li>so if an encoding was specified, either at the API level or on the
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2909 document, libxml2 will again canonicalize the encoding name, lookup for a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2910 converter in the registered set or through iconv. If not found the
2911 function will return an error code</li>
2912 <li>the converter is placed before the I/O buffer layer, as another kind of
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2913 buffer, then libxml2 will simply push the UTF-8 serialization to through
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2914 that buffer, which will then progressively be converted and pushed onto
2915 the I/O layer.</li>
2916 <li>It is possible that the converter code fails on some input, for example
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2917 trying to push an UTF-8 encoded Chinese character through the UTF-8 to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2918 ISO-8859-1 converter won't work. Since the encoders are progressive they
2919 will just report the error and the number of bytes converted, at that
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2920 point libxml2 will decode the offending character, remove it from the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2921 buffer and replace it with the associated charRef encoding &amp;#123; and
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2922 resume the conversion. This guarantees that any document will be saved
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2923 without losses (except for markup names where this is not legal, this is
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]2924 a problem in the current version, in practice avoid using non-ascii
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2925 characters for tags or attributes names @@). A special "ascii" encoding
2926 name is used to save documents to a pure ascii form can be used when
2927 portability is really crucial</li>
2928</ol>
2929
2930<p>Here is a few examples based on the same test document:</p>
2931<pre>~/XML -&gt; ./xmllint isolat1
2932&lt;?xml version="1.0" encoding="ISO-8859-1"?&gt;
2933&lt;très&gt;là&lt;/très&gt;
2934~/XML -&gt; ./xmllint --encode UTF-8 isolat1
2935&lt;?xml version="1.0" encoding="UTF-8"?&gt;
2936&lt;très&gt;là  &lt;/très&gt;
2937~/XML -&gt; </pre>
2938
2939<p>The same processing is applied (and reuse most of the code) for HTML I18N
2940processing. Looking up and modifying the content encoding is a bit more
2941difficult since it is located in a &lt;meta&gt; tag under the &lt;head&gt;,
2942so a couple of functions htmlGetMetaEncoding() and htmlSetMetaEncoding() have
2943been provided. The parser also attempts to switch encoding on the fly when
2944detecting such a tag on input. Except for that the processing is the same
2945(and again reuses the same code).</p>
2946
2947<h3><a name="Default">Default supported encodings</a></h3>
2948
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2949<p>libxml2 has a set of default converters for the following encodings
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2950(located in encoding.c):</p>
2951<ol>
2952 <li>UTF-8 is supported by default (null handlers)</li>
2953 <li>UTF-16, both little and big endian</li>
2954 <li>ISO-Latin-1 (ISO-8859-1) covering most western languages</li>
2955 <li>ASCII, useful mostly for saving</li>
2956 <li>HTML, a specific handler for the conversion of UTF-8 to ASCII with HTML
2957 predefined entities like &amp;copy; for the Copyright sign.</li>
2958</ol>
2959
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]2960<p>More over when compiled on an Unix platform with iconv support the full
2961set of encodings supported by iconv can be instantly be used by libxml. On a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2962linux machine with glibc-2.1 the list of supported encodings and aliases fill
29633 full pages, and include UCS-4, the full set of ISO-Latin encodings, and the
2964various Japanese ones.</p>
2965
2966<h4>Encoding aliases</h4>
2967
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2968<p>From 2.2.3, libxml2 has support to register encoding names aliases. The
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2969goal is to be able to parse document whose encoding is supported but where
2970the name differs (for example from the default set of names accepted by
2971iconv). The following functions allow to register and handle new aliases for
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]2972existing encodings. Once registered libxml2 will automatically lookup the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]2973aliases when handling a document:</p>
2974<ul>
2975 <li>int xmlAddEncodingAlias(const char *name, const char *alias);</li>
2976 <li>int xmlDelEncodingAlias(const char *alias);</li>
2977 <li>const char * xmlGetEncodingAlias(const char *alias);</li>
2978 <li>void xmlCleanupEncodingAliases(void);</li>
2979</ul>
2980
2981<h3><a name="extend">How to extend the existing support</a></h3>
2982
2983<p>Well adding support for new encoding, or overriding one of the encoders
2984(assuming it is buggy) should not be hard, just write an input and output
2985conversion routines to/from UTF-8, and register them using
2986xmlNewCharEncodingHandler(name, xxxToUTF8, UTF8Toxxx), and they will be
2987called automatically if the parser(s) encounter such an encoding name
2988(register it uppercase, this will help). The description of the encoders,
2989their arguments and expected return values are described in the encoding.h
2990header.</p>
2991
2992<p>A quick note on the topic of subverting the parser to use a different
2993internal encoding than UTF-8, in some case people will absolutely want to
2994keep the internal encoding different, I think it's still possible (but the
2995encoding must be compliant with ASCII on the same subrange) though I didn't
2996tried it. The key is to override the default conversion routines (by
2997registering null encoders/decoders for your charsets), and bypass the UTF-8
2998checking of the parser by setting the parser context charset
2999(ctxt-&gt;charset) to something different than XML_CHAR_ENCODING_UTF8, but
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3000there is no guarantee that this will work. You may also have some troubles
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3001saving back.</p>
3002
3003<p>Basically proper I18N support is important, this requires at least
3004libxml-2.0.0, but a lot of features and corrections are really available only
3005starting 2.2.</p>
3006
3007<h2><a name="IO">I/O Interfaces</a></h2>
3008
3009<p>Table of Content:</p>
3010<ol>
3011 <li><a href="#General1">General overview</a></li>
3012 <li><a href="#basic">The basic buffer type</a></li>
3013 <li><a href="#Input">Input I/O handlers</a></li>
3014 <li><a href="#Output">Output I/O handlers</a></li>
3015 <li><a href="#entities">The entities loader</a></li>
3016 <li><a href="#Example2">Example of customized I/O</a></li>
3017</ol>
3018
3019<h3><a name="General1">General overview</a></h3>
3020
3021<p>The module <code><a
3022href="http://xmlsoft.org/html/libxml-xmlio.html">xmlIO.h</a></code> provides
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3023the interfaces to the libxml2 I/O system. This consists of 4 main parts:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3024<ul>
3025 <li>Entities loader, this is a routine which tries to fetch the entities
3026 (files) based on their PUBLIC and SYSTEM identifiers. The default loader
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3027 don't look at the public identifier since libxml2 do not maintain a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3028 catalog. You can redefine you own entity loader by using
3029 <code>xmlGetExternalEntityLoader()</code> and
Daniel Veillard9c466822001-10-25 12:03:39 +0000[diff] [blame]3030 <code>xmlSetExternalEntityLoader()</code>. <a href="#entities">Check the
3031 example</a>.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3032 <li>Input I/O buffers which are a commodity structure used by the parser(s)
3033 input layer to handle fetching the informations to feed the parser. This
3034 provides buffering and is also a placeholder where the encoding
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3035 converters to UTF8 are piggy-backed.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3036 <li>Output I/O buffers are similar to the Input ones and fulfill similar
3037 task but when generating a serialization from a tree.</li>
3038 <li>A mechanism to register sets of I/O callbacks and associate them with
3039 specific naming schemes like the protocol part of the URIs.
3040 <p>This affect the default I/O operations and allows to use specific I/O
3041 handlers for certain names.</p>
3042 </li>
3043</ul>
3044
3045<p>The general mechanism used when loading http://rpmfind.net/xml.html for
3046example in the HTML parser is the following:</p>
3047<ol>
3048 <li>The default entity loader calls <code>xmlNewInputFromFile()</code> with
3049 the parsing context and the URI string.</li>
3050 <li>the URI string is checked against the existing registered handlers
3051 using their match() callback function, if the HTTP module was compiled
3052 in, it is registered and its match() function will succeeds</li>
3053 <li>the open() function of the handler is called and if successful will
3054 return an I/O Input buffer</li>
3055 <li>the parser will the start reading from this buffer and progressively
3056 fetch information from the resource, calling the read() function of the
3057 handler until the resource is exhausted</li>
3058 <li>if an encoding change is detected it will be installed on the input
3059 buffer, providing buffering and efficient use of the conversion
3060 routines</li>
3061 <li>once the parser has finished, the close() function of the handler is
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3062 called once and the Input buffer and associated resources are
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3063 deallocated.</li>
3064</ol>
3065
3066<p>The user defined callbacks are checked first to allow overriding of the
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3067default libxml2 I/O routines.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3068
3069<h3><a name="basic">The basic buffer type</a></h3>
3070
3071<p>All the buffer manipulation handling is done using the
3072<code>xmlBuffer</code> type define in <code><a
3073href="http://xmlsoft.org/html/libxml-tree.html">tree.h</a> </code>which is a
3074resizable memory buffer. The buffer allocation strategy can be selected to be
3075either best-fit or use an exponential doubling one (CPU vs. memory use
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3076trade-off). The values are <code>XML_BUFFER_ALLOC_EXACT</code> and
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3077<code>XML_BUFFER_ALLOC_DOUBLEIT</code>, and can be set individually or on a
3078system wide basis using <code>xmlBufferSetAllocationScheme()</code>. A number
3079of functions allows to manipulate buffers with names starting with the
3080<code>xmlBuffer...</code> prefix.</p>
3081
3082<h3><a name="Input">Input I/O handlers</a></h3>
3083
3084<p>An Input I/O handler is a simple structure
3085<code>xmlParserInputBuffer</code> containing a context associated to the
3086resource (file descriptor, or pointer to a protocol handler), the read() and
3087close() callbacks to use and an xmlBuffer. And extra xmlBuffer and a charset
3088encoding handler are also present to support charset conversion when
3089needed.</p>
3090
3091<h3><a name="Output">Output I/O handlers</a></h3>
3092
3093<p>An Output handler <code>xmlOutputBuffer</code> is completely similar to an
3094Input one except the callbacks are write() and close().</p>
3095
3096<h3><a name="entities">The entities loader</a></h3>
3097
3098<p>The entity loader resolves requests for new entities and create inputs for
3099the parser. Creating an input from a filename or an URI string is done
3100through the xmlNewInputFromFile() routine. The default entity loader do not
3101handle the PUBLIC identifier associated with an entity (if any). So it just
3102calls xmlNewInputFromFile() with the SYSTEM identifier (which is mandatory in
3103XML).</p>
3104
3105<p>If you want to hook up a catalog mechanism then you simply need to
3106override the default entity loader, here is an example:</p>
3107<pre>#include &lt;libxml/xmlIO.h&gt;
3108
3109xmlExternalEntityLoader defaultLoader = NULL;
3110
3111xmlParserInputPtr
3112xmlMyExternalEntityLoader(const char *URL, const char *ID,
3113 xmlParserCtxtPtr ctxt) {
3114 xmlParserInputPtr ret;
3115 const char *fileID = NULL;
3116 /* lookup for the fileID depending on ID */
3117
3118 ret = xmlNewInputFromFile(ctxt, fileID);
3119 if (ret != NULL)
3120 return(ret);
3121 if (defaultLoader != NULL)
3122 ret = defaultLoader(URL, ID, ctxt);
3123 return(ret);
3124}
3125
3126int main(..) {
3127 ...
3128
3129 /*
3130 * Install our own entity loader
3131 */
3132 defaultLoader = xmlGetExternalEntityLoader();
3133 xmlSetExternalEntityLoader(xmlMyExternalEntityLoader);
3134
3135 ...
3136}</pre>
3137
3138<h3><a name="Example2">Example of customized I/O</a></h3>
3139
3140<p>This example come from <a href="http://xmlsoft.org/messages/0708.html">a
3141real use case</a>, xmlDocDump() closes the FILE * passed by the application
3142and this was a problem. The <a
3143href="http://xmlsoft.org/messages/0711.html">solution</a> was to redefine a
3144new output handler with the closing call deactivated:</p>
3145<ol>
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]3146 <li>First define a new I/O output allocator where the output don't close
3147 the file:
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3148 <pre>xmlOutputBufferPtr
3149xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) {
3150    xmlOutputBufferPtr ret;
3151    
3152    if (xmlOutputCallbackInitialized == 0)
3153        xmlRegisterDefaultOutputCallbacks();
3154
3155    if (file == NULL) return(NULL);
3156    ret = xmlAllocOutputBuffer(encoder);
3157    if (ret != NULL) {
3158        ret-&gt;context = file;
3159        ret-&gt;writecallback = xmlFileWrite;
3160        ret-&gt;closecallback = NULL; /* No close callback */
3161    }
Daniel Veillardf83a2c72003-04-08 13:48:40 +0000[diff] [blame]3162    return(ret);
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3163} </pre>
3164 </li>
3165 <li>And then use it to save the document:
3166 <pre>FILE *f;
3167xmlOutputBufferPtr output;
3168xmlDocPtr doc;
3169int res;
3170
3171f = ...
3172doc = ....
3173
3174output = xmlOutputBufferCreateOwn(f, NULL);
3175res = xmlSaveFileTo(output, doc, NULL);
3176 </pre>
3177 </li>
3178</ol>
3179
3180<h2><a name="Catalog">Catalog support</a></h2>
3181
3182<p>Table of Content:</p>
3183<ol>
3184 <li><a href="General2">General overview</a></li>
3185 <li><a href="#definition">The definition</a></li>
3186 <li><a href="#Simple">Using catalogs</a></li>
3187 <li><a href="#Some">Some examples</a></li>
3188 <li><a href="#reference">How to tune catalog usage</a></li>
3189 <li><a href="#validate">How to debug catalog processing</a></li>
3190 <li><a href="#Declaring">How to create and maintain catalogs</a></li>
3191 <li><a href="#implemento">The implementor corner quick review of the
3192 API</a></li>
3193 <li><a href="#Other">Other resources</a></li>
3194</ol>
3195
3196<h3><a name="General2">General overview</a></h3>
3197
3198<p>What is a catalog? Basically it's a lookup mechanism used when an entity
3199(a file or a remote resource) references another entity. The catalog lookup
3200is inserted between the moment the reference is recognized by the software
3201(XML parser, stylesheet processing, or even images referenced for inclusion
3202in a rendering) and the time where loading that resource is actually
3203started.</p>
3204
3205<p>It is basically used for 3 things:</p>
3206<ul>
3207 <li>mapping from "logical" names, the public identifiers and a more
3208 concrete name usable for download (and URI). For example it can associate
3209 the logical name
3210 <p>"-//OASIS//DTD DocBook XML V4.1.2//EN"</p>
3211 <p>of the DocBook 4.1.2 XML DTD with the actual URL where it can be
3212 downloaded</p>
3213 <p>http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd</p>
3214 </li>
3215 <li>remapping from a given URL to another one, like an HTTP indirection
3216 saying that
3217 <p>"http://www.oasis-open.org/committes/tr.xsl"</p>
3218 <p>should really be looked at</p>
3219 <p>"http://www.oasis-open.org/committes/entity/stylesheets/base/tr.xsl"</p>
3220 </li>
3221 <li>providing a local cache mechanism allowing to load the entities
3222 associated to public identifiers or remote resources, this is a really
3223 important feature for any significant deployment of XML or SGML since it
3224 allows to avoid the aleas and delays associated to fetching remote
3225 resources.</li>
3226</ul>
3227
3228<h3><a name="definition">The definitions</a></h3>
3229
3230<p>Libxml, as of 2.4.3 implements 2 kind of catalogs:</p>
3231<ul>
3232 <li>the older SGML catalogs, the official spec is SGML Open Technical
3233 Resolution TR9401:1997, but is better understood by reading <a
3234 href="http://www.jclark.com/sp/catalog.htm">the SP Catalog page</a> from
3235 James Clark. This is relatively old and not the preferred mode of
3236 operation of libxml.</li>
3237 <li><a href="http://www.oasis-open.org/committees/entity/spec.html">XML
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]3238 Catalogs</a> is far more flexible, more recent, uses an XML syntax and
3239 should scale quite better. This is the default option of libxml.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3240</ul>
3241
3242<p></p>
3243
3244<h3><a name="Simple">Using catalog</a></h3>
3245
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3246<p>In a normal environment libxml2 will by default check the presence of a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3247catalog in /etc/xml/catalog, and assuming it has been correctly populated,
3248the processing is completely transparent to the document user. To take a
3249concrete example, suppose you are authoring a DocBook document, this one
3250starts with the following DOCTYPE definition:</p>
3251<pre>&lt;?xml version='1.0'?&gt;
3252&lt;!DOCTYPE book PUBLIC "-//Norman Walsh//DTD DocBk XML V3.1.4//EN"
3253 "http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd"&gt;</pre>
3254
3255<p>When validating the document with libxml, the catalog will be
3256automatically consulted to lookup the public identifier "-//Norman Walsh//DTD
3257DocBk XML V3.1.4//EN" and the system identifier
3258"http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd", and if these entities have
3259been installed on your system and the catalogs actually point to them, libxml
3260will fetch them from the local disk.</p>
3261
3262<p style="font-size: 10pt"><strong>Note</strong>: Really don't use this
3263DOCTYPE example it's a really old version, but is fine as an example.</p>
3264
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3265<p>Libxml2 will check the catalog each time that it is requested to load an
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3266entity, this includes DTD, external parsed entities, stylesheets, etc ... If
3267your system is correctly configured all the authoring phase and processing
3268should use only local files, even if your document stays portable because it
3269uses the canonical public and system ID, referencing the remote document.</p>
3270
3271<h3><a name="Some">Some examples:</a></h3>
3272
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3273<p>Here is a couple of fragments from XML Catalogs used in libxml2 early
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3274regression tests in <code>test/catalogs</code> :</p>
3275<pre>&lt;?xml version="1.0"?&gt;
3276&lt;!DOCTYPE catalog PUBLIC
3277 "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
3278 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3279&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"&gt;
3280 &lt;public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
3281 uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/&gt;
3282...</pre>
3283
3284<p>This is the beginning of a catalog for DocBook 4.1.2, XML Catalogs are
3285written in XML, there is a specific namespace for catalog elements
3286"urn:oasis:names:tc:entity:xmlns:xml:catalog". The first entry in this
3287catalog is a <code>public</code> mapping it allows to associate a Public
3288Identifier with an URI.</p>
3289<pre>...
3290 &lt;rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/"
3291 rewritePrefix="file:///usr/share/xml/docbook/"/&gt;
3292...</pre>
3293
3294<p>A <code>rewriteSystem</code> is a very powerful instruction, it says that
3295any URI starting with a given prefix should be looked at another URI
3296constructed by replacing the prefix with an new one. In effect this acts like
3297a cache system for a full area of the Web. In practice it is extremely useful
3298with a file prefix if you have installed a copy of those resources on your
3299local system.</p>
3300<pre>...
3301&lt;delegatePublic publicIdStartString="-//OASIS//DTD XML Catalog //"
3302 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3303&lt;delegatePublic publicIdStartString="-//OASIS//ENTITIES DocBook XML"
3304 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3305&lt;delegatePublic publicIdStartString="-//OASIS//DTD DocBook XML"
3306 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3307&lt;delegateSystem systemIdStartString="http://www.oasis-open.org/docbook/"
3308 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3309&lt;delegateURI uriStartString="http://www.oasis-open.org/docbook/"
3310 catalog="file:///usr/share/xml/docbook.xml"/&gt;
3311...</pre>
3312
3313<p>Delegation is the core features which allows to build a tree of catalogs,
3314easier to maintain than a single catalog, based on Public Identifier, System
3315Identifier or URI prefixes it instructs the catalog software to look up
3316entries in another resource. This feature allow to build hierarchies of
3317catalogs, the set of entries presented should be sufficient to redirect the
3318resolution of all DocBook references to the specific catalog in
3319<code>/usr/share/xml/docbook.xml</code> this one in turn could delegate all
3320references for DocBook 4.2.1 to a specific catalog installed at the same time
3321as the DocBook resources on the local machine.</p>
3322
3323<h3><a name="reference">How to tune catalog usage:</a></h3>
3324
3325<p>The user can change the default catalog behaviour by redirecting queries
3326to its own set of catalogs, this can be done by setting the
3327<code>XML_CATALOG_FILES</code> environment variable to a list of catalogs, an
3328empty one should deactivate loading the default <code>/etc/xml/catalog</code>
3329default catalog</p>
3330
3331<h3><a name="validate">How to debug catalog processing:</a></h3>
3332
3333<p>Setting up the <code>XML_DEBUG_CATALOG</code> environment variable will
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3334make libxml2 output debugging informations for each catalog operations, for
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3335example:</p>
3336<pre>orchis:~/XML -&gt; xmllint --memory --noout test/ent2
3337warning: failed to load external entity "title.xml"
3338orchis:~/XML -&gt; export XML_DEBUG_CATALOG=
3339orchis:~/XML -&gt; xmllint --memory --noout test/ent2
3340Failed to parse catalog /etc/xml/catalog
3341Failed to parse catalog /etc/xml/catalog
3342warning: failed to load external entity "title.xml"
3343Catalogs cleanup
3344orchis:~/XML -&gt; </pre>
3345
3346<p>The test/ent2 references an entity, running the parser from memory makes
3347the base URI unavailable and the the "title.xml" entity cannot be loaded.
3348Setting up the debug environment variable allows to detect that an attempt is
3349made to load the <code>/etc/xml/catalog</code> but since it's not present the
3350resolution fails.</p>
3351
3352<p>But the most advanced way to debug XML catalog processing is to use the
3353<strong>xmlcatalog</strong> command shipped with libxml2, it allows to load
3354catalogs and make resolution queries to see what is going on. This is also
3355used for the regression tests:</p>
3356<pre>orchis:~/XML -&gt; ./xmlcatalog test/catalogs/docbook.xml \
3357 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3358http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3359orchis:~/XML -&gt; </pre>
3360
3361<p>For debugging what is going on, adding one -v flags increase the verbosity
3362level to indicate the processing done (adding a second flag also indicate
3363what elements are recognized at parsing):</p>
3364<pre>orchis:~/XML -&gt; ./xmlcatalog -v test/catalogs/docbook.xml \
3365 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3366Parsing catalog test/catalogs/docbook.xml's content
3367Found public match -//OASIS//DTD DocBook XML V4.1.2//EN
3368http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3369Catalogs cleanup
3370orchis:~/XML -&gt; </pre>
3371
3372<p>A shell interface is also available to debug and process multiple queries
3373(and for regression tests):</p>
3374<pre>orchis:~/XML -&gt; ./xmlcatalog -shell test/catalogs/docbook.xml \
3375 "-//OASIS//DTD DocBook XML V4.1.2//EN"
3376&gt; help
3377Commands available:
3378public PublicID: make a PUBLIC identifier lookup
3379system SystemID: make a SYSTEM identifier lookup
3380resolve PublicID SystemID: do a full resolver lookup
3381add 'type' 'orig' 'replace' : add an entry
3382del 'values' : remove values
3383dump: print the current catalog state
3384debug: increase the verbosity level
3385quiet: decrease the verbosity level
3386exit: quit the shell
3387&gt; public "-//OASIS//DTD DocBook XML V4.1.2//EN"
3388http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
3389&gt; quit
3390orchis:~/XML -&gt; </pre>
3391
3392<p>This should be sufficient for most debugging purpose, this was actually
3393used heavily to debug the XML Catalog implementation itself.</p>
3394
3395<h3><a name="Declaring">How to create and maintain</a> catalogs:</h3>
3396
3397<p>Basically XML Catalogs are XML files, you can either use XML tools to
3398manage them or use <strong>xmlcatalog</strong> for this. The basic step is
3399to create a catalog the -create option provide this facility:</p>
3400<pre>orchis:~/XML -&gt; ./xmlcatalog --create tst.xml
3401&lt;?xml version="1.0"?&gt;
3402&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
3403 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3404&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/&gt;
3405orchis:~/XML -&gt; </pre>
3406
3407<p>By default xmlcatalog does not overwrite the original catalog and save the
3408result on the standard output, this can be overridden using the -noout
3409option. The <code>-add</code> command allows to add entries in the
3410catalog:</p>
3411<pre>orchis:~/XML -&gt; ./xmlcatalog --noout --create --add "public" \
3412 "-//OASIS//DTD DocBook XML V4.1.2//EN" \
3413 http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd tst.xml
3414orchis:~/XML -&gt; cat tst.xml
3415&lt;?xml version="1.0"?&gt;
3416&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" \
3417 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3418&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"&gt;
3419&lt;public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
3420 uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/&gt;
3421&lt;/catalog&gt;
3422orchis:~/XML -&gt; </pre>
3423
3424<p>The <code>-add</code> option will always take 3 parameters even if some of
3425the XML Catalog constructs (like nextCatalog) will have only a single
3426argument, just pass a third empty string, it will be ignored.</p>
3427
3428<p>Similarly the <code>-del</code> option remove matching entries from the
3429catalog:</p>
3430<pre>orchis:~/XML -&gt; ./xmlcatalog --del \
3431 "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" tst.xml
3432&lt;?xml version="1.0"?&gt;
3433&lt;!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
3434 "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"&gt;
3435&lt;catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/&gt;
3436orchis:~/XML -&gt; </pre>
3437
3438<p>The catalog is now empty. Note that the matching of <code>-del</code> is
3439exact and would have worked in a similar fashion with the Public ID
3440string.</p>
3441
3442<p>This is rudimentary but should be sufficient to manage a not too complex
3443catalog tree of resources.</p>
3444
3445<h3><a name="implemento">The implementor corner quick review of the
3446API:</a></h3>
3447
3448<p>First, and like for every other module of libxml, there is an
3449automatically generated <a href="html/libxml-catalog.html">API page for
3450catalog support</a>.</p>
3451
3452<p>The header for the catalog interfaces should be included as:</p>
3453<pre>#include &lt;libxml/catalog.h&gt;</pre>
3454
3455<p>The API is voluntarily kept very simple. First it is not obvious that
3456applications really need access to it since it is the default behaviour of
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]3457libxml2 (Note: it is possible to completely override libxml2 default catalog
3458by using <a href="html/libxml-parser.html">xmlSetExternalEntityLoader</a> to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3459plug an application specific resolver).</p>
3460
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3461<p>Basically libxml2 support 2 catalog lists:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3462<ul>
3463 <li>the default one, global shared by all the application</li>
3464 <li>a per-document catalog, this one is built if the document uses the
3465 <code>oasis-xml-catalog</code> PIs to specify its own catalog list, it is
3466 associated to the parser context and destroyed when the parsing context
3467 is destroyed.</li>
3468</ul>
3469
3470<p>the document one will be used first if it exists.</p>
3471
3472<h4>Initialization routines:</h4>
3473
3474<p>xmlInitializeCatalog(), xmlLoadCatalog() and xmlLoadCatalogs() should be
3475used at startup to initialize the catalog, if the catalog should be
3476initialized with specific values xmlLoadCatalog() or xmlLoadCatalogs()
3477should be called before xmlInitializeCatalog() which would otherwise do a
3478default initialization first.</p>
3479
3480<p>The xmlCatalogAddLocal() call is used by the parser to grow the document
3481own catalog list if needed.</p>
3482
3483<h4>Preferences setup:</h4>
3484
3485<p>The XML Catalog spec requires the possibility to select default
3486preferences between public and system delegation,
3487xmlCatalogSetDefaultPrefer() allows this, xmlCatalogSetDefaults() and
3488xmlCatalogGetDefaults() allow to control if XML Catalogs resolution should
3489be forbidden, allowed for global catalog, for document catalog or both, the
3490default is to allow both.</p>
3491
3492<p>And of course xmlCatalogSetDebug() allows to generate debug messages
3493(through the xmlGenericError() mechanism).</p>
3494
3495<h4>Querying routines:</h4>
3496
3497<p>xmlCatalogResolve(), xmlCatalogResolveSystem(), xmlCatalogResolvePublic()
3498and xmlCatalogResolveURI() are relatively explicit if you read the XML
3499Catalog specification they correspond to section 7 algorithms, they should
3500also work if you have loaded an SGML catalog with a simplified semantic.</p>
3501
3502<p>xmlCatalogLocalResolve() and xmlCatalogLocalResolveURI() are the same but
3503operate on the document catalog list</p>
3504
3505<h4>Cleanup and Miscellaneous:</h4>
3506
3507<p>xmlCatalogCleanup() free-up the global catalog, xmlCatalogFreeLocal() is
3508the per-document equivalent.</p>
3509
3510<p>xmlCatalogAdd() and xmlCatalogRemove() are used to dynamically modify the
3511first catalog in the global list, and xmlCatalogDump() allows to dump a
3512catalog state, those routines are primarily designed for xmlcatalog, I'm not
3513sure that exposing more complex interfaces (like navigation ones) would be
3514really useful.</p>
3515
3516<p>The xmlParseCatalogFile() is a function used to load XML Catalog files,
3517it's similar as xmlParseFile() except it bypass all catalog lookups, it's
3518provided because this functionality may be useful for client tools.</p>
3519
3520<h4>threaded environments:</h4>
3521
3522<p>Since the catalog tree is built progressively, some care has been taken to
3523try to avoid troubles in multithreaded environments. The code is now thread
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3524safe assuming that the libxml2 library has been compiled with threads
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3525support.</p>
3526
3527<p></p>
3528
3529<h3><a name="Other">Other resources</a></h3>
3530
3531<p>The XML Catalog specification is relatively recent so there isn't much
3532literature to point at:</p>
3533<ul>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3534 <li>You can find a good rant from Norm Walsh about <a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3535 href="http://www.arbortext.com/Think_Tank/XML_Resources/Issue_Three/issue_three.html">the
3536 need for catalogs</a>, it provides a lot of context informations even if
Daniel Veillard93d3a472002-04-26 14:04:55 +0000[diff] [blame]3537 I don't agree with everything presented. Norm also wrote a more recent
3538 article <a
3539 href="http://wwws.sun.com/software/xml/developers/resolver/article/">XML
3540 entities and URI resolvers</a> describing them.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3541 <li>An <a href="http://home.ccil.org/~cowan/XML/XCatalog.html">old XML
3542 catalog proposal</a> from John Cowan</li>
3543 <li>The <a href="http://www.rddl.org/">Resource Directory Description
3544 Language</a> (RDDL) another catalog system but more oriented toward
3545 providing metadata for XML namespaces.</li>
3546 <li>the page from the OASIS Technical <a
3547 href="http://www.oasis-open.org/committees/entity/">Committee on Entity
3548 Resolution</a> who maintains XML Catalog, you will find pointers to the
3549 specification update, some background and pointers to others tools
3550 providing XML Catalog support</li>
Daniel Veillard35e937a2002-01-19 22:21:54 +0000[diff] [blame]3551 <li>Here is a <a href="buildDocBookCatalog">shell script</a> to generate
3552 XML Catalogs for DocBook 4.1.2 . If it can write to the /etc/xml/
3553 directory, it will set-up /etc/xml/catalog and /etc/xml/docbook based on
3554 the resources found on the system. Otherwise it will just create
3555 ~/xmlcatalog and ~/dbkxmlcatalog and doing:
Daniel Veillard8594de92003-04-25 10:08:44 +0000[diff] [blame]3556 <p><code>export XML_CATALOG_FILES=$HOME/xmlcatalog</code></p>
Daniel Veillard35e937a2002-01-19 22:21:54 +0000[diff] [blame]3557 <p>should allow to process DocBook documentations without requiring
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3558 network accesses for the DTD or stylesheets</p>
Daniel Veillard35e937a2002-01-19 22:21:54 +0000[diff] [blame]3559 </li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3560 <li>I have uploaded <a href="ftp://xmlsoft.org/test/dbk412catalog.tar.gz">a
Daniel Veillard35e937a2002-01-19 22:21:54 +0000[diff] [blame]3561 small tarball</a> containing XML Catalogs for DocBook 4.1.2 which seems
3562 to work fine for me too</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3563 <li>The <a href="http://www.xmlsoft.org/xmlcatalog_man.html">xmlcatalog
3564 manual page</a></li>
3565</ul>
3566
3567<p>If you have suggestions for corrections or additions, simply contact
3568me:</p>
3569
3570<h2><a name="library">The parser interfaces</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3571
3572<p>This section is directly intended to help programmers getting bootstrapped
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3573using the XML tollkit from the C language. It is not intended to be
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]3574extensive. I hope the automatically generated documents will provide the
3575completeness required, but as a separate set of documents. The interfaces of
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]3576the XML parser are by principle low level, Those interested in a higher level
3577API should <a href="#DOM">look at DOM</a>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]3578
Daniel Veillard9cb5ff42001-01-29 08:22:21 +0000[diff] [blame]3579<p>The <a href="html/libxml-parser.html">parser interfaces for XML</a> are
3580separated from the <a href="html/libxml-htmlparser.html">HTML parser
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3581interfaces</a>. Let's have a look at how the XML parser can be called:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3582
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3583<h3><a name="Invoking">Invoking the parser : the pull method</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3584
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3585<p>Usually, the first thing to do is to read an XML input. The parser accepts
3586documents either from in-memory strings or from files. The functions are
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3587defined in "parser.h":</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]3588<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3589 <dt><code>xmlDocPtr xmlParseMemory(char *buffer, int size);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3590 <dd><p>Parse a null-terminated string containing the document.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3591 </dd>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]3592</dl>
3593<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3594 <dt><code>xmlDocPtr xmlParseFile(const char *filename);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3595 <dd><p>Parse an XML document contained in a (possibly compressed)
3596 file.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3597 </dd>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]3598</dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3599
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3600<p>The parser returns a pointer to the document structure (or NULL in case of
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]3601failure).</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3602
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3603<h3 id="Invoking1">Invoking the parser: the push method</h3>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3604
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]3605<p>In order for the application to keep the control when the document is
Daniel Veillard560c2a42003-07-06 21:13:49 +0000[diff] [blame]3606being fetched (which is common for GUI based programs) libxml2 provides a
3607push interface, too, as of version 1.8.3. Here are the interface
3608functions:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3609<pre>xmlParserCtxtPtr xmlCreatePushParserCtxt(xmlSAXHandlerPtr sax,
3610 void *user_data,
3611 const char *chunk,
3612 int size,
3613 const char *filename);
3614int xmlParseChunk (xmlParserCtxtPtr ctxt,
3615 const char *chunk,
3616 int size,
3617 int terminate);</pre>
3618
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3619<p>and here is a simple example showing how to use the interface:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3620<pre> FILE *f;
3621
3622 f = fopen(filename, "r");
3623 if (f != NULL) {
3624 int res, size = 1024;
3625 char chars[1024];
3626 xmlParserCtxtPtr ctxt;
3627
3628 res = fread(chars, 1, 4, f);
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3629 if (res &gt; 0) {
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3630 ctxt = xmlCreatePushParserCtxt(NULL, NULL,
3631 chars, res, filename);
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3632 while ((res = fread(chars, 1, size, f)) &gt; 0) {
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3633 xmlParseChunk(ctxt, chars, res, 0);
3634 }
3635 xmlParseChunk(ctxt, chars, 0, 1);
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3636 doc = ctxt-&gt;myDoc;
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3637 xmlFreeParserCtxt(ctxt);
3638 }
3639 }</pre>
3640
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3641<p>The HTML parser embedded into libxml2 also has a push interface; the
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]3642functions are just prefixed by "html" rather than "xml".</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3643
3644<h3 id="Invoking2">Invoking the parser: the SAX interface</h3>
3645
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]3646<p>The tree-building interface makes the parser memory-hungry, first loading
3647the document in memory and then building the tree itself. Reading a document
3648without building the tree is possible using the SAX interfaces (see SAX.h and
3649<a href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">James
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3650Henstridge's documentation</a>). Note also that the push interface can be
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3651limited to SAX: just use the two first arguments of
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3652<code>xmlCreatePushParserCtxt()</code>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]3653
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]3654<h3><a name="Building">Building a tree from scratch</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3655
3656<p>The other way to get an XML tree in memory is by building it. Basically
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3657there is a set of functions dedicated to building new elements. (These are
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]3658also described in &lt;libxml/tree.h&gt;.) For example, here is a piece of
3659code that produces the XML document used in the previous examples:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3660<pre> #include &lt;libxml/tree.h&gt;
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]3661 xmlDocPtr doc;
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3662 xmlNodePtr tree, subtree;
3663
3664 doc = xmlNewDoc("1.0");
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3665 doc-&gt;children = xmlNewDocNode(doc, NULL, "EXAMPLE", NULL);
3666 xmlSetProp(doc-&gt;children, "prop1", "gnome is great");
3667 xmlSetProp(doc-&gt;children, "prop2", "&amp; linux too");
3668 tree = xmlNewChild(doc-&gt;children, NULL, "head", NULL);
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3669 subtree = xmlNewChild(tree, NULL, "title", "Welcome to Gnome");
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3670 tree = xmlNewChild(doc-&gt;children, NULL, "chapter", NULL);
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3671 subtree = xmlNewChild(tree, NULL, "title", "The Linux adventure");
3672 subtree = xmlNewChild(tree, NULL, "p", "bla bla bla ...");
3673 subtree = xmlNewChild(tree, NULL, "image", NULL);
3674 xmlSetProp(subtree, "href", "linus.gif");</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3675
3676<p>Not really rocket science ...</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3677
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]3678<h3><a name="Traversing">Traversing the tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3679
Daniel Veillard9cb5ff42001-01-29 08:22:21 +0000[diff] [blame]3680<p>Basically by <a href="html/libxml-tree.html">including "tree.h"</a> your
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]3681code has access to the internal structure of all the elements of the tree.
3682The names should be somewhat simple like <strong>parent</strong>,
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]3683<strong>children</strong>, <strong>next</strong>, <strong>prev</strong>,
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3684<strong>properties</strong>, etc... For example, still with the previous
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]3685example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3686<pre><code>doc-&gt;children-&gt;children-&gt;children</code></pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3687
3688<p>points to the title element,</p>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3689<pre>doc-&gt;children-&gt;children-&gt;next-&gt;children-&gt;children</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3690
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3691<p>points to the text node containing the chapter title "The Linux
3692adventure".</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]3693
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]3694<p><strong>NOTE</strong>: XML allows <em>PI</em>s and <em>comments</em> to be
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3695present before the document root, so <code>doc-&gt;children</code> may point
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3696to an element which is not the document Root Element; a function
Daniel Veillard5cb5ab81999-12-21 15:35:29 +0000[diff] [blame]3697<code>xmlDocGetRootElement()</code> was added for this purpose.</p>
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]3698
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]3699<h3><a name="Modifying">Modifying the tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3700
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3701<p>Functions are provided for reading and writing the document content. Here
Daniel Veillard9cb5ff42001-01-29 08:22:21 +0000[diff] [blame]3702is an excerpt from the <a href="html/libxml-tree.html">tree API</a>:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3703<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]3704 <dt><code>xmlAttrPtr xmlSetProp(xmlNodePtr node, const xmlChar *name, const
3705 xmlChar *value);</code></dt>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]3706 <dd><p>This sets (or changes) an attribute carried by an ELEMENT node.
3707 The value can be NULL.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3708 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3709</dl>
3710<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]3711 <dt><code>const xmlChar *xmlGetProp(xmlNodePtr node, const xmlChar
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3712 *name);</code></dt>
Daniel Veillardc92c3042000-09-29 02:42:04 +0000[diff] [blame]3713 <dd><p>This function returns a pointer to new copy of the property
3714 content. Note that the user must deallocate the result.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3715 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3716</dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3717
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]3718<p>Two functions are provided for reading and writing the text associated
3719with elements:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3720<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]3721 <dt><code>xmlNodePtr xmlStringGetNodeList(xmlDocPtr doc, const xmlChar
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3722 *value);</code></dt>
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]3723 <dd><p>This function takes an "external" string and converts it to one
3724 text node or possibly to a list of entity and text nodes. All
3725 non-predefined entity references like &amp;Gnome; will be stored
3726 internally as entity nodes, hence the result of the function may not be
3727 a single node.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3728 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3729</dl>
3730<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]3731 <dt><code>xmlChar *xmlNodeListGetString(xmlDocPtr doc, xmlNodePtr list, int
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3732 inLine);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3733 <dd><p>This function is the inverse of
3734 <code>xmlStringGetNodeList()</code>. It generates a new string
3735 containing the content of the text and entity nodes. Note the extra
3736 argument inLine. If this argument is set to 1, the function will expand
3737 entity references. For example, instead of returning the &amp;Gnome;
3738 XML encoding in the string, it will substitute it with its value (say,
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3739 "GNU Network Object Model Environment").</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3740 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3741</dl>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]3742
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]3743<h3><a name="Saving">Saving a tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3744
3745<p>Basically 3 options are possible:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3746<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]3747 <dt><code>void xmlDocDumpMemory(xmlDocPtr cur, xmlChar**mem, int
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3748 *size);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3749 <dd><p>Returns a buffer into which the document has been saved.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3750 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3751</dl>
3752<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3753 <dt><code>extern void xmlDocDump(FILE *f, xmlDocPtr doc);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3754 <dd><p>Dumps a document to an open file descriptor.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3755 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3756</dl>
3757<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3758 <dt><code>int xmlSaveFile(const char *filename, xmlDocPtr cur);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3759 <dd><p>Saves the document to a file. In this case, the compression
3760 interface is triggered if it has been turned on.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3761 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3762</dl>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]3763
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]3764<h3><a name="Compressio">Compression</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3765
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3766<p>The library transparently handles compression when doing file-based
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3767accesses. The level of compression on saves can be turned on either globally
3768or individually for one file:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3769<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3770 <dt><code>int xmlGetDocCompressMode (xmlDocPtr doc);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3771 <dd><p>Gets the document compression ratio (0-9).</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3772 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3773</dl>
3774<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3775 <dt><code>void xmlSetDocCompressMode (xmlDocPtr doc, int mode);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3776 <dd><p>Sets the document compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3777 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3778</dl>
3779<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3780 <dt><code>int xmlGetCompressMode(void);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3781 <dd><p>Gets the default compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3782 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3783</dl>
3784<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3785 <dt><code>void xmlSetCompressMode(int mode);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3786 <dd><p>Sets the default compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]3787 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]3788</dl>
3789
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]3790<h2><a name="Entities">Entities or no entities</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3791
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3792<p>Entities in principle are similar to simple C macros. An entity defines an
3793abbreviation for a given string that you can reuse many times throughout the
3794content of your document. Entities are especially useful when a given string
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3795may occur frequently within a document, or to confine the change needed to a
3796document to a restricted area in the internal subset of the document (at the
3797beginning). Example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3798<pre>1 &lt;?xml version="1.0"?&gt;
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]37992 &lt;!DOCTYPE EXAMPLE SYSTEM "example.dtd" [
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]38003 &lt;!ENTITY xml "Extensible Markup Language"&gt;
38014 ]&gt;
38025 &lt;EXAMPLE&gt;
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]38036 &amp;xml;
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]38047 &lt;/EXAMPLE&gt;</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3805
3806<p>Line 3 declares the xml entity. Line 6 uses the xml entity, by prefixing
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3807its name with '&amp;' and following it by ';' without any spaces added. There
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3808are 5 predefined entities in libxml2 allowing you to escape characters with
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3809predefined meaning in some parts of the xml document content:
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3810<strong>&amp;lt;</strong> for the character '&lt;', <strong>&amp;gt;</strong>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3811for the character '&gt;', <strong>&amp;apos;</strong> for the character ''',
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3812<strong>&amp;quot;</strong> for the character '"', and
3813<strong>&amp;amp;</strong> for the character '&amp;'.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3814
3815<p>One of the problems related to entities is that you may want the parser to
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3816substitute an entity's content so that you can see the replacement text in
3817your application. Or you may prefer to keep entity references as such in the
3818content to be able to save the document back without losing this usually
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]3819precious information (if the user went through the pain of explicitly
3820defining entities, he may have a a rather negative attitude if you blindly
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3821substitute them as saving time). The <a
Daniel Veillard5373ea12003-07-24 13:09:13 +0000[diff] [blame]3822href="html/libxml-parser.html#xmlSubstituteEntitiesDefault">xmlSubstituteEntitiesDefault()</a>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3823function allows you to check and change the behaviour, which is to not
3824substitute entities by default.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3825
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3826<p>Here is the DOM tree built by libxml2 for the previous document in the
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3827default case:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3828<pre>/gnome/src/gnome-xml -&gt; ./xmllint --debug test/ent1
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3829DOCUMENT
3830version=1.0
3831 ELEMENT EXAMPLE
3832 TEXT
3833 content=
3834 ENTITY_REF
3835 INTERNAL_GENERAL_ENTITY xml
3836 content=Extensible Markup Language
3837 TEXT
3838 content=</pre>
3839
3840<p>And here is the result when substituting entities:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3841<pre>/gnome/src/gnome-xml -&gt; ./tester --debug --noent test/ent1
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3842DOCUMENT
3843version=1.0
3844 ELEMENT EXAMPLE
3845 TEXT
3846 content= Extensible Markup Language</pre>
3847
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3848<p>So, entities or no entities? Basically, it depends on your use case. I
3849suggest that you keep the non-substituting default behaviour and avoid using
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3850entities in your XML document or data if you are not willing to handle the
3851entity references elements in the DOM tree.</p>
3852
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3853<p>Note that at save time libxml2 enforces the conversion of the predefined
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3854entities where necessary to prevent well-formedness problems, and will also
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3855transparently replace those with chars (i.e. it will not generate entity
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3856reference elements in the DOM tree or call the reference() SAX callback when
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3857finding them in the input).</p>
3858
Daniel Veillard7b9c4b72000-08-25 16:26:50 +0000[diff] [blame]3859<p><span style="background-color: #FF0000">WARNING</span>: handling entities
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3860on top of the libxml2 SAX interface is difficult!!! If you plan to use
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3861non-predefined entities in your documents, then the learning curve to handle
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3862then using the SAX API may be long. If you plan to use complex documents, I
Daniel Veillard7b9c4b72000-08-25 16:26:50 +0000[diff] [blame]3863strongly suggest you consider using the DOM interface instead and let libxml
Daniel Veillard8c6d6af2000-08-25 17:14:13 +0000[diff] [blame]3864deal with the complexity rather than trying to do it yourself.</p>
Daniel Veillard7b9c4b72000-08-25 16:26:50 +0000[diff] [blame]3865
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]3866<h2><a name="Namespaces">Namespaces</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3867
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3868<p>The libxml2 library implements <a
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]3869href="http://www.w3.org/TR/REC-xml-names/">XML namespaces</a> support by
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3870recognizing namespace constructs in the input, and does namespace lookup
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]3871automatically when building the DOM tree. A namespace declaration is
3872associated with an in-memory structure and all elements or attributes within
3873that namespace point to it. Hence testing the namespace is a simple and fast
3874equality operation at the user level.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3875
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3876<p>I suggest that people using libxml2 use a namespace, and declare it in the
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3877root element of their document as the default namespace. Then they don't need
3878to use the prefix in the content but we will have a basis for future semantic
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3879refinement and merging of data from different sources. This doesn't increase
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]3880the size of the XML output significantly, but significantly increases its
3881value in the long-term. Example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3882<pre>&lt;mydoc xmlns="http://mydoc.example.org/schemas/"&gt;
3883 &lt;elem1&gt;...&lt;/elem1&gt;
3884 &lt;elem2&gt;...&lt;/elem2&gt;
3885&lt;/mydoc&gt;</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3886
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]3887<p>The namespace value has to be an absolute URL, but the URL doesn't have to
3888point to any existing resource on the Web. It will bind all the element and
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]3889attributes with that URL. I suggest to use an URL within a domain you
3890control, and that the URL should contain some kind of version information if
3891possible. For example, <code>"http://www.gnome.org/gnumeric/1.0/"</code> is a
3892good namespace scheme.</p>
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]3893
3894<p>Then when you load a file, make sure that a namespace carrying the
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]3895version-independent prefix is installed on the root element of your document,
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3896and if the version information don't match something you know, warn the user
3897and be liberal in what you accept as the input. Also do *not* try to base
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3898namespace checking on the prefix value. &lt;foo:text&gt; may be exactly the
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3899same as &lt;bar:text&gt; in another document. What really matters is the URI
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]3900associated with the element or the attribute, not the prefix string (which is
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3901just a shortcut for the full URI). In libxml, element and attributes have an
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]3902<code>ns</code> field pointing to an xmlNs structure detailing the namespace
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3903prefix and its URI.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3904
3905<p>@@Interfaces@@</p>
Daniel Veillard3e35f8e2003-10-21 00:05:38 +0000[diff] [blame]3906<pre>xmlNodePtr node;
Daniel Veillardfc8dc352003-10-18 09:07:46 +0000[diff] [blame]3907if(!strncmp(node-&gt;name,"mytag",5)
3908 &amp;&amp; node-&gt;ns
3909 &amp;&amp; !strcmp(node-&gt;ns-&gt;href,"http://www.mysite.com/myns/1.0")) {
3910 ...
Daniel Veillard3e35f8e2003-10-21 00:05:38 +0000[diff] [blame]3911}</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3912
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3913<p>Usually people object to using namespaces together with validity checking.
3914I will try to make sure that using namespaces won't break validity checking,
3915so even if you plan to use or currently are using validation I strongly
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]3916suggest adding namespaces to your document. A default namespace scheme
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3917<code>xmlns="http://...."</code> should not break validity even on less
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]3918flexible parsers. Using namespaces to mix and differentiate content coming
Daniel Veillard3e35f8e2003-10-21 00:05:38 +0000[diff] [blame]3919from multiple DTDs will certainly break current validation schemes. To check
3920such documents one needs to use schema-validation, which is supported in
3921libxml2 as well. See <a href="http://www.relaxng.org/">relagx-ng</a> and <a
3922href="http://www.w3c.org/XML/Schema">w3c-schema</a>.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3923
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3924<h2><a name="Upgrading">Upgrading 1.x code</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3925
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3926<p>Incompatible changes:</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3927
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]3928<p>Version 2 of libxml2 is the first version introducing serious backward
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3929incompatible changes. The main goals were:</p>
3930<ul>
3931 <li>a general cleanup. A number of mistakes inherited from the very early
3932 versions couldn't be changed due to compatibility constraints. Example
3933 the "childs" element in the nodes.</li>
3934 <li>Uniformization of the various nodes, at least for their header and link
3935 parts (doc, parent, children, prev, next), the goal is a simpler
3936 programming model and simplifying the task of the DOM implementors.</li>
3937 <li>better conformances to the XML specification, for example version 1.x
3938 had an heuristic to try to detect ignorable white spaces. As a result the
3939 SAX event generated were ignorableWhitespace() while the spec requires
3940 character() in that case. This also mean that a number of DOM node
3941 containing blank text may populate the DOM tree which were not present
3942 before.</li>
3943</ul>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3944
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3945<h3>How to fix libxml-1.x code:</h3>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]3946
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3947<p>So client code of libxml designed to run with version 1.x may have to be
3948changed to compile against version 2.x of libxml. Here is a list of changes
3949that I have collected, they may not be sufficient, so in case you find other
Daniel Veillardfc8dc352003-10-18 09:07:46 +0000[diff] [blame]3950change which are required, <a href="mailto:Daniel.Veillard@w3.org">drop me a
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3951mail</a>:</p>
3952<ol>
3953 <li>The package name have changed from libxml to libxml2, the library name
3954 is now -lxml2 . There is a new xml2-config script which should be used to
3955 select the right parameters libxml2</li>
3956 <li>Node <strong>childs</strong> field has been renamed
3957 <strong>children</strong> so s/childs/children/g should be applied
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3958 (probability of having "childs" anywhere else is close to 0+</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3959 <li>The document don't have anymore a <strong>root</strong> element it has
3960 been replaced by <strong>children</strong> and usually you will get a
3961 list of element here. For example a Dtd element for the internal subset
3962 and it's declaration may be found in that list, as well as processing
3963 instructions or comments found before or after the document root element.
3964 Use <strong>xmlDocGetRootElement(doc)</strong> to get the root element of
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3965 a document. Alternatively if you are sure to not reference DTDs nor have
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3966 PIs or comments before or after the root element
3967 s/-&gt;root/-&gt;children/g will probably do it.</li>
3968 <li>The white space issue, this one is more complex, unless special case of
3969 validating parsing, the line breaks and spaces usually used for indenting
3970 and formatting the document content becomes significant. So they are
3971 reported by SAX and if your using the DOM tree, corresponding nodes are
3972 generated. Too approach can be taken:
3973 <ol>
3974 <li>lazy one, use the compatibility call
3975 <strong>xmlKeepBlanksDefault(0)</strong> but be aware that you are
3976 relying on a special (and possibly broken) set of heuristics of
3977 libxml to detect ignorable blanks. Don't complain if it breaks or
3978 make your application not 100% clean w.r.t. to it's input.</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3979 <li>the Right Way: change you code to accept possibly insignificant
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3980 blanks characters, or have your tree populated with weird blank text
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3981 nodes. You can spot them using the commodity function
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3982 <strong>xmlIsBlankNode(node)</strong> returning 1 for such blank
3983 nodes.</li>
3984 </ol>
3985 <p>Note also that with the new default the output functions don't add any
3986 extra indentation when saving a tree in order to be able to round trip
3987 (read and save) without inflating the document with extra formatting
3988 chars.</p>
3989 </li>
3990 <li>The include path has changed to $prefix/libxml/ and the includes
3991 themselves uses this new prefix in includes instructions... If you are
3992 using (as expected) the
3993 <pre>xml2-config --cflags</pre>
3994 <p>output to generate you compile commands this will probably work out of
3995 the box</p>
3996 </li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]3997 <li>xmlDetectCharEncoding takes an extra argument indicating the length in
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]3998 byte of the head of the document available for character detection.</li>
3999</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]4000
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4001<h3>Ensuring both libxml-1.x and libxml-2.x compatibility</h3>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]4002
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4003<p>Two new version of libxml (1.8.11) and libxml2 (2.3.4) have been released
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]4004to allow smooth upgrade of existing libxml v1code while retaining
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4005compatibility. They offers the following:</p>
4006<ol>
4007 <li>similar include naming, one should use
4008 <strong>#include&lt;libxml/...&gt;</strong> in both cases.</li>
4009 <li>similar identifiers defined via macros for the child and root fields:
4010 respectively <strong>xmlChildrenNode</strong> and
4011 <strong>xmlRootNode</strong></li>
4012 <li>a new macro <strong>LIBXML_TEST_VERSION</strong> which should be
4013 inserted once in the client code</li>
4014</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]4015
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4016<p>So the roadmap to upgrade your existing libxml applications is the
4017following:</p>
4018<ol>
4019 <li>install the libxml-1.8.8 (and libxml-devel-1.8.8) packages</li>
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]4020 <li>find all occurrences where the xmlDoc <strong>root</strong> field is
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4021 used and change it to <strong>xmlRootNode</strong></li>
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]4022 <li>similarly find all occurrences where the xmlNode
4023 <strong>childs</strong> field is used and change it to
4024 <strong>xmlChildrenNode</strong></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4025 <li>add a <strong>LIBXML_TEST_VERSION</strong> macro somewhere in your
4026 <strong>main()</strong> or in the library init entry point</li>
4027 <li>Recompile, check compatibility, it should still work</li>
Daniel Veillardc0801af2002-05-28 16:28:42 +0000[diff] [blame]4028 <li>Change your configure script to look first for xml2-config and fall
4029 back using xml-config . Use the --cflags and --libs output of the command
4030 as the Include and Linking parameters needed to use libxml.</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4031 <li>install libxml2-2.3.x and libxml2-devel-2.3.x (libxml-1.8.y and
4032 libxml-devel-1.8.y can be kept simultaneously)</li>
4033 <li>remove your config.cache, relaunch your configuration mechanism, and
4034 recompile, if steps 2 and 3 were done right it should compile as-is</li>
4035 <li>Test that your application is still running correctly, if not this may
4036 be due to extra empty nodes due to formating spaces being kept in libxml2
4037 contrary to libxml1, in that case insert xmlKeepBlanksDefault(1) in your
4038 code before calling the parser (next to
4039 <strong>LIBXML_TEST_VERSION</strong> is a fine place).</li>
4040</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]4041
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4042<p>Following those steps should work. It worked for some of my own code.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]4043
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4044<p>Let me put some emphasis on the fact that there is far more changes from
4045libxml 1.x to 2.x than the ones you may have to patch for. The overall code
4046has been considerably cleaned up and the conformance to the XML specification
4047has been drastically improved too. Don't take those changes as an excuse to
4048not upgrade, it may cost a lot on the long term ...</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]4049
Daniel Veillard52dcab32001-10-30 12:51:17 +0000[diff] [blame]4050<h2><a name="Thread">Thread safety</a></h2>
4051
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]4052<p>Starting with 2.4.7, libxml2 makes provisions to ensure that concurrent
Daniel Veillard52dcab32001-10-30 12:51:17 +0000[diff] [blame]4053threads can safely work in parallel parsing different documents. There is
4054however a couple of things to do to ensure it:</p>
4055<ul>
4056 <li>configure the library accordingly using the --with-threads options</li>
4057 <li>call xmlInitParser() in the "main" thread before using any of the
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]4058 libxml2 API (except possibly selecting a different memory allocator)</li>
Daniel Veillard52dcab32001-10-30 12:51:17 +0000[diff] [blame]4059</ul>
4060
4061<p>Note that the thread safety cannot be ensured for multiple threads sharing
4062the same document, the locking must be done at the application level, libxml
4063exports a basic mutex and reentrant mutexes API in &lt;libxml/threads.h&gt;.
4064The parts of the library checked for thread safety are:</p>
4065<ul>
4066 <li>concurrent loading</li>
4067 <li>file access resolution</li>
4068 <li>catalog access</li>
4069 <li>catalog building</li>
4070 <li>entities lookup/accesses</li>
4071 <li>validation</li>
4072 <li>global variables per-thread override</li>
4073 <li>memory handling</li>
4074</ul>
4075
4076<p>XPath is supposed to be thread safe now, but this wasn't tested
4077seriously.</p>
4078
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]4079<h2><a name="DOM"></a><a name="Principles">DOM Principles</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4080
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]4081<p><a href="http://www.w3.org/DOM/">DOM</a> stands for the <em>Document
4082Object Model</em>; this is an API for accessing XML or HTML structured
4083documents. Native support for DOM in Gnome is on the way (module gnome-dom),
4084and will be based on gnome-xml. This will be a far cleaner interface to
4085manipulate XML files within Gnome since it won't expose the internal
4086structure.</p>
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4087
Daniel Veillard8a469172003-06-12 16:05:07 +0000[diff] [blame]4088<p>The current DOM implementation on top of libxml2 is the <a
Daniel Veillarda47fb3d2001-03-25 17:23:49 +0000[diff] [blame]4089href="http://cvs.gnome.org/lxr/source/gdome2/">gdome2 Gnome module</a>, this
4090is a full DOM interface, thanks to Paolo Casarini, check the <a
4091href="http://www.cs.unibo.it/~casarini/gdome2/">Gdome2 homepage</a> for more
4092informations.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]4093
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]4094<h2><a name="Example"></a><a name="real">A real example</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4095
4096<p>Here is a real size example, where the actual content of the application
4097data is not kept in the DOM tree but uses internal structures. It is based on
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4098a proposal to keep a database of jobs related to Gnome, with an XML based
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4099storage structure. Here is an <a href="gjobs.xml">XML encoded jobs
4100base</a>:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4101<pre>&lt;?xml version="1.0"?&gt;
4102&lt;gjob:Helping xmlns:gjob="http://www.gnome.org/some-location"&gt;
4103 &lt;gjob:Jobs&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4104
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4105 &lt;gjob:Job&gt;
4106 &lt;gjob:Project ID="3"/&gt;
4107 &lt;gjob:Application&gt;GBackup&lt;/gjob:Application&gt;
4108 &lt;gjob:Category&gt;Development&lt;/gjob:Category&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4109
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4110 &lt;gjob:Update&gt;
4111 &lt;gjob:Status&gt;Open&lt;/gjob:Status&gt;
4112 &lt;gjob:Modified&gt;Mon, 07 Jun 1999 20:27:45 -0400 MET DST&lt;/gjob:Modified&gt;
4113 &lt;gjob:Salary&gt;USD 0.00&lt;/gjob:Salary&gt;
4114 &lt;/gjob:Update&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4115
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4116 &lt;gjob:Developers&gt;
4117 &lt;gjob:Developer&gt;
4118 &lt;/gjob:Developer&gt;
4119 &lt;/gjob:Developers&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4120
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4121 &lt;gjob:Contact&gt;
4122 &lt;gjob:Person&gt;Nathan Clemons&lt;/gjob:Person&gt;
4123 &lt;gjob:Email&gt;nathan@windsofstorm.net&lt;/gjob:Email&gt;
4124 &lt;gjob:Company&gt;
4125 &lt;/gjob:Company&gt;
4126 &lt;gjob:Organisation&gt;
4127 &lt;/gjob:Organisation&gt;
4128 &lt;gjob:Webpage&gt;
4129 &lt;/gjob:Webpage&gt;
4130 &lt;gjob:Snailmail&gt;
4131 &lt;/gjob:Snailmail&gt;
4132 &lt;gjob:Phone&gt;
4133 &lt;/gjob:Phone&gt;
4134 &lt;/gjob:Contact&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4135
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4136 &lt;gjob:Requirements&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4137 The program should be released as free software, under the GPL.
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4138 &lt;/gjob:Requirements&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4139
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4140 &lt;gjob:Skills&gt;
4141 &lt;/gjob:Skills&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4142
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4143 &lt;gjob:Details&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4144 A GNOME based system that will allow a superuser to configure
4145 compressed and uncompressed files and/or file systems to be backed
4146 up with a supported media in the system. This should be able to
4147 perform via find commands generating a list of files that are passed
4148 to tar, dd, cpio, cp, gzip, etc., to be directed to the tape machine
4149 or via operations performed on the filesystem itself. Email
4150 notification and GUI status display very important.
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4151 &lt;/gjob:Details&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4152
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4153 &lt;/gjob:Job&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4154
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4155 &lt;/gjob:Jobs&gt;
4156&lt;/gjob:Helping&gt;</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4157
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]4158<p>While loading the XML file into an internal DOM tree is a matter of
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]4159calling only a couple of functions, browsing the tree to gather the data and
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]4160generate the internal structures is harder, and more error prone.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4161
4162<p>The suggested principle is to be tolerant with respect to the input
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]4163structure. For example, the ordering of the attributes is not significant,
4164the XML specification is clear about it. It's also usually a good idea not to
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]4165depend on the order of the children of a given node, unless it really makes
4166things harder. Here is some code to parse the information for a person:</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4167<pre>/*
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4168 * A person record
4169 */
4170typedef struct person {
4171 char *name;
4172 char *email;
4173 char *company;
4174 char *organisation;
4175 char *smail;
4176 char *webPage;
4177 char *phone;
4178} person, *personPtr;
4179
4180/*
4181 * And the code needed to parse it
4182 */
4183personPtr parsePerson(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
4184 personPtr ret = NULL;
4185
4186DEBUG("parsePerson\n");
4187 /*
4188 * allocate the struct
4189 */
4190 ret = (personPtr) malloc(sizeof(person));
4191 if (ret == NULL) {
4192 fprintf(stderr,"out of memory\n");
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4193 return(NULL);
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4194 }
4195 memset(ret, 0, sizeof(person));
4196
4197 /* We don't care what the top level element name is */
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4198 cur = cur-&gt;xmlChildrenNode;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4199 while (cur != NULL) {
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4200 if ((!strcmp(cur-&gt;name, "Person")) &amp;&amp; (cur-&gt;ns == ns))
4201 ret-&gt;name = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4202 if ((!strcmp(cur-&gt;name, "Email")) &amp;&amp; (cur-&gt;ns == ns))
4203 ret-&gt;email = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4204 cur = cur-&gt;next;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4205 }
4206
4207 return(ret);
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4208}</pre>
4209
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]4210<p>Here are a couple of things to notice:</p>
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4211<ul>
Daniel Veillard91e9d582001-02-26 07:31:12 +0000[diff] [blame]4212 <li>Usually a recursive parsing style is the more convenient one: XML data
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]4213 is by nature subject to repetitive constructs and usually exhibits highly
4214 structured patterns.</li>
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]4215 <li>The two arguments of type <em>xmlDocPtr</em> and <em>xmlNsPtr</em>,
4216 i.e. the pointer to the global XML document and the namespace reserved to
4217 the application. Document wide information are needed for example to
4218 decode entities and it's a good coding practice to define a namespace for
4219 your application set of data and test that the element and attributes
4220 you're analyzing actually pertains to your application space. This is
4221 done by a simple equality test (cur-&gt;ns == ns).</li>
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]4222 <li>To retrieve text and attributes value, you can use the function
4223 <em>xmlNodeListGetString</em> to gather all the text and entity reference
4224 nodes generated by the DOM output and produce an single text string.</li>
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4225</ul>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4226
4227<p>Here is another piece of code used to parse another level of the
4228structure:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4229<pre>#include &lt;libxml/tree.h&gt;
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]4230/*
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4231 * a Description for a Job
4232 */
4233typedef struct job {
4234 char *projectID;
4235 char *application;
4236 char *category;
4237 personPtr contact;
4238 int nbDevelopers;
4239 personPtr developers[100]; /* using dynamic alloc is left as an exercise */
4240} job, *jobPtr;
4241
4242/*
4243 * And the code needed to parse it
4244 */
4245jobPtr parseJob(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
4246 jobPtr ret = NULL;
4247
4248DEBUG("parseJob\n");
4249 /*
4250 * allocate the struct
4251 */
4252 ret = (jobPtr) malloc(sizeof(job));
4253 if (ret == NULL) {
4254 fprintf(stderr,"out of memory\n");
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4255 return(NULL);
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4256 }
4257 memset(ret, 0, sizeof(job));
4258
4259 /* We don't care what the top level element name is */
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4260 cur = cur-&gt;xmlChildrenNode;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4261 while (cur != NULL) {
4262
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4263 if ((!strcmp(cur-&gt;name, "Project")) &amp;&amp; (cur-&gt;ns == ns)) {
4264 ret-&gt;projectID = xmlGetProp(cur, "ID");
4265 if (ret-&gt;projectID == NULL) {
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4266 fprintf(stderr, "Project has no ID\n");
4267 }
4268 }
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]4269 if ((!strcmp(cur-&gt;name, "Application")) &amp;&amp; (cur-&gt;ns == ns))
4270 ret-&gt;application = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4271 if ((!strcmp(cur-&gt;name, "Category")) &amp;&amp; (cur-&gt;ns == ns))
4272 ret-&gt;category = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
4273 if ((!strcmp(cur-&gt;name, "Contact")) &amp;&amp; (cur-&gt;ns == ns))
4274 ret-&gt;contact = parsePerson(doc, ns, cur);
4275 cur = cur-&gt;next;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4276 }
4277
4278 return(ret);
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4279}</pre>
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]4280
Daniel Veillardec70e912001-02-26 20:10:45 +0000[diff] [blame]4281<p>Once you are used to it, writing this kind of code is quite simple, but
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]4282boring. Ultimately, it could be possible to write stubbers taking either C
Daniel Veillard3d6ae1c2001-08-15 13:12:39 +0000[diff] [blame]4283data structure definitions, a set of XML examples or an XML DTD and produce
4284the code needed to import and export the content between C data and XML
4285storage. This is left as an exercise to the reader :-)</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4286
Daniel Veillard6f0adb52000-07-03 11:41:26 +0000[diff] [blame]4287<p>Feel free to use <a href="example/gjobread.c">the code for the full C
4288parsing example</a> as a template, it is also available with Makefile in the
4289Gnome CVS base under gnome-xml/example</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]4290
Daniel Veillardc310d562000-06-23 18:32:15 +0000[diff] [blame]4291<h2><a name="Contributi">Contributions</a></h2>
4292<ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4293 <li>Bjorn Reese, William Brack and Thomas Broyer have provided a number of
4294 patches, Gary Pennington worked on the validation API, threading support
4295 and Solaris port.</li>
4296 <li>John Fleck helps maintaining the documentation and man pages.</li>
Daniel Veillard7b4b2f92003-01-06 13:11:20 +0000[diff] [blame]4297 <li><a href="mailto:igor@zlatkovic.com">Igor Zlatkovic</a> is now the
4298 maintainer of the Windows port, <a
4299 href="http://www.zlatkovic.com/projects/libxml/index.html">he provides
4300 binaries</a></li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]4301 <li><a href="mailto:Gary.Pennington@sun.com">Gary Pennington</a> provides
4302 <a href="http://garypennington.net/libxml2/">Solaris binaries</a></li>
Daniel Veillarde356c282001-03-10 12:32:04 +0000[diff] [blame]4303 <li><a
4304 href="http://mail.gnome.org/archives/xml/2001-March/msg00014.html">Matt
Daniel Veillard63d83142002-05-20 06:51:05 +0000[diff] [blame]4305 Sergeant</a> developed <a
4306 href="http://axkit.org/download/">XML::LibXSLT</a>, a Perl wrapper for
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]4307 libxml2/libxslt as part of the <a href="http://axkit.com/">AxKit XML
4308 application server</a></li>
4309 <li><a href="mailto:fnatter@gmx.net">Felix Natter</a> and <a
4310 href="mailto:geertk@ai.rug.nl">Geert Kloosterman</a> provide <a
Daniel Veillardca989762001-06-23 17:39:29 +0000[diff] [blame]4311 href="libxml-doc.el">an emacs module</a> to lookup libxml(2) functions
Daniel Veillard3f6f7f62000-06-30 17:58:25 +0000[diff] [blame]4312 documentation</li>
Daniel Veillardaf43f632002-03-08 15:05:20 +0000[diff] [blame]4313 <li><a href="mailto:sherwin@nlm.nih.gov">Ziying Sherwin</a> provided <a
4314 href="http://xmlsoft.org/messages/0488.html">man pages</a></li>
Daniel Veillard5168dbf2001-07-07 00:18:23 +0000[diff] [blame]4315 <li>there is a module for <a
4316 href="http://acs-misc.sourceforge.net/nsxml.html">libxml/libxslt support
4317 in OpenNSD/AOLServer</a></li>
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000[diff] [blame]4318 <li><a href="mailto:dkuhlman@cutter.rexx.com">Dave Kuhlman</a> provided the
4319 first version of libxml/libxslt <a
4320 href="http://www.rexx.com/~dkuhlman">wrappers for Python</a></li>
Daniel Veillard1aadc442001-11-28 13:10:32 +0000[diff] [blame]4321 <li>Petr Kozelka provides <a
4322 href="http://sourceforge.net/projects/libxml2-pas">Pascal units to glue
4323 libxml2</a> with Kylix and Delphi and other Pascal compilers</li>
Daniel Veillard2d347fa2002-03-17 10:34:11 +0000[diff] [blame]4324 <li><a href="mailto:aleksey@aleksey.com">Aleksey Sanin</a> implemented the
4325 <a href="http://www.w3.org/Signature/">XML Canonicalization and XML
4326 Digital Signature</a> <a
4327 href="http://www.aleksey.com/xmlsec/">implementations for libxml2</a></li>
Daniel Veillard17bed982003-02-24 20:11:43 +0000[diff] [blame]4328 <li><a href="mailto:Steve.Ball@zveno.com">Steve Ball</a>, <a
4329 href="http://www.zveno.com/">Zveno</a> and contributors maintain <a
4330 href="http://tclxml.sourceforge.net/">tcl bindings for libxml2 and
4331 libxslt</a>, as well as <a
4332 href="http://tclxml.sf.net/tkxmllint.html">tkxmllint</a> a GUI for
4333 xmllint and <a href="http://tclxml.sf.net/tkxsltproc.html">tkxsltproc</a>
4334 a GUI for xsltproc.</li>
Daniel Veillardc310d562000-06-23 18:32:15 +0000[diff] [blame]4335</ul>
4336
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]4337<p></p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]4338</body>
4339</html>