Gitiles
Code Review Sign In
gerrit-public.fairphone.software / fp2-dev / platform / external / libxml2 / c948420a0c6a46578a23da66ce837e112937251d / . / doc / bugs.html
blob: ca7fe707abd8d7eec4c3102d36e8d46c8672afb9 [file] [log] [blame]
Daniel Veillardc9484202001-10-24 12:35:52 +0000[diff] [blame^]1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
2<html>
3<head>
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}
11--></style>
12<title>Reporting bugs and getting help</title>
13</head>
14<body bgcolor="#8b7765" text="#000000" link="#000000" vlink="#000000">
15<table border="0" width="100%" cellpadding="5" cellspacing="0" align="center"><tr>
16<td width="180">
17<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>
18</td>
19<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">
20<h1>The XML C library for Gnome</h1>
21<h2>Reporting bugs and getting help</h2>
22</td></tr></table></td></tr></table></td>
23</tr></table>
24<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>
25<td valign="top" width="200" bgcolor="#8b7765"><table border="0" cellspacing="0" cellpadding="1" width="100%" bgcolor="#000000"><tr><td><table width="100%" border="0" cellspacing="1" cellpadding="3">
26<tr><td colspan="1" bgcolor="#eecfa1" align="center"><center><b>Main Menu</b></center></td></tr>
27<tr><td bgcolor="#fffacd"><ul style="margin-left: -2pt">
28<li><a href="index.html">Home</a></li>
29<li><a href="FAQ.html">FAQ</a></li>
30<li><a href="intro.html">Introduction</a></li>
31<li><a href="docs.html">Documentation</a></li>
32<li><a href="bugs.html">Reporting bugs and getting help</a></li>
33<li><a href="help.html">How to help</a></li>
34<li><a href="downloads.html">Downloads</a></li>
35<li><a href="news.html">News</a></li>
36<li><a href="XML.html">XML</a></li>
37<li><a href="XSLT.html">XSLT</a></li>
38<li><a href="architecture.html">An overview of libxml architecture</a></li>
39<li><a href="tree.html">The tree output</a></li>
40<li><a href="interface.html">The SAX interface</a></li>
41<li><a href="library.html">The XML library interfaces</a></li>
42<li><a href="entities.html">Entities or no entities</a></li>
43<li><a href="namespaces.html">Namespaces</a></li>
44<li><a href="valid.html">Validation, or are you afraid of DTDs ?</a></li>
45<li><a href="DOM.html">DOM Principles</a></li>
46<li><a href="example.html">A real example</a></li>
47<li><a href="contribs.html">Contributions</a></li>
48<li><a href="encoding.html">Encodings support</a></li>
49<li><a href="catalog.html">Catalogs support</a></li>
50<li><a href="xmlio.html">I/O interfaces</a></li>
51<li><a href="xmlmem.html">Memory interfaces</a></li>
52<li><a href="xmldtd.html">DTD support</a></li>
53<li><a href="xml.html">flat page</a></li>
54</ul></td></tr>
55</table></td></tr></table></td>
56<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">
57<p>Well, bugs or missing features are always possible, and I will make a
58point of fixing them in a timely fashion. The best way to report a bug is to
59use the <a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml">Gnome
60bug tracking database</a> (make sure to use the &quot;libxml&quot; module name). I look
61at reports there regularly and it's good to have a reminder when a bug is
62still open. Check the <a href="http://bugzilla.gnome.org/bugwritinghelp.html">instructions on
63reporting bugs</a> and be sure to specify that the bug is for the package
64libxml.</p>
65<p>There is also a mailing-list <a href="mailto:xml@gnome.org">xml@gnome.org</a> for libxml, with an <a href="http://mail.gnome.org/archives/xml/">on-line archive</a> (<a href="http://xmlsoft.org/messages">old</a>). To subscribe to this list,
66please visit the <a href="http://mail.gnome.org/mailman/listinfo/xml">associated Web</a> page and
67follow the instructions. <strong>Do not send code, I won't debug it</strong>
68(but patches are really appreciated!).</p>
69<p>Check the following <strong><span style="color: #FF0000">before
70posting</span></strong>:</p>
71<ul>
72<li>read the <a href="FAQ.html">FAQ</a>
73</li>
74<li>make sure you are <a href="ftp://xmlsoft.org/">using a recent
75 version</a>, and that the problem still shows up in those</li>
76<li>check the <a href="http://mail.gnome.org/archives/xml/">list
77 archives</a> to see if the problem was reported already, in this case
78 there is probably a fix available, similary check the <a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml">registered
79 open bugs</a>
80</li>
81<li>make sure you can reproduce the bug with xmllint or one of the test
82 programs found in source in the distribution</li>
83<li>Please send the command showing the error as well as the input (as an
84 attachement)</li>
85</ul>
86<p>Then send the bug with associated informations to reproduce it to the <a href="mailto:xml@gnome.org">xml@gnome.org</a> list; if it's really libxml
87related I will approve it.. Please do not send me mail directly, it makes
88things really harder to track and in some cases I'm not the best person to
89answer a given question, ask the list instead.</p>
90<p>Of course, bugs reported with a suggested patch for fixing them will
91probably be processed faster.</p>
92<p>If you're looking for help, a quick look at <a href="http://mail.gnome.org/archives/xml/">the list archive</a> may actually
93provide the answer, I usually send source samples when answering libxml usage
94questions. The <a href="http://xmlsoft.org/html/book1.html">auto-generated
95documentantion</a> is not as polished as I would like (i need to learn more
96about Docbook), but it's a good starting point.</p>
97<p><a href="mailto:daniel@veillard.com">Daniel Veillard</a></p>
98</td></tr></table></td></tr></table></td></tr></table></td>
99</tr></table></td></tr></table>
100</body>
101</html>