Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / libxml2 / c6271d208e0dc8768aac1dd7c162ddef121fbaa3 / . / doc / FAQ.html
blob: c14c3d7c9d67306bc5d0cfd7438a9564ffaee601 [file] [log] [blame]
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]2<html>
3<head>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]4<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
5<style type="text/css"><!--
6TD {font-size: 10pt; font-family: Verdana,Arial,Helvetica}
7BODY {font-size: 10pt; font-family: Verdana,Arial,Helvetica; margin-top: 5pt; margin-left: 0pt; margin-right: 0pt}
8H1 {font-size: 16pt; font-family: Verdana,Arial,Helvetica}
9H2 {font-size: 14pt; font-family: Verdana,Arial,Helvetica}
10H3 {font-size: 12pt; font-family: Verdana,Arial,Helvetica}
11A:link, A:visited, A:active { text-decoration: underline }
12--></style>
13<title>FAQ</title>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]14</head>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]15<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>
29<tr><td bgcolor="#fffacd"><ul style="margin-left: -2pt">
30<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>
38<li><a href="XML.html">XML</a></li>
39<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>
52<li><a href="DOM.html">DOM Principles</a></li>
53<li><a href="example.html">A real example</a></li>
54<li><a href="contribs.html">Contributions</a></li>
55<li>
56<a href="xml.html">flat page</a>, <a href="site.xsl">stylesheet</a>
57</li>
58</ul></td></tr>
59</table>
60<table width="100%" border="0" cellspacing="1" cellpadding="3">
61<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Related links</b></center></td></tr>
62<tr><td bgcolor="#fffacd"><ul style="margin-left: -2pt">
63<li><a href="http://mail.gnome.org/archives/xml/">Mail archive</a></li>
64<li><a href="http://xmlsoft.org/XSLT/">XSLT libxslt</a></li>
65<li><a href="http://www.cs.unibo.it/~casarini/gdome2/">DOM gdome2</a></li>
66<li><a href="ftp://xmlsoft.org/">FTP</a></li>
67<li><a href="http://www.fh-frankfurt.de/~igor/projects/libxml/">Windows binaries</a></li>
68<li><a href="http://pages.eidosnet.co.uk/~garypen/libxml/">Solaris binaries</a></li>
Daniel Veillardc6271d22001-10-27 07:50:58 +0000[diff] [blame^]69<li><a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml">Bug Tracker</a></li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]70</ul></td></tr>
71</table>
72</td></tr></table></td>
73<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 +0000[diff] [blame]74<p>Table of Content:</p>
75<ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]76<li><a href="FAQ.html#Licence">Licence(s)</a></li>
77<li><a href="FAQ.html#Installati">Installation</a></li>
78<li><a href="FAQ.html#Compilatio">Compilation</a></li>
79<li><a href="FAQ.html#Developer">Developer corner</a></li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]80</ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]81<h3>
82<a name="Licence">Licence</a>(s)</h3>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]83<ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]84<li>
85<em>Licensing Terms for libxml</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]86 <p>libxml is released under 2 (compatible) licences:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]87<ul>
88<li>the <a href="http://www.gnu.org/copyleft/lgpl.html">LGPL</a>: GNU
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]89 Library General Public License</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]90<li>the <a href="http://www.w3.org/Consortium/Legal/copyright-software-19980720.html">W3C
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]91 IPR</a>: very similar to the XWindow licence</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]92</ul>
93</li>
94<li>
95<em>Can I embed libxml in a proprietary application ?</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]96 <p>Yes. The W3C IPR allows you to also keep proprietary the changes you
97 made to libxml, but it would be graceful to provide back bugfixes and
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]98 improvements as patches for possible incorporation in the main
99 development tree</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]100</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]101</ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]102<h3><a name="Installati">Installation</a></h3>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]103<ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]104<li>Unless you are forced to because your application links with a Gnome
Daniel Veillarde0c1d722001-03-21 10:28:36 +0000[diff] [blame]105 library requiring it, <strong><span style="background-color: #FF0000">Do
106 Not Use libxml1</span></strong>, use libxml2</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]107<li>
108<em>Where can I get libxml</em>
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]109 ?
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]110 <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>
111</p>
112<p>Most linux and Bsd distribution includes libxml, this is probably the
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]113 safer way for end-users</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]114<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>
115</p>
116</li>
117<li>
118<em>I see libxml and libxml2 releases, which one should I install ?</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]119 <ul>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]120<li>If you are not concerned by any existing backward compatibility
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]121 with existing application, install libxml2 only</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]122<li>If you are not doing development, you can safely install both.
123 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 +0000[diff] [blame]124 compatible (this is not the case for development packages)</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]125<li>If you are a developer and your system provides separate packaging
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]126 for shared libraries and the development components, it is possible
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]127 to install libxml and libxml2, and also <a href="http://rpmfind.net/linux/RPM/libxml-devel.html">libxml-devel</a>
128 and <a href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml2-devel</a>
Daniel Veillard480363b2001-03-16 22:04:15 +0000[diff] [blame]129 too for libxml2 &gt;= 2.3.0</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]130<li>If you are developing a new application, please develop against
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]131 libxml2(-devel)</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]132</ul>
133</li>
134<li>
135<em>I can't install the libxml package it conflicts with libxml0</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]136 <p>You probably have an old libxml0 package used to provide the shared
137 library for libxml.so.0, you can probably safely remove it. Anyway the
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]138 libxml packages provided on <a href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> provides
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]139 libxml.so.0</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]140</li>
141<li>
142<em>I can't install the libxml(2) RPM package due to failed
Daniel Veillardc654d602001-05-01 12:42:26 +0000[diff] [blame]143 dependancies</em>
144 <p>The most generic solution is to refetch the latest src.rpm , and
145 rebuild it locally with</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]146<p><code>rpm --rebuild libxml(2)-xxx.src.rpm</code></p>
147<p>if everything goes well it will generate two binary rpm (one providing
Daniel Veillardc654d602001-05-01 12:42:26 +0000[diff] [blame]148 the shared libs and xmllint, and the other one, the -devel package
149 providing includes, static libraries and scripts needed to build
150 applications with libxml(2)) that you can install locally.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]151</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]152</ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]153<h3><a name="Compilatio">Compilation</a></h3>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]154<ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]155<li>
156<em>What is the process to compile libxml ?</em>
157 <p>As most UNIX libraries libxml follows the &quot;standard&quot;:</p>
158<p><code>gunzip -c xxx.tar.gz | tar xvf -</code></p>
159<p><code>cd libxml-xxxx</code></p>
160<p><code>./configure --help</code></p>
161<p>to see the options, then the compilation/installation proper</p>
162<p><code>./configure [possible options]</code></p>
163<p><code>make</code></p>
164<p><code>make install</code></p>
165<p>At that point you may have to rerun ldconfig or similar utility to
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]166 update your list of installed shared libs.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]167</li>
168<li>
169<em>What other libraries are needed to compile/install libxml ?</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]170 <p>Libxml does not requires any other library, the normal C ANSI API
171 should be sufficient (please report any violation to this rule you may
172 find).</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]173<p>However if found at configuration time libxml will detect and use the
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]174 following libs:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]175<ul>
176<li>
177<a href="http://www.info-zip.org/pub/infozip/zlib/">libz</a>
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]178 : a highly portable and available widely compression library</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]179<li>iconv: a powerful character encoding conversion library. It's
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]180 included by default on recent glibc libraries, so it doesn't need to
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]181 be installed specifically on linux. It seems it's now <a href="http://www.opennc.org/onlinepubs/7908799/xsh/iconv.html">part
182 of the official UNIX</a> specification. Here is one <a href="http://clisp.cons.org/~haible/packages-libiconv.html">implementation
183 of the library</a> which source can be found <a href="ftp://ftp.ilog.fr/pub/Users/haible/gnu/">here</a>.</li>
184</ul>
185</li>
186<li>
187<em>libxml does not compile with HP-UX's optional ANSI-C compiler</em>
188 <p>this is due to macro limitations. Try to add &quot; -Wp,-H16800 -Ae&quot; to the
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]189 CFLAGS</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]190<p>you can also install and use gcc instead or use a precompiled version
191 of libxml, both available from the <a href="http://hpux.cae.wisc.edu/hppd/auto/summary_all.html">HP-UX Porting
192 and Archive Centre</a>
193</p>
194</li>
195<li>
196<em>make check fails on some platforms</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]197 <p>Sometime the regression tests results don't completely match the value
198 produced by the parser, and the makefile uses diff to print the delta. On
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]199 some platforms the diff return breaks the compilation process, if the
200 diff is small this is probably not a serious problem</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]201</li>
202<li>
203<em>I use the CVS version and there is no configure script</em>
Daniel Veillard6761eee2001-06-11 10:29:38 +0000[diff] [blame]204 <p>The configure (and other Makefiles) are generated. Use the autogen.sh
205 script to regenerate the configure and Makefiles, like:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]206<p><code>./autogen.sh --prefix=/usr --disable-shared</code></p>
207</li>
208<li>
209<em>I have troubles when running make tests with gcc-3.0</em>
Daniel Veillard7b06bcb2001-06-22 16:03:51 +0000[diff] [blame]210 <p>It seems the initial release of gcc-3.0 has a problem with the
211 optimizer which miscompiles the URI module. Please use another
212 compiler</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]213</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]214</ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]215<h3>
216<a name="Developer">Developer</a> corner</h3>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]217<ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]218<li>
219<em>xmlDocDump() generates output on one line</em>
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]220 <p>libxml will not <strong>invent</strong> spaces in the content of a
221 document since <strong>all spaces in the content of a document are
222 significant</strong>. If you build a tree from the API and want
223 indentation:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]224<ol>
225<li>the correct way is to generate those yourself too</li>
226<li>the dangerous way is to ask libxml to add those blanks to your
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]227 content <strong>modifying the content of your document in the
228 process</strong>. The result may not be what you expect. There is
229 <strong>NO</strong> way to guarantee that such a modification won't
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]230 impact other part of the content of your document. See <a href="http://xmlsoft.org/html/libxml-parser.html#XMLKEEPBLANKSDEFAULT">xmlKeepBlanksDefault
231 ()</a> and <a href="http://xmlsoft.org/html/libxml-tree.html#XMLSAVEFORMATFILE">xmlSaveFormatFile
232 ()</a>
233</li>
234</ol>
235</li>
236<li>Extra nodes in the document:
Daniel Veillard62bccd52001-02-10 09:40:10 +0000[diff] [blame]237 <p><em>For a XML file as below:</em></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]238<pre>&lt;?xml version=&quot;1.0&quot;?&gt;
239&lt;PLAN xmlns=&quot;http://www.argus.ca/autotest/1.0/&quot;&gt;
240&lt;NODE CommFlag=&quot;0&quot;/&gt;
241&lt;NODE CommFlag=&quot;1&quot;/&gt;
Daniel Veillard62bccd52001-02-10 09:40:10 +0000[diff] [blame]242&lt;/PLAN&gt;</pre>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]243<p><em>after parsing it with the function
Daniel Veillard480363b2001-03-16 22:04:15 +0000[diff] [blame]244 pxmlDoc=xmlParseFile(...);</em></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]245<p><em>I want to the get the content of the first node (node with the
246 CommFlag=&quot;0&quot;)</em></p>
247<p><em>so I did it as following;</em></p>
248<pre>xmlNodePtr pode;
Daniel Veillard62bccd52001-02-10 09:40:10 +0000[diff] [blame]249pnode=pxmlDoc-&gt;children-&gt;children;</pre>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]250<p><em>but it does not work. If I change it to</em></p>
251<pre>pnode=pxmlDoc-&gt;children-&gt;children-&gt;next;</pre>
252<p><em>then it works. Can someone explain it to me.</em></p>
253<p>
254<p>In XML all characters in the content of the document are significant
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000[diff] [blame]255 <strong>including blanks and formatting line breaks</strong>.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]256<p>The extra nodes you are wondering about are just that, text nodes with
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000[diff] [blame]257 the formatting spaces wich are part of the document but that people tend
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]258 to forget. There is a function <a href="http://xmlsoft.org/html/libxml-parser.html">xmlKeepBlanksDefault
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000[diff] [blame]259 ()</a> to remove those at parse time, but that's an heuristic, and its
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]260 use should be limited to case where you are sure there is no
261 mixed-content in the document.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]262</li>
263<li>
264<em>I get compilation errors of existing code like when accessing
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]265 <strong>root</strong> or <strong>childs fields</strong> of nodes</em>
Daniel Veillard3f3b4f32001-03-13 15:12:39 +0000[diff] [blame]266 <p>You are compiling code developed for libxml version 1 and using a
267 libxml2 development environment. Either switch back to libxml v1 devel or
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]268 even better fix the code to compile with libxml2 (or both) by <a href="upgrade.html">following the instructions</a>.</p>
269</li>
270<li>
271<em>I get compilation errors about non existing
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]272 <strong>xmlRootNode</strong> or <strong>xmlChildrenNode</strong>
273 fields</em>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]274 <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 +0000[diff] [blame]275 and libxml2, but you need to install a more recent version:
276 libxml(-devel) &gt;= 1.8.8 or libxml2(-devel) &gt;= 2.1.0</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]277</li>
278<li>
279<em>XPath implementation looks seriously broken</em>
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]280 <p>XPath implementation prior to 2.3.0 was really incomplete, upgrade to
281 a recent version, the implementation and debug of libxslt generated fixes
Daniel Veillard480363b2001-03-16 22:04:15 +0000[diff] [blame]282 for most obvious problems.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]283</li>
284<li>
285<em>The example provided in the web page does not compile</em>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]286 <p>It's hard to maintain the documentation in sync with the code
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]287 &lt;grin/&gt; ...</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]288<p>Check the previous points 1/ and 2/ raised before, and send
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]289 patches.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]290</li>
291<li>
292<em>Where can I get more examples and informations than in the web
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]293 page</em>
294 <p>Ideally a libxml book would be nice. I have no such plan ... But you
295 can:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]296<ul>
297<li>check more deeply the <a href="html/libxml-lib.html">existing
298 generated doc</a>
299</li>
300<li>looks for examples of use for libxml function using the Gnome code
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]301 for example the following will query the full Gnome CVs base for the
302 use of the <strong>xmlAddChild()</strong> function:
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]303 <p><a href="http://cvs.gnome.org/lxr/search?string=xmlAddChild">http://cvs.gnome.org/lxr/search?string=xmlAddChild</a></p>
304<p>This may be slow, a large hardware donation to the gnome project
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]305 could cure this :-)</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]306</li>
307<li>
308<a href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gnome-xml">Browse
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]309 the libxml source</a>
310 , I try to write code as clean and documented as possible, so
311 looking at it may be helpful</li>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]312</ul>
313</li>
314<li>What about C++ ?
Daniel Veillard008186f2001-09-13 14:24:44 +0000[diff] [blame]315 <p>libxml is written in pure C in order to allow easy reuse on a number
316 of platforms, including embedded systems. I don't intend to convert to
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]317 C++.</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]318<p>There is however a C++ wrapper provided by Ari Johnson
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]319 &lt;ari@btigate.com&gt; which may fullfill your needs:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]320<p>Website: <a href="http://lusis.org/~ari/xml++/">http://lusis.org/~ari/xml++/</a>
321</p>
322<p>Download: <a href="http://lusis.org/~ari/xml++/libxml++.tar.gz">http://lusis.org/~ari/xml++/libxml++.tar.gz</a>
323</p>
324</li>
325<li>How to validate a document a posteriori ?
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]326 <p>It is possible to validate documents which had not been validated at
327 initial parsing time or documents who have been built from scratch using
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]328 the API. Use the <a href="http://xmlsoft.org/html/libxml-valid.html#XMLVALIDATEDTD">xmlValidateDtd()</a>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]329 function. It is also possible to simply add a Dtd to an existing
330 document:</p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]331<pre>xmlDocPtr doc; /* your existing document */
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]332 xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]333 dtd-&gt;name = xmlStrDup((xmlChar*)&quot;root_name&quot;); /* use the given root */
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]334
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]335 doc-&gt;intSubset = dtd;
336 if (doc-&gt;children == NULL) xmlAddChild((xmlNodePtr)doc, (xmlNodePtr)dtd);
337 else xmlAddPrevSibling(doc-&gt;children, (xmlNodePtr)dtd);
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]338 </pre>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]339</li>
340<li>etc ...</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]341</ol>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]342<p>
Daniel Veillardc5d64342001-06-24 12:13:24 +0000[diff] [blame]343<p><a href="mailto:daniel@veillard.com">Daniel Veillard</a></p>
Daniel Veillardb8cfbd12001-10-25 10:53:28 +0000[diff] [blame]344</td></tr></table></td></tr></table></td></tr></table></td>
345</tr></table></td></tr></table>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]346</body>
347</html>