Cart
[Home] [By Thread] [By Date] [Recent Entries]
> 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?) This is reasonable, it's just not what we wanted to do, because we have existing programs (which previously processed "normalised SGML") which (a) expect to see all entities fully expanded and (b) expect to see pcdata including references put together into a single bit. For example, our grep-like program should match the example when searching for the text "xa". -- Richard xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
