Hello,
It's not misbehaving and it's not illegal xml. It's a well documented
fact that the character data function may be called more than once. The
normal programming practice is to put the strings that are given to you
at each call into a buffer. Then you write code in the end handler to
Hi Jeff,
Nachricht vom Montag, 18. August 2003, 18:14:37:
I've come across this frustrating behavior with the XML parser when it
reads an escaped ampersand (amp;)
If the xml being evaluated is: COLORSBlue, Green amp; Red/COLORS
it calls the character data handler 3 times:
the first
Timo Boettcher wrote:
Hi Jeff,
Nachricht vom Montag, 18. August 2003, 18:14:37:
I've come across this frustrating behavior with the XML parser when it
reads an escaped ampersand (amp;)
If the xml being evaluated is: COLORSBlue, Green amp; Red/COLORS
The ampersand character () and
I've come across this frustrating behavior with the XML parser when it
reads an escaped ampersand (amp;)
If the xml being evaluated is: COLORSBlue, Green amp; Red/COLORS
it calls the character data handler 3 times:
the first time the $data is Blue, Green
the second time is
and the third
This is normal. You have illegal XML there, as it should be
in ![CDATA[ value ]]. I have run across this, and have
to clean it up with an awk script. Ampersand is a no-no.
Just running xmllint on the file will tell you about the problem(s).
_justin
Jeff Bearer wrote:
I've come across this
The data contains escaped ampersands - amp;
Which is as far as I know the way one represents ampersands in their
data. In my post below, the value of $data the second time is
because it has been evaluated by the xml parser.
And btw xmllint has no problems with amp;
On Mon, 2003-08-18 at
6 matches
Mail list logo
