[ expat-Bugs-707021 ] Improve internal entity reporting

Bugs item #707021, was opened at 2003-03-20 12:30
Message generated for change (Comment added) made by fdrake
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=707021&group_id=10127

Category: None
Group: Feature Request
Status: Open
>Resolution: Postponed
Priority: 5
Submitted By: Karl Waclawek (kwaclaw)
Assigned to: Karl Waclawek (kwaclaw)
Summary: Improve internal entity reporting

Initial Comment:
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
  ends.
- 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
  skipped

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.

----------------------------------------------------------------------

>Comment By: Fred L. Drake, Jr. (fdrake)
Date: 2005-01-28 00:02

Message:
Logged In: YES 
user_id=3066

Postponed to Expat 3.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110127&aid=707021&group_id=10127