From c0801af9f83bdf00d69e540d4fa7ba1f5bda75e6 Mon Sep 17 00:00:00 2001
From: Daniel Veillard Yes. The MIT License allows you to also keep proprietary the changes
- you made to libxml, but it would be graceful to provide back bug fixes and
- improvements as patches for possible incorporation in the main
+ you made to libxml, but it would be graceful to provide back bug fixes
+ and improvements as patches for possible incorporation in the main
development tree More over when compiled on an Unix platform with iconv support the full set
-of encodings supported by iconv can be instantly be used by libxml. On a
+ More over when compiled on an Unix platform with iconv support the full
+set of encodings supported by iconv can be instantly be used by libxml. On a
linux machine with glibc-2.1 the list of supported encodings and aliases fill
3 full pages, and include UCS-4, the full set of ISO-Latin encodings, and the
various Japanese ones.
The namespace value has to be an absolute URL, but the URL doesn't have to
point to any existing resource on the Web. It will bind all the element and
-attributes with that URL. I suggest to use an URL within a domain you control,
-and that the URL should contain some kind of version information if possible.
-For example, "http://www.gnome.org/gnumeric/1.0/"
is a good
-namespace scheme.
"http://www.gnome.org/gnumeric/1.0/"
is a
+good namespace scheme.
Then when you load a file, make sure that a namespace carrying the version-independent prefix is installed on the root element of your document, and if the version information don't match something you know, warn the user diff --git a/doc/news.html b/doc/news.html index f62d95ca..88b6a928 100644 --- a/doc/news.html +++ b/doc/news.html @@ -93,6 +93,17 @@ to test those
This release is both a bug fix release and also contains the early XML Schemas structures and datatypes code, beware, all @@ -573,8 +584,8 @@ it's actually not compiled in by default. The real fixes are:
The distribution includes a set of Python bindings, which are guaranteed to -be maintained as part of the library in the future, though the Python +
The distribution includes a set of Python bindings, which are guaranteed +to be maintained as part of the library in the future, though the Python interface have not yet reached the maturity of the C API.
To install the Python bindings there are 2 options:
name
: returns the node nametype
: returns a string indicating the node
- typetype
: returns a string indicating the node type
content
: returns the content of the node, it is based on
xmlNodeGetContent() and hence is recursive.Yes. The MIT License allows you to also keep proprietary the changes - you made to libxml, but it would be graceful to provide back bug fixes and - improvements as patches for possible incorporation in the main + you made to libxml, but it would be graceful to provide back bug fixes + and improvements as patches for possible incorporation in the main development tree
This release is both a bug fix release and also contains the early XML @@ -1116,8 +1128,8 @@ it's actually not compiled in by default. The real fixes are:
The distribution includes a set of Python bindings, which are guaranteed to -be maintained as part of the library in the future, though the Python +
The distribution includes a set of Python bindings, which are guaranteed +to be maintained as part of the library in the future, though the Python interface have not yet reached the maturity of the C API.
To install the Python bindings there are 2 options:
@@ -1468,8 +1480,7 @@ prefix is removed and the casing convention are kept). All node seen at the binding level share the same subset of accessors:name
: returns the node nametype
: returns a string indicating the node
- typetype
: returns a string indicating the node typecontent
: returns the content of the node, it is based on
xmlNodeGetContent() and hence is recursive.parent
, children
, last
,
@@ -1857,8 +1868,8 @@ interface.
DTD is the acronym for Document Type Definition. This is a description of the content for a family of XML files. This is part of the XML 1.0 -specification, and allows to describe and check that a given document instance -conforms to a set of rules detailing its structure and content.
+specification, and allows to describe and check that a given document +instance conforms to a set of rules detailing its structure and content.Validation is the process of checking a document against a DTD (more generally against a set of construction rules).
@@ -1925,9 +1936,9 @@ is placed in the filemydtd
in the subdirectory
<!ELEMENT spec (front, body, back?)>
it also expresses that the spec element contains one front
,
-one body
and one optional back
children elements
-in this order. The declaration of one element of the structure and its
-content are done in a single declaration. Similarly the following declares
+one body
and one optional back
children elements in
+this order. The declaration of one element of the structure and its content
+are done in a single declaration. Similarly the following declares
div1
elements:
<!ELEMENT div1 (head, (p | list | note)*, div2?)>
More over when compiled on an Unix platform with iconv support the full set -of encodings supported by iconv can be instantly be used by libxml. On a +
More over when compiled on an Unix platform with iconv support the full +set of encodings supported by iconv can be instantly be used by libxml. On a linux machine with glibc-2.1 the list of supported encodings and aliases fill 3 full pages, and include UCS-4, the full set of ISO-Latin encodings, and the various Japanese ones.
@@ -2583,8 +2594,8 @@ and this was a problem. The solution was to redefine a new output handler with the closing call deactivated:xmlOutputBufferPtr xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) { xmlOutputBufferPtr ret; @@ -2612,6 +2623,7 @@ xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) { + }
The namespace value has to be an absolute URL, but the URL doesn't have to
point to any existing resource on the Web. It will bind all the element and
-attributes with that URL. I suggest to use an URL within a domain you control,
-and that the URL should contain some kind of version information if possible.
-For example, "http://www.gnome.org/gnumeric/1.0/"
is a good
-namespace scheme.
"http://www.gnome.org/gnumeric/1.0/"
is a
+good namespace scheme.
Then when you load a file, make sure that a namespace carrying the version-independent prefix is installed on the root element of your document, @@ -3466,14 +3478,15 @@ following:
Well what is validation and what is a DTD ?
DTD is the acronym for Document Type Definition. This is a description of the content for a family of XML files. This is part of the XML 1.0 -specification, and allows to describe and check that a given document instance -conforms to a set of rules detailing its structure and content.
+specification, and allows to describe and check that a given document +instance conforms to a set of rules detailing its structure and content.Validation is the process of checking a document against a DTD (more generally against a set of construction rules).
The validation process and building DTDs are the two most difficult parts
@@ -158,9 +158,9 @@ is placed in the file mydtd
in the subdirectory
The following declares an element spec
:
<!ELEMENT spec (front, body, back?)>
it also expresses that the spec element contains one front
,
-one body
and one optional back
children elements
-in this order. The declaration of one element of the structure and its
-content are done in a single declaration. Similarly the following declares
+one body
and one optional back
children elements in
+this order. The declaration of one element of the structure and its content
+are done in a single declaration. Similarly the following declares
div1
elements:
<!ELEMENT div1 (head, (p | list | note)*, div2?)>
means div1 contains one head
then a series of optional
diff --git a/doc/xmlio.html b/doc/xmlio.html
index 4d96574e..c9bf2ff0 100644
--- a/doc/xmlio.html
+++ b/doc/xmlio.html
@@ -205,8 +205,8 @@ real use case, xmlDocDump() closes the FILE * passed by the application
and this was a problem. The solution was to redefine a
new output handler with the closing call deactivated:
xmlOutputBufferPtr xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) { xmlOutputBufferPtr ret; @@ -234,6 +234,7 @@ xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) { + }