Imported Upstream version 2.91.2

[platform/upstream/libxml++.git] / docs / manual / html / ch02s02.html

diff --git a/docs/manual/html/ch02s02.html b/docs/manual/html/ch02s02.html
index d2a7eac..05bad88 100644 (file)
--- a/docs/manual/html/ch02s02.html
+++ b/docs/manual/html/ch02s02.html
@@ -24,13 +24,13 @@
 </div>
 <div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="idp84222080"></a>SAX Parser</h2></div></div></div>
+<a name="idp89461168"></a>SAX Parser</h2></div></div></div>
 <p>The SAX (Simple API for XML) parser presents each node of the XML document in sequence. So when you process one node, you must have already stored information about any relevant previous nodes, and you have no information at that time about subsequent nodes. The SAX parser uses less memory than the DOM parser and it is a suitable abstraction for documents that can be processed sequentially rather than as a whole.</p>
 <p>By using the <code class="literal">parse_chunk()</code> method instead of <code class="literal">parse()</code>, you can even parse parts of the XML document before you have received the whole document.</p>
 <p>As shown in the example, you should derive your own class from SaxParser and override some of the virtual methods. These "handler" methods will be called while the document is parsed.</p>
 <div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp84226192"></a>Example</h3></div></div></div>
+<a name="idp89465008"></a>Example</h3></div></div></div>
 <p>This example shows how the handler methods are called during parsing.</p>
 <p><a class="ulink" href="http://git.gnome.org/browse/libxml++/tree/examples/sax_parser" target="_top">Source Code</a></p>
 <p>File: myparser.h