tree be58418ef7cf598ac7edf797b1c8b1f8990dd4ca
parent ae960cac9664328200aa37866cfa1d5e8c3bb1fe
author Nick Wellnhofer <wellnhofer@aevum.de> 1714485188 +0200
committer Nick Wellnhofer <wellnhofer@aevum.de> 1714485188 +0200

tree: Don't call xmlNewCharRef in xmlNodeParseContent

xmlNewCharRef also tries to handle strings like '&name;' but in
xmlNodeParseContentInternal, we really want to use the possibly invalid
name without modification. Otherwise, content like '&&quot;' could
create a reference to a predefined entity.