Re: [Saxdotnet-devel] SAX holes
Brought to you by:
jeffrafter,
kwaclaw
From: Karl W. <ka...@wa...> - 2004-12-08 00:24:20
|
> Karl Waclawek wrote: > > >> <quote> >> Because of the streaming event model that SAX uses, some entity boundaries cannot be reported >> under >> any circumstances: >> >> a.. general entities within attribute values >> b.. parameter entities within declarations >> These will be silently expanded, with no indication of where the original entity boundaries were. >> </quote> > > > The problem is not failing to report entity boundaries. That's minor. The problem is when an > entity in an attribute value is not expanded. This has the potential to lose information silently, > which I think is a very bad thing. Absolutely, but the reason for that is that the boundaries can't be reported. If they could, then SkippedEntity() could be called. While working on Expat we discussed that potentially we could insert invalid XML characters into the attribute value reported to the application, to serve as markers for the start and end of the entity. (as per user option) But nothing really caught on. Karl |