Yes. The W3C IPR allows you to also keep proprietary the changes you made to libxml, but it would be graceful to provide back bugfixes and - improvements as patches for possible incorporation in the main development - tree
+ improvements as patches for possible incorporation in the main + development treeThe original distribution comes from rpmfind.net or gnome.org
@@ -64,16 +65,16 @@ href="http://xmlsoft.org/messages/">http://xmlsoft.org/messages/However if found at configuration time libxml will detect and use the following libs:
Sometime the regression tests results don't completely match the value produced by the parser, and the makefile uses diff to print the delta. On - some platforms the diff return breaks the compilation process, if the diff - is small this is probably not a serious problem
+ some platforms the diff return breaks the compilation process, if the + diff is small this is probably not a serious problemThe configure (and other Makefiles) are generated. Use the autogen.sh @@ -162,6 +163,24 @@ href="http://xmlsoft.org/messages/">http://xmlsoft.org/messages/
libxml will not invent spaces in the content of a + document since all spaces in the content of a document are + significant. If you build a tree from the API and want + indentation:
+For a XML file as below:
<?xml version="1.0"?> @@ -187,8 +206,8 @@ pnode=pxmlDoc->children->children;to forget. There is a function xmlKeepBlanksDefault () to remove those at parse time, but that's an heuristic, and its - use should be limited to case where you are sure there is no mixed-content - in the document. + use should be limited to case where you are sure there is no + mixed-content in the document.
The source code you are using has been upgraded to be able to compile with both libxml - and libxml2, but you need to install a more recent version: libxml(-devel) - >= 1.8.8 or libxml2(-devel) >= 2.1.0
+ and libxml2, but you need to install a more recent version: + libxml(-devel) >= 1.8.8 or libxml2(-devel) >= 2.1.0XPath implementation prior to 2.3.0 was really incomplete, upgrade to a - recent version, the implementation and debug of libxslt generated fixes +
XPath implementation prior to 2.3.0 was really incomplete, upgrade to + a recent version, the implementation and debug of libxslt generated fixes for most obvious problems.
libxml is written in pure C in order to allow easy reuse on a number of - platforms, including embedded systems. I don't intend to convert to +
libxml is written in pure C in order to allow easy reuse on a number + of platforms, including embedded systems. I don't intend to convert to C++.
There is however a C++ wrapper provided by Ari Johnson <ari@btigate.com> which may fullfill your needs:
diff --git a/doc/xml.html b/doc/xml.html index 55cb7417..2f66881f 100644 --- a/doc/xml.html +++ b/doc/xml.html @@ -155,8 +155,10 @@ href="http://mail.gnome.org/mailman/listinfo/xml">associated Web page and follow the instructions. Do not send code, I won't debug it (but patches are really appreciated!). -Check the following too before posting:
+Check the following before +posting:
Alternatively, you can just send the bug to the 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 especially -for portability problem, 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.
+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.
@@ -1687,6 +1688,6 @@ Gnome CVS base under gnome-xml/example -$Id: xml.html,v 1.108 2001/08/24 00:49:01 veillard Exp $
+$Id: xml.html,v 1.109 2001/09/12 18:51:29 veillard Exp $