Home | All Classes | Main Classes | Annotated | Grouped Classes | Functions |
The TQXmlLexicalHandler class provides an interface to report the lexical content of XML data. More...
All the functions in this class are reentrant when TQt is built with thread support.
#include <ntqxml.h>
Inherited by TQXmlDefaultHandler.
The events in the lexical handler apply to the entire document, not just to the document element, and all lexical handler events appear between the content handler's startDocument and endDocument events.
You can set the lexical handler with TQXmlReader::setLexicalHandler().
This interface's design is based on the the SAX2 extension LexicalHandler.
The interface provides the startDTD(), endDTD(), startEntity(), endEntity(), startCDATA(), endCDATA() and comment() functions.
See also the Introduction to SAX2.
See also TQXmlDTDHandler, TQXmlDeclHandler, TQXmlContentHandler, TQXmlEntityResolver, TQXmlErrorHandler, and XML.
The reader calls this function to report an XML comment anywhere in the document. It reports the text of the comment in ch.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error message.
The reader calls this function to report the end of a CDATA section.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error message.
See also startCDATA() and TQXmlContentHandler::characters().
The reader calls this function to report the end of a DTD declaration, if any.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error message.
See also startDTD().
The reader calls this function to report the end of an entity called name.
For every startEntity() call, there is a corresponding endEntity() call. The calls to startEntity() and endEntity() are properly nested.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error message.
See also startEntity(), TQXmlContentHandler::skippedEntity(), and TQXmlSimpleReader::setFeature().
The reader calls this function to get an error string if any of the handler functions returns FALSE.
The reader calls this function to report the start of a CDATA section. The content of the CDATA section is reported through the TQXmlContentHandler::characters() function. This function is intended only to report the boundary.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error message.
See also endCDATA().
The reader calls this function to report the start of a DTD declaration, if any. It reports the name of the document type in name, the public identifier in publicId and the system identifier in systemId.
If the public identifier is missing, publicId is set to TQString::null. If the system identifier is missing, systemId is set to TQString::null. Note that it is not valid XML to have a public identifier but no system identifier; in such cases a parse error will occur.
All declarations reported through TQXmlDTDHandler or TQXmlDeclHandler appear between the startDTD() and endDTD() calls.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error message.
See also endDTD().
The reader calls this function to report the start of an entity called name.
Note that if the entity is unknown, the reader reports it through TQXmlContentHandler::skippedEntity() and not through this function.
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error message.
See also endEntity() and TQXmlSimpleReader::setFeature().
This file is part of the TQt toolkit. Copyright © 1995-2007 Trolltech. All Rights Reserved.
Copyright © 2007 Trolltech | Trademarks | TQt 3.3.8
|