Interface Summary : ILexicalHandler

SAX2 extension handler for lexical events.
This module, both source code and documentation, is in the Public Domain, and comes with NO WARRANTY.

This is an optional extension handler for SAX2 to provide lexical information about an XML document, such as comments and CDATA section boundaries. XML readers are not required to recognize this handler, and it is not part of core-only SAX2 distributions.

The events in the lexical handler apply to the entire document, not just to the document element, and all lexical handler events must appear between the content handler's startDocument and endDocument events.

To set the LexicalHandler for an XML reader, use the getProperty method with the property name http://xml.org/sax/properties/lexical-handler and an object implementing this interface (or nil) as the value. If the reader does not report lexical events, it will throw a ESAXNotRecognizedException when you attempt to register the handler.


Since : SAX 2.0 (extensions 1.0)

Methods

procedure startDTD(SAXString, SAXString, SAXString)
procedure endDTD()
procedure startEntity(SAXString)
procedure endEntity(SAXString)
procedure startCDATA()
procedure endCDATA()
procedure comment(SAXString)


procedure startDTD(const name : SAXString; const publicId : SAXString; const systemId : SAXString);

Report the start of DTD declarations, if any.

This method is intended to report the beginning of the DOCTYPE declaration; if the document has no DOCTYPE declaration, this method will not be invoked.

All declarations reported through IDTDHandler or IDeclHandler events must appear between the startDTD and endDTD events. Declarations are assumed to belong to the internal DTD subset unless they appear between startEntity and endEntity events. Comments and processing instructions from the DTD should also be reported between the startDTD and endDTD events, in their original order of (logical) occurrence; they are not required to appear in their correct locations relative to DTDHandler or DeclHandler events, however.

Note that the start/endDTD events will appear within the start/endDocument events from IContentHandler and before the first startElement event.


Parameter : name The document type name.
Parameter : publicId The declared public identifier for the external DTD subset, or an empty string if none was declared.
Parameter : systemId The declared system identifier for the external DTD subset, or an empty string if none was declared. (Note that this is not resolved against the document base URI.)
Exception : ESAXException The application may raise an exception.
See : ILexicalHandler.endDTD
See : ILexicalHandler.startEntity

Top


procedure endDTD();

Report the end of DTD declarations.

This method is intended to report the end of the DOCTYPE declaration; if the document has no DOCTYPE declaration, this method will not be invoked.


Exception : ESAXException The application may raise an exception.
See : ILexicalHandler.startDTD

Top


procedure startEntity(const name : SAXString);

Report the beginning of some internal and external XML entities.

The reporting of parameter entities (including the external DTD subset) is optional, and SAX2 drivers that report ILexicalHandler events may not implement it; you can use the http://xml.org/sax/features/lexical-handler/parameter-entities feature to query or control the reporting of parameter entities.

General entities are reported with their regular names, parameter entities have '%' prepended to their names, and the external DTD subset has the pseudo-entity name "[dtd]".

When a SAX2 driver is providing these events, all other events must be properly nested within start/end entity events. There is no additional requirement that events from IDeclHandler or IDTDHandler be properly ordered.

Note that skipped entities will be reported through the skippedEntity event, which is part of the IContentHandler interface.

Because of the streaming event model that SAX uses, some entity boundaries cannot be reported under any circumstances:

These will be silently expanded, with no indication of where the original entity boundaries were.

Note also that the boundaries of character references (which are not really entities anyway) are not reported.

All start/endEntity events must be properly nested.


Parameter : name The name of the entity. If it is a parameter entity, the name will begin with '%', and if it is the external DTD subset, it will be "[dtd]".
Exception : SAXException The application may raise an exception.
See : ILexicalHandler.endEntity
See : IDeclHandler.internalEntityDecl
See : IDeclHandler.externalEntityDecl /

Top


procedure endEntity(const name : SAXString);

Report the end of an entity.
Parameter : name The name of the entity that is ending.
Exception : ESAXException The application may raise an exception.
See : ILexicalHandler.startEntity

Top


procedure startCDATA();

Report the start of a CDATA section.

The contents of the CDATA section will be reported through the regular characters event; this event is intended only to report the boundary.


Exception : ESAXException The application may raise an exception.
See : ILexicalHandler.endCDATA

Top


procedure endCDATA();

Report the end of a CDATA section.
Exception : ESAXException The application may raise an exception.
See : ILexicalHandler.startCDATA

Top


procedure comment(const ch : SAXString);

Report an XML comment anywhere in the document.

This callback will be used for comments inside or outside the document element, including comments in the external DTD subset (if read). Comments in the DTD must be properly nested inside start/endDTD and start/endEntity events (if used).


Parameter : ch The characters in the comment.
Exception : ESAXException The application may raise an exception.

Top