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