Follow-up Comment #12, bug #67508 (group denemo):
[comment #11 comment #11:]
> "However I think there is now enough evidence of a regression in libxml2
> v2.13.x+ that you may want to report this - I don't think there is anything
> wrong with Upbeat,denemo XML syntax and xmllint doesn't report anything
> incorrect in it."
>
> Is "you" here someone with a knowledge of Denemo and libxml2? I don't think
> there is such a person about - some years ago the saving of denemo files in
> compressed .gz format stopped working and I was unable to find out why...
> Sorry to be so clueless.
I sort-of assumed you knew the code better than me since you responded! I
looked at it for the first time a couple days ago because it came up in Debian
"Tiny Tasks" as a package that needed some 'easy' changes to fix the build
failure and update for GCC v15!
I've come to the conclusion there are two issues here:
1. libxml2 xmlNodeListGetString() has changed its behaviour since v2.13.0
*BUT* it was previously incorrectly processing child elements as well as
attributes, text, entities, etc.
2. denemo incorrectly relied on that behaviour and as a result is now broken.
So libxml2 has become more correct but in the process broken applications that
rely on its pre v2.13 behaviour.
The correct fix here is, I think, for denemo to import child element nodes in
the 'correct' way (what-ever that is - I'm not a libxml2 user!).
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67508>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
