http://swpat.ffii.org/Action against software patents http://www.gnome.org/Gnome2 Logo http://www.w3.org/StatusW3C Logo http://www.redhat.com/Red Hat Logo http://xmlsoft.org/Made with Libxml2 Logo The XML C parser and toolkit of Gnome
Reporting bugs and getting help
Main Menu index.htmlHome html/index.htmlReference Manual intro.htmlIntroduction FAQ.htmlFAQ docs.htmlDeveloper Menu bugs.htmlReporting bugs and getting help help.htmlHow to help downloads.htmlDownloads news.htmlReleases XMLinfo.htmlXML XSLT.htmlXSLT xmldtd.htmlValidation & DTDs encoding.htmlEncodings support catalog.htmlCatalog support namespaces.htmlNamespaces contribs.htmlContributions examples/index.htmlCode Examples html/index.htmlAPI Menu guidelines.htmlXML Guidelines ChangeLog.htmlRecent Changes Related links http://mail.gnome.org/archives/xml/Mail archive http://xmlsoft.org/XSLT/XSLT libxslt http://phd.cs.unibo.it/gdome2/DOM gdome2 http://www.aleksey.com/xmlsec/XML-DSig xmlsec ftp://xmlsoft.org/FTP http://www.zlatkovic.com/projects/libxml/Windows binaries http://www.blastwave.org/packages.php/libxml2Solaris binaries http://www.explain.com.au/oss/libxml2xslt.htmlMacOsX binaries http://libxmlplusplus.sourceforge.net/C++ bindings http://www.zend.com/php5/articles/php5-xmlphp.php#Heading4PHP bindings http://sourceforge.net/projects/libxml2-pas/Pascal bindings http://rubyforge.org/projects/xml-tools/Ruby bindings http://tclxml.sourceforge.net/Tcl bindings http://bugzilla.gnome.org/buglist.cgi?product=libxml2Bug Tracker 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 
http://bugzilla.gnome.org/buglist.cgi?product=libxml2Gnome
bug tracking database
 (make sure to use the "libxml2" 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 libxml2.
For small problems you can try to get help on IRC, the #xml channel on
irc.gnome.org (port 6667) usually have a few person subscribed which may help
(but there is no garantee and if a real issue is raised it should go on the
mailing-list for archival).
There is also a mailing-list mailto:xml@gnome.orgxml@gnome.org  for libxml, with an  http://mail.gnome.org/archives/xml/on-line archive  ( http://xmlsoft.org/messagesold ). To subscribe to this list,
please visit the 
http://mail.gnome.org/mailman/listinfo/xmlassociated Web  page and
follow the instructions. 
Do not send code, I won't debug it(but patches are really appreciated!).
Please note that with the current amount of virus and SPAM, sending mail
to the list without being subscribed won't work. There is *far too many
bounces* (in the order of a thousand a day !) I cannot approve them manually
anymore. If your mail to the list bounced waiting for administrator approval,
it is LOST ! Repost it and fix the problem triggering the error.
Check the following before
posting
:
Read the FAQ.htmlFAQ  and search.phpuse the
    search engine
 to get information related to your problem.  
Make sure you are ftp://xmlsoft.org/using a recent
    version
, and that the problem still shows up in a recent version.  
Check the http://mail.gnome.org/archives/xml/list
    archives
 to see if the problem was reported already. In this case
    there is probably a fix available, similarly check the 
http://bugzilla.gnome.org/buglist.cgi?product=libxml2registered
    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
    attachment)
Then send the bug with associated information to reproduce it to the mailto:xml@gnome.orgxml@gnome.org  list; if it's really libxml
related I will approve it. Please do not send mail to me directly, it makes
things really hard to track and in some cases I am not the best person to
answer a given question, ask on the list.
To be really clear about support:
Support or help requests MUST be sent to
    the list or on bugzilla
 in case of problems, so that the Question
    and Answers can be shared publicly. Failing to do so carries the implicit
    message "I want free support but I don't want to share the benefits with
    others" and is not welcome. I will automatically Carbon-Copy the
    xml@gnome.org mailing list for any technical reply made about libxml2 or
    libxslt.
  
There is no garantee of support, if
    your question remains unanswered after a week, repost it, making sure you
    gave all the detail needed and the information requested.
  
Failing to provide information as requested or double checking first
    for prior feedback also carries the implicit message "the time of the
    library maintainers is less valuable than my time" and might not be
    welcome.
Of course, bugs reported with a suggested patch for fixing them will
probably be processed faster than those without.
If you're looking for help, a quick look at http://mail.gnome.org/archives/xml/the list archive  may actually
provide the answer. I usually send source samples when answering libxml2
usage questions. The 
http://xmlsoft.org/html/book1.htmlauto-generated documentation  is
not as polished as I would like (i need to learn more about DocBook), but
it's a good starting point.
bugs.htmlDaniel Veillard 
