The CDataSection of batik SVGDOM is splitted into multiple CDataSection on each new line? is it a bug?
I guess you could argue this either way we create a CDATA node every time the SAX parser calls us with a chunk of characters (see batik.dom.util.SAXDocumentFactory.characters). It would be possible to store these in a StringBuffer and only create the CDATA/TextNode when something other than a character is parsed. This is tricky as there are lots of things that might end it (this is especially problematic for text not such much CDATA which is explicitly delimited).
The problem occur when the SVGDom generated by batik is to be serialized/writing back to text file. Because the result of serialized is not the same with the loaded one due to different in CDataSection. Batik itself also unable to open/load the result of serialization.
This is (IMHO) a much bigger deal I'll look into it (could you file this in Bugzilla).
I attached the file to reproduce the problem.
Thanks!
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
