...we duplicate events here and the thereby modify the SAX stream. Should be no problem.... but who knows ;)
with the patch:
characters(36k) -> event string 32k event string 4k
I guess it would be better to have it like this:
characters(36k) -> event string 32k string 4k
So what goes in comes out the same way.
We could also increasing the max length of a stored character event in general. ...but that would waste 2 bytes per event. Hm...
What do you think?
This was what I meant when writing "If we split the text node here into littler parts, will they be re-read as *one* text node when reading the XMLByteStream?"
Where exactly is the XMLByteStream used? If it is possible to apply a transformation step afterwards I see possible unexpected behaviour:
<xsl:template match="text()"> <p><xsl:value-of select="."/></p> </xsl:template>
If we talk about the same problem I see, there will possibly be later more <p> than there should be. It should be fixed then.
Joerg
