RE: [libxml++] libxml++ future

[Murray Cumming <murrayc usa net>]

On Mon, 2003-09-29 at 20:17, Dan Dennedy wrote:
> > So I think a large part of this is: Adding 
> > class Entity : public Node
> > and telling libxml to give us Entities instead of substituting them. I
> > think there's some libxml function for that. (We should add the option
> > to libxml++ as well).
> 
> I did some work over the weekend.

Excellent. You work fast.

>  I extended SaxParser with internal
> subset, entity declaration, and entity reference callbacks. In my parser
> implementation, I also implemented the getEntity callback and told
> SaxParser to use it, but I was curious about the difference between
> getEntity and reference.

I can't find documentation on these callbacks. I think you should ask on
the libxml list.

>  I was able to get everything working except for
> keeping entity references in tact--at least as far as xml serialization
> is concerned.

Again, the libxml mailing list will be useful.

>  I need to anaylze the resultant node tree further to see
> if content is a list of text and entity reference nodes. Either,
> libxml2, encodes entity references from "&ref;" to "&ref;" or I can
> set resolveEntities=1 in the libxml2 parser context to make it expand.
> The SAX reference callback is never called upon.
> 
> Also, I still need to subclass Node as Entity in order to prevent a
> libxml2 xmlEntity* from being a part of the interface.

-- 
Murray Cumming
murrayc usa net
www.murrayc.com