Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / libxml2 / 189446d2fa02c2075c6025703f97cc6fadcae9d4 / . / doc / xml.html
blob: 19d82f11ca072ce7aa7afdb687b6fcaf2cfef608 [file] [log] [blame]
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]2 "http://www.w3.org/TR/REC-html40/loose.dtd">
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]3<html>
4<head>
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000[diff] [blame]5 <title>The XML C library for Gnome</title>
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]6 <meta name="GENERATOR" content="amaya V3.2.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 Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]11<p><a href="http://www.gnome.org/"><img src="smallfootonly.gif"
12alt="Gnome Logo"></a><a href="http://www.w3.org/Status"><img src="w3c.png"
13alt="W3C Logo"></a></p>
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]14
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000[diff] [blame]15<h1 align="center">The XML C library for Gnome</h1>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]16
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]17<h2 style="text-align: center">libxml, a.k.a. gnome-xml</h2>
18
19<p></p>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]20<ul>
21 <li><a href="#Introducti">Introduction</a></li>
22 <li><a href="#Documentat">Documentation</a></li>
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]23 <li><a href="#Reporting">Reporting bugs and getting help</a></li>
24 <li><a href="#help">how to help</a></li>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]25 <li><a href="#Downloads">Downloads</a></li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]26 <li><a href="#News">News</a></li>
27 <li><a href="#XML">XML</a></li>
28 <li><a href="#tree">The tree output</a></li>
29 <li><a href="#interface">The SAX interface</a></li>
30 <li><a href="#library">The XML library interfaces</a>
31 <ul>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]32 <li><a href="#Invoking">Invoking the parser: the pull way</a></li>
33 <li><a href="#Invoking">Invoking the parser: the push way</a></li>
34 <li><a href="#Invoking2">Invoking the parser: the SAX interface</a></li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]35 <li><a href="#Building">Building a tree from scratch</a></li>
36 <li><a href="#Traversing">Traversing the tree</a></li>
37 <li><a href="#Modifying">Modifying the tree</a></li>
38 <li><a href="#Saving">Saving the tree</a></li>
39 <li><a href="#Compressio">Compression</a></li>
40 </ul>
41 </li>
42 <li><a href="#Entities">Entities or no entities</a></li>
43 <li><a href="#Namespaces">Namespaces</a></li>
44 <li><a href="#Validation">Validation</a></li>
45 <li><a href="#Principles">DOM principles</a></li>
46 <li><a href="#real">A real example</a></li>
Daniel Veillard96984452000-08-31 13:50:12 +0000[diff] [blame]47 <li><a href="#Contributi">Contributions</a></li>
48</ul>
49
50<p>Separate documents:</p>
51<ul>
52 <li><a href="upgrade.html">upgrade instructions for migrating to
53 libxml2</a></li>
54 <li><a href="encoding.html">libxml Internationalization support</a></li>
55 <li><a href="xmlio.html">libxml Input/Output interfaces</a></li>
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]56 <li><a href="xmlmem.html">libxml Memory interfaces</a></li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]57</ul>
58
59<h2><a name="Introducti">Introduction</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]60
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]61<p>This document describes libxml, the <a
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000[diff] [blame]62href="http://www.w3.org/XML/">XML</a> C library developped for the <a
63href="http://www.gnome.org/">Gnome</a> project. <a
64href="http://www.w3.org/XML/">XML is a standard</a> for building tag-based
65structured documents/data.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]66
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]67<p>Here are some key points about libxml:</p>
68<ul>
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]69 <li>Libxml exports Push and Pull type parser interfaces for both XML and
70 HTML.</li>
71 <li>Libxml can do Dtd validation at parse time, using a parsed document
72 instance, or with an arbitrary Dtd.</li>
73 <li>Libxml now includes a nearly complete <a
74 href="http://www.w3.org/TR/xpath">XPath</a> and <a
75 href="http://www.w3.org/TR/xptr/">XPointer</a> implementations.</li>
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000[diff] [blame]76 <li>It is written in plain C, making as few assumptions as possible, and
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]77 sticking closely to ANSI C/POSIX for easy embedding. Works on
78 Linux/Unix/Windows, ported to a number of other platforms. </li>
79 <li>Basic support for HTTP and FTP client allowing to fetch remote
80 resources</li>
81 <li>The design of modular, most of the extensions can be compiled out.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]82 <li>The internal document repesentation is as close as possible to the <a
83 href="http://www.w3.org/DOM/">DOM</a> interfaces.</li>
84 <li>Libxml also has a <a href="http://www.megginson.com/SAX/index.html">SAX
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]85 like interface</a>; the interface is designed to be compatible with <a
86 href="http://www.jclark.com/xml/expat.html">Expat</a>.</li>
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]87 <li>This library is released both under the <a
88 href="http://www.w3.org/Consortium/Legal/copyright-software-19980720.html">W3C
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]89 IPR</a> and the <a href="http://www.gnu.org/copyleft/lesser.html">GNU
90 LGPL</a>. Use either at your convenience, basically this should make
91 everybody happy, if not, drop me a mail.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]92</ul>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]93
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]94<h2><a name="Documentat">Documentation</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]95
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]96<p>There are some on-line resources about using libxml:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]97<ol>
Daniel Veillard365e13b2000-07-02 07:56:37 +0000[diff] [blame]98 <li>Check the <a href="FAQ.html">FAQ</a></li>
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]99 <li>Check the <a href="http://xmlsoft.org/html/libxml-lib.html">extensive
Daniel Veillard8c6d6af2000-08-25 17:14:13 +0000[diff] [blame]100 documentation</a> automatically extracted from code comments (using <a
101 href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gtk-doc">gtk
102 doc</a>).</li>
Daniel Veillard8d869642000-07-14 12:12:59 +0000[diff] [blame]103 <li>Look at the documentation about <a href="encoding.html">libxml
104 internationalization support</a></li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]105 <li>This page provides a global overview and <a href="#real">some
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]106 examples</a> on how to use libxml.</li>
107 <li><a href="mailto:james@daa.com.au">James Henstridge</a> wrote <a
108 href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">some nice
109 documentation</a> explaining how to use the libxml SAX interface.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]110 <li>George Lebl wrote <a
111 href="http://www-4.ibm.com/software/developer/library/gnome3/">an article
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]112 for IBM developerWorks</a> about using libxml.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]113 <li>It is also a good idea to check to <a href="mailto:raph@levien.com">Raph
114 Levien</a> <a href="http://levien.com/gnome/">web site</a> since he is
115 building the <a href="http://levien.com/gnome/gdome.html">DOM interface
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]116 gdome</a> on top of libxml result tree and an implementation of <a
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]117 href="http://www.w3.org/Graphics/SVG/">SVG</a> called <a
118 href="http://www.levien.com/svg/">gill</a>. Check his <a
119 href="http://www.levien.com/gnome/domination.html">DOMination
120 paper</a>.</li>
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]121 <li>Check <a href="http://cvs.gnome.org/lxr/source/gnome-xml/TODO">the TODO
122 file</a></li>
123 <li>Read the <a href="upgrade.html">1.x to 2.x upgrade path</a>. If you are
124 starting a new project using libxml you should really use the 2.x
125 version.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]126 <li>And don't forget to look at the <a href="/messages/">mailing-list
Daniel Veillardc310d562000-06-23 18:32:15 +0000[diff] [blame]127 archive</a>.</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]128</ol>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]129
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]130<h2><a name="Reporting">Reporting bugs and getting help</a></h2>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]131
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]132<p>Well, bugs or missing features are always possible, and I will make a point
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]133of fixing them in a timely fashion. The best way to report a bug is to use the
134<a href="http://bugs.gnome.org/db/pa/lgnome-xml.html">Gnome bug tracking
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]135database</a> (make sure to use the "gnome-xml" module name, not libxml or
136libxml2). I look at reports there regularly and it's good to have a reminder
137when a bug is still open. Check the <a
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]138href="http://bugs.gnome.org/Reporting.html">instructions on reporting bugs</a>
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]139and be sure to specify that the bug is for the package gnome-xml.</p>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]140
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]141<p>There is also a mailing-list <a
Daniel Veillardf121ab72000-08-29 23:40:42 +0000[diff] [blame]142href="mailto:xml@rpmfind.net">xml@rpmfind.net</a> for libxml, with an <a
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]143href="http://xmlsoft.org/messages">on-line archive</a>. To subscribe to this
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]144majordomo based list, send a mail message to <a
Daniel Veillardf121ab72000-08-29 23:40:42 +0000[diff] [blame]145href="mailto:majordomo@rpmfind.net">majordomo@rpmfind.net</a> with "subscribe
146xml" in the <strong>content</strong> of the message.</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]147
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]148<p>Alternatively, you can just send the bug to the <a
Daniel Veillardf121ab72000-08-29 23:40:42 +0000[diff] [blame]149href="mailto:xml@rpmfind.net">xml@rpmfind.net</a> list, if it's really libxml
150related I will approve it..</p>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]151
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]152<p>Of course, bugs reports with a suggested patch for fixing them will
153probably be processed faster.</p>
154
155<p>If you're looking for help, a quick look at <a
156href="http://xmlsoft.org/messages/#407">the list archive</a> may actually
157provide the answer, I usually send source samples when answering libxml usage
Daniel Veillard6f0adb52000-07-03 11:41:26 +0000[diff] [blame]158questions. The <a href="http://xmlsoft.org/html/book1.html">auto-generated
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]159documentantion</a> is not as polished as I would like (i need to learn more
160about Docbook), but it's a good starting point.</p>
161
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]162<h2><a name="help">How to help</a></h2>
163
164<p>You can help the project in various ways, the best thing to do first is to
165subscribe to the mailing-list as explained before, check the <a
166href="http://xmlsoft.org/messages/">archives </a>and the <a
167href="http://bugs.gnome.org/db/pa/lgnome-xml.html">Gnome bug
168database:</a>:</p>
169<ol>
170 <li>provide patches when you find problems</li>
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]171 <li>provide the diffs when you port libxml to a new platform. They may not
172 be integrated in all cases but help pinpointing portability problems and
173 </li>
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]174 <li>provice documentation fixes (either as patches to the code comments or
175 as HTML diffs).</li>
176 <li>provide new documentations pieces (translations, examples, etc ...)</li>
177 <li>Check the TODO file and try to close one of the items</li>
178 <li>take one of the points raised in the archive or the bug database and
179 provide a fix. <a href="mailto:Daniel.Veillard@w3.org">Get in touch with
180 me </a>before to avoid synchronization problems and check that the
181 suggested fix will fit in nicely :-)</li>
182</ol>
183
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]184<h2><a name="Downloads">Downloads</a></h2>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]185
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]186<p>The latest versions of libxml can be found on <a
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]187href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> or on the <a
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]188href="ftp://ftp.gnome.org/pub/GNOME/MIRRORS.html">Gnome FTP server</a> either
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]189as a <a href="ftp://ftp.gnome.org/pub/GNOME/stable/sources/libxml/">source
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]190archive</a> or <a
191href="ftp://ftp.gnome.org/pub/GNOME/contrib/redhat/SRPMS/">RPM packages</a>.
192(NOTE that you need both the <a
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]193href="http://rpmfind.net/linux/RPM/libxml2.html">libxml(2)</a> and <a
194href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml(2)-devel</a>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]195packages installed to compile applications using libxml.)</p>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]196
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]197<p><a name="Snapshot">Snapshot:</a></p>
198<ul>
199 <li>Code from the W3C cvs base libxml <a
200 href="ftp://rpmfind.net/pub/libxml/cvs-snapshot.tar.gz">cvs-snapshot.tar.gz</a></li>
201 <li>Docs, content of the web site, the list archive included <a
202 href="ftp://rpmfind.net/pub/libxml/libxml-docs.tar.gz">libxml-docs.tar.gz</a></li>
203</ul>
204
205<p><a name="Contribs">Contribs:</a></p>
206
207<p>I do accept external contributions, especially if compiling on another
208platform, get in touch with me to upload the package. I will keep them in the
209<a href="ftp://rpmfind.net/pub/libxml/contribs/">contrib directory</a></p>
210
Daniel Veillardc310d562000-06-23 18:32:15 +0000[diff] [blame]211<p>Libxml is also available from 2 CVS bases:</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]212<ul>
213 <li><p>The <a href="http://dev.w3.org/cvsweb/XML/">W3C CVS base</a>,
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]214 available read-only using the CVS pserver authentification (I tend to use
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]215 this base for my own development, so it's updated more regularly, but the
216 content may not be as stable):</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]217 <pre>CVSROOT=:pserver:anonymous@dev.w3.org:/sources/public
Daniel Veillard365e13b2000-07-02 07:56:37 +0000[diff] [blame]218 password: anonymous
219 module: XML</pre>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]220 </li>
221 <li><p>The <a
222 href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gnome-xml">Gnome
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]223 CVS base</a>. Check the <a
224 href="http://developer.gnome.org/tools/cvs.html">Gnome CVS Tools</a> page;
225 the CVS module is <b>gnome-xml</b>.</p>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]226 </li>
227</ul>
228
229<h2><a name="News">News</a></h2>
230
Daniel Veillard944b5ff1999-12-15 19:08:24 +0000[diff] [blame]231<h3>CVS only : check the <a
232href="http://cvs.gnome.org/lxr/source/gnome-xml/ChangeLog">Changelog</a> file
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]233for a really accurate description</h3>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]234<ul>
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]235 <li>XPointer implementation and testsuite</li>
236 <li>Lot of XPath fixes, added variable and functions registration, more
237 tests</li>
238 <li>Portability fixes, lots of enhancements toward an easy Windows build and
239 release</li>
240 <li>Late validation fixes</li>
241 <li>Integrated a lot of contributed patches</li>
242 <li>added memory management docs</li>
243</ul>
244
245<p>Item floating around but not actively worked on, get in touch with me if
246you want to test those</p>
247<ul>
248 <li>working on HTML and XML links recognition layers</li>
249 <li>parsing/import of Docbook SGML docs</li>
250</ul>
251
252<h3>2.2.4: Oct 1 2000:</h3>
253<ul>
254 <li>main XPath problem fixed</li>
255 <li>Integrated portability patches for Windows</li>
256 <li>Serious bug fixes on the URI and HTML code</li>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]257</ul>
258
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]259<h3>2.2.3: Sep 17 2000</h3>
260<ul>
261 <li>bug fixes</li>
262 <li>cleanup of entity handling code</li>
263 <li>overall review of all loops in the parsers, all sprintf usage has been
264 checked too</li>
265 <li>Far better handling of larges Dtd. Validating against Docbook XML Dtd
266 works smoothly now.</li>
267</ul>
268
269<h3>1.8.10: Sep 6 2000</h3>
270<ul>
271 <li>bug fix release for some Gnome projects</li>
272</ul>
273
274<h3>2.2.2: August 12 2000</h3>
Daniel Veillard786d7c82000-08-12 23:38:57 +0000[diff] [blame]275<ul>
276 <li>mostly bug fixes</li>
Daniel Veillardec78c0f2000-08-25 10:25:23 +0000[diff] [blame]277 <li>started adding routines to access xml parser context options</li>
Daniel Veillard786d7c82000-08-12 23:38:57 +0000[diff] [blame]278</ul>
279
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]280<h3>2.2.1: July 21 2000</h3>
Daniel Veillarda2679fa2000-07-22 02:38:15 +0000[diff] [blame]281<ul>
282 <li>a purely bug fixes release</li>
283 <li>fixed an encoding support problem when parsing from a memory block</li>
284 <li>fixed a DOCTYPE parsing problem</li>
285 <li>removed a bug in the function allowing to override the memory allocation
286 routines</li>
287</ul>
288
Daniel Veillardd5f97f82000-09-17 16:38:14 +0000[diff] [blame]289<h3>2.2.0: July 14 2000</h3>
Daniel Veillard94e90602000-07-17 14:38:19 +0000[diff] [blame]290<ul>
291 <li>applied a lot of portability fixes</li>
292 <li>better encoding support/cleanup and saving (content is now always
293 encoded in UTF-8)</li>
294 <li>the HTML parser now correctly handles encodings</li>
295 <li>added xmlHasProp()</li>
296 <li>fixed a serious problem with &amp;#38;</li>
297 <li>propagated the fix to FTP client</li>
298 <li>cleanup, bugfixes, etc ...</li>
299 <li>Added a page about <a href="encoding.html">libxml Internationalization
300 support</a></li>
301</ul>
302
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]303<h3>1.8.9: July 9 2000</h3>
304<ul>
305 <li>fixed the spec the RPMs should be better</li>
306 <li>fixed a serious bug in the FTP implementation, released 1.8.9 to solve
307 rpmfind users problem</li>
308</ul>
309
Daniel Veillard6388e172000-07-03 16:07:19 +0000[diff] [blame]310<h3>2.1.1: July 1 2000</h3>
311<ul>
312 <li>fixes a couple of bugs in the 2.1.0 packaging</li>
313 <li>improvements on the HTML parser</li>
314</ul>
315
Daniel Veillard3f6f7f62000-06-30 17:58:25 +0000[diff] [blame]316<h3>2.1.0 and 1.8.8: June 29 2000</h3>
317<ul>
318 <li>1.8.8 is mostly a comodity package for upgrading to libxml2 accoding to
319 <a href="upgrade.html">new instructions</a>. It fixes a nasty problem
320 about &amp;#38; charref parsing</li>
321 <li>2.1.0 also ease the upgrade from libxml v1 to the recent version. it
322 also contains numerous fixes and enhancements:
323 <ul>
324 <li>added xmlStopParser() to stop parsing</li>
325 <li>improved a lot parsing speed when there is large CDATA blocs</li>
326 <li>includes XPath patches provided by Picdar Technology</li>
327 <li>tried to fix as much as possible DtD validation and namespace
328 related problems</li>
329 <li>output to a given encoding has been added/tested</li>
330 <li>lot of various fixes</li>
331 </ul>
332 </li>
333</ul>
334
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]335<h3>2.0.0: Apr 12 2000</h3>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]336<ul>
337 <li>First public release of libxml2. If you are using libxml, it's a good
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]338 idea to check the 1.x to 2.x upgrade instructions. NOTE: while initally
339 scheduled for Apr 3 the relase occured only on Apr 12 due to massive
340 workload.</li>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]341 <li>The include are now located under $prefix/include/libxml (instead of
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]342 $prefix/include/gnome-xml), they also are referenced by
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]343 <pre>#include &lt;libxml/xxx.h&gt;</pre>
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]344 <p>instead of</p>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]345 <pre>#include "xxx.h"</pre>
346 </li>
Daniel Veillard8f621982000-03-20 13:07:15 +0000[diff] [blame]347 <li>a new URI module for parsing URIs and following strictly RFC 2396</li>
348 <li>the memory allocation routines used by libxml can now be overloaded
349 dynamically by using xmlMemSetup()</li>
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]350 <li>The previously CVS only tool tester has been renamed
351 <strong>xmllint</strong> and is now installed as part of the libxml2
352 package</li>
Daniel Veillarde0aed302000-04-16 08:52:20 +0000[diff] [blame]353 <li>The I/O interface has been revamped. There is now ways to plug in
354 specific I/O modules, either at the URI scheme detection level using
355 xmlRegisterInputCallbacks() or by passing I/O functions when creating a
356 parser context using xmlCreateIOParserCtxt()</li>
357 <li>there is a C preprocessor macro LIBXML_VERSION providing the version
358 number of the libxml module in use</li>
359 <li>a number of optional features of libxml can now be excluded at configure
360 time (FTP/HTTP/HTML/XPath/Debug)</li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]361</ul>
362
363<h3>2.0.0beta: Mar 14 2000</h3>
364<ul>
365 <li>This is a first Beta release of libxml version 2</li>
366 <li>It's available only from<a href="ftp://rpmfind.net/pub/libxml/">
367 rpmfind.net FTP</a>, it's packaged as libxml2-2.0.0beta and available as
368 tar and RPMs</li>
369 <li>This version is now the head in the Gnome CVS base, the old one is
370 available under the tag LIB_XML_1_X</li>
371 <li>This includes a very large set of changes. Froma programmatic point of
372 view applications should not have to be modified too much, check the <a
373 href="upgrade.html">upgrade page</a></li>
374 <li>Some interfaces may changes (especially a bit about encoding).</li>
375 <li>the updates includes:
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]376 <ul>
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]377 <li>fix I18N support. ISO-Latin-x/UTF-8/UTF-16 (nearly) seems correctly
378 handled now</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]379 <li>Better handling of entities, especially well formedness checking and
380 proper PEref extensions in external subsets</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]381 <li>DTD conditional sections</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]382 <li>Validation now correcly handle entities content</li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]383 <li><a href="http://rpmfind.net/tools/gdome/messages/0039.html">change
384 structures to accomodate DOM</a></li>
Daniel Veillard6c8b1172000-03-01 00:40:41 +0000[diff] [blame]385 </ul>
386 </li>
Daniel Veillardedfb29b2000-03-14 19:59:05 +0000[diff] [blame]387 <li>Serious progress were made toward compliance, <a
388 href="conf/result.html">here are the result of the test</a> against the
389 OASIS testsuite (except the japanese tests since I don't support that
390 encoding yet). This URL is rebuilt every couple of hours using the CVS
391 head version.</li>
Daniel Veillarde41f2b72000-01-30 20:00:07 +0000[diff] [blame]392</ul>
393
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]394<h3>1.8.7: Mar 6 2000</h3>
395<ul>
396 <li>This is a bug fix release:</li>
397 <li>It is possible to disable the ignorable blanks heuristic used by
398 libxml-1.x, a new function xmlKeepBlanksDefault(0) will allow this. Note
399 that for adherence to XML spec, this behaviour will be disabled by default
400 in 2.x . The same function will allow to keep compatibility for old
401 code.</li>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]402 <li>Blanks in &lt;a&gt; &lt;/a&gt; constructs are not ignored anymore,
403 avoiding heuristic is really the Right Way :-\</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]404 <li>The unchecked use of snprintf which was breaking libxml-1.8.6
405 compilation on some platforms has been fixed</li>
406 <li>nanoftp.c nanohttp.c: Fixed '#' and '?' stripping when processing
407 URIs</li>
408</ul>
409
Daniel Veillarde41f2b72000-01-30 20:00:07 +0000[diff] [blame]410<h3>1.8.6: Jan 31 2000</h3>
411<ul>
412 <li>added a nanoFTP transport module, debugged until the new version of <a
413 href="http://rpmfind.net/linux/rpm2html/rpmfind.html">rpmfind</a> can use
414 it without troubles</li>
Daniel Veillardda07c342000-01-25 18:31:22 +0000[diff] [blame]415</ul>
416
417<h3>1.8.5: Jan 21 2000</h3>
418<ul>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]419 <li>adding APIs to parse a well balanced chunk of XML (production <a
420 href="http://www.w3.org/TR/REC-xml#NT-content">[43] content</a> of the XML
421 spec)</li>
Daniel Veillard461a66c2000-01-18 18:01:01 +0000[diff] [blame]422 <li>fixed a hideous bug in xmlGetProp pointed by Rune.Djurhuus@fast.no</li>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]423 <li>Jody Goldberg &lt;jgoldberg@home.com&gt; provided another patch trying
424 to solve the zlib checks problems</li>
Daniel Veillard461a66c2000-01-18 18:01:01 +0000[diff] [blame]425 <li>The current state in gnome CVS base is expected to ship as 1.8.5 with
426 gnumeric soon</li>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]427</ul>
428
429<h3>1.8.4: Jan 13 2000</h3>
430<ul>
431 <li>bug fixes, reintroduced xmlNewGlobalNs(), fixed xmlNewNs()</li>
432 <li>all exit() call should have been removed from libxml</li>
433 <li>fixed a problem with INCLUDE_WINSOCK on WIN32 platform</li>
434 <li>added newDocFragment()</li>
Daniel Veillardf84f71f2000-01-05 19:54:23 +0000[diff] [blame]435</ul>
436
437<h3>1.8.3: Jan 5 2000</h3>
438<ul>
439 <li>a Push interface for the XML and HTML parsers</li>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]440 <li>a shell-like interface to the document tree (try tester --shell :-)</li>
Daniel Veillarddbfd6411999-12-28 16:35:14 +0000[diff] [blame]441 <li>lots of bug fixes and improvement added over XMas hollidays</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +0000[diff] [blame]442 <li>fixed the DTD parsing code to work with the xhtml DTD</li>
Daniel Veillardf84f71f2000-01-05 19:54:23 +0000[diff] [blame]443 <li>added xmlRemoveProp(), xmlRemoveID() and xmlRemoveRef()</li>
444 <li>Fixed bugs in xmlNewNs()</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +0000[diff] [blame]445 <li>External entity loading code has been revamped, now it uses
Daniel Veillardf84f71f2000-01-05 19:54:23 +0000[diff] [blame]446 xmlLoadExternalEntity(), some fix on entities processing were added</li>
Daniel Veillard437b87b2000-01-03 17:30:46 +0000[diff] [blame]447 <li>cleaned up WIN32 includes of socket stuff</li>
Daniel Veillard5cb5ab81999-12-21 15:35:29 +0000[diff] [blame]448</ul>
449
450<h3>1.8.2: Dec 21 1999</h3>
451<ul>
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]452 <li>I got another problem with includes and C++, I hope this issue is fixed
453 for good this time</li>
Daniel Veillard5cb5ab81999-12-21 15:35:29 +0000[diff] [blame]454 <li>Added a few tree modification functions: xmlReplaceNode,
455 xmlAddPrevSibling, xmlAddNextSibling, xmlNodeSetName and
456 xmlDocSetRootElement</li>
457 <li>Tried to improve the HTML output with help from <a
458 href="mailto:clahey@umich.edu">Chris Lahey</a></li>
Daniel Veillarde4e51311999-12-18 15:32:46 +0000[diff] [blame]459</ul>
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]460
Daniel Veillarde4e51311999-12-18 15:32:46 +0000[diff] [blame]461<h3>1.8.1: Dec 18 1999</h3>
462<ul>
463 <li>various patches to avoid troubles when using libxml with C++ compilers
464 the "namespace" keyword and C escaping in include files</li>
465 <li>a problem in one of the core macros IS_CHAR was corrected</li>
466 <li>fixed a bug introduced in 1.8.0 breaking default namespace processing,
467 and more specifically the Dia application</li>
Daniel Veillard944b5ff1999-12-15 19:08:24 +0000[diff] [blame]468 <li>fixed a posteriori validation (validation after parsing, or by using a
469 Dtd not specified in the original document)</li>
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]470 <li>fixed a bug in</li>
Daniel Veillard10a2c651999-12-12 13:03:50 +0000[diff] [blame]471</ul>
472
473<h3>1.8.0: Dec 12 1999</h3>
474<ul>
475 <li>cleanup, especially memory wise</li>
476 <li>the parser should be more reliable, especially the HTML one, it should
477 not crash, whatever the input !</li>
478 <li>Integrated various patches, especially a speedup improvement for large
479 dataset from <a href="mailto:cnygard@bellatlantic.net">Carl Nygard</a>,
480 configure with --with-buffers to enable them.</li>
481 <li>attribute normalization, oops should have been added long ago !</li>
482 <li>attributes defaulted from Dtds should be available, xmlSetProp() now
483 does entities escapting by default.</li>
Daniel Veillard4c3a2031999-11-19 17:46:26 +0000[diff] [blame]484</ul>
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]485
486<h3>1.7.4: Oct 25 1999</h3>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]487<ul>
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]488 <li>Lots of HTML improvement</li>
489 <li>Fixed some errors when saving both XML and HTML</li>
490 <li>More examples, the regression tests should now look clean</li>
491 <li>Fixed a bug with contiguous charref</li>
492</ul>
493
494<h3>1.7.3: Sep 29 1999</h3>
495<ul>
496 <li>portability problems fixed</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]497 <li>snprintf was used unconditionnally, leading to link problems on system
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]498 were it's not available, fixed</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]499</ul>
500
501<h3>1.7.1: Sep 24 1999</h3>
502<ul>
503 <li>The basic type for strings manipulated by libxml has been renamed in
504 1.7.1 from <strong>CHAR</strong> to <strong>xmlChar</strong>. The reason
505 is that CHAR was conflicting with a predefined type on Windows. However on
506 non WIN32 environment, compatibility is provided by the way of a
507 <strong>#define </strong>.</li>
508 <li>Changed another error : the use of a structure field called errno, and
509 leading to troubles on platforms where it's a macro</li>
510</ul>
511
512<h3>1.7.0: sep 23 1999</h3>
513<ul>
514 <li>Added the ability to fetch remote DTD or parsed entities, see the <a
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]515 href="html/gnome-xml-nanohttp.html">nanohttp</a> module.</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]516 <li>Added an errno to report errors by another mean than a simple printf
517 like callback</li>
518 <li>Finished ID/IDREF support and checking when validation</li>
519 <li>Serious memory leaks fixed (there is now a <a
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]520 href="html/gnome-xml-xmlmemory.html">memory wrapper</a> module)</li>
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]521 <li>Improvement of <a href="http://www.w3.org/TR/xpath">XPath</a>
522 implementation</li>
523 <li>Added an HTML parser front-end</li>
524</ul>
525
526<h2><a name="XML">XML</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]527
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]528<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]529markup-based structured documents. Here is <a name="example">an example XML
530document</a>:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]531<pre>&lt;?xml version="1.0"?&gt;
532&lt;EXAMPLE prop1="gnome is great" prop2="&amp;amp; linux too"&gt;
533 &lt;head&gt;
534 &lt;title&gt;Welcome to Gnome&lt;/title&gt;
535 &lt;/head&gt;
536 &lt;chapter&gt;
537 &lt;title&gt;The Linux adventure&lt;/title&gt;
538 &lt;p&gt;bla bla bla ...&lt;/p&gt;
539 &lt;image href="linus.gif"/&gt;
540 &lt;p&gt;...&lt;/p&gt;
541 &lt;/chapter&gt;
542&lt;/EXAMPLE&gt;</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]543
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]544<p>The first line specifies that it's an XML document and gives useful
545information about its encoding. Then the document is a text format whose
546structure is specified by tags between brackets. <strong>Each tag opened has
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]547to be closed</strong>. XML is pedantic about this. However, if a tag is empty
548(no content), a single tag can serve as both the opening and closing tag if it
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]549ends with <code>/&gt;</code> rather than with <code>&gt;</code>. Note that,
550for example, the image tag has no content (just an attribute) and is closed by
551ending the tag with <code>/&gt;</code>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]552
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]553<p>XML can be applied sucessfully to a wide range of uses, from long term
554structured document maintenance (where it follows the steps of SGML) to simple
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]555data encoding mechanisms like configuration file formatting (glade),
556spreadsheets (gnumeric), or even shorter lived documents such as WebDAV where
557it is used to encode remote calls between a client and a server.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]558
Daniel Veillard4540be42000-08-19 16:40:28 +0000[diff] [blame]559<h2>An overview of libxml architecture</h2>
560
561<p>Libxml is made of multiple components, some of them optionals, and most of
562the block interfaces are public. The main components are:</p>
563<ul>
564 <li>an Input/Output layer</li>
565 <li>FTP and HTTP client layers (optionnal)</li>
566 <li>an Internationalization layer managing the encodings support</li>
567 <li>an URI module</li>
568 <li>the XML parser and its basic SAX interface</li>
569 <li>an HTML parser using the same SAX interface (optionnal)</li>
570 <li>a SAX tree module to build an in-memory DOM representation</li>
571 <li>a tree module to manipulate the DOM representation</li>
572 <li>a validation module using the DOM representation (optionnal)</li>
573 <li>an XPath module for global lookup in a DOM representation
574 (optionnal)</li>
575 <li>a debug module (optionnal)</li>
576</ul>
577
578<p>Graphically this gives the following:</p>
579
580<p><img src="libxml.gif" alt="a graphical view of the various"></p>
581
582<p></p>
583
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]584<h2><a name="tree">The tree output</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]585
586<p>The parser returns a tree built during the document analysis. The value
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]587returned is an <strong>xmlDocPtr</strong> (i.e., a pointer to an
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]588<strong>xmlDoc</strong> structure). This structure contains information such
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]589as the file name, the document type, and a <strong>children</strong> pointer
590which is the root of the document (or more exactly the first child under the
591root which is the document). The tree is made of <strong>xmlNode</strong>s,
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]592chained in double-linked lists of siblings and with children&lt;-&gt;parent
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]593relationship. An xmlNode can also carry properties (a chain of xmlAttr
594structures). An attribute may have a value which is a list of TEXT or
595ENTITY_REF nodes.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]596
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]597<p>Here is an example (erroneous with respect to the XML spec since there
598should be only one ELEMENT under the root):</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]599
600<p><img src="structure.gif" alt=" structure.gif "></p>
601
602<p>In the source package there is a small program (not installed by default)
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]603called <strong>xmllint</strong> which parses XML files given as argument and
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]604prints them back as parsed. This is useful for detecting errors both in XML
605code and in the XML parser itself. It has an option <strong>--debug</strong>
606which prints the actual in-memory structure of the document, here is the
607result with the <a href="#example">example</a> given before:</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]608<pre>DOCUMENT
609version=1.0
610standalone=true
611 ELEMENT EXAMPLE
612 ATTRIBUTE prop1
613 TEXT
614 content=gnome is great
615 ATTRIBUTE prop2
616 ENTITY_REF
617 TEXT
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]618 content= linux too
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]619 ELEMENT head
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]620 ELEMENT title
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]621 TEXT
622 content=Welcome to Gnome
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]623 ELEMENT chapter
624 ELEMENT title
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]625 TEXT
626 content=The Linux adventure
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]627 ELEMENT p
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]628 TEXT
629 content=bla bla bla ...
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]630 ELEMENT image
631 ATTRIBUTE href
632 TEXT
633 content=linus.gif
634 ELEMENT p
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]635 TEXT
636 content=...</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]637
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]638<p>This should be useful for learning the internal representation model.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]639
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]640<h2><a name="interface">The SAX interface</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]641
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]642<p>Sometimes the DOM tree output is just too large to fit reasonably into
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]643memory. In that case (and if you don't expect to save back the XML document
644loaded using libxml), it's better to use the SAX interface of libxml. SAX is a
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]645<strong>callback-based interface</strong> to the parser. Before parsing, the
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]646application layer registers a customized set of callbacks which are called by
647the library as it progresses through the XML input.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]648
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]649<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]650libxml, see the <a
651href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">nice
652documentation</a>.written by <a href="mailto:james@daa.com.au">James
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]653Henstridge</a>.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]654
655<p>You can debug the SAX behaviour by using the <strong>testSAX</strong>
656program located in the gnome-xml module (it's usually not shipped in the
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]657binary packages of libxml, but you can find it in the tar source
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]658distribution). Here is the sequence of callbacks that would be reported by
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]659testSAX when parsing the example XML document shown earlier:</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]660<pre>SAX.setDocumentLocator()
661SAX.startDocument()
662SAX.getEntity(amp)
663SAX.startElement(EXAMPLE, prop1='gnome is great', prop2='&amp;amp; linux too')
664SAX.characters( , 3)
665SAX.startElement(head)
666SAX.characters( , 4)
667SAX.startElement(title)
668SAX.characters(Welcome to Gnome, 16)
669SAX.endElement(title)
670SAX.characters( , 3)
671SAX.endElement(head)
672SAX.characters( , 3)
673SAX.startElement(chapter)
674SAX.characters( , 4)
675SAX.startElement(title)
676SAX.characters(The Linux adventure, 19)
677SAX.endElement(title)
678SAX.characters( , 4)
679SAX.startElement(p)
680SAX.characters(bla bla bla ..., 15)
681SAX.endElement(p)
682SAX.characters( , 4)
683SAX.startElement(image, href='linus.gif')
684SAX.endElement(image)
685SAX.characters( , 4)
686SAX.startElement(p)
687SAX.characters(..., 3)
688SAX.endElement(p)
689SAX.characters( , 3)
690SAX.endElement(chapter)
691SAX.characters( , 1)
692SAX.endElement(EXAMPLE)
693SAX.endDocument()</pre>
694
Daniel Veillard402e8c82000-02-29 22:57:47 +0000[diff] [blame]695<p>Most of the other functionalities of libxml are based on the DOM
696tree-building facility, so nearly everything up to the end of this document
697presupposes the use of the standard DOM tree build. Note that the DOM tree
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]698itself is built by a set of registered default callbacks, without internal
699specific interface.</p>
700
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]701<h2><a name="library">The XML library interfaces</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]702
703<p>This section is directly intended to help programmers getting bootstrapped
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]704using the XML library from the C language. It is not intended to be extensive.
705I hope the automatically generated documents will provide the completeness
706required, but as a separate set of documents. The interfaces of the XML
707library are by principle low level, there is nearly zero abstraction. Those
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]708interested in a higher level API should <a href="#DOM">look at DOM</a>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]709
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]710<p>The <a href="html/gnome-xml-parser.html">parser interfaces for XML</a> are
711separated from the <a href="html/gnome-xml-htmlparser.html">HTML parser
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]712interfaces</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]713
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]714<h3><a name="Invoking">Invoking the parser : the pull method</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]715
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]716<p>Usually, the first thing to do is to read an XML input. The parser accepts
717documents either from in-memory strings or from files. The functions are
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]718defined in "parser.h":</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]719<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]720 <dt><code>xmlDocPtr xmlParseMemory(char *buffer, int size);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]721 <dd><p>Parse a null-terminated string containing the document.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]722 </dd>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]723</dl>
724<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]725 <dt><code>xmlDocPtr xmlParseFile(const char *filename);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]726 <dd><p>Parse an XML document contained in a (possibly compressed)
727 file.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]728 </dd>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]729</dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]730
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]731<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]732failure).</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]733
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]734<h3 id="Invoking1">Invoking the parser: the push method</h3>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]735
736<p>In order for the application to keep the control when the document is been
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]737fetched (which is common for GUI based programs) libxml provides a push
738interface, too, as of version 1.8.3. Here are the interface functions:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]739<pre>xmlParserCtxtPtr xmlCreatePushParserCtxt(xmlSAXHandlerPtr sax,
740 void *user_data,
741 const char *chunk,
742 int size,
743 const char *filename);
744int xmlParseChunk (xmlParserCtxtPtr ctxt,
745 const char *chunk,
746 int size,
747 int terminate);</pre>
748
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]749<p>and here is a simple example showing how to use the interface:</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]750<pre> FILE *f;
751
752 f = fopen(filename, "r");
753 if (f != NULL) {
754 int res, size = 1024;
755 char chars[1024];
756 xmlParserCtxtPtr ctxt;
757
758 res = fread(chars, 1, 4, f);
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]759 if (res &gt; 0) {
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]760 ctxt = xmlCreatePushParserCtxt(NULL, NULL,
761 chars, res, filename);
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]762 while ((res = fread(chars, 1, size, f)) &gt; 0) {
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]763 xmlParseChunk(ctxt, chars, res, 0);
764 }
765 xmlParseChunk(ctxt, chars, 0, 1);
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]766 doc = ctxt-&gt;myDoc;
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]767 xmlFreeParserCtxt(ctxt);
768 }
769 }</pre>
770
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]771<p>Also note that the HTML parser embedded into libxml also has a push
772interface; the functions are just prefixed by "html" rather than "xml"</p>
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]773
774<h3 id="Invoking2">Invoking the parser: the SAX interface</h3>
775
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]776<p>A couple of comments can be made, first this mean that the parser is
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]777memory-hungry, first to load the document in memory, second to build the tree.
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]778Reading a document without building the tree is possible using the SAX
779interfaces (see SAX.h and <a
780href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">James
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]781Henstridge's documentation</a>). Note also that the push interface can be
782limited to SAX. Just use the two first arguments of
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]783<code>xmlCreatePushParserCtxt()</code>.</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]784
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]785<h3><a name="Building">Building a tree from scratch</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]786
787<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]788there is a set of functions dedicated to building new elements. (These are
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]789also described in &lt;libxml/tree.h&gt;.) For example, here is a piece of code
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]790that produces the XML document used in the previous examples:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]791<pre> #include &lt;libxml/tree.h&gt;
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]792 xmlDocPtr doc;
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]793 xmlNodePtr tree, subtree;
794
795 doc = xmlNewDoc("1.0");
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]796 doc-&gt;children = xmlNewDocNode(doc, NULL, "EXAMPLE", NULL);
797 xmlSetProp(doc-&gt;children, "prop1", "gnome is great");
798 xmlSetProp(doc-&gt;children, "prop2", "&amp; linux too");
799 tree = xmlNewChild(doc-&gt;children, NULL, "head", NULL);
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]800 subtree = xmlNewChild(tree, NULL, "title", "Welcome to Gnome");
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]801 tree = xmlNewChild(doc-&gt;children, NULL, "chapter", NULL);
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]802 subtree = xmlNewChild(tree, NULL, "title", "The Linux adventure");
803 subtree = xmlNewChild(tree, NULL, "p", "bla bla bla ...");
804 subtree = xmlNewChild(tree, NULL, "image", NULL);
805 xmlSetProp(subtree, "href", "linus.gif");</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]806
807<p>Not really rocket science ...</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]808
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]809<h3><a name="Traversing">Traversing the tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]810
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]811<p>Basically by <a href="html/gnome-xml-tree.html">including "tree.h"</a> your
812code has access to the internal structure of all the elements of the tree. The
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]813names should be somewhat simple like <strong>parent</strong>,
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]814<strong>children</strong>, <strong>next</strong>, <strong>prev</strong>,
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]815<strong>properties</strong>, etc... For example, still with the previous
Daniel Veillard0142b842000-01-14 14:45:24 +0000[diff] [blame]816example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]817<pre><code>doc-&gt;children-&gt;children-&gt;children</code></pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]818
819<p>points to the title element,</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]820<pre>doc-&gt;children-&gt;children-&gt;next-&gt;child-&gt;child</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]821
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]822<p>points to the text node containing the chapter title "The Linux
823adventure".</p>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]824
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]825<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]826present before the document root, so <code>doc-&gt;children</code> may point
827to an element which is not the document Root Element, a function
Daniel Veillard5cb5ab81999-12-21 15:35:29 +0000[diff] [blame]828<code>xmlDocGetRootElement()</code> was added for this purpose.</p>
Daniel Veillardb24054a1999-12-18 15:32:46 +0000[diff] [blame]829
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]830<h3><a name="Modifying">Modifying the tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]831
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]832<p>Functions are provided for reading and writing the document content. Here
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]833is an excerpt from the <a href="html/gnome-xml-tree.html">tree API</a>:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]834<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]835 <dt><code>xmlAttrPtr xmlSetProp(xmlNodePtr node, const xmlChar *name, const
836 xmlChar *value);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]837 <dd><p>This sets (or changes) an attribute carried by an ELEMENT node. The
838 value can be NULL.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]839 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]840</dl>
841<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]842 <dt><code>const xmlChar *xmlGetProp(xmlNodePtr node, const xmlChar
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]843 *name);</code></dt>
Daniel Veillardc92c3042000-09-29 02:42:04 +0000[diff] [blame]844 <dd><p>This function returns a pointer to new copy of the property
845 content. Note that the user must deallocate the result.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]846 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]847</dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]848
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]849<p>Two functions are provided for reading and writing the text associated with
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]850elements:</p>
851<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]852 <dt><code>xmlNodePtr xmlStringGetNodeList(xmlDocPtr doc, const xmlChar
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]853 *value);</code></dt>
854 <dd><p>This function takes an "external" string and convert it to one text
855 node or possibly to a list of entity and text nodes. All non-predefined
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]856 entity references like &amp;Gnome; will be stored internally as entity
857 nodes, hence the result of the function may not be a single node.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]858 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]859</dl>
860<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]861 <dt><code>xmlChar *xmlNodeListGetString(xmlDocPtr doc, xmlNodePtr list, int
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]862 inLine);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]863 <dd><p>This function is the inverse of
864 <code>xmlStringGetNodeList()</code>. It generates a new string
865 containing the content of the text and entity nodes. Note the extra
866 argument inLine. If this argument is set to 1, the function will expand
867 entity references. For example, instead of returning the &amp;Gnome;
868 XML encoding in the string, it will substitute it with its value (say,
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]869 "GNU Network Object Model Environment"). Set this argument if you want
870 to use the string for non-XML usage like User Interface.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]871 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]872</dl>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]873
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]874<h3><a name="Saving">Saving a tree</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]875
876<p>Basically 3 options are possible:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]877<dl>
Daniel Veillarddd6b3671999-09-23 22:19:22 +0000[diff] [blame]878 <dt><code>void xmlDocDumpMemory(xmlDocPtr cur, xmlChar**mem, int
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]879 *size);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]880 <dd><p>Returns a buffer into which the document has been saved.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]881 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]882</dl>
883<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]884 <dt><code>extern void xmlDocDump(FILE *f, xmlDocPtr doc);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]885 <dd><p>Dumps a document to an open file descriptor.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]886 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]887</dl>
888<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]889 <dt><code>int xmlSaveFile(const char *filename, xmlDocPtr cur);</code></dt>
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]890 <dd><p>Saves the document to a file. In this case, the compression
891 interface is triggered if it has been turned on.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]892 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]893</dl>
Daniel Veillard10c6a8f1998-10-28 01:00:12 +0000[diff] [blame]894
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]895<h3><a name="Compressio">Compression</a></h3>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]896
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]897<p>The library transparently handles compression when doing file-based
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]898accesses. The level of compression on saves can be turned on either globally
899or individually for one file:</p>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]900<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]901 <dt><code>int xmlGetDocCompressMode (xmlDocPtr doc);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]902 <dd><p>Gets the document compression ratio (0-9).</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]903 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]904</dl>
905<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]906 <dt><code>void xmlSetDocCompressMode (xmlDocPtr doc, int mode);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]907 <dd><p>Sets the document compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]908 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]909</dl>
910<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]911 <dt><code>int xmlGetCompressMode(void);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]912 <dd><p>Gets the default compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]913 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]914</dl>
915<dl>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]916 <dt><code>void xmlSetCompressMode(int mode);</code></dt>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]917 <dd><p>Sets the default compression ratio.</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]918 </dd>
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]919</dl>
920
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]921<h2><a name="Entities">Entities or no entities</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]922
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]923<p>Entities in principle are similar to simple C macros. An entity defines an
924abbreviation for a given string that you can reuse many times throughout the
925content of your document. Entities are especially useful when a given string
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]926may occur frequently within a document, or to confine the change needed to a
927document to a restricted area in the internal subset of the document (at the
928beginning). Example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]929<pre>1 &lt;?xml version="1.0"?&gt;
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]9302 &lt;!DOCTYPE EXAMPLE SYSTEM "example.dtd" [
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]9313 &lt;!ENTITY xml "Extensible Markup Language"&gt;
9324 ]&gt;
9335 &lt;EXAMPLE&gt;
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]9346 &amp;xml;
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]9357 &lt;/EXAMPLE&gt;</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]936
937<p>Line 3 declares the xml entity. Line 6 uses the xml entity, by prefixing
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]938it's name with '&amp;' and following it by ';' without any spaces added. There
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]939are 5 predefined entities in libxml allowing you to escape charaters with
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]940predefined meaning in some parts of the xml document content:
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]941<strong>&amp;lt;</strong> for the character '&lt;', <strong>&amp;gt;</strong>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]942for the character '&gt;', <strong>&amp;apos;</strong> for the character ''',
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]943<strong>&amp;quot;</strong> for the character '"', and
944<strong>&amp;amp;</strong> for the character '&amp;'.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]945
946<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]947substitute an entity's content so that you can see the replacement text in
948your application. Or you may prefer to keep entity references as such in the
949content to be able to save the document back without losing this usually
950precious information (if the user went through the pain of explicitly defining
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]951entities, he may have a a rather negative attitude if you blindly susbtitute
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]952them as saving time). The <a
Daniel Veillardc19fccc2000-07-03 11:52:01 +0000[diff] [blame]953href="html/gnome-xml-parser.html#XMLSUBSTITUTEENTITIESDEFAULT">xmlSubstituteEntitiesDefault()</a>
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]954function allows you to check and change the behaviour, which is to not
955substitute entities by default.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]956
957<p>Here is the DOM tree built by libxml for the previous document in the
958default case:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]959<pre>/gnome/src/gnome-xml -&gt; ./xmllint --debug test/ent1
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]960DOCUMENT
961version=1.0
962 ELEMENT EXAMPLE
963 TEXT
964 content=
965 ENTITY_REF
966 INTERNAL_GENERAL_ENTITY xml
967 content=Extensible Markup Language
968 TEXT
969 content=</pre>
970
971<p>And here is the result when substituting entities:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]972<pre>/gnome/src/gnome-xml -&gt; ./tester --debug --noent test/ent1
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]973DOCUMENT
974version=1.0
975 ELEMENT EXAMPLE
976 TEXT
977 content= Extensible Markup Language</pre>
978
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]979<p>So, entities or no entities? Basically, it depends on your use case. I
980suggest that you keep the non-substituting default behaviour and avoid using
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]981entities in your XML document or data if you are not willing to handle the
982entity references elements in the DOM tree.</p>
983
984<p>Note that at save time libxml enforce the conversion of the predefined
985entities where necessary to prevent well-formedness problems, and will also
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]986transparently replace those with chars (i.e., it will not generate entity
987reference elements in the DOM tree or call the reference() SAX callback when
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]988finding them in the input).</p>
989
Daniel Veillard7b9c4b72000-08-25 16:26:50 +0000[diff] [blame]990<p><span style="background-color: #FF0000">WARNING</span>: handling entities
991on top of libxml SAX interface is difficult !!! If you plan to use
992non-predefined entities in your documents, then the learning cuvre to handle
993then using the SAX API may be long. If you plan to use complex document, I
994strongly suggest you consider using the DOM interface instead and let libxml
Daniel Veillard8c6d6af2000-08-25 17:14:13 +0000[diff] [blame]995deal with the complexity rather than trying to do it yourself.</p>
Daniel Veillard7b9c4b72000-08-25 16:26:50 +0000[diff] [blame]996
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]997<h2><a name="Namespaces">Namespaces</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]998
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]999<p>The libxml library implements <a
1000href="http://www.w3.org/TR/REC-xml-names/">XML namespaces</a> support by
1001recognizing namespace contructs in the input, and does namespace lookup
1002automatically when building the DOM tree. A namespace declaration is
1003associated with an in-memory structure and all elements or attributes within
1004that namespace point to it. Hence testing the namespace is a simple and fast
1005equality operation at the user level.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1006
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]1007<p>I suggest that people using libxml use a namespace, and declare it in the
1008root element of their document as the default namespace. Then they don't need
1009to use the prefix in the content but we will have a basis for future semantic
1010refinement and merging of data from different sources. This doesn't augment
1011significantly the size of the XML output, but significantly increase its value
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]1012in the long-term. Example:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1013<pre>&lt;mydoc xmlns="http://mydoc.example.org/schemas/"&gt;
1014 &lt;elem1&gt;...&lt;/elem1&gt;
1015 &lt;elem2&gt;...&lt;/elem2&gt;
1016&lt;/mydoc&gt;</pre>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1017
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]1018<p>Concerning the namespace value, this has to be an URL, but the URL doesn't
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]1019have to point to any existing resource on the Web. It will bind all the
1020element and atributes with that URL. I suggest to use an URL within a domain
1021you control, and that the URL should contain some kind of version information
1022if possible. For example, <code>"http://www.gnome.org/gnumeric/1.0/"</code> is
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]1023a good namespace scheme.</p>
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]1024
1025<p>Then when you load a file, make sure that a namespace carrying the
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]1026version-independent prefix is installed on the root element of your document,
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1027and if the version information don't match something you know, warn the user
1028and 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]1029namespace checking on the prefix value. &lt;foo:text&gt; may be exactly the
1030same as &lt;bar:text&gt; in another document. What really matter is the URI
1031associated with the element or the attribute, not the prefix string (which is
1032just a shortcut for the full URI). In libxml element and attributes have a
Daniel Veillardec303412000-03-24 13:41:54 +0000[diff] [blame]1033<code>ns</code> field pointing to an xmlNs structure detailing the namespace
1034prefix and it's URI.</p>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1035
1036<p>@@Interfaces@@</p>
1037
1038<p>@@Examples@@</p>
1039
1040<p>Usually people object using namespace in the case of validation, I object
1041this and will make sure that using namespaces won't break validity checking,
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]1042so even is you plan to use or currently are using validation I strongly
1043suggest adding namespaces to your document. A default namespace scheme
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1044<code>xmlns="http://...."</code> should not break validity even on less
Daniel Veillard88f00ae2000-03-02 00:15:55 +0000[diff] [blame]1045flexible parsers. Now using namespace to mix and differentiate content coming
1046from multiple DTDs will certainly break current validation schemes. I will try
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1047to provide ways to do this, but this may not be portable or standardized.</p>
1048
Daniel Veillard2f4dfc41999-09-24 14:03:48 +0000[diff] [blame]1049<h2><a name="Validation">Validation, or are you afraid of DTDs ?</a></h2>
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1050
1051<p>Well what is validation and what is a DTD ?</p>
1052
1053<p>Validation is the process of checking a document against a set of
1054construction rules, a <strong>DTD</strong> (Document Type Definition) is such
1055a set of rules.</p>
1056
1057<p>The validation process and building DTDs are the two most difficult parts
1058of XML life cycle. Briefly a DTD defines all the possibles element to be
1059found within your document, what is the formal shape of your document tree (by
1060defining the allowed content of an element, either text, a regular expression
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]1061for the allowed list of children, or mixed content i.e. both text and
1062children). The DTD also defines the allowed attributes for all elements and
1063the types of the attributes. For more detailed informations, I suggest to read
1064the related parts of the XML specification, the examples found under
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1065gnome-xml/test/valid/dtd and the large amount of books available on XML. The
1066dia example in gnome-xml/test/valid should be both simple and complete enough
1067to allow you to build your own.</p>
1068
1069<p>A word of warning, building a good DTD which will fit your needs of your
1070application in the long-term is far from trivial, however the extra level of
1071quality it can insure is well worth the price for some sets of applications or
1072if you already have already a DTD defined for your application field.</p>
1073
1074<p>The validation is not completely finished but in a (very IMHO) usable
1075state. Until a real validation interface is defined the way to do it is to
1076define and set the <strong>xmlDoValidityCheckingDefaultValue</strong> external
1077variable to 1, this will of course be changed at some point:</p>
1078
1079<p>extern int xmlDoValidityCheckingDefaultValue;</p>
1080
1081<p>...</p>
1082
1083<p>xmlDoValidityCheckingDefaultValue = 1;</p>
1084
1085<p></p>
1086
1087<p>To handle external entities, use the function
1088<strong>xmlSetExternalEntityLoader</strong>(xmlExternalEntityLoader f); to
1089link in you HTTP/FTP/Entities database library to the standard libxml
1090core.</p>
1091
1092<p>@@interfaces@@</p>
1093
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]1094<h2><a name="DOM"></a><a name="Principles">DOM Principles</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1095
1096<p><a href="http://www.w3.org/DOM/">DOM</a> stands for the <em>Document Object
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]1097Model</em> this is an API for accessing XML or HTML structured documents.
1098Native support for DOM in Gnome is on the way (module gnome-dom), and it will
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]1099be based on gnome-xml. This will be a far cleaner interface to manipulate XML
Daniel Veillardc08a2c61999-09-08 21:35:25 +0000[diff] [blame]1100files within Gnome since it won't expose the internal structure. DOM defines a
Daniel Veillard25940b71998-10-29 05:51:30 +0000[diff] [blame]1101set of IDL (or Java) interfaces allowing to traverse and manipulate a
1102document. The DOM library will allow accessing and modifying "live" documents
1103presents on other programs like this:</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1104
1105<p><img src="DOM.gif" alt=" DOM.gif "></p>
1106
1107<p>This should help greatly doing things like modifying a gnumeric spreadsheet
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]1108embedded in a GWP document for example.</p>
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1109
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1110<p>The current DOM implementation on top of libxml is the <a
1111href="http://cvs.gnome.org/lxr/source/gdome/">gdome Gnome module</a>, this is
1112a full DOM interface, thanks to <a href="mailto:raph@levien.com">Raph
1113Levien</a>.</p>
1114
1115<p>The gnome-dom module in the Gnome CVS base is obsolete</p>
1116
Daniel Veillard35008381999-10-25 13:15:52 +0000[diff] [blame]1117<h2><a name="Example"></a><a name="real">A real example</a></h2>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1118
1119<p>Here is a real size example, where the actual content of the application
1120data 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]1121a proposal to keep a database of jobs related to Gnome, with an XML based
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1122storage structure. Here is an <a href="gjobs.xml">XML encoded jobs
1123base</a>:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1124<pre>&lt;?xml version="1.0"?&gt;
1125&lt;gjob:Helping xmlns:gjob="http://www.gnome.org/some-location"&gt;
1126 &lt;gjob:Jobs&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1127
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1128 &lt;gjob:Job&gt;
1129 &lt;gjob:Project ID="3"/&gt;
1130 &lt;gjob:Application&gt;GBackup&lt;/gjob:Application&gt;
1131 &lt;gjob:Category&gt;Development&lt;/gjob:Category&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1132
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1133 &lt;gjob:Update&gt;
1134 &lt;gjob:Status&gt;Open&lt;/gjob:Status&gt;
1135 &lt;gjob:Modified&gt;Mon, 07 Jun 1999 20:27:45 -0400 MET DST&lt;/gjob:Modified&gt;
1136 &lt;gjob:Salary&gt;USD 0.00&lt;/gjob:Salary&gt;
1137 &lt;/gjob:Update&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1138
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1139 &lt;gjob:Developers&gt;
1140 &lt;gjob:Developer&gt;
1141 &lt;/gjob:Developer&gt;
1142 &lt;/gjob:Developers&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1143
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1144 &lt;gjob:Contact&gt;
1145 &lt;gjob:Person&gt;Nathan Clemons&lt;/gjob:Person&gt;
1146 &lt;gjob:Email&gt;nathan@windsofstorm.net&lt;/gjob:Email&gt;
1147 &lt;gjob:Company&gt;
1148 &lt;/gjob:Company&gt;
1149 &lt;gjob:Organisation&gt;
1150 &lt;/gjob:Organisation&gt;
1151 &lt;gjob:Webpage&gt;
1152 &lt;/gjob:Webpage&gt;
1153 &lt;gjob:Snailmail&gt;
1154 &lt;/gjob:Snailmail&gt;
1155 &lt;gjob:Phone&gt;
1156 &lt;/gjob:Phone&gt;
1157 &lt;/gjob:Contact&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1158
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1159 &lt;gjob:Requirements&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1160 The program should be released as free software, under the GPL.
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1161 &lt;/gjob:Requirements&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1162
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1163 &lt;gjob:Skills&gt;
1164 &lt;/gjob:Skills&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1165
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1166 &lt;gjob:Details&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1167 A GNOME based system that will allow a superuser to configure
1168 compressed and uncompressed files and/or file systems to be backed
1169 up with a supported media in the system. This should be able to
1170 perform via find commands generating a list of files that are passed
1171 to tar, dd, cpio, cp, gzip, etc., to be directed to the tape machine
1172 or via operations performed on the filesystem itself. Email
1173 notification and GUI status display very important.
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1174 &lt;/gjob:Details&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1175
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1176 &lt;/gjob:Job&gt;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1177
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1178 &lt;/gjob:Jobs&gt;
1179&lt;/gjob:Helping&gt;</pre>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1180
1181<p>While loading the XML file into an internal DOM tree is a matter of calling
1182only a couple of functions, browsing the tree to gather the informations and
1183generate the internals structures is harder, and more error prone.</p>
1184
1185<p>The suggested principle is to be tolerant with respect to the input
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]1186structure. For example, the ordering of the attributes is not significant,
1187Cthe XML specification is clear about it. It's also usually a good idea to not
Daniel Veillard306be992000-07-03 12:38:45 +0000[diff] [blame]1188be dependent of the orders of the children of a given node, unless it really
Daniel Veillardf13e1ed2000-03-06 07:41:49 +0000[diff] [blame]1189makes things harder. Here is some code to parse the informations for a
1190person:</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1191<pre>/*
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1192 * A person record
1193 */
1194typedef struct person {
1195 char *name;
1196 char *email;
1197 char *company;
1198 char *organisation;
1199 char *smail;
1200 char *webPage;
1201 char *phone;
1202} person, *personPtr;
1203
1204/*
1205 * And the code needed to parse it
1206 */
1207personPtr parsePerson(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
1208 personPtr ret = NULL;
1209
1210DEBUG("parsePerson\n");
1211 /*
1212 * allocate the struct
1213 */
1214 ret = (personPtr) malloc(sizeof(person));
1215 if (ret == NULL) {
1216 fprintf(stderr,"out of memory\n");
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1217 return(NULL);
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1218 }
1219 memset(ret, 0, sizeof(person));
1220
1221 /* We don't care what the top level element name is */
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1222 cur = cur-&gt;xmlChildrenNode;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1223 while (cur != NULL) {
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1224 if ((!strcmp(cur-&gt;name, "Person")) &amp;&amp; (cur-&gt;ns == ns))
1225 ret-&gt;name = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
1226 if ((!strcmp(cur-&gt;name, "Email")) &amp;&amp; (cur-&gt;ns == ns))
1227 ret-&gt;email = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
1228 cur = cur-&gt;next;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1229 }
1230
1231 return(ret);
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1232}</pre>
1233
1234<p>Here is a couple of things to notice:</p>
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1235<ul>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1236 <li>Usually a recursive parsing style is the more convenient one, XML data
1237 being by nature subject to repetitive constructs and usualy exibit highly
1238 stuctured patterns.</li>
1239 <li>The two arguments of type <em>xmlDocPtr</em> and <em>xmlNsPtr</em>, i.e.
1240 the pointer to the global XML document and the namespace reserved to the
1241 application. Document wide information are needed for example to decode
1242 entities and it's a good coding practice to define a namespace for your
1243 application set of data and test that the element and attributes you're
1244 analyzing actually pertains to your application space. This is done by a
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1245 simple equality test (cur-&gt;ns == ns).</li>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1246 <li>To retrieve text and attributes value, it is suggested to use the
1247 function <em>xmlNodeListGetString</em> to gather all the text and entity
1248 reference nodes generated by the DOM output and produce an single text
1249 string.</li>
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1250</ul>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1251
1252<p>Here is another piece of code used to parse another level of the
1253structure:</p>
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1254<pre>#include &lt;libxml/tree.h&gt;
Daniel Veillard361d8452000-04-03 19:48:13 +0000[diff] [blame]1255/*
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1256 * a Description for a Job
1257 */
1258typedef struct job {
1259 char *projectID;
1260 char *application;
1261 char *category;
1262 personPtr contact;
1263 int nbDevelopers;
1264 personPtr developers[100]; /* using dynamic alloc is left as an exercise */
1265} job, *jobPtr;
1266
1267/*
1268 * And the code needed to parse it
1269 */
1270jobPtr parseJob(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
1271 jobPtr ret = NULL;
1272
1273DEBUG("parseJob\n");
1274 /*
1275 * allocate the struct
1276 */
1277 ret = (jobPtr) malloc(sizeof(job));
1278 if (ret == NULL) {
1279 fprintf(stderr,"out of memory\n");
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1280 return(NULL);
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1281 }
1282 memset(ret, 0, sizeof(job));
1283
1284 /* We don't care what the top level element name is */
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1285 cur = cur-&gt;xmlChildrenNode;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1286 while (cur != NULL) {
1287
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1288 if ((!strcmp(cur-&gt;name, "Project")) &amp;&amp; (cur-&gt;ns == ns)) {
1289 ret-&gt;projectID = xmlGetProp(cur, "ID");
1290 if (ret-&gt;projectID == NULL) {
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1291 fprintf(stderr, "Project has no ID\n");
1292 }
1293 }
Daniel Veillard60979bd2000-07-10 12:17:33 +0000[diff] [blame]1294 if ((!strcmp(cur-&gt;name, "Application")) &amp;&amp; (cur-&gt;ns == ns))
1295 ret-&gt;application = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
1296 if ((!strcmp(cur-&gt;name, "Category")) &amp;&amp; (cur-&gt;ns == ns))
1297 ret-&gt;category = xmlNodeListGetString(doc, cur-&gt;xmlChildrenNode, 1);
1298 if ((!strcmp(cur-&gt;name, "Contact")) &amp;&amp; (cur-&gt;ns == ns))
1299 ret-&gt;contact = parsePerson(doc, ns, cur);
1300 cur = cur-&gt;next;
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1301 }
1302
1303 return(ret);
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1304}</pre>
Daniel Veillard14fff061999-06-22 21:49:07 +0000[diff] [blame]1305
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1306<p>One can notice that once used to it, writing this kind of code is quite
1307simple, but boring. Ultimately, it could be possble to write stubbers taking
1308either C data structure definitions, a set of XML examples or an XML DTD and
1309produce the code needed to import and export the content between C data and
1310XML storage. This is left as an exercise to the reader :-)</p>
1311
Daniel Veillard6f0adb52000-07-03 11:41:26 +0000[diff] [blame]1312<p>Feel free to use <a href="example/gjobread.c">the code for the full C
1313parsing example</a> as a template, it is also available with Makefile in the
1314Gnome CVS base under gnome-xml/example</p>
Daniel Veillardb05deb71999-08-10 19:04:08 +0000[diff] [blame]1315
Daniel Veillardc310d562000-06-23 18:32:15 +0000[diff] [blame]1316<h2><a name="Contributi">Contributions</a></h2>
1317<ul>
1318 <li><a href="mailto:ari@btigate.com">Ari Johnson</a> provides a C++ wrapper
1319 for libxml:
1320 <p>Website: <a
1321 href="http://lusis.org/~ari/xml++/">http://lusis.org/~ari/xml++/</a></p>
1322 <p>Download: <a
1323 href="http://lusis.org/~ari/xml++/libxml++.tar.gz">http://lusis.org/~ari/xml++/libxml++.tar.gz</a></p>
1324 </li>
1325 <li><a href="mailto:doolin@cs.utk.edu">David Doolin</a> provides a
1326 precompiled Windows version
1327 <p><a
1328 href="http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/">http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/</a></p>
1329 </li>
Daniel Veillard3f6f7f62000-06-30 17:58:25 +0000[diff] [blame]1330 <li><a href="mailto:fnatter@gmx.net">Felix Natter</a> provided <a
1331 href="libxml-doc.el">an emacs module</a> to lookup libxml functions
1332 documentation</li>
Daniel Veillardc310d562000-06-23 18:32:15 +0000[diff] [blame]1333 <li><a href="mailto:sherwin@nlm.nih.gov">Ziying Sherwin</a> provided <a
1334 href="http://xmlsoft.org/messages/0488.html">man pages</a> (not yet
1335 integrated in the distribution)</li>
1336</ul>
1337
Daniel Veillardc8eab3a1999-09-04 18:27:23 +0000[diff] [blame]1338<p></p>
1339
1340<p><a href="mailto:Daniel.Veillard@w3.org">Daniel Veillard</a></p>
1341
Daniel Veillard189446d2000-10-13 10:23:06 +0000[diff] [blame^]1342<p>$Id: xml.html,v 1.53 2000/09/29 02:42:04 veillard Exp $</p>
Daniel Veillardccb09631998-10-27 06:21:04 +0000[diff] [blame]1343</body>
1344</html>