Home | History | Annotate | Download | only in doc

Lines Matching full:handler

80     <li><a href="#setting">Handler Setting Functions</a>
154 handler) functions with the parser and then start feeding it the
156 call the appropriate handler for that part (if you've registered one.)
177 <dd>Set handler for text.</dd>
190 above functions (it doesn't need to set a character handler.) The
193 parent element that contains them. The start handler does all the
217 } /* End of start handler */
226 } /* End of end handler */
452 information onto the stack in the start handler and you pop it off in
453 the end handler.</p>
460 which the element started. When the end tag handler encounters the
504 manipulated in the start and end handlers. The end tag handler should
505 be the mirror image of the start tag handler. This is necessary to
506 properly model containment. Since, in the start tag handler, we
508 in the end handler, we need to manipulate it <em>before</em> the main
510 handler, then we'd have had to decrement it last thing in the end
511 handler.</p>
528 <p>One common case where multiple calls to a single handler may need
530 content passed to the character data handler (set by <code><a href=
535 reported by a single call to the character data handler. Expat, like
554 set a handler that uses the information in the XML declaration to
592 occur. This means that your start handler will not see these
599 are passed to the appropriate handler in expanded form. By default
619 tag handler and the EndNamespaceDeclHandler is called after the
621 start handler gets passed the prefix and URI for the namespace. For a
624 unset. The namespace end handler just gets the prefix for the closing
630 tag handler is called, once for each declaration.</p>
665 to the <code>UnknownEncodingHandler</code>. This handler gets passed
667 structure. Your handler must fill in this structure and return
669 encoding. Otherwise the handler should return
670 <code>XML_STATUS_ERROR</code>. The handler also gets passed a pointer
672 you set the handler.</p>
711 references are silently ignored. Otherwise, it calls your handler with
714 <p>Your handler isn't actually responsible for parsing the entity, but
723 your handler should be prepared to be called recursively.</p>
742 entity reference handler as described above.</p>
747 parsing temporarily from within a handler function, even if more data
879 <p>To stop parsing from a handler function, use the <code><a href=
997 XML_GetBuffer</a></code> must not be called from within a handler
999 did not call the handler. For example, it is OK to call the parsing
1099 call-back handler, except when aborting (when <code>resumable</code>
1104 <li> the end element handler for empty elements when stopped in the
1105 start element handler,</li>
1106 <li> the end namespace declaration handler when stopped in the end
1107 element handler,</li>
1108 <li> the character data handler when stopped in the character data handler
1146 external entity reference handler returns. It is up to the
1147 implementation of that handler to call <code><a href=
1164 within a handler call-back. Returns same status codes as <code><a
1210 <h3><a name="setting">Handler Setting</a></h3>
1213 application may choose to set or change the handler for a parsing event
1216 way it could do this is to set the character handler when a para start tag
1219 <p>A handler may be <em>unset</em> by providing a NULL pointer to the
1220 appropriate handler setter. None of the handler setting functions have
1230 <div class="handler">
1242 <p>Set handler for start (and empty) tags. Attributes are passed to the start
1243 handler as a pointer to a vector of char pointers. Each attribute seen in
1251 <div class="handler">
1262 <p>Set handler for end (and empty) tags. As noted above, an empty tag
1266 <div class="handler">
1276 <div class="handler">
1288 <p>Set a text handler. The string your handler receives
1291 free of markup may still result in a sequence of calls to this handler.
1293 be split across calls to this handler. Note: Setting this handler to NULL
1299 <div class="handler">
1312 <p>Set a handler for processing instructions. The target is the first word
1317 <div class="handler">
1328 <p>Set a handler for comments. The data is all text inside the comment
1332 <div class="handler">
1342 <p>Set a handler that gets called at the beginning of a CDATA section.</p>
1345 <div class="handler">
1355 <p>Set a handler that gets called at the end of a CDATA section.</p>
1358 <div class="handler">
1368 <div class="handler">
1381 <p>Sets a handler for any characters in the document which wouldn't
1384 be reported but which currently has no handler set. The characters
1388 default handler. There are no guarantees about how characters are
1389 divided between calls to the default handler: for example, a comment
1390 might be split between multiple calls. Setting the handler with
1393 passed to the default handler.</p>
1399 <div class="handler">
1411 <p>This sets a default handler, but doesn't inhibit the expansion of
1413 to the default handler.</p>
1419 <div class="handler">
1433 <p>Set an external entity reference handler. This handler is also
1442 valid only until the handler returns, so if the referenced entity is
1454 <p>There are a couple of ways in which this handler differs from
1455 others. First, this handler returns a status indicator (an
1469 <p>Since this handler may be called recursively, it should not be saving
1481 handler set using <code><a href="#XML_SetExternalEntityRefHandler"
1483 NULL, the argument passed to the handler function will be the parser
1489 <code>void *</code> to be passed to the handler, while the handler
1494 actual type of the argument passed to the handler and to manage it
1498 <div class="handler">
1502 XML_SkippedEntityHandler handler)
1510 <p>Set a skipped entity handler. This is called in two situations:</p>
1525 <div class="handler">
1545 <p>Set a handler to deal with encodings other than the <a
1549 given parser.</p> <p>If the handler knows how to deal with an encoding
1552 should return <code>XML_STATUS_ERROR</code>. The handler will be called
1555 the handler.</p>
1574 <div class="handler">
1586 <p>Set a handler to be called when a namespace is declared. Namespace
1588 handler is called before the start tag handler for each namespace declared
1592 <div class="handler">
1603 <p>Set a handler to be called when leaving the scope of a namespace
1605 after the handler for the end tag of the element in which the
1609 <div class="handler">
1619 <div class="handler">
1632 <p>Sets a handler that is called for XML declarations and also for
1642 <div class="handler">
1656 <p>Set a handler that is called at the start of a DOCTYPE declaration,
1662 <div class="handler">
1672 <p>Set a handler that is called at the end of a DOCTYPE declaration,
1676 <div class="handler">
1686 <div class="handler">
1725 <p>Sets a handler for element declarations in a DTD. The handler gets
1758 <div class="handler">
1773 <p>Set a handler for attlist declarations in the DTD. This handler is
1776 handler. The <code>elname</code> parameter returns the name of the
1791 <div class="handler">
1795 XML_EntityDeclHandler handler);
1809 <p>Sets a handler that will be called for all entity declarations.
1825 <div class="handler">
1840 <p>Set a handler that receives declarations of unparsed entities. These
1846 <p>This handler is obsolete and is provided for backwards
1851 <div class="handler">
1865 <p>Set a handler that receives notation declarations.</p>
1868 <div class="handler">
1878 <p>Set a handler that is called if the document is not "standalone".
1881 declaration. If this handler returns <code>XML_STATUS_ERROR</code>,
1902 called from within a DTD declaration handler.</p>
1976 <p>This should only be called from within a handler during an active
1978 the handler that made the call. This input buffer contains the
2054 When attributes are reported to the start handler in the atts vector,
2059 <code>atts</code> array passed to the start tag handler of the first
2061 call to a start handler. If called inside a start handler, then that
2073 attribute. If called inside a start handler, then that means the
2128 external entity reference handler set via <code><a href=
2143 the external entity reference handler returns without action.</p>
2173 This can be called within a handler for a start element, end element,
2175 markup to be passed to the default handler set by <code><a
2179 not a default handler.