diff --git a/ChangeLog b/ChangeLog
index d22e1ef2..05874b3c 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,12 @@
+Sat Oct 18 11:04:32 CEST 2003 Daniel Veillard
+
+ * xmlreader.c include/libxml/xmlreader.h: added new APIs
+ for creating reader from sources or reusing a reader with
+ a new source, like the xmlReadxx and xmlCtxtReadxxx
+ * win32/libxml2.def.src doc/libxml2-api.xml doc/apibuild.py
+ doc/Makefile.am: regenerated the APIs
+ * doc/xml.html: applied a patch from Stefan Kost for namesapce docs
+
Sat Oct 18 12:46:02 HKT 2003 William Brack
* genChRanges.py, chvalid.c, include/libxml/chvalid.h,
diff --git a/doc/Makefile.am b/doc/Makefile.am
index d018f397..7aef77d3 100644
--- a/doc/Makefile.am
+++ b/doc/Makefile.am
@@ -60,7 +60,7 @@ xmlcatalog.1: xmlcatalog_man.xml
-@(xsltproc --nonet xmlcatalog_man.xml)
scan:
- -gtkdoc-scan --module=libxml --source-dir=$(DOC_SOURCE_DIR) --ignore-headers="acconfig.h config.h win32config.h trio.h triostr.h triop.h config-mac.h XMLTestPrefix2.h XMLTestPrefix.h triodef.h trionan.h xlink.h libxml.h libxml2-py.h libxml_wrap.h"
+ -gtkdoc-scan --module=libxml --source-dir=$(DOC_SOURCE_DIR) --ignore-headers="acconfig.h config.h win32config.h trio.h triostr.h triop.h config-mac.h XMLTestPrefix2.h XMLTestPrefix.h triodef.h trionan.h xlink.h libxml.h libxml2-py.h libxml_wrap.h chvalid.h"
templates: scan
-gtkdoc-mktmpl --module=libxml
diff --git a/doc/apibuild.py b/doc/apibuild.py
index 59cc0cf2..ce2f738c 100755
--- a/doc/apibuild.py
+++ b/doc/apibuild.py
@@ -25,6 +25,9 @@ ignored_files = {
"testOOM.c": "out of memory tester",
"testOOMlib.h": "out of memory tester",
"testOOMlib.c": "out of memory tester",
+ "chvalid.h": "internal only + parsing problems",
+ "pattern.c": "not integrated yet",
+ "pattern.h": "not integrated yet",
}
ignored_words = {
diff --git a/doc/libxml2-api.xml b/doc/libxml2-api.xml
index 4cfee68b..1effbc0b 100644
--- a/doc/libxml2-api.xml
+++ b/doc/libxml2-api.xml
@@ -140,15 +140,7 @@
-
-
-
-
-
-
-
-
@@ -206,6 +198,7 @@
+
@@ -1385,6 +1378,16 @@
+
+
+
+
+
+
+
+
+
+
@@ -4911,6 +4914,7 @@ actually an xmlCharEncoding'/>
+
@@ -8053,41 +8057,11 @@ actually an xmlCharEncoding'/>
-
- Check whether the character is allowed by the production [85] BaseChar ::= ... long list see REC ... VI is your friend ! :1,$ s/\[#x\([0-9A-Z]*\)-#x\([0-9A-Z]*\)\]/ (((c) >= 0x\1) \&\& ((c) <= 0x\2)) ||/ and :1,$ s/#x\([0-9A-Z]*\)/ ((c) == 0x\1) ||/
-
-
-
-
- Check whether the character is allowed by the production [3] S ::= (#x20 | #x9 | #xD | #xA)+ Also available as a macro IS_BLANK()
-
-
-
Checks whether this node is an empty or whitespace only (and possibly ignorable) text-node.
-
- Check whether the character is allowed by the production [2] Char ::= #x9 | #xA | #xD | [#x20-#xD7FF] | [#xE000-#xFFFD] | [#x10000-#x10FFFF] any Unicode character, excluding the surrogate blocks, FFFE, and FFFF. Also available as a macro IS_CHAR()
-
-
-
-
- Check whether the character is allowed by the production [87] CombiningChar ::= ... long list see REC ...
-
-
-
-
- Check whether the character is allowed by the production [88] Digit ::= ... long list see REC ...
-
-
-
-
- Check whether the character is allowed by the production [89] Extender ::= #x00B7 | #x02D0 | #x02D1 | #x0387 | #x0640 | #x0E46 | #x0EC6 | #x3005 | [#x3031-#x3035] | [#x309D-#x309E] | [#x30FC-#x30FE]
-
-
-
Determine whether an attribute is of type ID. In case we have DTD(s) then this is done if DTD loading has been requested. In the case of HTML documents parsed with the HTML parser, then ID detection is done systematically.
@@ -8095,11 +8069,6 @@ actually an xmlCharEncoding'/>
-
- Check whether the character is allowed by the production [86] Ideographic ::= [#x4E00-#x9FA5] | #x3007 | [#x3021-#x3029]
-
-
-
Check whether the character is allowed by the production [84] Letter ::= BaseChar | Ideographic
@@ -8115,11 +8084,6 @@ actually an xmlCharEncoding'/>
-
- Check whether the character is allowed by the production [13] PubidChar ::= #x20 | #xD | #xA | [a-zA-Z0-9] | [-'()+,./:=?;!*#@$_%]
-
-
-
Determine whether an attribute is of type Ref. In case we have DTD(s) then this is simple, otherwise we use an heuristic: name Ref (upper or lowercase).
@@ -9700,6 +9664,95 @@ actually an xmlCharEncoding'/>
+
+ Create an xmltextReader for an XML in-memory document.
+
+
+
+
+
+
+
+ Create an xmltextReader for an XML from a file descriptor.
+
+
+
+
+
+
+
+ parse an XML file from the filesystem or the network.
+
+
+
+
+
+
+ Create an xmltextReader for an XML document from I/O functions and source.
+
+
+
+
+
+
+
+
+
+ Create an xmltextReader for an XML in-memory document.
+
+
+
+
+
+
+
+
+ Setup an xmltextReader to parse an XML in-memory document. This reuses the existing @reader xmlTextReader.
+
+
+
+
+
+
+
+
+ Setup an xmltextReader to parse an XML from a file descriptor. This reuses the existing @reader xmlTextReader.
+
+
+
+
+
+
+
+
+ parse an XML file from the filesystem or the network. This reuses the existing @reader xmlTextReader.
+
+
+
+
+
+
+
+ Setup an xmltextReader to parse an XML document from I/O functions and source. This reuses the existing @reader xmlTextReader.
+
+
+
+
+
+
+
+
+
+
+ Setup an xmltextReader to parse an XML in-memory document. This reuses the existing @reader xmlTextReader.
+
+
+
+
+
+
+
+
Signature for a realloc() implementation.
diff --git a/doc/namespaces.html b/doc/namespaces.html
index d50f10ba..6f15c5fd 100644
--- a/doc/namespaces.html
+++ b/doc/namespaces.html
@@ -34,12 +34,21 @@ same as <bar:text> in another document. What really matters is the URI
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@@
@@Examples@@
Usually people object to using namespaces together with validity checking.
+prefix and its URI.
@@Interfaces@@
+xmlNodePtr node;
+if(!strncmp(node->name,"mytag",5)
+ && node->ns
+ && !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
flexible parsers. Using namespaces to mix and differentiate content coming
-from multiple DTDs will certainly break current validation schemes. I will
-try to provide ways to do this, but this may not be portable or
-standardized.
Daniel Veillard