xml.html

libxml,在UNIX/LINUX下非常重要的一个库,为XML相关应用提供方便.目前上载的是最新版本,若要取得最新版本,请参考里面的readme.

    examples</a> on how to use libxml.</li>
  <li><a href="examples/index.html">Code examples</a></li>
  <li>John Fleck's libxml2 tutorial: <a href="tutorial/index.html">html</a>
    or <a href="tutorial/xmltutorial.pdf">pdf</a>.</li>
  <li>If you need to parse large files, check the <a
    href="xmlreader.html">xmlReader</a> API tutorial</li>
  <li><a href="mailto:[e-mail]">James Henstridge</a> wrote <a
    href="http://www.daa.com.au/~james/gnome/xml-sax/xml-sax.html">some nice
    documentation</a> explaining how to use the libxml SAX interface.</li>
  <li>George Lebl wrote <a
    href="http://www-106.ibm.com/developerworks/library/l-gnome3/">an article
    for IBM developerWorks</a> about using libxml.</li>
  <li>Check <a href="http://cvs.gnome.org/lxr/source/gnome-xml/TODO">the TODO
    file</a>.</li>
  <li>Read the <a href="upgrade.html">1.x to 2.x upgrade path</a>
    description. If you are starting a new project using libxml you should
    really use the 2.x version.</li>
  <li>And don't forget to look at the <a
    href="http://mail.gnome.org/archives/xml/">mailing-list archive</a>.</li>
</ol>

<h2><a name="Reporting">Reporting bugs and getting help</a></h2>

<p>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 <a href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome
bug tracking database</a> (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.</p>

<p>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).</p>

<p>There is also a mailing-list <a
href="mailto:[e-mail]">[e-mail]</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,
please visit the <a
href="http://mail.gnome.org/mailman/listinfo/xml">associated Web</a> page and
follow the instructions. <strong>Do not send code, I won't debug it</strong>
(but patches are really appreciated!).</p>

<p>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.</p>

<p>Check the following <strong><span style="color: #FF0000">before
posting</span></strong>:</p>
<ul>
  <li>Read the <a href="FAQ.html">FAQ</a> and <a href="search.php">use the
    search engine</a> to get information related to your problem.</li>
  <li>Make sure you are <a href="ftp://xmlsoft.org/">using a recent
    version</a>, and that the problem still shows up in a recent version.</li>
  <li>Check the <a href="http://mail.gnome.org/archives/xml/">list
    archives</a> to see if the problem was reported already. In this case
    there is probably a fix available, similarly check the <a
    href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">registered
    open bugs</a>.</li>
  <li>Make sure you can reproduce the bug with xmllint or one of the test
    programs found in source in the distribution.</li>
  <li>Please send the command showing the error as well as the input (as an
    attachment)</li>
</ul>

<p>Then send the bug with associated information to reproduce it to the <a
href="mailto:[e-mail]">[e-mail]</a> 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.</p>

<p>To <span style="color: #E50000">be really clear about support</span>:</p>
<ul>
  <li>Support or help <span style="color: #E50000">requests MUST be sent to
    the list or on bugzilla</span> 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
    [e-mail] mailing list for any technical reply made about libxml2 or
    libxslt.</li>
  <li>There is <span style="color: #E50000">no garantee of support</span>, if
    your question remains unanswered after a week, repost it, making sure you
    gave all the detail needed and the information requested.</li>
  <li>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.</li>
</ul>

<p>Of course, bugs reported with a suggested patch for fixing them will
probably be processed faster than those without.</p>

<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
provide the answer. I usually send source samples when answering libxml2
usage questions. The <a
href="http://xmlsoft.org/html/book1.html">auto-generated documentation</a> is
not as polished as I would like (i need to learn more about DocBook), but
it's a good starting point.</p>

<h2><a name="help">How to help</a></h2>

