blob: eb12d6f22379cfcd860e643a7141de768085b40b [file] [log] [blame]
Daniel Veillard43d3f612001-11-10 11:57:23 +00001<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
Daniel Veillardaf743792000-07-01 11:49:28 +00002<html>
3<head>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +00004<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
5<style type="text/css"><!--
Daniel Veillard2c748c62002-01-16 15:37:50 +00006TD {font-size: 14pt; font-family: Verdana,Arial,Helvetica}
7BODY {font-size: 14pt; font-family: Verdana,Arial,Helvetica; margin-top: 2em; margin-left: 0em; margin-right: 0em}
8H1 {font-size: 20pt; font-family: Verdana,Arial,Helvetica}
9H2 {font-size: 18pt; font-family: Verdana,Arial,Helvetica}
10H3 {font-size: 16pt; font-family: Verdana,Arial,Helvetica}
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000011A:link, A:visited, A:active { text-decoration: underline }
12--></style>
13<title>FAQ</title>
Daniel Veillardaf743792000-07-01 11:49:28 +000014</head>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000015<body bgcolor="#8b7765" text="#000000" link="#000000" vlink="#000000">
16<table border="0" width="100%" cellpadding="5" cellspacing="0" align="center"><tr>
17<td width="180">
18<a href="http://www.gnome.org/"><img src="smallfootonly.gif" alt="Gnome Logo"></a><a href="http://www.w3.org/Status"><img src="w3c.png" alt="W3C Logo"></a><a href="http://www.redhat.com/"><img src="redhat.gif" alt="Red Hat Logo"></a>
19</td>
20<td><table border="0" width="90%" cellpadding="2" cellspacing="0" align="center" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3" bgcolor="#fffacd"><tr><td align="center">
21<h1>The XML C library for Gnome</h1>
22<h2>FAQ</h2>
23</td></tr></table></td></tr></table></td>
24</tr></table>
25<table border="0" cellpadding="4" cellspacing="0" width="100%" align="center"><tr><td bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="2" width="100%"><tr>
26<td valign="top" width="200" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td>
27<table width="100%" border="0" cellspacing="1" cellpadding="3">
28<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Main Menu</b></center></td></tr>
Daniel Veillard8acca112002-01-21 09:52:27 +000029<tr><td bgcolor="#fffacd"><ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000030<li><a href="index.html">Home</a></li>
31<li><a href="intro.html">Introduction</a></li>
32<li><a href="FAQ.html">FAQ</a></li>
33<li><a href="docs.html">Documentation</a></li>
34<li><a href="bugs.html">Reporting bugs and getting help</a></li>
35<li><a href="help.html">How to help</a></li>
36<li><a href="downloads.html">Downloads</a></li>
37<li><a href="news.html">News</a></li>
Daniel Veillard7b602b42002-01-08 13:26:00 +000038<li><a href="XMLinfo.html">XML</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000039<li><a href="XSLT.html">XSLT</a></li>
40<li><a href="architecture.html">libxml architecture</a></li>
41<li><a href="tree.html">The tree output</a></li>
42<li><a href="interface.html">The SAX interface</a></li>
43<li><a href="xmldtd.html">Validation &amp; DTDs</a></li>
44<li><a href="xmlmem.html">Memory Management</a></li>
45<li><a href="encoding.html">Encodings support</a></li>
46<li><a href="xmlio.html">I/O Interfaces</a></li>
47<li><a href="catalog.html">Catalog support</a></li>
48<li><a href="library.html">The parser interfaces</a></li>
49<li><a href="entities.html">Entities or no entities</a></li>
50<li><a href="namespaces.html">Namespaces</a></li>
51<li><a href="upgrade.html">Upgrading 1.x code</a></li>
Daniel Veillard52dcab32001-10-30 12:51:17 +000052<li><a href="threads.html">Thread safety</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000053<li><a href="DOM.html">DOM Principles</a></li>
54<li><a href="example.html">A real example</a></li>
55<li><a href="contribs.html">Contributions</a></li>
56<li>
57<a href="xml.html">flat page</a>, <a href="site.xsl">stylesheet</a>
58</li>
59</ul></td></tr>
60</table>
61<table width="100%" border="0" cellspacing="1" cellpadding="3">
62<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Related links</b></center></td></tr>
Daniel Veillard8acca112002-01-21 09:52:27 +000063<tr><td bgcolor="#fffacd"><ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000064<li><a href="http://mail.gnome.org/archives/xml/">Mail archive</a></li>
65<li><a href="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li>
Daniel Veillard4a859202002-01-08 11:49:22 +000066<li><a href="http://phd.cs.unibo.it/gdome2/">DOM gdome2</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000067<li><a href="ftp://xmlsoft.org/">FTP</a></li>
68<li><a href="http://www.fh-frankfurt.de/~igor/projects/libxml/">Windows binaries</a></li>
Daniel Veillarddb9dfd92001-11-26 17:25:02 +000069<li><a href="http://garypennington.net/libxml2/">Solaris binaries</a></li>
Daniel Veillardc6271d22001-10-27 07:50:58 +000070<li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml">Bug Tracker</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000071</ul></td></tr>
72</table>
73</td></tr></table></td>
74<td valign="top" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%"><tr><td><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table border="0" cellpadding="3" cellspacing="1" width="100%"><tr><td bgcolor="#fffacd">
Daniel Veillardaf743792000-07-01 11:49:28 +000075<p>Table of Content:</p>
76<ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000077<li><a href="FAQ.html#Licence">Licence(s)</a></li>
78<li><a href="FAQ.html#Installati">Installation</a></li>
79<li><a href="FAQ.html#Compilatio">Compilation</a></li>
80<li><a href="FAQ.html#Developer">Developer corner</a></li>
Daniel Veillardaf743792000-07-01 11:49:28 +000081</ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000082<h3>
83<a name="Licence">Licence</a>(s)</h3>
Daniel Veillardaf743792000-07-01 11:49:28 +000084<ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000085<li>
86<em>Licensing Terms for libxml</em>
Daniel Veillardaf743792000-07-01 11:49:28 +000087 <p>libxml is released under 2 (compatible) licences:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000088<ul>
89<li>the <a href="http://www.gnu.org/copyleft/lgpl.html">LGPL</a>: GNU
Daniel Veillardaf743792000-07-01 11:49:28 +000090 Library General Public License</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000091<li>the <a href="http://www.w3.org/Consortium/Legal/copyright-software-19980720.html">W3C
Daniel Veillardaf743792000-07-01 11:49:28 +000092 IPR</a>: very similar to the XWindow licence</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +000093</ul>
94</li>
95<li>
96<em>Can I embed libxml in a proprietary application ?</em>
Daniel Veillardaf743792000-07-01 11:49:28 +000097 <p>Yes. The W3C IPR allows you to also keep proprietary the changes you
98 made to libxml, but it would be graceful to provide back bugfixes and
Daniel Veillard008186f2001-09-13 14:24:44 +000099 improvements as patches for possible incorporation in the main
100 development tree</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000101</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000102</ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000103<h3><a name="Installati">Installation</a></h3>
Daniel Veillardaf743792000-07-01 11:49:28 +0000104<ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000105<li>Unless you are forced to because your application links with a Gnome
Daniel Veillarde0c1d722001-03-21 10:28:36 +0000106 library requiring it, <strong><span style="background-color: #FF0000">Do
107 Not Use libxml1</span></strong>, use libxml2</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000108<li>
109<em>Where can I get libxml</em>
Daniel Veillard008186f2001-09-13 14:24:44 +0000110 ?
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000111 <p>The original distribution comes from <a href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> or <a href="ftp://ftp.gnome.org/pub/GNOME/stable/sources/libxml/">gnome.org</a>
112</p>
113<p>Most linux and Bsd distribution includes libxml, this is probably the
Daniel Veillardaf743792000-07-01 11:49:28 +0000114 safer way for end-users</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000115<p>David Doolin provides precompiled Windows versions at <a href="http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/ ">http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/</a>
116</p>
117</li>
118<li>
119<em>I see libxml and libxml2 releases, which one should I install ?</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000120 <ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000121<li>If you are not concerned by any existing backward compatibility
Daniel Veillard008186f2001-09-13 14:24:44 +0000122 with existing application, install libxml2 only</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000123<li>If you are not doing development, you can safely install both.
124 usually the packages <a href="http://rpmfind.net/linux/RPM/libxml.html">libxml</a> and <a href="http://rpmfind.net/linux/RPM/libxml2.html">libxml2</a> are
Daniel Veillardaf743792000-07-01 11:49:28 +0000125 compatible (this is not the case for development packages)</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000126<li>If you are a developer and your system provides separate packaging
Daniel Veillard008186f2001-09-13 14:24:44 +0000127 for shared libraries and the development components, it is possible
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000128 to install libxml and libxml2, and also <a href="http://rpmfind.net/linux/RPM/libxml-devel.html">libxml-devel</a>
129 and <a href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml2-devel</a>
Daniel Veillard480363b2001-03-16 22:04:15 +0000130 too for libxml2 &gt;= 2.3.0</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000131<li>If you are developing a new application, please develop against
Daniel Veillardaf743792000-07-01 11:49:28 +0000132 libxml2(-devel)</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000133</ul>
134</li>
135<li>
136<em>I can't install the libxml package it conflicts with libxml0</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000137 <p>You probably have an old libxml0 package used to provide the shared
138 library for libxml.so.0, you can probably safely remove it. Anyway the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000139 libxml packages provided on <a href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> provides
Daniel Veillardaf743792000-07-01 11:49:28 +0000140 libxml.so.0</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000141</li>
142<li>
143<em>I can't install the libxml(2) RPM package due to failed
Daniel Veillardc654d602001-05-01 12:42:26 +0000144 dependancies</em>
145 <p>The most generic solution is to refetch the latest src.rpm , and
146 rebuild it locally with</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000147<p><code>rpm --rebuild libxml(2)-xxx.src.rpm</code></p>
148<p>if everything goes well it will generate two binary rpm (one providing
Daniel Veillardc654d602001-05-01 12:42:26 +0000149 the shared libs and xmllint, and the other one, the -devel package
150 providing includes, static libraries and scripts needed to build
151 applications with libxml(2)) that you can install locally.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000152</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000153</ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000154<h3><a name="Compilatio">Compilation</a></h3>
Daniel Veillardaf743792000-07-01 11:49:28 +0000155<ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000156<li>
157<em>What is the process to compile libxml ?</em>
158 <p>As most UNIX libraries libxml follows the &quot;standard&quot;:</p>
159<p><code>gunzip -c xxx.tar.gz | tar xvf -</code></p>
160<p><code>cd libxml-xxxx</code></p>
161<p><code>./configure --help</code></p>
162<p>to see the options, then the compilation/installation proper</p>
163<p><code>./configure [possible options]</code></p>
164<p><code>make</code></p>
165<p><code>make install</code></p>
166<p>At that point you may have to rerun ldconfig or similar utility to
Daniel Veillardaf743792000-07-01 11:49:28 +0000167 update your list of installed shared libs.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000168</li>
169<li>
170<em>What other libraries are needed to compile/install libxml ?</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000171 <p>Libxml does not requires any other library, the normal C ANSI API
172 should be sufficient (please report any violation to this rule you may
173 find).</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000174<p>However if found at configuration time libxml will detect and use the
Daniel Veillardaf743792000-07-01 11:49:28 +0000175 following libs:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000176<ul>
177<li>
178<a href="http://www.info-zip.org/pub/infozip/zlib/">libz</a>
Daniel Veillard008186f2001-09-13 14:24:44 +0000179 : a highly portable and available widely compression library</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000180<li>iconv: a powerful character encoding conversion library. It's
Daniel Veillardaf743792000-07-01 11:49:28 +0000181 included by default on recent glibc libraries, so it doesn't need to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000182 be installed specifically on linux. It seems it's now <a href="http://www.opennc.org/onlinepubs/7908799/xsh/iconv.html">part
183 of the official UNIX</a> specification. Here is one <a href="http://clisp.cons.org/~haible/packages-libiconv.html">implementation
184 of the library</a> which source can be found <a href="ftp://ftp.ilog.fr/pub/Users/haible/gnu/">here</a>.</li>
185</ul>
186</li>
187<li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000188<em>make check fails on some platforms</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000189 <p>Sometime the regression tests results don't completely match the value
190 produced by the parser, and the makefile uses diff to print the delta. On
Daniel Veillard008186f2001-09-13 14:24:44 +0000191 some platforms the diff return breaks the compilation process, if the
192 diff is small this is probably not a serious problem</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000193</li>
194<li>
195<em>I use the CVS version and there is no configure script</em>
Daniel Veillard6761eee2001-06-11 10:29:38 +0000196 <p>The configure (and other Makefiles) are generated. Use the autogen.sh
197 script to regenerate the configure and Makefiles, like:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000198<p><code>./autogen.sh --prefix=/usr --disable-shared</code></p>
199</li>
200<li>
201<em>I have troubles when running make tests with gcc-3.0</em>
Daniel Veillard7b06bcb2001-06-22 16:03:51 +0000202 <p>It seems the initial release of gcc-3.0 has a problem with the
203 optimizer which miscompiles the URI module. Please use another
204 compiler</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000205</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000206</ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000207<h3>
208<a name="Developer">Developer</a> corner</h3>
Daniel Veillardaf743792000-07-01 11:49:28 +0000209<ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000210<li>
211<em>xmlDocDump() generates output on one line</em>
Daniel Veillard008186f2001-09-13 14:24:44 +0000212 <p>libxml will not <strong>invent</strong> spaces in the content of a
213 document since <strong>all spaces in the content of a document are
214 significant</strong>. If you build a tree from the API and want
215 indentation:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000216<ol>
217<li>the correct way is to generate those yourself too</li>
218<li>the dangerous way is to ask libxml to add those blanks to your
Daniel Veillard008186f2001-09-13 14:24:44 +0000219 content <strong>modifying the content of your document in the
220 process</strong>. The result may not be what you expect. There is
221 <strong>NO</strong> way to guarantee that such a modification won't
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000222 impact other part of the content of your document. See <a href="http://xmlsoft.org/html/libxml-parser.html#XMLKEEPBLANKSDEFAULT">xmlKeepBlanksDefault
223 ()</a> and <a href="http://xmlsoft.org/html/libxml-tree.html#XMLSAVEFORMATFILE">xmlSaveFormatFile
224 ()</a>
225</li>
226</ol>
227</li>
228<li>Extra nodes in the document:
Daniel Veillard62bccd52001-02-10 09:40:10 +0000229 <p><em>For a XML file as below:</em></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000230<pre>&lt;?xml version=&quot;1.0&quot;?&gt;
231&lt;PLAN xmlns=&quot;http://www.argus.ca/autotest/1.0/&quot;&gt;
232&lt;NODE CommFlag=&quot;0&quot;/&gt;
233&lt;NODE CommFlag=&quot;1&quot;/&gt;
Daniel Veillard62bccd52001-02-10 09:40:10 +0000234&lt;/PLAN&gt;</pre>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000235<p><em>after parsing it with the function
Daniel Veillard480363b2001-03-16 22:04:15 +0000236 pxmlDoc=xmlParseFile(...);</em></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000237<p><em>I want to the get the content of the first node (node with the
238 CommFlag=&quot;0&quot;)</em></p>
239<p><em>so I did it as following;</em></p>
240<pre>xmlNodePtr pode;
Daniel Veillard62bccd52001-02-10 09:40:10 +0000241pnode=pxmlDoc-&gt;children-&gt;children;</pre>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000242<p><em>but it does not work. If I change it to</em></p>
243<pre>pnode=pxmlDoc-&gt;children-&gt;children-&gt;next;</pre>
244<p><em>then it works. Can someone explain it to me.</em></p>
245<p>
246<p>In XML all characters in the content of the document are significant
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000247 <strong>including blanks and formatting line breaks</strong>.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000248<p>The extra nodes you are wondering about are just that, text nodes with
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000249 the formatting spaces wich are part of the document but that people tend
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000250 to forget. There is a function <a href="http://xmlsoft.org/html/libxml-parser.html">xmlKeepBlanksDefault
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000251 ()</a> to remove those at parse time, but that's an heuristic, and its
Daniel Veillard008186f2001-09-13 14:24:44 +0000252 use should be limited to case where you are sure there is no
253 mixed-content in the document.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000254</li>
255<li>
256<em>I get compilation errors of existing code like when accessing
Daniel Veillardaf743792000-07-01 11:49:28 +0000257 <strong>root</strong> or <strong>childs fields</strong> of nodes</em>
Daniel Veillard3f3b4f32001-03-13 15:12:39 +0000258 <p>You are compiling code developed for libxml version 1 and using a
259 libxml2 development environment. Either switch back to libxml v1 devel or
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000260 even better fix the code to compile with libxml2 (or both) by <a href="upgrade.html">following the instructions</a>.</p>
261</li>
262<li>
263<em>I get compilation errors about non existing
Daniel Veillardaf743792000-07-01 11:49:28 +0000264 <strong>xmlRootNode</strong> or <strong>xmlChildrenNode</strong>
265 fields</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000266 <p>The source code you are using has been <a href="upgrade.html">upgraded</a> to be able to compile with both libxml
Daniel Veillard008186f2001-09-13 14:24:44 +0000267 and libxml2, but you need to install a more recent version:
268 libxml(-devel) &gt;= 1.8.8 or libxml2(-devel) &gt;= 2.1.0</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000269</li>
270<li>
271<em>XPath implementation looks seriously broken</em>
Daniel Veillard008186f2001-09-13 14:24:44 +0000272 <p>XPath implementation prior to 2.3.0 was really incomplete, upgrade to
273 a recent version, the implementation and debug of libxslt generated fixes
Daniel Veillard480363b2001-03-16 22:04:15 +0000274 for most obvious problems.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000275</li>
276<li>
277<em>The example provided in the web page does not compile</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000278 <p>It's hard to maintain the documentation in sync with the code
Daniel Veillarde9202a02000-10-16 16:58:19 +0000279 &lt;grin/&gt; ...</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000280<p>Check the previous points 1/ and 2/ raised before, and send
Daniel Veillardaf743792000-07-01 11:49:28 +0000281 patches.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000282</li>
283<li>
284<em>Where can I get more examples and informations than in the web
Daniel Veillardaf743792000-07-01 11:49:28 +0000285 page</em>
286 <p>Ideally a libxml book would be nice. I have no such plan ... But you
287 can:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000288<ul>
289<li>check more deeply the <a href="html/libxml-lib.html">existing
290 generated doc</a>
291</li>
292<li>looks for examples of use for libxml function using the Gnome code
Daniel Veillardaf743792000-07-01 11:49:28 +0000293 for example the following will query the full Gnome CVs base for the
294 use of the <strong>xmlAddChild()</strong> function:
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000295 <p><a href="http://cvs.gnome.org/lxr/search?string=xmlAddChild">http://cvs.gnome.org/lxr/search?string=xmlAddChild</a></p>
296<p>This may be slow, a large hardware donation to the gnome project
Daniel Veillardaf743792000-07-01 11:49:28 +0000297 could cure this :-)</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000298</li>
299<li>
300<a href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gnome-xml">Browse
Daniel Veillard008186f2001-09-13 14:24:44 +0000301 the libxml source</a>
302 , I try to write code as clean and documented as possible, so
303 looking at it may be helpful</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000304</ul>
305</li>
306<li>What about C++ ?
Daniel Veillard008186f2001-09-13 14:24:44 +0000307 <p>libxml is written in pure C in order to allow easy reuse on a number
308 of platforms, including embedded systems. I don't intend to convert to
Daniel Veillardaf743792000-07-01 11:49:28 +0000309 C++.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000310<p>There is however a C++ wrapper provided by Ari Johnson
Daniel Veillarde9202a02000-10-16 16:58:19 +0000311 &lt;ari@btigate.com&gt; which may fullfill your needs:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000312<p>Website: <a href="http://lusis.org/~ari/xml++/">http://lusis.org/~ari/xml++/</a>
313</p>
314<p>Download: <a href="http://lusis.org/~ari/xml++/libxml++.tar.gz">http://lusis.org/~ari/xml++/libxml++.tar.gz</a>
315</p>
316</li>
317<li>How to validate a document a posteriori ?
Daniel Veillardaf743792000-07-01 11:49:28 +0000318 <p>It is possible to validate documents which had not been validated at
319 initial parsing time or documents who have been built from scratch using
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000320 the API. Use the <a href="http://xmlsoft.org/html/libxml-valid.html#XMLVALIDATEDTD">xmlValidateDtd()</a>
Daniel Veillardaf743792000-07-01 11:49:28 +0000321 function. It is also possible to simply add a Dtd to an existing
322 document:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000323<pre>xmlDocPtr doc; /* your existing document */
Daniel Veillardaf743792000-07-01 11:49:28 +0000324 xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000325 dtd-&gt;name = xmlStrDup((xmlChar*)&quot;root_name&quot;); /* use the given root */
Daniel Veillardaf743792000-07-01 11:49:28 +0000326
Daniel Veillarde9202a02000-10-16 16:58:19 +0000327 doc-&gt;intSubset = dtd;
328 if (doc-&gt;children == NULL) xmlAddChild((xmlNodePtr)doc, (xmlNodePtr)dtd);
329 else xmlAddPrevSibling(doc-&gt;children, (xmlNodePtr)dtd);
Daniel Veillardaf743792000-07-01 11:49:28 +0000330 </pre>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000331</li>
332<li>etc ...</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000333</ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000334<p>
Daniel Veillardc5d64342001-06-24 12:13:24 +0000335<p><a href="mailto:daniel@veillard.com">Daniel Veillard</a></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000336</td></tr></table></td></tr></table></td></tr></table></td>
337</tr></table></td></tr></table>
Daniel Veillardaf743792000-07-01 11:49:28 +0000338</body>
339</html>