diff options
Diffstat (limited to 'doc/man/man3/tqxmlcontenthandler.3qt')
| -rw-r--r-- | doc/man/man3/tqxmlcontenthandler.3qt | 52 |
1 files changed, 26 insertions, 26 deletions
diff --git a/doc/man/man3/tqxmlcontenthandler.3qt b/doc/man/man3/tqxmlcontenthandler.3qt index bd5dee5fa..f42807693 100644 --- a/doc/man/man3/tqxmlcontenthandler.3qt +++ b/doc/man/man3/tqxmlcontenthandler.3qt @@ -1,5 +1,5 @@ '\" t -.TH QXmlContentHandler 3qt "2 February 2007" "Trolltech AS" \" -*- nroff -*- +.TH TQXmlContentHandler 3qt "2 February 2007" "Trolltech AS" \" -*- nroff -*- .\" Copyright 1992-2007 Trolltech ASA. All rights reserved. See the .\" license file included in the distribution for a complete license .\" statement. @@ -7,18 +7,18 @@ .ad l .nh .SH NAME -QXmlContentHandler \- Interface to report the logical content of XML data +TQXmlContentHandler \- Interface to report the logical content of XML data .SH SYNOPSIS All the functions in this class are reentrant when TQt is built with thread support.</p> .PP -\fC#include <ntqxml.h>\fR +\fC#include <tqxml.h>\fR .PP -Inherited by QXmlDefaultHandler. +Inherited by TQXmlDefaultHandler. .PP .SS "Public Members" .in +1c .ti -1c -.BI "virtual void \fBsetDocumentLocator\fR ( QXmlLocator * locator ) = 0" +.BI "virtual void \fBsetDocumentLocator\fR ( TQXmlLocator * locator ) = 0" .br .ti -1c .BI "virtual bool \fBstartDocument\fR () = 0" @@ -33,7 +33,7 @@ Inherited by QXmlDefaultHandler. .BI "virtual bool \fBendPrefixMapping\fR ( const TQString & prefix ) = 0" .br .ti -1c -.BI "virtual bool \fBstartElement\fR ( const TQString & namespaceURI, const TQString & localName, const TQString & qName, const QXmlAttributes & atts ) = 0" +.BI "virtual bool \fBstartElement\fR ( const TQString & namespaceURI, const TQString & localName, const TQString & qName, const TQXmlAttributes & atts ) = 0" .br .ti -1c .BI "virtual bool \fBendElement\fR ( const TQString & namespaceURI, const TQString & localName, const TQString & qName ) = 0" @@ -55,35 +55,35 @@ Inherited by QXmlDefaultHandler. .br .in -1c .SH DESCRIPTION -The QXmlContentHandler class provides an interface to report the logical content of XML data. +The TQXmlContentHandler class provides an interface to report the logical content of XML data. .PP -If the application needs to be informed of basic parsing events, it can implement this interface and activate it using QXmlReader::setContentHandler(). The reader can then report basic document-related events like the start and end of elements and character data through this interface. +If the application needs to be informed of basic parsing events, it can implement this interface and activate it using TQXmlReader::setContentHandler(). The reader can then report basic document-related events like the start and end of elements and character data through this interface. .PP The order of events in this interface is very important, and mirrors the order of information in the document itself. For example, all of an element's content (character data, processing instructions, and sub-elements) appears, in order, between the startElement() event and the corresponding endElement() event. .PP -The class QXmlDefaultHandler provides a default implementation for this interface; subclassing from the QXmlDefaultHandler class is very convenient if you only want to be informed of some parsing events. +The class TQXmlDefaultHandler provides a default implementation for this interface; subclassing from the TQXmlDefaultHandler class is very convenient if you only want to be informed of some parsing events. .PP The startDocument() function is called at the start of the document, and endDocument() is called at the end. Before parsing begins setDocumentLocator() is called. For each element startElement() is called, with endElement() being called at the end of each element. The characters() function is called with chunks of character data; ignorableWhitespace() is called with chunks of whitespace and processingInstruction() is called with processing instructions. If an entity is skipped skippedEntity() is called. At the beginning of prefix-URI scopes startPrefixMapping() is called. .PP See also the Introduction to SAX2. .PP -See also QXmlDTDHandler, QXmlDeclHandler, QXmlEntityResolver, QXmlErrorHandler, QXmlLexicalHandler, and XML. +See also TQXmlDTDHandler, TQXmlDeclHandler, TQXmlEntityResolver, TQXmlErrorHandler, TQXmlLexicalHandler, and XML. .SH MEMBER FUNCTION DOCUMENTATION -.SH "bool QXmlContentHandler::characters ( const TQString & ch )\fC [pure virtual]\fR" -The reader calls this function when it has parsed a chunk of character data (either normal character data or character data inside a CDATA section; if you need to distinguish between those two types you must use QXmlLexicalHandler::startCDATA() and QXmlLexicalHandler::endCDATA()). The character data is reported in \fIch\fR. +.SH "bool TQXmlContentHandler::characters ( const TQString & ch )\fC [pure virtual]\fR" +The reader calls this function when it has parsed a chunk of character data (either normal character data or character data inside a CDATA section; if you need to distinguish between those two types you must use TQXmlLexicalHandler::startCDATA() and TQXmlLexicalHandler::endCDATA()). The character data is reported in \fIch\fR. .PP Some readers report whitespace in element content using the ignorableWhitespace() function rather than using this one. .PP A reader may report the character data of an element in more than one chunk; e.g. a reader might want to report "a<b" in three characters() events ("a ", "<" and " b"). .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. -.SH "bool QXmlContentHandler::endDocument ()\fC [pure virtual]\fR" +.SH "bool TQXmlContentHandler::endDocument ()\fC [pure virtual]\fR" The reader calls this function after it has finished parsing. It is called just once, and is the last handler function called. It is called after the reader has read all input or has abandoned parsing because of a fatal error. .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. .PP See also startDocument(). -.SH "bool QXmlContentHandler::endElement ( const TQString & namespaceURI, const TQString & localName, const TQString & qName )\fC [pure virtual]\fR" +.SH "bool TQXmlContentHandler::endElement ( const TQString & namespaceURI, const TQString & localName, const TQString & qName )\fC [pure virtual]\fR" The reader calls this function when it has parsed an end element tag with the qualified name \fIqName\fR, the local name \fIlocalName\fR and the namespace URI \fInamespaceURI\fR. .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. @@ -93,7 +93,7 @@ See also the namespace description. See also startElement(). .PP Example: xml/tagreader/structureparser.cpp. -.SH "bool QXmlContentHandler::endPrefixMapping ( const TQString & prefix )\fC [pure virtual]\fR" +.SH "bool TQXmlContentHandler::endPrefixMapping ( const TQString & prefix )\fC [pure virtual]\fR" The reader calls this function to signal the end of a prefix mapping for the prefix \fIprefix\fR. .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. @@ -101,35 +101,35 @@ If this function returns FALSE the reader stops parsing and reports an error. Th See also the namespace description. .PP See also startPrefixMapping(). -.SH "TQString QXmlContentHandler::errorString ()\fC [pure virtual]\fR" +.SH "TQString TQXmlContentHandler::errorString ()\fC [pure virtual]\fR" The reader calls this function to get an error string, e.g. if any of the handler functions returns FALSE. -.SH "bool QXmlContentHandler::ignorableWhitespace ( const TQString & ch )\fC [pure virtual]\fR" +.SH "bool TQXmlContentHandler::ignorableWhitespace ( const TQString & ch )\fC [pure virtual]\fR" Some readers may use this function to report each chunk of whitespace in element content. The whitespace is reported in \fIch\fR. .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. -.SH "bool QXmlContentHandler::processingInstruction ( const TQString & target, const TQString & data )\fC [pure virtual]\fR" +.SH "bool TQXmlContentHandler::processingInstruction ( const TQString & target, const TQString & data )\fC [pure virtual]\fR" The reader calls this function when it has parsed a processing instruction. .PP \fItarget\fR is the target name of the processing instruction and \fIdata\fR is the data in the processing instruction. .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. -.SH "void QXmlContentHandler::setDocumentLocator ( QXmlLocator * locator )\fC [pure virtual]\fR" -The reader calls this function before it starts parsing the document. The argument \fIlocator\fR is a pointer to a QXmlLocator which allows the application to get the parsing position within the document. +.SH "void TQXmlContentHandler::setDocumentLocator ( TQXmlLocator * locator )\fC [pure virtual]\fR" +The reader calls this function before it starts parsing the document. The argument \fIlocator\fR is a pointer to a TQXmlLocator which allows the application to get the parsing position within the document. .PP Do not destroy the \fIlocator\fR; it is destroyed when the reader is destroyed. (Do not use the \fIlocator\fR after the reader is destroyed). -.SH "bool QXmlContentHandler::skippedEntity ( const TQString & name )\fC [pure virtual]\fR" +.SH "bool TQXmlContentHandler::skippedEntity ( const TQString & name )\fC [pure virtual]\fR" Some readers may skip entities if they have not seen the declarations (e.g. because they are in an external DTD). If they do so they report that they skipped the entity called \fIname\fR by calling this function. .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. -.SH "bool QXmlContentHandler::startDocument ()\fC [pure virtual]\fR" -The reader calls this function when it starts parsing the document. The reader calls this function just once, after the call to setDocumentLocator(), and before any other functions in this class or in the QXmlDTDHandler class are called. +.SH "bool TQXmlContentHandler::startDocument ()\fC [pure virtual]\fR" +The reader calls this function when it starts parsing the document. The reader calls this function just once, after the call to setDocumentLocator(), and before any other functions in this class or in the TQXmlDTDHandler class are called. .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. .PP See also endDocument(). .PP Example: xml/tagreader/structureparser.cpp. -.SH "bool QXmlContentHandler::startElement ( const TQString & namespaceURI, const TQString & localName, const TQString & qName, const QXmlAttributes & atts )\fC [pure virtual]\fR" +.SH "bool TQXmlContentHandler::startElement ( const TQString & namespaceURI, const TQString & localName, const TQString & qName, const TQXmlAttributes & atts )\fC [pure virtual]\fR" The reader calls this function when it has parsed a start element tag. .PP There is a corresponding endElement() call when the corresponding end element tag is read. The startElement() and endElement() calls are always nested correctly. Empty element tags (e.g. \fC<x/>\fR) cause a startElement() call to be immediately followed by an endElement() call. @@ -145,7 +145,7 @@ See also the namespace description. See also endElement(). .PP Example: xml/tagreader/structureparser.cpp. -.SH "bool QXmlContentHandler::startPrefixMapping ( const TQString & prefix, const TQString & uri )\fC [pure virtual]\fR" +.SH "bool TQXmlContentHandler::startPrefixMapping ( const TQString & prefix, const TQString & uri )\fC [pure virtual]\fR" The reader calls this function to signal the begin of a prefix-URI namespace mapping scope. This information is not necessary for normal namespace processing since the reader automatically replaces prefixes for element and attribute names. .PP Note that startPrefixMapping() and endPrefixMapping() calls are not guaranteed to be properly nested relative to each other: all startPrefixMapping() events occur before the corresponding startElement() event, and all endPrefixMapping() events occur after the corresponding endElement() event, but their order is not otherwise guaranteed. @@ -159,7 +159,7 @@ See also the namespace description. See also endPrefixMapping(). .SH "SEE ALSO" -.BR http://doc.trolltech.com/qxmlcontenthandler.html +.BR http://doc.trolltech.com/tqxmlcontenthandler.html .BR http://www.trolltech.com/faq/tech.html .SH COPYRIGHT Copyright 1992-2007 Trolltech ASA, http://www.trolltech.com. See the |