Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / libxml2 / 7f41b3eb5b4f0ee45e58f6bc2c2899cad065063c / . / doc / FAQ.html
blob: 765f60e14b908f25a107d4b0a5584851add11a99 [file] [log] [blame]
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000[diff] [blame^]1<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]3<html>
4<head>
5 <title>Libxml Frequently asqued Questions</title>
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000[diff] [blame^]6 <meta name="GENERATOR" content="amaya V4.1">
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]7 <meta http-equiv="Content-Type" content="text/html">
8</head>
9
10<body bgcolor="#ffffff">
11<h1 align="center">Libxml Frequently Asqued Questions</h1>
12
13<p>Location: <a
14href="http://xmlsoft.org/FAQ.html">http://xmlsoft.org/FAQ.html</a></p>
15
16<p>Libxml home page: <a href="http://xmlsoft.org/">http://xmlsoft.org/</a></p>
17
18<p>Mailing-list archive: <a
19href="http://xmlsoft.org/messages/">http://xmlsoft.org/messages/</a></p>
20
Daniel Veillardbe40c8b2000-07-14 12:10:59 +0000[diff] [blame]21<p>Version: $Revision$</p>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]22
23<p>Table of Content:</p>
24<ul>
25 <li><a href="#Licence">Licence(s)</a></li>
26 <li><a href="#Installati">Installation</a></li>
27 <li><a href="#Compilatio">Compilation</a></li>
28 <li><a href="#Developper">Developper corner</a></li>
29</ul>
30
31<h2><a name="Licence">Licence</a>(s)</h2>
32<ol>
33 <li><em>Licensing Terms for libxml</em>
34 <p>libxml is released under 2 (compatible) licences:</p>
35 <ul>
36 <li>the <a href="http://www.gnu.org/copyleft/lgpl.html">LGPL</a>: GNU
37 Library General Public License</li>
38 <li>the <a
39 href="http://www.w3.org/Consortium/Legal/copyright-software-19980720.html">W3C
40 IPR</a>: very similar to the XWindow licence</li>
41 </ul>
42 </li>
43 <li><em>Can I embed libxml in a proprietary application ?</em>
44 <p>Yes. The W3C IPR allows you to also keep proprietary the changes you
45 made to libxml, but it would be graceful to provide back bugfixes and
46 improvements as patches for possible incorporation in the main
47 developement tree</p>
48 </li>
49</ol>
50
51<h2><a name="Installati">Installation</a></h2>
52<ol>
53 <li><em>Where can I get libxml</em> ?
54 <p>The original distribution comes from <a
55 href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> or <a
56 href="ftp://ftp.gnome.org/pub/GNOME/stable/sources/libxml/">gnome.org</a></p>
57 <p>Most linux and Bsd distribution includes libxml, this is probably the
58 safer way for end-users</p>
59 <p>David Doolin provides precompiled Windows versions at <a
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]60 href="http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/ ">http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/</a></p>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]61 </li>
62 <li><em>I see libxml and libxml2 releases, which one should I install ?</em>
63 <ul>
64 <li>If you are not concerned by any existing backward compatibility with
65 existing application, install libxml2 only</li>
66 <li>If you are not doing development, you can safely install both.
67 usually the packages <a
68 href="http://rpmfind.net/linux/RPM/libxml.html">libxml</a> and <a
69 href="http://rpmfind.net/linux/RPM/libxml2.html">libxml2</a> are
70 compatible (this is not the case for development packages)</li>
71 <li>If you are a developper and your system provides separate packaging
72 for shared libraries and the development components, it is possible to
73 install libxml and libxml2, and depending on your development needs
74 have either <a
75 href="http://rpmfind.net/linux/RPM/libxml-devel.html">libxml-devel</a>
76 or <a
77 href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml2-devel</a>
78 too</li>
79 <li>If you are developping a new application, please develop against
80 libxml2(-devel)</li>
81 </ul>
82 </li>
83 <li><em>I can't install the libxml package it conflicts with libxml0</em>
84 <p>You probably have an old libxml0 package used to provide the shared
85 library for libxml.so.0, you can probably safely remove it. Anyway the
86 libxml packages provided on <a
87 href="ftp://rpmfind.net/pub/libxml/">rpmfind.net</a> provides
88 libxml.so.0</p>
89 </li>
90</ol>
91
92<h2><a name="Compilatio">Compilation</a></h2>
93<ol>
94 <li><em>What is the process to compile libxml ?</em>
95 <p>As most UNIX libraries libxml follows the "standard":</p>
96 <p><code>gunzip -c xxx.tar.gz | tar xvf -</code></p>
97 <p><code>cd libxml-xxxx</code></p>
98 <p><code>./configure --help</code></p>
99 <p>to see the options, then the compilation/installation proper</p>
100 <p><code>./configure [possible options]</code></p>
101 <p><code>make</code></p>
102 <p><code>make install</code></p>
103 <p>At that point you may have to rerun ldconfig or similar utility to
104 update your list of installed shared libs.</p>
105 </li>
106 <li><em>What other libraries are needed to compile/install libxml ?</em>
107 <p>Libxml does not requires any other library, the normal C ANSI API
108 should be sufficient (please report any violation to this rule you may
109 find).</p>
110 <p>However if found at configuration time libxml will deect and use the
111 following libs:</p>
112 <ul>
113 <li><a href="http://www.info-zip.org/pub/infozip/zlib/">libz</a>: a
114 highly portable and available widely compression library</li>
115 <li>iconv: a powerful character encoding conversion library. It's
116 included by default on recent glibc libraries, so it doesn't need to
117 be installed specifically on linux. It seems it's now <a
118 href="http://www.opennc.org/onlinepubs/7908799/xsh/iconv.html">part of
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]119 the official UNIX</a> specification. Here is one <a
120 href="http://clisp.cons.org/~haible/packages-libiconv.html">implementation
121 of the library</a> which source can be found <a
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000[diff] [blame^]122 href="ftp://ftp.ilog.fr/pub/Users/haible/gnu/">here</a>.</li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]123 </ul>
124 </li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]125 <li><em>libxml does not compile with HP-UX's optional ANSI-C compiler</em>
126 <p>this is due to macro limitations. Try to add " -Wp,-H16800 -Ae" to the
127 CFLAGS</p>
128 <p>you can also install and use gcc instead or use a precompiled version
129 of libxml, both available from the <a
130 href="http://hpux.cae.wisc.edu/hppd/auto/summary_all.html">HP-UX Porting
131 and Archive Centre</a></p>
132 </li>
133 <li><em>make check fails on some platforms</em>
134 <p>Sometime the regression tests results don't completely match the value
135 produced by the parser, and the makefile uses diff to print the delta. On
136 some platforms the diff return breaks the compilation process, if the diff
137 is small this is probably not a serious problem</p>
138 </li>
139</ol>
140
141<h2><a name="Developper">Developper</a> corner</h2>
142<ol>
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000[diff] [blame^]143 <li>Extra nodes in the document:
144 <p><em>For a XML file as below:</em><br>
145 </p>
146 <p><code><em>&lt;?xml version="1.0"?&gt;</em></code></p>
147 <p><code><em>&lt;PLAN
148 xmlns="http://www.argus.ca/autotest/1.0/"&gt;</em></code></p>
149 <p><code><em>&lt;NODE CommFlag="0"/&gt;</em></code></p>
150 <p><code><em>&lt;NODE CommFlag="1"/&gt;</em></code></p>
151 <p><code><em>&lt;/PLAN&gt; </em></code></p>
152 <p><em>after parsing it with the function
153 pxmlDoc=xmlParseFile(...);</em></p>
154 <p><em>I want to the get the content of the first node (node with the
155 CommFlag="0")</em></p>
156 <p><em>so I did it as following;</em></p>
157 <p><code><em>xmlNodePtr pode;</em></code></p>
158 <p><code><em>pnode=pxmlDoc-&gt;children-&gt;children;</em></code></p>
159 <p><em>but it does not work. If I change it to</em></p>
160 <p><code><em>pnode=pxmlDoc-&gt;children-&gt;children-&gt;next;</em></code></p>
161 <p><em>then it works. Can someone explain it to me.</em></p>
162 <p></p>
163 <p>In XML all characters in the content of the document are signifficant
164 <strong>including blanks and formatting line breaks</strong>.</p>
165 <p>The extra nodes you are wondering about are just that, text nodes with
166 the formatting spaces wich are part of the document but that people tend
167 to forget. There is a function <a
168 href="http://xmlsoft.org/html/libxml-parser.html">xmlKeepBlanksDefault
169 ()</a> to remove those at parse time, but that's an heuristic, and its
170 use should be limited to case where you are sure there is no mixed-content
171 in the document.</p>
172 </li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]173 <li><em>I get compilation errors of existing code like when accessing
174 <strong>root</strong> or <strong>childs fields</strong> of nodes</em>
175 <p>You are compiling code developped for libxml version 1 and using a
176 libxml2 developement environment. Either switch back to libxml v1 devel or
177 even better fix the code to compile with libxml2 (or both) by <a
178 href="upgrade.html">following the instructions</a>.</p>
179 </li>
180 <li><em>I get compilation errors about non existing
181 <strong>xmlRootNode</strong> or <strong>xmlChildrenNode</strong>
182 fields</em>
183 <p>The source code you are using has been <a
184 href="upgrade.html">upgraded</a> to be able to compile with both libxml
185 and libxml2, but you need to install a more recent version: libxml(-devel)
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]186 &gt;= 1.8.8 or libxml2(-devel) &gt;= 2.1.0</p>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]187 </li>
188 <li><em>XPath implementation looks seriously broken</em>
Daniel Veillard7f41b3e2001-02-10 09:35:37 +0000[diff] [blame^]189 <p>XPath implementation prior to 2.3.0 was really incomplete, upgrade to a
190 recent version, the implementation and debug of libxslt generated fixes
191 for most obvious problems. </p>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]192 </li>
193 <li><em>The example provided in the web page does not compile</em>
194 <p>It's hard to maintain the documentation in sync with the code
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]195 &lt;grin/&gt; ...</p>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]196 <p>Check the previous points 1/ and 2/ raised before, and send
197 patches.</p>
198 </li>
199 <li><em>Where can I get more examples and informations than in the web
200 page</em>
201 <p>Ideally a libxml book would be nice. I have no such plan ... But you
202 can:</p>
203 <ul>
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]204 <li>check more deeply the <a href="html/libxml-lib.html">existing
205 generated doc</a></li>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]206 <li>looks for examples of use for libxml function using the Gnome code
207 for example the following will query the full Gnome CVs base for the
208 use of the <strong>xmlAddChild()</strong> function:
209 <p><a
210 href="http://cvs.gnome.org/lxr/search?string=xmlAddChild">http://cvs.gnome.org/lxr/search?string=xmlAddChild</a></p>
211 <p>This may be slow, a large hardware donation to the gnome project
212 could cure this :-)</p>
213 </li>
214 <li><a
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]215 href="http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnome&amp;dir=gnome-xml">Browse
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]216 the libxml source</a>, I try to write code as clean and documented as
217 possible, so looking at it may be helpful</li>
218 </ul>
219 </li>
220 <li>What about C++ ?
221 <p>libxml is written in pure C in order to allow easy reuse on a number of
222 platforms, including embedded systems. I don't intend to convert to
223 C++.</p>
224 <p>There is however a C++ wrapper provided by Ari Johnson
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]225 &lt;ari@btigate.com&gt; which may fullfill your needs:</p>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]226 <p>Website: <a
227 href="http://lusis.org/~ari/xml++/">http://lusis.org/~ari/xml++/</a></p>
228 <p>Download: <a
229 href="http://lusis.org/~ari/xml++/libxml++.tar.gz">http://lusis.org/~ari/xml++/libxml++.tar.gz</a></p>
230 </li>
231 <li>How to validate a document a posteriori ?
232 <p>It is possible to validate documents which had not been validated at
233 initial parsing time or documents who have been built from scratch using
234 the API. Use the <a
Daniel Veillard9cb5ff42001-01-29 08:22:21 +0000[diff] [blame]235 href="http://xmlsoft.org/html/libxml-valid.html#XMLVALIDATEDTD">xmlValidateDtd()</a>
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]236 function. It is also possible to simply add a Dtd to an existing
237 document:</p>
238 <pre>xmlDocPtr doc; /* your existing document */
239 xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]240 dtd-&gt;name = xmlStrDup((xmlChar*)"root_name"); /* use the given root */
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]241
Daniel Veillarde9202a02000-10-16 16:58:19 +0000[diff] [blame]242 doc-&gt;intSubset = dtd;
243 if (doc-&gt;children == NULL) xmlAddChild((xmlNodePtr)doc, (xmlNodePtr)dtd);
244 else xmlAddPrevSibling(doc-&gt;children, (xmlNodePtr)dtd);
Daniel Veillardaf743792000-07-01 11:49:28 +0000[diff] [blame]245 </pre>
246 </li>
247 <li>etc ...</li>
248</ol>
249
250<p><a href="mailto:Daniel.Veillard@w3.org">Daniel Veillard</a></p>
251
252<p>$Id$</p>
253</body>
254</html>