#247 Improve internal entity reporting

Feature Request

Currently there are limitations to the reporting
of internal entities, which affects DOM building
and validation on top of Epat:

- When internal entities are expanded, then there
is no way to determine when an entity starts or
- When they are not expanded (in content) then
the entity references are reported through the
skippedEntityHandler or the defaultHandler,
which is a crude way to detect entity boundaries
since it now places the burden of expansion on
the call-back code.
- PE references in entity values (declarations)
and GE references in attribute values are always
silently expanded (if possible) and there is
no way to detect entity boundaries, even when

It would be nice to have a way to report internal
entity boundaries in character content, entity values
and attribute values in a uniform way, whether
the entity is expanded or not.

It could be an optional feature, but likely not
through setting start/endEntityHandlers, since
such handlers would not work for attribute and
entity values, as these are not reported in a
streaming fashion.


  • Fred L. Drake, Jr.

    • status: open --> open-postponed
  • Fred L. Drake, Jr.

    Logged In: YES

    Postponed to Expat 3.


Log in to post a comment.