[xml] Adjacent text node merging
- From: Nikolay Sivov <bunglehead gmail com>
- To: xml gnome org
- Subject: [xml] Adjacent text node merging
- Date: Sat, 04 May 2013 11:59:50 +0400
I think it's more a question for Daniel, but any help is welcome of
course. Libxml2 merges text nodes to a single node when you add text
child next to existing text node for example, so at least
xmlAddNextSibling, xmlAddPrevSibling and xmlAddChild are doing that. For
a project I'm using libxml2 I want all nodes to be preserved as I add
them, so for example I can edit text content of particular text node in
children list. The question is what could or will potentially break if
I'll use my own versions of these tree manipulation calls that do not
perform such merging? e.g. does a lib really expect to have only one
text node with no text siblings somewhere in the code, or maybe libxslt
does?
P.S. attached patch is just to fix a compiler warning I'm seeing with
current git builds, obviously completely unrelated to this topic.
Attachment:
0001-Cast-encoding-name-to-char-pointer-to-match-arg-type.patch
Description: Text document
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]