<p>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 <a
href="http://mail.gnome.org/archives/xml/">archives </a>and the <a
href="http://bugzilla.gnome.org/buglist.cgi?product=libxml2">Gnome bug
database</a>:</p>
<ol>
  <li>Provide patches when you find problems.</li>
  <li>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</li>
  <li>Provide documentation fixes (either as patches to the code comments or
    as HTML diffs).</li>
  <li>Provide new documentations pieces (translations, examples, etc
  ...).</li>
  <li>Check the TODO file and try to close one of the items.</li>
  <li>Take one of the points raised in the archive or the bug database and
    provide a fix. <a href="mailto:[e-mail]">Get in touch with me
    </a>before to avoid synchronization problems and check that the suggested
    fix will fit in nicely :-)</li>
</ol>

<h2><a name="Downloads">Downloads</a></h2>

<p>The latest versions of libxml2 can be found on the <a
href="ftp://xmlsoft.org/">xmlsoft.org</a> server ( <a
href="http://xmlsoft.org/sources/">HTTP</a>, <a
href="ftp://xmlsoft.org/">FTP</a> and rsync are available), there is also
mirrors (<a href="ftp://ftp.planetmirror.com/pub/xmlsoft/">Australia</a>( <a
href="http://xmlsoft.planetmirror.com/">Web</a>), <a
href="ftp://fr.rpmfind.net/pub/libxml/">France</a>) or on the <a
href="ftp://ftp.gnome.org/pub/GNOME/MIRRORS.html">Gnome FTP server</a> as <a
href="ftp://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/">source archive</a>
, Antonin Sprinzl also provide <a href="ftp://gd.tuwien.ac.at/pub/libxml/">a
mirror in Austria</a>. (NOTE that you need both the <a
href="http://rpmfind.net/linux/RPM/libxml2.html">libxml(2)</a> and <a
href="http://rpmfind.net/linux/RPM/libxml2-devel.html">libxml(2)-devel</a>
packages installed to compile applications using libxml.)</p>

<p>You can find all the history of libxml(2) and libxslt releases in the <a
href="http://xmlsoft.org/sources/old/">old</a> directory. The precompiled
Windows binaries made by Igor Zlatovic are available in the <a
href="http://xmlsoft.org/sources/win32/">win32</a> directory.</p>

<p>Binary ports:</p>
<ul>
  <li>Red Hat RPMs for i386 are available directly on <a
    href="ftp://xmlsoft.org/">xmlsoft.org</a>, the source RPM will compile on
    any architecture supported by Red Hat.</li>
  <li><a href="mailto:[e-mail]">Igor Zlatkovic</a> is now the
    maintainer of the Windows port, <a
    href="http://www.zlatkovic.com/projects/libxml/index.html">he provides
    binaries</a>.</li>
  <li>Blastwave provides
    <a href="http://www.blastwave.org/packages.php/libxml2">Solaris binaries</a>.</li>
  <li><a href="mailto:[e-mail]">Steve Ball</a> provides <a
    href="http://www.zveno.com/open_source/libxml2xslt.html">Mac Os X
    binaries</a>.</li>
  <li>The HP-UX porting center provides <a
    href="http://hpux.connect.org.uk/hppd/hpux/Gnome/">HP-UX binaries</a></li>
</ul>

<p>If you know other supported binary ports, please <a
href="http://veillard.com/">contact me</a>.</p>

<p><a name="Snapshot">Snapshot:</a></p>
<ul>
  <li>Code from the W3C cvs base libxml2 module, updated hourly <a
    href="ftp://xmlsoft.org/libxml2-cvs-snapshot.tar.gz">libxml2-cvs-snapshot.tar.gz</a>.</li>
  <li>Docs, content of the web site, the list archive included <a
    href="ftp://xmlsoft.org/libxml-docs.tar.gz">libxml-docs.tar.gz</a>.</li>
</ul>

<p><a name="Contribs">Contributions:</a></p>

<p>I do accept external contributions, especially if compiling on another
platform,  get in touch with the list to upload the package, wrappers for
various languages have been provided, and can be found in the <a
href="python.html">bindings section</a></p>

