diff --git a/doc/contribs.html b/doc/contribs.html
index 27a5abb0..d880c8e4 100644
--- a/doc/contribs.html
+++ b/doc/contribs.html
@@ -77,7 +77,7 @@ A:link, A:visited, A:active { text-decoration: underline }
John Fleck helps maintaining the documentation and man pages.
Ari Johnson
- provides a C++ wrapper for libxml:
+ provides a C++ wrapper for libxml:
Website: http://lusis.org/~ari/xml++/
Download: http://lusis.org/~ari/xml++/libxml++.tar.gz
diff --git a/doc/index.html b/doc/index.html
index e13480d6..bdd2470a 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -71,30 +71,66 @@ A:link, A:visited, A:active { text-decoration: underline }
+ Libxml is the XML C library developped for the Gnome project. XML itself
+is a metalanguage to design markup languages, i.e. text language where
+semantic and structure are added to the content using extra "markup"
+information enclosed between angle bracket. HTML is the most well-known
+markup language.
+Libxml2 implements a number of existing standards related to markup
+languages:
+In most cases libxml tries to implement the specifications in a relatively
+strict way. To some extent libxml2 provide some support for the following
+other specification but don't claim to implement them:
+
+- Document Object Model (DOM) http://www.w3.org/TR/DOM-Level-2-Core/
+ it doesn't implement the API itself, gdome2 does this in top of
+ libxml2
+-
+RFC 959
+ : libxml implements a basic FTP client code
+-
+RFC 1945
+ : HTTP/1.0, again a basic HTTP client code
+- SAX: a minimal SAX implementation compatible with early expat
+ versions
+- DocBook SGML v4: libxml2 includes a hackish parser to transition to
+ XML
+
+
Separate documents:
Daniel Veillard
|
|
|
|
diff --git a/doc/xml.html b/doc/xml.html
index de3f4043..3ebb6537 100644
--- a/doc/xml.html
+++ b/doc/xml.html
@@ -10,34 +10,74 @@
The XML C library for Gnome
+Note: this is the flat content of the web
+site
+
libxml, a.k.a. gnome-xml
+
+Libxml is the XML C library developped for the Gnome project. XML itself
+is a metalanguage to design markup languages, i.e. text language where
+semantic and structure are added to the content using extra "markup"
+information enclosed between angle bracket. HTML is the most well-known
+markup language.
+
+Libxml2 implements a number of existing standards related to markup
+languages:
+In most cases libxml tries to implement the specifications in a relatively
+strict way. To some extent libxml2 provide some support for the following
+other specification but don't claim to implement them:
+
+ - Document Object Model (DOM) http://www.w3.org/TR/DOM-Level-2-Core/
+ it doesn't implement the API itself, gdome2 does this in top of
+ libxml2
+ - RFC 959
+ : libxml implements a basic FTP client code
+ - RFC 1945
+ : HTTP/1.0, again a basic HTTP client code
+ - SAX: a minimal SAX implementation compatible with early expat
+ versions
+ - DocBook SGML v4: libxml2 includes a hackish parser to transition to
+ XML
+
+
+
+
Separate documents:
@@ -1322,8 +1362,7 @@ interface.
The definition
Simple rules
- - How to reference a DTD from a
- document
+ - How to reference a DTD from a document
- Declaring elements
- Declaring attributes
@@ -1521,8 +1560,7 @@ should be both simple and complete enough to allow you to build your own.
Table of Content:
- General overview
- - Setting libxml set of memory
- routines
+ - Setting libxml set of memory routines
- Cleaning up after parsing
- Debugging routines
- General memory requirements
@@ -1945,8 +1983,8 @@ the interfaces to the libxml I/O system. This consists of 4 main parts:
don't look at the public identifier since libxml do not maintain a
catalog. You can redefine you own entity loader by using
xmlGetExternalEntityLoader()
and
- xmlSetExternalEntityLoader()
. Check the example.
+ xmlSetExternalEntityLoader()
. Check the
+ example.
Input I/O buffers which are a commodity structure used by the parser(s)
input layer to handle fetching the informations to feed the parser. This
provides buffering and is also a placeholder where the encoding
@@ -2081,6 +2119,8 @@ xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) {
+
+
}
And then use it to save the document:
@@ -3170,7 +3210,7 @@ Gnome CVS base under gnome-xml/example
and Solaris port.
John Fleck helps maintaining the documentation and man pages.
Ari Johnson
- provides a C++ wrapper for libxml:
+ provides a C++ wrapper for libxml:
Website: http://lusis.org/~ari/xml++/
Download: The definition
Simple rules
-- How to reference a DTD from a
- document
+- How to reference a DTD from a document
- Declaring elements
- Declaring attributes
diff --git a/doc/xmlio.html b/doc/xmlio.html
index f87e900e..f2288528 100644
--- a/doc/xmlio.html
+++ b/doc/xmlio.html
@@ -88,7 +88,8 @@ the interfaces to the libxml I/O system. This consists of 4 main parts:
don't look at the public identifier since libxml do not maintain a
catalog. You can redefine you own entity loader by using
xmlGetExternalEntityLoader()
and
- xmlSetExternalEntityLoader()
. Check the example.
+ xmlSetExternalEntityLoader()
. Check the
+ example.
Input I/O buffers which are a commodity structure used by the parser(s)
input layer to handle fetching the informations to feed the parser. This
provides buffering and is also a placeholder where the encoding
@@ -208,6 +209,8 @@ xmlOutputBufferCreateOwn(FILE *file, xmlCharEncodingHandlerPtr encoder) {
+
+
}
And then use it to save the document:
diff --git a/doc/xmlmem.html b/doc/xmlmem.html
index f0a17974..4ef14ed5 100644
--- a/doc/xmlmem.html
+++ b/doc/xmlmem.html
@@ -73,8 +73,7 @@ A:link, A:visited, A:active { text-decoration: underline }
Table of Content:
- General overview
-- Setting libxml set of memory
- routines
+- Setting libxml set of memory routines
- Cleaning up after parsing
- Debugging routines
- General memory requirements