The QXmlLexicalHandler class provides an interface to report the lexical content of XML data.
.PP
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.
.PP
You can set the lexical handler with QXmlReader::setLexicalHandler().
.PP
This interface's design is based on the the SAX2 extension LexicalHandler.
.PP
The interface provides the startDTD(), endDTD(), startEntity(), endEntity(), startCDATA(), endCDATA() and comment() functions.
.PP
See also the Introduction to SAX2.
.PP
See also QXmlDTDHandler, QXmlDeclHandler, QXmlContentHandler, QXmlEntityResolver, QXmlErrorHandler, and XML.
The reader calls this function to report the start of a CDATA section. The content of the CDATA section is reported through the QXmlContentHandler::characters() function. This function is intended only to report the boundary.
.PP
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 start of a DTD declaration, if any. It reports the name of the document type in \fIname\fR, the public identifier in \fIpublicId\fR and the system identifier in \fIsystemId\fR.
.PP
If the public identifier is missing, \fIpublicId\fR is set to QString::null. If the system identifier is missing, \fIsystemId\fR is set to QString::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.
.PP
All declarations reported through QXmlDTDHandler or QXmlDeclHandler appear between the startDTD() and endDTD() calls.
.PP
If this function returns FALSE the reader stops parsing and reports an error. The reader uses the function errorString() to get the error message.