>I don't see how that excludes my example. The tags and elements *do*
>begin and end in the same entity.
Sorry, the sentence "it may end in a different entity from the one it
started in" "tricked" me into not reading your example fully, I thought I
saw "a</b>c" and not "a<b/>c" (as you stated).
>(suppose foo is defined as "a<b/>c";
>then the first bit returned from "x&foo;y" is "xa".
Ok. My current design will first return PCData="x", then entity ref="foo",
and (if the client want entities expanded: PCData="a" followed by
EmptyElement="b" and then PCData="c".)
ie it may return two consecutive PCData's, with perhaps some
EntityExpansionStart and -End signals between them.
(Is this design flawed?)
Cheers,
Jarle