From 024f19966eafc5943d32f212894b1e73cf06e2ea Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Wed, 10 Dec 2003 16:43:49 +0000 Subject: [PATCH] fixed to point to releases of libxml2-2.6, Daniel --- doc/FAQ.html | 18 ++++---- doc/XMLinfo.html | 6 +-- doc/XSLT.html | 2 +- doc/bugs.html | 10 ++--- doc/catalog.html | 104 ++++++++++++++++++++++---------------------- doc/downloads.html | 2 +- doc/encoding.html | 18 ++++---- doc/entities.html | 8 ++-- doc/example.html | 30 ++++++------- doc/index.html | 2 +- doc/library.html | 36 +++++++-------- doc/namespaces.html | 10 ++--- doc/news.html | 14 +++--- doc/python.html | 82 +++++++++++++++++----------------- doc/threads.html | 2 +- doc/upgrade.html | 4 +- doc/xml.html | 4 +- doc/xmldtd.html | 8 ++-- doc/xmlmem.html | 2 +- 19 files changed, 181 insertions(+), 181 deletions(-) diff --git a/doc/FAQ.html b/doc/FAQ.html index 3424e3f0..472863fb 100644 --- a/doc/FAQ.html +++ b/doc/FAQ.html @@ -25,7 +25,7 @@ A:link, A:visited, A:active { text-decoration: underline }

Installation

  1. Do Not Use libxml1, use libxml2
  2. Where can I get libxml ? -

    The original distribution comes from rpmfind.net or gnome.org

    +

    The original distribution comes from rpmfind.net or gnome.org

    Most Linux and BSD distributions include libxml, this is probably the safer way for end-users to use libxml.

    David Doolin provides precompiled Windows versions at http://www.ce.berkeley.edu/~doolin/code/libxmlwin32/

    @@ -61,7 +61,7 @@ A:link, A:visited, A:active { text-decoration: underline } applications with libxml(2)) that you can install locally.

Compilation

  1. What is the process to compile libxml2 ? -

    As most UNIX libraries libxml2 follows the "standard":

    +

    As most UNIX libraries libxml2 follows the "standard":

    gunzip -c xxx.tar.gz | tar xvf -

    cd libxml-xxxx

    ./configure --help

    @@ -134,15 +134,15 @@ A:link, A:visited, A:active { text-decoration: underline }
  • Extra nodes in the document:

    For a XML file as below:

    - 
    <?xml version="1.0"?>
-<PLAN xmlns="http://www.argus.ca/autotest/1.0/">
-<NODE CommFlag="0"/>
-<NODE CommFlag="1"/>
+    
    <?xml version="1.0"?>
+<PLAN xmlns="http://www.argus.ca/autotest/1.0/">
+<NODE CommFlag="0"/>
+<NODE CommFlag="1"/>
 </PLAN>
    
     
    after parsing it with the function
     pxmlDoc=xmlParseFile(...);
    
     
    I want to the get the content of the first node (node with the
-    CommFlag="0")
    
+    CommFlag="0")
    
     
    so I did it as following;
    
     
    xmlNodePtr pnode;
 pnode=pxmlDoc->children->children;
    
@@ -227,14 +227,14 @@ pnode=pxmlDoc->children->children;
    xmlDocPtr doc; /* your existing document */
 xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
 
-        dtd->name = xmlStrDup((xmlChar*)"root_name"); /* use the given root */
+        dtd->name = xmlStrDup((xmlChar*)"root_name"); /* use the given root */
 
         doc->intSubset = dtd;
         if (doc->children == NULL) xmlAddChild((xmlNodePtr)doc, (xmlNodePtr)dtd);
         else xmlAddPrevSibling(doc->children, (xmlNodePtr)dtd);
    • -
  • So what is this funky "xmlChar" used all the time? +
  • So what is this funky "xmlChar" used all the time?

    It is a null terminated sequence of utf-8 characters. And only utf-8! You need to convert strings encoded in different ways to utf-8 before passing them to the API. This can be accomplished with the iconv library diff --git a/doc/XMLinfo.html b/doc/XMLinfo.html index ef03b245..2642bcb1 100644 --- a/doc/XMLinfo.html +++ b/doc/XMLinfo.html @@ -9,15 +9,15 @@ H3 {font-family: Verdana,Arial,Helvetica} A:link, A:visited, A:active { text-decoration: underline } XML
    Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
    Made with Libxml2 Logo

    The XML C parser and toolkit of Gnome

    XML

    Main Menu
    Related links

    XML is a standard for markup-based structured documents. Here is an example XML -document:

    <?xml version="1.0"?>
-<EXAMPLE prop1="gnome is great" prop2="&amp; linux too">
+document:
    <?xml version="1.0"?>
+<EXAMPLE prop1="gnome is great" prop2="&amp; linux too">
   <head>
    <title>Welcome to Gnome</title>
   </head>
   <chapter>
    <title>The Linux adventure</title>
    <p>bla bla bla ...</p>
-   <image href="linus.gif"/>
+   <image href="linus.gif"/>
    <p>...</p>
   </chapter>
 </EXAMPLE>
    The first line specifies that it is an XML document and gives useful
diff --git a/doc/XSLT.html b/doc/XSLT.html
index 138e5120..00f4b498 100644
--- a/doc/XSLT.html
+++ b/doc/XSLT.html
@@ -10,5 +10,5 @@ A:link, A:visited, A:active { text-decoration: underline }
 XSLT
    Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
    Made with Libxml2 Logo
    The XML C parser and toolkit of Gnome
    XSLT
    Main Menu
    Related links
    Check the separate libxslt page
    XSL Transformations,  is a
 language for transforming XML documents into other XML documents (or
 HTML/textual output).
    A separate library called libxslt is available implementing XSLT-1.0 for
-libxml2. This module "libxslt" too can be found in the Gnome CVS base.
    You can check the features
+libxml2. This module "libxslt" too can be found in the Gnome CVS base.
    You can check the features
 supported and the progresses on the Changelog.
    Daniel Veillard
    
diff --git a/doc/bugs.html b/doc/bugs.html
index fcd3e18a..270912bd 100644
--- a/doc/bugs.html
+++ b/doc/bugs.html
@@ -10,7 +10,7 @@ A:link, A:visited, A:active { text-decoration: underline }
 Reporting bugs and getting help
    Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
    Made with Libxml2 Logo
    The XML C parser and toolkit of Gnome
    Reporting bugs and getting help
    Main Menu
    Related links
    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 Gnome
