http://swpat.ffii.org/
Action against software patents
http://www.gnome.org/
Gnome2 Logo
http://www.w3.org/Status
W3C Logo
http://www.redhat.com/
Red Hat Logo
http://xmlsoft.org/
Made with Libxml2 Logo
The XML C parser and toolkit of Gnome
How to help
Main Menu
index.html
Home
http://xmlsoft.org/wiki
Wiki
html/index.html
Reference Manual
intro.html
Introduction
FAQ.html
FAQ
docs.html
Developer Menu
bugs.html
Reporting bugs and getting help
help.html
How to help
downloads.html
Downloads
news.html
Releases
XMLinfo.html
XML
XSLT.html
XSLT
xmldtd.html
Validation & DTDs
encoding.html
Encodings support
catalog.html
Catalog support
namespaces.html
Namespaces
contribs.html
Contributions
examples/index.html
Code Examples
html/index.html
API Menu
guidelines.html
XML Guidelines
ChangeLog.html
Recent 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/libxml2
Solaris binaries
http://www.explain.com.au/oss/libxml2xslt.html
MacOsX binaries
http://libxmlplusplus.sourceforge.net/
C++ bindings
http://www.zend.com/php5/articles/php5-xmlphp.php#Heading4
PHP 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=libxml2
Bug Tracker
You can help the project in various ways, the best thing to do first is to
subscribe to the mailing-list as explained before, check the
http://mail.gnome.org/archives/xml/
archives
and the
http://bugzilla.gnome.org/buglist.cgi?product=libxml2
Gnome bug
database
:
Provide patches when you find problems.
Provide the diffs when you port libxml2 to a new platform. They may not
be integrated in all cases but help pinpointing portability problems
and
Provide documentation fixes (either as patches to the code comments or
as HTML diffs).
Provide new documentations pieces (translations, examples, etc
...).
Check the TODO file and try to close one of the items.
Take one of the points raised in the archive or the bug database and
provide a fix.
mailto:daniel@veillard.com
Get in touch with me
before to avoid synchronization problems and check that the suggested
fix will fit in nicely :-)
bugs.html
Daniel Veillard
