RE: [libxml++] Rename Element::add_content() to add_text_content?
- From: Murray Cumming Comneon com
- To: libxmlplusplus-general lists sourceforge net
- Subject: RE: [libxml++] Rename Element::add_content() to add_text_content?
- Date: Mon, 27 Oct 2003 07:44:34 +0100
> On Sat, 2003-10-25 at 10:28, Murray Cumming Comneon com wrote:
> > > > We don't have Element::add_entity_reference() I think.
> > > >
> > > > If needed please provide a patch.
> > >
> > > Heh, wow, this makes me wonder if we have been following each
> > > others' discussions at all! :-) Most of my discussion in
> > > this matter have been with murraryc and Daniel Veillard, so I
> > > do not intend to critisize you.
> > > add_entity_reference() is what I have been wanting to have
> > > for some time. However, it is quite difficult to implement,
> > > not directly available through libxml2, and we would have to
> > > pull code from libxml2, or submit patches to libxml2 to
> > > expose some facilities it uses internally.
> >
> > That's new to me. I would have expected that to be simple.
> After all,
> > I think that an entity reference is just something between & and ;
> > characters. Whether it is a resolvable entity reference is,
> of course,
> > more complex.
>
> Nope, that is encoded at &whatever;. The DOM *parser* can
> attempt to resolve entity references, but a dom builder must
> be able to add the appropriate nodes to the tree.
Sorry, I still don't understand. If I do
element.add_entity_reference(someentity);
1. what is difficult about adding "&someentity;" as an extra child text
node?
2. Should it ever be anything other than "&someentity;"?
Murray Cumming
www.murrayc.com
murrayc usa net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]