-bug tracking database (make sure to use the "libxml2" module name). I
+bug tracking database (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.
    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
@@ -37,16 +37,16 @@ things really hard to track and in some cases I am not the best person to
 answer a given question, ask on the list.
    To be really clear about support:
    • Support or help requests MUST be sent to
     the list or on bugzilla 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
+    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
     xml@gnome.org mailing list for any technical reply made about libxml2 or
     libxslt.
      • 
   
    • There is no garantee of support, if
     your question remains unanswered after a week, repost it, making sure you
     gave all the detail needed and the information requested.
      • 
   
    • 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
+    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.
      • 
 
    Of course, bugs reported with a suggested patch for fixing them will
 probably be processed faster than those without.
    If you're looking for help, a quick look at the list archive may actually
diff --git a/doc/catalog.html b/doc/catalog.html
index d2d7d021..23e55c23 100644
--- a/doc/catalog.html
+++ b/doc/catalog.html
@@ -22,19 +22,19 @@ A:link, A:visited, A:active { text-decoration: underline }
 is inserted between the moment the reference is recognized by the software
 (XML parser, stylesheet processing, or even images referenced for inclusion
 in a rendering) and the time where loading that resource is actually
-started.
    It is basically used for 3 things:
    • mapping from "logical" names, the public identifiers and a more
+started.
      It is basically used for 3 things:
      • mapping from "logical" names, the public identifiers and a more
     concrete name usable for download (and URI). For example it can associate
     the logical name
-    
        "-//OASIS//DTD DocBook XML V4.1.2//EN"
        
+    
        "-//OASIS//DTD DocBook XML V4.1.2//EN"
        
     
        of the DocBook 4.1.2 XML DTD with the actual URL where it can be
     downloaded
        
     
        http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
        
   
        • 
   
      • remapping from a given URL to another one, like an HTTP indirection
     saying that
-    
        "http://www.oasis-open.org/committes/tr.xsl"
        
+    
        "http://www.oasis-open.org/committes/tr.xsl"
        
     
        should really be looked at
        
-    
        "http://www.oasis-open.org/committes/entity/stylesheets/base/tr.xsl"
        
+    
        "http://www.oasis-open.org/committes/entity/stylesheets/base/tr.xsl"
        
   
        • 
   
      • providing a local cache mechanism allowing to load the entities
     associated to public identifiers or remote resources, this is a really
@@ -53,11 +53,11 @@ catalog in /etc/xml/catalog, and assuming it has been correctly populated,
 the processing is completely transparent to the document user. To take a
 concrete example, suppose you are authoring a DocBook document, this one
 starts with the following DOCTYPE definition:
        <?xml version='1.0'?>
-<!DOCTYPE book PUBLIC "-//Norman Walsh//DTD DocBk XML V3.1.4//EN"
-          "http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd">
        When validating the document with libxml, the catalog will be
-automatically consulted to lookup the public identifier "-//Norman Walsh//DTD
-DocBk XML V3.1.4//EN" and the system identifier
-"http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd", and if these entities have
+<!DOCTYPE book PUBLIC "-//Norman Walsh//DTD DocBk XML V3.1.4//EN"
+          "http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd">
        When validating the document with libxml, the catalog will be
+automatically consulted to lookup the public identifier "-//Norman Walsh//DTD
+DocBk XML V3.1.4//EN" and the system identifier
+"http://nwalsh.com/docbook/xml/3.1.4/db3xml.dtd", and if these entities have
 been installed on your system and the catalogs actually point to them, libxml
 will fetch them from the local disk.
        Note: Really don't use this
 DOCTYPE example it's a really old version, but is fine as an example.
        Libxml2 will check the catalog each time that it is requested to load an
@@ -65,36 +65,36 @@ entity, this includes DTD, external parsed entities, stylesheets, etc ... If
 your system is correctly configured all the authoring phase and processing
 should use only local files, even if your document stays portable because it
 uses the canonical public and system ID, referencing the remote document.
        Some examples:
        Here is a couple of fragments from XML Catalogs used in libxml2 early
-regression tests in test/catalogs :
        <?xml version="1.0"?>
+regression tests in test/catalogs :
        <?xml version="1.0"?>
 <!DOCTYPE catalog PUBLIC 
-   "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
-   "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
-<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
-  <public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
-   uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/>
+   "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
+   "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
+<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
+  <public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
+   uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/>
 ...
        This is the beginning of a catalog for DocBook 4.1.2, XML Catalogs are
 written in XML,  there is a specific namespace for catalog elements
-"urn:oasis:names:tc:entity:xmlns:xml:catalog". The first entry in this
+"urn:oasis:names:tc:entity:xmlns:xml:catalog". The first entry in this
 catalog is a public mapping it allows to associate a Public
 Identifier with an URI.
        ...
-    <rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/"
-                   rewritePrefix="file:///usr/share/xml/docbook/"/>
+    <rewriteSystem systemIdStartString="http://www.oasis-open.org/docbook/"
+                   rewritePrefix="file:///usr/share/xml/docbook/"/>
 ...
        A rewriteSystem is a very powerful instruction, it says that
 any URI starting with a given prefix should be looked at another  URI
 constructed by replacing the prefix with an new one. In effect this acts like
 a cache system for a full area of the Web. In practice it is extremely useful
 with a file prefix if you have installed a copy of those resources on your
 local system.
        ...
-<delegatePublic publicIdStartString="-//OASIS//DTD XML Catalog //"
-                catalog="file:///usr/share/xml/docbook.xml"/>
-<delegatePublic publicIdStartString="-//OASIS//ENTITIES DocBook XML"
-                catalog="file:///usr/share/xml/docbook.xml"/>
-<delegatePublic publicIdStartString="-//OASIS//DTD DocBook XML"
-                catalog="file:///usr/share/xml/docbook.xml"/>
-<delegateSystem systemIdStartString="http://www.oasis-open.org/docbook/"
-                catalog="file:///usr/share/xml/docbook.xml"/>
-<delegateURI uriStartString="http://www.oasis-open.org/docbook/"
-                catalog="file:///usr/share/xml/docbook.xml"/>
+<delegatePublic publicIdStartString="-//OASIS//DTD XML Catalog //"
+                catalog="file:///usr/share/xml/docbook.xml"/>
+<delegatePublic publicIdStartString="-//OASIS//ENTITIES DocBook XML"
+                catalog="file:///usr/share/xml/docbook.xml"/>
+<delegatePublic publicIdStartString="-//OASIS//DTD DocBook XML"
+                catalog="file:///usr/share/xml/docbook.xml"/>
+<delegateSystem systemIdStartString="http://www.oasis-open.org/docbook/"
+                catalog="file:///usr/share/xml/docbook.xml"/>
+<delegateURI uriStartString="http://www.oasis-open.org/docbook/"
+                catalog="file:///usr/share/xml/docbook.xml"/>
 ...
        Delegation is the core features which allows to build a tree of catalogs,
 easier to maintain than a single catalog, based on Public Identifier, System
 Identifier or URI prefixes it instructs the catalog software to look up
@@ -110,34 +110,34 @@ empty one should deactivate loading the default /etc/xml/catalog
 default catalog
        How to debug catalog processing:
        Setting up the XML_DEBUG_CATALOG environment variable will
 make libxml2 output debugging informations for each catalog operations, for
 example:
        orchis:~/XML -> xmllint --memory --noout test/ent2
-warning: failed to load external entity "title.xml"
+warning: failed to load external entity "title.xml"
 orchis:~/XML -> export XML_DEBUG_CATALOG=
 orchis:~/XML -> xmllint --memory --noout test/ent2
 Failed to parse catalog /etc/xml/catalog
 Failed to parse catalog /etc/xml/catalog
-warning: failed to load external entity "title.xml"
+warning: failed to load external entity "title.xml"
 Catalogs cleanup
 orchis:~/XML -> 
        The test/ent2 references an entity, running the parser from memory makes
-the base URI unavailable and the the "title.xml" entity cannot be loaded.
+the base URI unavailable and the the "title.xml" entity cannot be loaded.
 Setting up the debug environment variable allows to detect that an attempt is
 made to load the /etc/xml/catalog but since it's not present the
 resolution fails.
        But the most advanced way to debug XML catalog processing is to use the
 xmlcatalog command shipped with libxml2, it allows to load
 catalogs and make resolution queries to see what is going on. This is also
 used for the regression tests:
        orchis:~/XML -> ./xmlcatalog test/catalogs/docbook.xml \
-                   "-//OASIS//DTD DocBook XML V4.1.2//EN"
+                   "-//OASIS//DTD DocBook XML V4.1.2//EN"
 http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
 orchis:~/XML -> 
        For debugging what is going on, adding one -v flags increase the verbosity
 level to indicate the processing done (adding a second flag also indicate
 what elements are recognized at parsing):
        orchis:~/XML -> ./xmlcatalog -v test/catalogs/docbook.xml \
-                   "-//OASIS//DTD DocBook XML V4.1.2//EN"
+                   "-//OASIS//DTD DocBook XML V4.1.2//EN"
 Parsing catalog test/catalogs/docbook.xml's content
 Found public match -//OASIS//DTD DocBook XML V4.1.2//EN
 http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
 Catalogs cleanup
 orchis:~/XML -> 
        A shell interface is also available to debug and process multiple queries
 (and for regression tests):
        orchis:~/XML -> ./xmlcatalog -shell test/catalogs/docbook.xml \
-                   "-//OASIS//DTD DocBook XML V4.1.2//EN"
+                   "-//OASIS//DTD DocBook XML V4.1.2//EN"
 > help   
 Commands available:
 public PublicID: make a PUBLIC identifier lookup
@@ -149,40 +149,40 @@ dump: print the current catalog state
 debug: increase the verbosity level
 quiet: decrease the verbosity level
 exit:  quit the shell
-> public "-//OASIS//DTD DocBook XML V4.1.2//EN"
+> public "-//OASIS//DTD DocBook XML V4.1.2//EN"
 http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd
 > quit
 orchis:~/XML -> 
        This should be sufficient for most debugging purpose, this was actually
 used heavily to debug the XML Catalog implementation itself.
        How to create and maintain catalogs:
        Basically XML Catalogs are XML files, you can either use XML tools to
 manage them or use  xmlcatalog for this. The basic step is
 to create a catalog the -create option provide this facility:
        orchis:~/XML -> ./xmlcatalog --create tst.xml
-<?xml version="1.0"?>
-<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
-         "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
-<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/>
+<?xml version="1.0"?>
+<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
+         "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
+<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/>
 orchis:~/XML -> 
        By default xmlcatalog does not overwrite the original catalog and save the
 result on the standard output, this can be overridden using the -noout
 option. The -add command allows to add entries in the
-catalog:
        orchis:~/XML -> ./xmlcatalog --noout --create --add "public" \
-  "-//OASIS//DTD DocBook XML V4.1.2//EN" \
+catalog:
        orchis:~/XML -> ./xmlcatalog --noout --create --add "public" \
+  "-//OASIS//DTD DocBook XML V4.1.2//EN" \
   http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd tst.xml
 orchis:~/XML -> cat tst.xml
-<?xml version="1.0"?>
-<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" \
-  "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
-<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
-<public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
-        uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/>
+<?xml version="1.0"?>
+<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" \
+  "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
+<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
+<public publicId="-//OASIS//DTD DocBook XML V4.1.2//EN"
+        uri="http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd"/>
 </catalog>
 orchis:~/XML -> 
        The -add option will always take 3 parameters even if some of
 the XML Catalog constructs (like nextCatalog) will have only a single
 argument, just pass a third empty string, it will be ignored.
        Similarly the -del option remove matching entries from the
 catalog:
        orchis:~/XML -> ./xmlcatalog --del \
-  "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" tst.xml
-<?xml version="1.0"?>
-<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
-    "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
-<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/>
+  "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" tst.xml
+<?xml version="1.0"?>
+<!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN"
+    "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd">
+<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"/>
 orchis:~/XML -> 
        The catalog is now empty. Note that the matching of -del is
 exact and would have worked in a similar fashion with the Public ID
 string.
        This is rudimentary but should be sufficient to manage a not too complex
diff --git a/doc/downloads.html b/doc/downloads.html
index 94ada617..dc418c15 100644
--- a/doc/downloads.html
+++ b/doc/downloads.html
@@ -8,7 +8,7 @@ H2 {font-family: Verdana,Arial,Helvetica}
 H3 {font-family: Verdana,Arial,Helvetica}
 A:link, A:visited, A:active { text-decoration: underline }
 Downloads
        Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
        Made with Libxml2 Logo
        The XML C parser and toolkit of Gnome
        Downloads
        Main Menu
        Related links
        The latest versions of libxml2 can be found on xmlsoft.org (Seattle, France) or on the Gnome FTP server either
-as a source
+as a source
 archive
diff --git a/doc/encoding.html b/doc/encoding.html
index 8f5da77e..3124888e 100644
--- a/doc/encoding.html
+++ b/doc/encoding.html
@@ -28,7 +28,7 @@ bit overkill for Western languages encoding. Moreover the XML specification
 allows document to be encoded in other encodings at the condition that they
 are clearly labeled as such. For example the following is a wellformed XML
 document encoded in ISO-8859 1 and using accentuated letter that we French
-likes for both markup and content:
        <?xml version="1.0" encoding="ISO-8859-1"?>
+likes for both markup and content:
        <?xml version="1.0" encoding="ISO-8859-1"?>
 <très>là</très>
        Having internationalization support in libxml2 means the following:
        • the document is properly parsed
          • 
   
        • informations about it's encoding are saved
          • 
   
        • it can be modified
          • 
@@ -40,11 +40,11 @@ exception of a few routines to read with a specific encoding or save to a
 specific encoding, is completely agnostic about the original encoding of the
 document.
          It should be noted too that the HTML parser embedded in libxml2 now obey
 the same rules too, the following document will be (as of 2.2.2) handled  in
-an internationalized fashion by libxml2 too:
          <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
-                      "http://www.w3.org/TR/REC-html40/loose.dtd">
-<html lang="fr">
+an internationalized fashion by libxml2 too:
          <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
+                      "http://www.w3.org/TR/REC-html40/loose.dtd">
+<html lang="fr">
 <head>
-  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
+  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
 </head>
 <body>
 <p>W3C crée des standards pour le Web.</body>
@@ -116,7 +116,7 @@ err.xml:1: error: Bytes: 0xE8 0x73 0x3E 0x6C
     will report an error and stops processing:
     
          ~/XML -> ./xmllint err2.xml 
 err2.xml:1: error: Unsupported encoding UnsupportedEnc
-<?xml version="1.0" encoding="UnsupportedEnc"?>
+<?xml version="1.0" encoding="UnsupportedEnc"?>
                                              ^
          
   
   
        • From that point the encoder processes progressively the input (it is
@@ -154,14 +154,14 @@ encoding:
          1. if no encoding is given, libxml2 will look for an encoding
     resume the conversion. This guarantees that any document will be saved
     without losses (except for markup names where this is not legal, this is
     a problem in the current version, in practice avoid using non-ascii
-    characters for tags or attributes names  @@). A special "ascii" encoding
+    characters for tags or attributes names  @@). A special "ascii" encoding
     name is used to save documents to a pure ascii form can be used when
     portability is really crucial
            2. 
 
          Here is a few examples based on the same test document:
          ~/XML -> ./xmllint isolat1 
-<?xml version="1.0" encoding="ISO-8859-1"?>
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <très>là</très>
 ~/XML -> ./xmllint --encode UTF-8 isolat1 
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="UTF-8"?>
 <très>là  </très>
 ~/XML -> 
          The same processing is applied (and reuse most of the code) for HTML I18N
 processing. Looking up and modifying the content encoding is a bit more
diff --git a/doc/entities.html b/doc/entities.html
index 654fa2c1..563def47 100644
--- a/doc/entities.html
+++ b/doc/entities.html
@@ -12,9 +12,9 @@ abbreviation for a given string that you can reuse many times throughout the
 content of your document. Entities are especially useful when a given string
 may occur frequently within a document, or to confine the change needed to a
 document to a restricted area in the internal subset of the document (at the
-beginning). Example:
          1 <?xml version="1.0"?>
-2 <!DOCTYPE EXAMPLE SYSTEM "example.dtd" [
-3 <!ENTITY xml "Extensible Markup Language">
+beginning). Example:
          1 <?xml version="1.0"?>
+2 <!DOCTYPE EXAMPLE SYSTEM "example.dtd" [
+3 <!ENTITY xml "Extensible Markup Language">
 4 ]>
 5 <EXAMPLE>
 6    &xml;
@@ -24,7 +24,7 @@ are 5 predefined entities in libxml2 allowing you to escape characters with
 predefined meaning in some parts of the xml document content:
 &lt; for the character '<', &gt;
 for the character '>',  &apos; for the character ''',
-&quot; for the character '"', and
+&quot; for the character '"', and
 &amp; for the character '&'.
          One of the problems related to entities is that you may want the parser to
 substitute an entity's content so that you can see the replacement text in
 your application. Or you may prefer to keep entity references as such in the
diff --git a/doc/example.html b/doc/example.html
index 29d6efcf..b84524f6 100644
--- a/doc/example.html
+++ b/doc/example.html
@@ -11,12 +11,12 @@ A:link, A:visited, A:active { text-decoration: underline }
 data is not kept in the DOM tree but uses internal structures. It is based on
 a proposal to keep a database of jobs related to Gnome, with an XML based
 storage structure. Here is an XML encoded jobs
-base:
          <?xml version="1.0"?>
-<gjob:Helping xmlns:gjob="http://www.gnome.org/some-location">
+base:
          <?xml version="1.0"?>
+<gjob:Helping xmlns:gjob="http://www.gnome.org/some-location">
   <gjob:Jobs>
 
     <gjob:Job>
-      <gjob:Project ID="3"/>
+      <gjob:Project ID="3"/>
       <gjob:Application>GBackup</gjob:Application>
       <gjob:Category>Development</gjob:Category>
 
@@ -91,13 +91,13 @@ typedef struct person {
 personPtr parsePerson(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
     personPtr ret = NULL;
 
-DEBUG("parsePerson\n");
+DEBUG("parsePerson\n");
     /*
      * allocate the struct
      */
     ret = (personPtr) malloc(sizeof(person));
     if (ret == NULL) {
-        fprintf(stderr,"out of memory\n");
+        fprintf(stderr,"out of memory\n");
         return(NULL);
     }
     memset(ret, 0, sizeof(person));
@@ -105,9 +105,9 @@ DEBUG("parsePerson\n");
     /* We don't care what the top level element name is */
     cur = cur->xmlChildrenNode;
     while (cur != NULL) {
-        if ((!strcmp(cur->name, "Person")) && (cur->ns == ns))
+        if ((!strcmp(cur->name, "Person")) && (cur->ns == ns))
             ret->name = xmlNodeListGetString(doc, cur->xmlChildrenNode, 1);
-        if ((!strcmp(cur->name, "Email")) && (cur->ns == ns))
+        if ((!strcmp(cur->name, "Email")) && (cur->ns == ns))
             ret->email = xmlNodeListGetString(doc, cur->xmlChildrenNode, 1);
         cur = cur->next;
     }
@@ -146,13 +146,13 @@ typedef struct job {
 jobPtr parseJob(xmlDocPtr doc, xmlNsPtr ns, xmlNodePtr cur) {
     jobPtr ret = NULL;
 
-DEBUG("parseJob\n");
+DEBUG("parseJob\n");
     /*
      * allocate the struct
      */
     ret = (jobPtr) malloc(sizeof(job));
     if (ret == NULL) {
-        fprintf(stderr,"out of memory\n");
+        fprintf(stderr,"out of memory\n");
         return(NULL);
     }
     memset(ret, 0, sizeof(job));
@@ -161,17 +161,17 @@ DEBUG("parseJob\n");
     cur = cur->xmlChildrenNode;
     while (cur != NULL) {
         
-        if ((!strcmp(cur->name, "Project")) && (cur->ns == ns)) {
-            ret->projectID = xmlGetProp(cur, "ID");
+        if ((!strcmp(cur->name, "Project")) && (cur->ns == ns)) {
+            ret->projectID = xmlGetProp(cur, "ID");
             if (ret->projectID == NULL) {
-                fprintf(stderr, "Project has no ID\n");
+                fprintf(stderr, "Project has no ID\n");
             }
         }
-        if ((!strcmp(cur->name, "Application")) && (cur->ns == ns))
+        if ((!strcmp(cur->name, "Application")) && (cur->ns == ns))
             ret->application = xmlNodeListGetString(doc, cur->xmlChildrenNode, 1);
-        if ((!strcmp(cur->name, "Category")) && (cur->ns == ns))
+        if ((!strcmp(cur->name, "Category")) && (cur->ns == ns))
             ret->category = xmlNodeListGetString(doc, cur->xmlChildrenNode, 1);
-        if ((!strcmp(cur->name, "Contact")) && (cur->ns == ns))
+        if ((!strcmp(cur->name, "Contact")) && (cur->ns == ns))
             ret->contact = parsePerson(doc, ns, cur);
         cur = cur->next;
     }
diff --git a/doc/index.html b/doc/index.html
index 88d340c8..a9b30dd8 100644
--- a/doc/index.html
+++ b/doc/index.html
@@ -203,7 +203,7 @@ A:link, A:visited, A:active { text-decoration: underline }
 under the MIT
 License. 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 brackets. HTML is the most
+extra "markup" information enclosed between angle brackets. HTML is the most
 well-known markup language. Though the library is written in C a variety of language bindings make it available in
 other environments.
          
                                   
          Libxml2 is known to be very portable, the library should build and work
diff --git a/doc/library.html b/doc/library.html
index c2a2b3e5..842dea16 100644
--- a/doc/library.html
+++ b/doc/library.html
@@ -16,7 +16,7 @@ API should look at DOM.
          The HTML parser
 interfaces.  Let's have a look at how the XML parser can be called:
          Invoking the parser : the pull method
          Usually, the first thing to do is to read an XML input. The parser accepts
 documents either from in-memory strings or from files.  The functions are
-defined in "parser.h":
          xmlDocPtr xmlParseMemory(char *buffer, int size);
          
+defined in "parser.h":
          xmlDocPtr xmlParseMemory(char *buffer, int size);
          
     
          Parse a null-terminated string containing the document.
          
     
          
 
          xmlDocPtr xmlParseFile(const char *filename);
          
@@ -37,7 +37,7 @@ int              xmlParseChunk          (xmlParserCtxtPtr ctxt,
                                          int size,
                                          int terminate);
          and here is a simple example showing how to use the interface:
                      FILE *f;
 
-            f = fopen(filename, "r");
+            f = fopen(filename, "r");
             if (f != NULL) {
                 int res, size = 1024;
                 char chars[1024];
@@ -55,7 +55,7 @@ int              xmlParseChunk          (xmlParserCtxtPtr ctxt,
                     xmlFreeParserCtxt(ctxt);
                 }
             }
          The HTML parser embedded into libxml2 also has a push interface; the
-functions are just prefixed by "html" rather than "xml".
          Invoking the parser: the SAX interface
          The tree-building interface makes the parser memory-hungry, first loading
+functions are just prefixed by "html" rather than "xml".
          Invoking the parser: the SAX interface
          The tree-building interface makes the parser memory-hungry, first loading
 the document in memory and then building the tree itself. Reading a document
 without building the tree is possible using the SAX interfaces (see SAX.h and
 James
@@ -68,23 +68,23 @@ code that produces the XML document used in the previous examples:
              #
     xmlDocPtr doc;
     xmlNodePtr tree, subtree;
 
-    doc = xmlNewDoc("1.0");
-    doc->children = xmlNewDocNode(doc, NULL, "EXAMPLE", NULL);
-    xmlSetProp(doc->children, "prop1", "gnome is great");
-    xmlSetProp(doc->children, "prop2", "& linux too");
-    tree = xmlNewChild(doc->children, NULL, "head", NULL);
-    subtree = xmlNewChild(tree, NULL, "title", "Welcome to Gnome");
-    tree = xmlNewChild(doc->children, NULL, "chapter", NULL);
-    subtree = xmlNewChild(tree, NULL, "title", "The Linux adventure");
-    subtree = xmlNewChild(tree, NULL, "p", "bla bla bla ...");
-    subtree = xmlNewChild(tree, NULL, "image", NULL);
-    xmlSetProp(subtree, "href", "linus.gif");
          Not really rocket science ...
          Traversing the tree
          Basically by including "tree.h" your
+    doc = xmlNewDoc("1.0");
+    doc->children = xmlNewDocNode(doc, NULL, "EXAMPLE", NULL);
+    xmlSetProp(doc->children, "prop1", "gnome is great");
+    xmlSetProp(doc->children, "prop2", "& linux too");
+    tree = xmlNewChild(doc->children, NULL, "head", NULL);
+    subtree = xmlNewChild(tree, NULL, "title", "Welcome to Gnome");
+    tree = xmlNewChild(doc->children, NULL, "chapter", NULL);
+    subtree = xmlNewChild(tree, NULL, "title", "The Linux adventure");
+    subtree = xmlNewChild(tree, NULL, "p", "bla bla bla ...");
+    subtree = xmlNewChild(tree, NULL, "image", NULL);
+    xmlSetProp(subtree, "href", "linus.gif");
          Not really rocket science ...
          Traversing the tree
          Basically by including "tree.h" your
 code has access to the internal structure of all the elements of the tree.
 The names should be somewhat simple like parent,
 children, next, prev,
 properties, etc... For example, still with the previous
-example:
          doc->children->children->children
          points to the title element,
          doc->children->children->next->children->children
          points to the text node containing the chapter title "The Linux
-adventure".
          NOTE: XML allows PIs and comments to be
+example:
          doc->children->children->children
          points to the title element,
          doc->children->children->next->children->children
          points to the text node containing the chapter title "The Linux
+adventure".
          NOTE: XML allows PIs and comments to be
 present before the document root, so doc->children may point
 to an element which is not the document Root Element; a function
 xmlDocGetRootElement() was added for this purpose.
          Modifying the tree
          Functions are provided for reading and writing the document content. Here
@@ -101,7 +101,7 @@ is an excerpt from the tree API:
          
 
          Two functions are provided for reading and writing the text associated
 with elements:
          xmlNodePtr xmlStringGetNodeList(xmlDocPtr doc, const xmlChar
   *value);
          
-    
          This function takes an "external" string and converts it to one
+    
          This function takes an "external" string and converts it to one
       text node or possibly to a list of entity and text nodes. All
       non-predefined entity references like &Gnome; will be stored
       internally as entity nodes, hence the result of the function may not be
@@ -115,7 +115,7 @@ with elements:
          xmlNodePtr xmlStringGetNodeList(xmlDocPtr doc, c
       argument inLine. If this argument is set to 1, the function will expand
       entity references.  For example, instead of returning the &Gnome;
       XML encoding in the string, it will substitute it with its value (say,
-      "GNU Network Object Model Environment").
          
+      "GNU Network Object Model Environment").
          
     
          
 
          Saving a tree
          Basically 3 options are possible:
          void xmlDocDumpMemory(xmlDocPtr cur, xmlChar**mem, int
   *size);
          
diff --git a/doc/namespaces.html b/doc/namespaces.html
index 689a721d..6b9ab996 100644
--- a/doc/namespaces.html
+++ b/doc/namespaces.html
@@ -17,14 +17,14 @@ root element of their document as the default namespace. Then they don't need
 to use the prefix in the content but we will have a basis for future semantic
 refinement and  merging of data from different sources. This doesn't increase
 the size of the XML output significantly, but significantly increases its
-value in the long-term. Example:
          <mydoc xmlns="http://mydoc.example.org/schemas/">
+value in the long-term. Example:
          <mydoc xmlns="http://mydoc.example.org/schemas/">
    <elem1>...</elem1>
    <elem2>...</elem2>
 </mydoc>
          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
+possible. For example, "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
@@ -35,15 +35,15 @@ associated with the element or the attribute, not the prefix string (which is
 just a shortcut for the full URI). In libxml, element and attributes have an
 ns field pointing to an xmlNs structure detailing the namespace
 prefix and its URI.
          @@Interfaces@@
          xmlNodePtr node;
-if(!strncmp(node->name,"mytag",5)
+if(!strncmp(node->name,"mytag",5)
   && node->ns
-  && !strcmp(node->ns->href,"http://www.mysite.com/myns/1.0")) {
+  && !strcmp(node->ns->href,"http://www.mysite.com/myns/1.0")) {
   ...
 }
          Usually people object to using namespaces together with validity checking.
 I will try to make sure that using namespaces won't break validity checking,
 so even if you plan to use or currently are using validation I strongly
 suggest adding namespaces to your document. A default namespace scheme
-xmlns="http://...." should not break validity even on less
+xmlns="http://...." should not break validity even on less
 flexible parsers. Using namespaces to mix and differentiate content coming
 from multiple DTDs will certainly break current validation schemes. To check
 such documents one needs to use schema-validation, which is supported in
diff --git a/doc/news.html b/doc/news.html
index 7dca4215..cd71924e 100644
--- a/doc/news.html
+++ b/doc/news.html
@@ -135,7 +135,7 @@ to test those
          • More testing on RelaxNG
            • 
     xmlSearchNs() by Luca Padovani. The xmlReader should do far less
     allocation and it speed should get closer to SAX. Chris Anderson worked
     on speeding and cleaning up repetitive checking code.
-  
          • cleanup of "make tests"
            • 
+  
          • cleanup of "make tests"
            • 
   
          • libxml-2.0-uninstalled.pc from Malcolm Tredinnick
            • 
   
          • deactivated the broken docBook SGML parser code and plugged the XML
     parser instead.
            • 
@@ -191,7 +191,7 @@ to test those
            • More testing on RelaxNG
              • 
   
            • Fixes: update of the Trio code (Bjorn), WXS Date and Duration fixes
     (Charles Bozeman), DTD and namespaces (Brent Hendricks), HTML push parser
     and zero bytes handling, some missing Windows file path conversions,
-    behaviour of the parser and validator in the presence of "out of memory"
+    behaviour of the parser and validator in the presence of "out of memory"
     error conditions
              • 
   
            • extended the API to be able to plug a garbage collecting memory
     allocator, added xmlMallocAtomic() and modified the allocations
@@ -284,7 +284,7 @@ to test those
              • More testing on RelaxNG
                • 
   
              • 2 bug fixes in the XML push parser
                • 
   
              • potential memory leak removed (Martin Stoilov)
                • 
   
              • fix to the configure script for Unix (Dimitri Papadopoulos)
                • 
-  
              • added encoding support for XInclude parse="text"
                • 
+  
              • added encoding support for XInclude parse="text"
                • 
   
              • autodetection of XHTML1 and specific serialization rules added
                • 
   
              • nasty threading bug fixed (William Brack)
                • 
 
              2.4.27: Nov 17 2002
              • fixes for the Python bindings
                • 
@@ -370,8 +370,8 @@ it's actually not compiled in by default. The real fixes are:
                • a coupl
   
                • serious cleanup of the Python makefiles
                  • 
   
                • speedup patch to XPath very effective for DocBook stylesheets
                  • 
   
                • Fixes for Windows build, cleanup of the documentation
                  • 
-
                2.4.17: Mar 8 2002
                • a lot of bug fixes, including "namespace nodes have no parents in
-  XPath"
                  • 
+
                2.4.17: Mar 8 2002
                • a lot of bug fixes, including "namespace nodes have no parents in
+  XPath"
                  • 
   
                • fixed/improved the Python wrappers, added more examples and more
     regression tests, XPath extension functions can now return node-sets
                  • 
   
                • added the XML Canonicalization support from Aleksey Sanin
                  • 
@@ -684,7 +684,7 @@ it's actually not compiled in by default. The real fixes are:
                  • a coupl
     $prefix/include/gnome-xml), they also are referenced by
     
                    #include <libxml/xxx.h>
                    
     
                    instead of
                    
-    
                    #include "xxx.h"
                    
+    
                    #include "xxx.h"
                    
   
                    • 
   
                  • a new URI module for parsing URIs and following strictly RFC 2396
                    • 
   
                  • the memory allocation routines used by libxml can now be overloaded
@@ -765,7 +765,7 @@ it's actually not compiled in by default. The real fixes are:
                    • a coupl
     xmlDocSetRootElement
                      • 
   
                    • Tried to improve the HTML output with help from Chris Lahey
                      • 
 
                    1.8.1: Dec 18 1999
                    • various patches to avoid troubles when using libxml with C++ compilers
-    the "namespace" keyword and C escaping in include files
                      • 
+    the "namespace" keyword and C escaping in include files
   
                    • a problem in one of the core macros IS_CHAR was corrected
                      • 
   
                    • fixed a bug introduced in 1.8.0 breaking default namespace processing,
     and more specifically the Dia application
                      • 
diff --git a/doc/python.html b/doc/python.html
index 99477340..44e3d097 100644
--- a/doc/python.html
+++ b/doc/python.html
@@ -33,7 +33,7 @@ or libxslt wrappers or bindings:
                      The distribution includes a set of examples and regression tests for the
 python bindings in the python/tests directory. Here are some
 excerpts from those tests:
                      tst.py:
                      This is a basic test of the file interface and DOM navigation:
                      import libxml2, sys
 
-doc = libxml2.parseFile("tst.xml")
-if doc.name != "tst.xml":
-    print "doc.name failed"
+doc = libxml2.parseFile("tst.xml")
+if doc.name != "tst.xml":
+    print "doc.name failed"
     sys.exit(1)
 root = doc.children
-if root.name != "doc":
-    print "root.name failed"
+if root.name != "doc":
+    print "root.name failed"
     sys.exit(1)
 child = root.children
-if child.name != "foo":
-    print "child.name failed"
+if child.name != "foo":
+    print "child.name failed"
     sys.exit(1)
 doc.freeDoc()
                      The Python module is called libxml2; parseFile is the equivalent of
 xmlParseFile (most of the bindings are automatically generated, and the xml
@@ -101,14 +101,14 @@ def noerr(ctx, str):
 
 libxml2.registerErrorHandler(noerr, None)
 
-ctxt = libxml2.createFileParserCtxt("invalid.xml")
+ctxt = libxml2.createFileParserCtxt("invalid.xml")
 ctxt.validate(1)
 ctxt.parseDocument()
 doc = ctxt.doc()
 valid = ctxt.isValid()
 doc.freeDoc()
 if valid != 0:
-    print "validity check failed"
          The first thing to notice is the call to registerErrorHandler(), it
+    print "validity check failed"
          The first thing to notice is the call to registerErrorHandler(), it
 defines a new error handler global to the library. It is used to avoid seeing
 the error messages when trying to validate the invalid document.
          The main interest of that test is the creation of a parser context with
 createFileParserCtxt() and how the behaviour can be changed before calling
@@ -118,8 +118,8 @@ C function interfaces in terms of objects method as much as possible. The
 best to get a complete view of what methods are supported is to look at the
 libxml2.py module containing all the wrappers.
          push.py:
          This test show how to activate the push parser interface:
          import libxml2
 
-ctxt = libxml2.createPushParser(None, "<foo", 4, "test.xml")
-ctxt.parseChunk("/>", 2, 1)
+ctxt = libxml2.createPushParser(None, "<foo", 4, "test.xml")
+ctxt.parseChunk("/>", 2, 1)
 doc = ctxt.doc()
 
 doc.freeDoc()
          The context is created with a special call based on the
@@ -129,71 +129,71 @@ the resource in case URI-References need to be computed by the parser.
          The
 setting the third argument terminate to 1.
          pushSAX.py:
          this test show the use of the event based parsing interfaces. In this case
 the parser does not build a document, but provides callback information as
 the parser makes progresses analyzing the data being provided:
          import libxml2
-log = ""
+log = ""
 
 class callback:
     def startDocument(self):
         global log
-        log = log + "startDocument:"
+        log = log + "startDocument:"
 
     def endDocument(self):
         global log
-        log = log + "endDocument:"
+        log = log + "endDocument:"
 
     def startElement(self, tag, attrs):
         global log
-        log = log + "startElement %s %s:" % (tag, attrs)
+        log = log + "startElement %s %s:" % (tag, attrs)
 
     def endElement(self, tag):
         global log
-        log = log + "endElement %s:" % (tag)
+        log = log + "endElement %s:" % (tag)
 
     def characters(self, data):
         global log
-        log = log + "characters: %s:" % (data)
+        log = log + "characters: %s:" % (data)
 
     def warning(self, msg):
         global log
-        log = log + "warning: %s:" % (msg)
+        log = log + "warning: %s:" % (msg)
 
     def error(self, msg):
         global log
-        log = log + "error: %s:" % (msg)
+        log = log + "error: %s:" % (msg)
 
     def fatalError(self, msg):
         global log
-        log = log + "fatalError: %s:" % (msg)
+        log = log + "fatalError: %s:" % (msg)
 
 handler = callback()
 
-ctxt = libxml2.createPushParser(handler, "<foo", 4, "test.xml")
-chunk = " url='tst'>b"
+ctxt = libxml2.createPushParser(handler, "<foo", 4, "test.xml")
+chunk = " url='tst'>b"
 ctxt.parseChunk(chunk, len(chunk), 0)
-chunk = "ar</foo>"
+chunk = "ar</foo>"
 ctxt.parseChunk(chunk, len(chunk), 1)
 
-reference = "startDocument:startElement foo {'url': 'tst'}:" + \ 
-            "characters: bar:endElement foo:endDocument:"
+reference = "startDocument:startElement foo {'url': 'tst'}:" + \ 
+            "characters: bar:endElement foo:endDocument:"
 if log != reference:
-    print "Error got: %s" % log
-    print "Expected: %s" % reference
          The key object in that test is the handler, it provides a number of entry
+    print "Error got: %s" % log
+    print "Expected: %s" % reference
          The key object in that test is the handler, it provides a number of entry
 points which can be called by the parser as it makes progresses to indicate
 the information set obtained. The full set of callback is larger than what
 the callback class in that specific example implements (see the SAX
 definition for a complete list). The wrapper will only call those supplied by
 the object when activated. The startElement receives the names of the element
 and a dictionary containing the attributes carried by this element.
          Also note that the reference string generated from the callback shows a
-single character call even though the string "bar" is passed to the parser
+single character call even though the string "bar" is passed to the parser
 from 2 different call to parseChunk()
          xpath.py:
          This is a basic test of XPath wrappers support
          import libxml2
 
-doc = libxml2.parseFile("tst.xml")
+doc = libxml2.parseFile("tst.xml")
 ctxt = doc.xpathNewContext()
-res = ctxt.xpathEval("//*")
+res = ctxt.xpathEval("//*")
 if len(res) != 2:
-    print "xpath query: wrong node set size"
+    print "xpath query: wrong node set size"
     sys.exit(1)
-if res[0].name != "doc" or res[1].name != "foo":
-    print "xpath query: wrong node set value"
+if res[0].name != "doc" or res[1].name != "foo":
+    print "xpath query: wrong node set value"
     sys.exit(1)
 doc.freeDoc()
 ctxt.xpathFreeContext()
          This test parses a file, then create an XPath context to evaluate XPath
@@ -208,12 +208,12 @@ python:
          import libxml2
 def foo(ctx, x):
     return x + 1
 
-doc = libxml2.parseFile("tst.xml")
+doc = libxml2.parseFile("tst.xml")
 ctxt = doc.xpathNewContext()
-libxml2.registerXPathFunction(ctxt._o, "foo", None, foo)
-res = ctxt.xpathEval("foo(1)")
+libxml2.registerXPathFunction(ctxt._o, "foo", None, foo)
+res = ctxt.xpathEval("foo(1)")
 if res != 2:
-    print "xpath extension failure"
+    print "xpath extension failure"
 doc.freeDoc()
 ctxt.xpathFreeContext()
          Note how the extension function is registered with the context (but that
 part is not yet finalized, this may change slightly in the future).
          tstxpath.py:
          This test is similar to the previous one but shows how the extension
@@ -232,9 +232,9 @@ evaluation point.
          Memory debugging:
          last but not least, all tests
 libxml2.debugMemory(1)
          • and ends with the following epilogue:
          #memory debug specific
 libxml2.cleanupParser()
 if libxml2.debugMemory(1) == 0:
-    print "OK"
+    print "OK"
 else:
-    print "Memory leak %d bytes" % (libxml2.debugMemory(1))
+    print "Memory leak %d bytes" % (libxml2.debugMemory(1))
     libxml2.dumpMemory()
          Those activate the memory debugging interface of libxml2 where all
 allocated block in the library are tracked. The prologue then cleans up the
 library state and checks that all allocated memory has been freed. If not it
diff --git a/doc/threads.html b/doc/threads.html
index 27c68bfe..3eacf999 100644
--- a/doc/threads.html
+++ b/doc/threads.html
@@ -10,7 +10,7 @@ A:link, A:visited, A:active { text-decoration: underline }
 Thread safety
          Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
          Made with Libxml2 Logo
          The XML C parser and toolkit of Gnome
          Thread safety
          Developer Menu
          API Indexes
          Related links
          Starting with 2.4.7, libxml2 makes provisions to ensure that concurrent
 threads can safely work in parallel parsing different documents. There is
 however a couple of things to do to ensure it:
          • configure the library accordingly using the --with-threads options
            • 
-  
          • call xmlInitParser() in the "main" thread before using any of the
+  
          • call xmlInitParser() in the "main" thread before using any of the
     libxml2 API (except possibly selecting a different memory allocator)
            • 
 
          Note that the thread safety cannot be ensured for multiple threads sharing
 the same document, the locking must be done at the application level, libxml
diff --git a/doc/upgrade.html b/doc/upgrade.html
index 34fac4d5..a7ea3e34 100644
--- a/doc/upgrade.html
+++ b/doc/upgrade.html
@@ -10,7 +10,7 @@ A:link, A:visited, A:active { text-decoration: underline }
 Upgrading 1.x code
          Action against software patentsGnome2 LogoW3C LogoRed Hat Logo
          Made with Libxml2 Logo
          The XML C parser and toolkit of Gnome
          Upgrading 1.x code
          Developer Menu
          API Indexes
          Related links
          Incompatible changes:
          Version 2 of libxml2 is the first version introducing serious backward
 incompatible changes. The main goals were:
          • a general cleanup. A number of mistakes inherited from the very early
     versions couldn't be changed due to compatibility constraints. Example
-    the "childs" element in the nodes.
            • 
+    the "childs" element in the nodes.
   
          • Uniformization of the various nodes, at least for their header and link
     parts (doc, parent, children, prev, next), the goal is a simpler
     programming model and simplifying the task of the DOM implementors.
            • 
@@ -29,7 +29,7 @@ mail:
            1. The package name have changed from libxml to libxml2, the l
     select the right parameters libxml2
              2. 
   
            2. Node childs field has been renamed
     children so s/childs/children/g should be  applied
-    (probability of having "childs" anywhere else is close to 0+
              3. 
+    (probability of having "childs" anywhere else is close to 0+
   
            3. The document don't have anymore a root element it has
     been replaced by children and usually you will get a
     list of element here. For example a Dtd element for the internal subset
diff --git a/doc/xml.html b/doc/xml.html
index 63c99a26..fcd49ad2 100644
--- a/doc/xml.html
+++ b/doc/xml.html
@@ -194,7 +194,7 @@ libxml2
              
   
            4. Where can I get libxml ?
     
              The original distribution comes from rpmfind.net or gnome.org
              
+    href="ftp://ftp.gnome.org/pub/GNOME/sources/libxml2/2.6/">gnome.org
              
     
              Most Linux and BSD distributions include libxml, this is probably the
     safer way for end-users to use libxml.
              
     
              David Doolin provides precompiled Windows versions at xmlsoft.org (Seattle, France) or on the Gnome FTP server either
-as a source
+as a source
 archive
diff --git a/doc/xmldtd.html b/doc/xmldtd.html
index 8a25088b..5287148f 100644
--- a/doc/xmldtd.html
+++ b/doc/xmldtd.html
@@ -40,7 +40,7 @@ harder to design. I will just focus on DTDs for a formats with a fixed simple
 structure. It is just a set of basic rules, and definitely not exhaustive nor
 usable for complex DTD design.
              How to reference a DTD from a document:
              Assuming the top element of the document is spec and the dtd
 is placed in the file mydtd in the subdirectory
-dtds of the directory from where the document were loaded:
              <!DOCTYPE spec SYSTEM "dtds/mydtd">
              Notes: