|
Well, bugs or missing features are always possible, and I will make a
point of fixing them in a timely fashion. The best way to report a bug is to
use the Gnome
bug tracking database (make sure to use the "libxml" module name). I look
at reports there regularly and it's good to have a reminder when a bug is
still open. Be sure to specify that the bug is for the package libxml.
There is also a mailing-list xml@gnome.org for libxml, with an on-line archive (old). To subscribe to this list,
please visit the associated Web page and
follow the instructions. Do not send code, I won't debug it
(but patches are really appreciated!).
Check the following before
posting:
- read the FAQ
- make sure you are using a recent
version, and that the problem still shows up in those
- check the list
archives to see if the problem was reported already, in this case
there is probably a fix available, similary check the registered
open bugs
- make sure you can reproduce the bug with xmllint or one of the test
programs found in source in the distribution
- Please send the command showing the error as well as the input (as an
attachement)
Then send the bug with associated informations to reproduce it to the xml@gnome.org list; if it's really libxml
related I will approve it.. Please do not send me mail directly, it makes
things really harder to track and in some cases I'm not the best person to
answer a given question, ask the list instead.
Of course, bugs reported with a suggested patch for fixing them will
probably be processed faster.
If you're looking for help, a quick look at the list archive may actually
provide the answer, I usually send source samples when answering libxml usage
questions. The auto-generated
documentantion is not as polished as I would like (i need to learn more
about Docbook), but it's a good starting point.
Daniel Veillard
| 
