Lines Matching full:handler

112     <li><a href="#setting">Handler Setting Functions</a>
196 handler) functions with the parser and then start feeding it the
198 call the appropriate handler for that part (if you've registered one.)
219 <dd>Set handler for text.</dd>
232 above functions (it doesn't need to set a character handler.) The
235 parent element that contains them. The start handler does all the
259 } /* End of start handler */
268 } /* End of end handler */
529 information onto the stack in the start handler and you pop it off in
530 the end handler.</p>
537 which the element started. When the end tag handler encounters the
581 manipulated in the start and end handlers. The end tag handler should
582 be the mirror image of the start tag handler. This is necessary to
583 properly model containment. Since, in the start tag handler, we
585 in the end handler, we need to manipulate it <em>before</em> the main
587 handler, then we'd have had to decrement it last thing in the end
588 handler.</p>
605 <p>One common case where multiple calls to a single handler may need
607 content passed to the character data handler (set by <code><a href=
612 reported by a single call to the character data handler. Expat, like
631 set a handler that uses the information in the XML declaration to
669 occur. This means that your start handler will not see these
676 are passed to the appropriate handler in expanded form. By default
696 tag handler and the EndNamespaceDeclHandler is called after the
698 start handler gets passed the prefix and URI for the namespace. For a
702 unset. The namespace end handler just gets the prefix for the closing
708 tag handler is called, once for each declaration.</p>
743 to the <code>UnknownEncodingHandler</code>. This handler gets passed
745 structure. Your handler must fill in this structure and return
747 encoding. Otherwise the handler should return
748 <code>XML_STATUS_ERROR</code>. The handler also gets passed a pointer
750 you set the handler.</p>
789 references are silently ignored. Otherwise, it calls your handler with
792 <p>Your handler isn't actually responsible for parsing the entity, but
801 your handler should be prepared to be called recursively.</p>
820 entity reference handler as described above.</p>
825 parsing temporarily from within a handler function, even if more data
957 <p>To stop parsing from a handler function, use the <code><a href=
1096 XML_GetBuffer</a></code> must not be called from within a handler
1098 did not call the handler. For example, it is OK to call the parsing
1151 concluding call</a> will all handler callbacks and parsing errors have
1249 call-back handler, except when aborting (when <code>resumable</code>
1254 <li> the end element handler for empty elements when stopped in the
1255 start element handler,</li>
1256 <li> the end namespace declaration handler when stopped in the end
1257 element handler,</li>
1258 <li> the character data handler when stopped in the character data handler
1296 external entity reference handler returns. It is up to the
1297 implementation of that handler to call <code><a href=
1315 within a handler call-back. Returns same status codes as <code><a
1362 <h3><a name="setting">Handler Setting</a></h3>
1365 application may choose to set or change the handler for a parsing event
1368 way it could do this is to set the character handler when a para start tag
1371 <p>A handler may be <em>unset</em> by providing a <code>NULL</code> pointer to the
1372 appropriate handler setter. None of the handler setting functions have
1382 <div class="handler">
1395 <p>Set handler for start (and empty) tags. Attributes are passed to the start
1396 handler as a pointer to a vector of char pointers. Each attribute seen in
1404 <div class="handler">
1416 <p>Set handler for end (and empty) tags. As noted above, an empty tag
1420 <div class="handler">
1431 <div class="handler">
1444 <p>Set a text handler. The string your handler receives
1447 free of markup may still result in a sequence of calls to this handler.
1449 be split across calls to this handler. Note: Setting this handler to <code>NULL</code>
1455 <div class="handler">
1469 <p>Set a handler for processing instructions. The target is the first word
1474 <div class="handler">
1486 <p>Set a handler for comments. The data is all text inside the comment
1490 <div class="handler">
1501 <p>Set a handler that gets called at the beginning of a CDATA section.</p>
1504 <div class="handler">
1515 <p>Set a handler that gets called at the end of a CDATA section.</p>
1518 <div class="handler">
1529 <div class="handler">
1543 <p>Sets a handler for any characters in the document which wouldn't
1546 be reported but which currently has no handler set. The characters
1550 default handler. There are no guarantees about how characters are
1551 divided between calls to the default handler: for example, a comment
1552 might be split between multiple calls. Setting the handler with
1555 passed to the default handler.</p>
1561 <div class="handler">
1574 <p>This sets a default handler, but doesn't inhibit the expansion of
1576 to the default handler.</p>
1582 <div class="handler">
1597 <p>Set an external entity reference handler. This handler is also
1606 valid only until the handler returns, so if the referenced entity is
1618 <p>There are a couple of ways in which this handler differs from
1619 others. First, this handler returns a status indicator (an
1633 <p>Since this handler may be called recursively, it should not be saving
1646 handler set using <code><a href="#XML_SetExternalEntityRefHandler"
1648 <code>NULL</code>, the argument passed to the handler function will be the parser
1654 <code>void *</code> to be passed to the handler, while the handler
1659 actual type of the argument passed to the handler and to manage it
1663 <div class="handler">
1668 XML_SkippedEntityHandler handler)
1676 <p>Set a skipped entity handler. This is called in two situations:</p>
1691 <div class="handler">
1712 <p>Set a handler to deal with encodings other than the <a
1716 given parser.</p> <p>If the handler knows how to deal with an encoding
1719 should return <code>XML_STATUS_ERROR</code>. The handler will be called
1722 the handler.</p>
1741 <div class="handler">
1754 <p>Set a handler to be called when a namespace is declared. Namespace
1756 handler is called before the start tag handler for each namespace declared
1760 <div class="handler">
1772 <p>Set a handler to be called when leaving the scope of a namespace
1774 after the handler for the end tag of the element in which the
1778 <div class="handler">
1789 <div class="handler">
1803 <p>Sets a handler that is called for XML declarations and also for
1813 <div class="handler">
1828 <p>Set a handler that is called at the start of a DOCTYPE declaration,
1834 <div class="handler">
1845 <p>Set a handler that is called at the end of a DOCTYPE declaration,
1849 <div class="handler">
1860 <div class="handler">
1900 <p>Sets a handler for element declarations in a DTD. The handler gets
1905 There is no need to free the model from the handler, it can be kept
1934 <div class="handler">
1950 <p>Set a handler for attlist declarations in the DTD. This handler is
1953 handler. The <code>elname</code> parameter returns the name of the
1968 <div class="handler">
1973 XML_EntityDeclHandler handler);
1987 <p>Sets a handler that will be called for all entity declarations.
2003 <div class="handler">
2019 <p>Set a handler that receives declarations of unparsed entities. These
2025 <p>This handler is obsolete and is provided for backwards
2030 <div class="handler">
2045 <p>Set a handler that receives notation declarations.</p>
2048 <div class="handler">
2059 <p>Set a handler that is called if the document is not "standalone".
2062 declaration. If this handler returns <code>XML_STATUS_ERROR</code>,
2083 called from within a DTD declaration handler.</p>
2164 <p>This should only be called from within a handler during an active
2166 the handler that made the call. This input buffer contains the
2357 When attributes are reported to the start handler in the atts vector,
2362 <code>atts</code> array passed to the start tag handler of the first
2364 call to a start handler. If called inside a start handler, then that
2377 attribute. If called inside a start handler, then that means the
2480 external entity reference handler set via <code><a href=
2495 the external entity reference handler returns without action.</p>
2527 This can be called within a handler for a start element, end element,
2529 markup to be passed to the default handler set by <code><a
2533 not a default handler.