<p>Libxml2 is also available from CVS:</p>
<ul>
  <li><p>The <a href="http://cvs.gnome.org/viewcvs/libxml2/">Gnome CVS
    base</a>. Check the <a
    href="http://developer.gnome.org/tools/cvs.html">Gnome CVS Tools</a>
    page; the CVS module is <b>libxml2</b>.</p>
  </li>
  <li>The <strong>libxslt</strong> module is also present there</li>
</ul>

<h2><a name="News">Releases</a></h2>

<p>Items not finished and worked on, get in touch with the list if you want
to help those</p>
<ul>
  <li>More testing on RelaxNG</li>
  <li>Finishing up <a href="http://www.w3.org/TR/xmlschema-1/">XML
  Schemas</a></li>
</ul>

<p>The <a href="ChangeLog.html">change log</a> describes the recents commits
to the <a href="http://cvs.gnome.org/viewcvs/libxml2/">CVS</a> code base.</p>

<p>There is the list of public releases:</p>

<h3>2.6.19: Apr 02 2005</h3>
<ul>
  <li> build fixes: drop .la from RPMs, --with-minimum build fix (William
       Brack), use XML_SOCKLEN_T instead of SOCKLEN_T because it breaks with
       AIX 5.3 compiler, fixed elfgcchack.h generation and PLT reduction
       code on Linux/ELF/gcc4</li>
  <li> bug fixes: schemas type decimal fixups (William Brack), xmmlint return
       code (Gerry Murphy), small schemas fixes (Matthew Burgess and
       GUY Fabrice), workaround "DAV:" namespace brokeness in c14n (Aleksey
       Sanin), segfault in Schemas (Kasimier Buchcik), Schemas attribute
       validation (Kasimier), Prop related functions and xmlNewNodeEatName
       (Rob Richards), HTML serialization of name attribute on a elements,
       Python error handlers leaks and improvement (Brent Hendricks), 
       uninitialized variable in encoding code, Relax-NG validation bug,
       potential crash if gnorableWhitespace is NULL, xmlSAXParseDoc and
       xmlParseDoc signatures, switched back to assuming UTF-8 in case 
       no encoding is given at serialization time</li>
  <li> improvements: lot of work on Schemas by Kasimier Buchcikii on facets
       checking and also mixed handling.</li>
  <li></li>
</ul>
<h3>2.6.18: Mar 13 2005</h3>
<ul>
  <li> build fixes: warnings (Peter Breitenlohner), testapi.c generation, 
       Bakefile support (Francesco Montorsi), Windows compilation (Joel Reed),
       some gcc4 fixes, HP-UX portability fixes (Rick Jones).</li>
  <li> bug fixes: xmlSchemaElementDump namespace (Kasimier Buchcik), push and
       xmlreader stopping on non-fatal errors, thread support for dictionnaries
       reference counting (Gary Coady), internal subset and push problem, 
       URL saved in xmlCopyDoc, various schemas bug fixes (Kasimier), Python
       paths fixup (Stephane Bidoul), xmlGetNodePath and namespaces, 
       xmlSetNsProp fix (Mike Hommey), warning should not count as error
       (William Brack), xmlCreatePushParser empty chunk, XInclude parser
       flags (William), cleanup FTP and HTTP code to reuse the uri parsing
       and IPv6 (William), xmlTextWriterStartAttributeNS fix (Rob Richards),
       XMLLINT_INDENT being empty (William), xmlWriter bugs (Rob Richards),
       multithreading on Windows (Rich Salz), xmlSearchNsByHref fix (Kasimier),
       Python binding leak (Brent Hendricks), aliasing bug exposed by gcc4
       on s390, xmlTextReaderNext bug (Rob Richards), Schemas decimal type
       fixes (William Brack), xmlByteConsumed static buffer (Ben Maurer).</li>
  <li> improvement: speedup parsing comments and DTDs, dictionnary support for
       hash tables, Schemas Identity constraints (Kasimier), streaming XPath
       subset, xmlTextReaderReadString added (Bjorn Reese), Schemas canonical
       values handling (Kasimier), add xmlTextReaderByteConsumed (Aron
       Stansvik), </li>