From 63d83142ffbff50f2c33c73415aa400ca920042c Mon Sep 17 00:00:00 2001 From: Daniel Veillard Date: Mon, 20 May 2002 06:51:05 +0000 Subject: [PATCH] Applied a spelling patch from Geert Kloosterman to xml.html, and regenerated the web site, Daniel --- doc/FAQ.html | 28 ++--- doc/XMLinfo.html | 2 +- doc/bugs.html | 8 +- doc/catalog.html | 4 +- doc/contribs.html | 2 +- doc/encoding.html | 32 ++--- doc/entities.html | 6 +- doc/example.html | 8 +- doc/index.html | 2 +- doc/intro.html | 8 +- doc/namespaces.html | 4 +- doc/news.html | 70 +++++------ doc/python.html | 37 +++--- doc/threads.html | 2 +- doc/upgrade.html | 20 ++-- doc/xml.html | 286 ++++++++++++++++++++++---------------------- doc/xmldtd.html | 24 ++-- doc/xmlio.html | 8 +- doc/xmlmem.html | 18 +-- 19 files changed, 284 insertions(+), 285 deletions(-) diff --git a/doc/FAQ.html b/doc/FAQ.html index d31c7255..d8bb8683 100644 --- a/doc/FAQ.html +++ b/doc/FAQ.html @@ -88,24 +88,24 @@ A:link, A:visited, A:active { text-decoration: underline }

Table of Content:

-Licence(s)

+License(s)
  1. Licensing Terms for libxml

    libxml is released under the MIT - Licence, see the file Copyright in the distribution for the precise + License, see the file Copyright in the distribution for the precise wording

  2. Can I embed libxml in a proprietary application ? -

    Yes. The MIT Licence allows you to also keep proprietary the changes - you made to libxml, but it would be graceful to provide back bugfixes and +

    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 development tree

    3. @@ -119,7 +119,7 @@ A:link, A:visited, A:active { text-decoration: underline } Where can I get libxml ?

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

    -

    Most linux and Bsd distribution includes libxml, this is probably the +

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

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

    @@ -150,8 +150,8 @@ A:link, A:visited, A:active { text-decoration: underline }
  3. I can't install the libxml(2) RPM package due to failed - dependancies -

    The most generic solution is to refetch the latest src.rpm , and + dependencies +

    The most generic solution is to re-fetch the latest src.rpm , and rebuild it locally with

    rpm --rebuild libxml(2)-xxx.src.rpm

    if everything goes well it will generate two binary rpm (one providing @@ -188,7 +188,7 @@ A:link, A:visited, A:active { text-decoration: underline } highly portable and available widely compression library

  4. iconv: a powerful character encoding conversion library. It's included by default on recent glibc libraries, so it doesn't need to - be installed specifically on linux. It seems it's now part + be installed specifically on Linux. It seems it's now part of the official UNIX specification. Here is one implementation of the library which source can be found here.
    5. @@ -248,7 +248,7 @@ A:link, A:visited, A:active { text-decoration: underline }

    I want to the get the content of the first node (node with the CommFlag="0")

    so I did it as following;

    -
    xmlNodePtr pode;
+
    xmlNodePtr pnode;
 pnode=pxmlDoc->children->children;
    
 
    but it does not work. If I change it to
    
 
    pnode=pxmlDoc->children->children->next;
    
@@ -257,7 +257,7 @@ pnode=pxmlDoc->children->children;

    In XML all characters in the content of the document are significant including blanks and formatting line breaks.

    The extra nodes you are wondering about are just that, text nodes with - the formatting spaces wich are part of the document but that people tend + the formatting spaces which are part of the document but that people tend 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 @@ -300,7 +300,7 @@ pnode=pxmlDoc->children->children; generated doc

  5. looks for examples of use for libxml function using the Gnome code - for example the following will query the full Gnome CVs base for the + for example the following will query the full Gnome CVS base for the use of the xmlAddChild() function:

    http://cvs.gnome.org/lxr/search?string=xmlAddChild

    This may be slow, a large hardware donation to the gnome project @@ -318,7 +318,7 @@ pnode=pxmlDoc->children->children;

    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 few C++ wrappers which may fullfill your needs:

    +

    There is however a few C++ wrappers which may fulfill your needs:

    • by Ari Johnson <ari@btigate.com>:

      Website: http://lusis.org/~ari/xml++/ @@ -336,7 +336,7 @@ pnode=pxmlDoc->children->children;

      It is possible to validate documents which had not been validated at initial parsing time or documents who have been built from scratch using the API. Use the xmlValidateDtd() - function. It is also possible to simply add a Dtd to an existing + function. It is also possible to simply add a DTD to an existing document:

      xmlDocPtr doc; /* your existing document */
         xmlDtdPtr dtd = xmlParseDTD(NULL, filename_of_dtd); /* parse the DTD */
diff --git a/doc/XMLinfo.html b/doc/XMLinfo.html
index b13fad68..134abd24 100644
--- a/doc/XMLinfo.html
+++ b/doc/XMLinfo.html
@@ -110,7 +110,7 @@ to be closed. XML is pedantic about this. However, if a tag is empty
 it ends with /> rather than with >. Note
 that, for example, the image tag has no content (just an attribute) and is
 closed by ending the tag with />.
      
-
      XML can be applied sucessfully to a wide range of uses, from long term
+
      XML can be applied successfully to a wide range of uses, from long term
 structured document maintenance (where it follows the steps of SGML) to
 simple data encoding mechanisms like configuration file formatting (glade),
 spreadsheets (gnumeric), or even shorter lived documents such as WebDAV where
diff --git a/doc/bugs.html b/doc/bugs.html
index 5df40ffb..bce54fbd 100644
--- a/doc/bugs.html
+++ b/doc/bugs.html
@@ -105,13 +105,13 @@ posting:
      
     version, and that the problem still shows up in those
    • check the list archives to see if the problem was reported already, in this case - there is probably a fix available, similary check the registered + there is probably a fix available, similarly check the registered open bugs
    • make sure you can reproduce the bug with xmllint or one of the test programs found in source in the distribution
    • Please send the command showing the error as well as the input (as an - attachement)
      • + attachment)

    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, it makes @@ -122,8 +122,8 @@ probably be processed faster.

    If you're looking for help, a quick look at the list archive may actually provide the answer, I usually send source samples when answering libxml usage questions. The auto-generated -documentantion is not as polished as I would like (i need to learn more -about Docbook), but it's a good starting point.

    +documentation is not as polished as I would like (i need to learn more +about DocBook), but it's a good starting point.

    Daniel Veillard

diff --git a/doc/catalog.html b/doc/catalog.html index 7f332bf7..57242929 100644 --- a/doc/catalog.html +++ b/doc/catalog.html @@ -384,7 +384,7 @@ support.

The XML Catalog specification is relatively recent so there isn't much literature to point at: