[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX Locator vs {start,end}Entity

• To: "Richard Tobin" <richard@c...>,<xml-dev@l...>
• Subject: Re: SAX Locator vs {start,end}Entity
• From: "Karl Waclawek" <karl@w...>
• Date: Wed, 19 Feb 2003 14:14:26 -0500
• References: <200302191848.SAA23972@m...>

----- Original Message -----
From: "Richard Tobin" <richard@c...>
To: <xml-dev@l...>
Sent: Wednesday, February 19, 2003 1:48 PM


> Does SAX make any guarantee about which entity the locator will refer
> to during the startEntity and endEntity callbacks?

Well the docs for getLine/ColumnNumber say this:

<quote>
The return value is an approximation of the line number in the document entity
or external parsed entity where the markup triggering the event appears.
</quote>

Which would mean the currently parsed entity.
In addition, the docs for getEncoding and getXMLVersion in Locator2
seem to imply the same.

Internal entities are a problem somehow, since they are not based
on a separate file/stream. The specs warn that internal entity expansion
may throw off the reported line/column numbers.

When I wrote a SAX adapter for Expat, this is how I interpreted it.


Karl

• References:
  • SAX Locator vs {start,end}Entity
    • From: Richard Tobin <richard@c...>

• Prev by Date: Re: SAX Locator vs {start,end}Entity
• Next by Date: XBRL loan applications [Was: Re:Are the publishing users happy? Why not?]
• Previous by thread: Re: SAX Locator vs {start,end}Entity
• Next by thread: XBRL loan applications [Was: Re:Are the publishing users happy? Why not?]
• Index(es):
  • Date
  • Thread