DO NOT REPLY [Bug 27209] New: - Xerces 2.5.0 does not build with option -t IconvGNU because of syntax errors!

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27119] - Improper handling of elements in external entities

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 27196] New: - base class warning in SAXException.hpp copy constructor

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: splits in character data using SAX

You save all of the text in your own buffer, until you get an event that's not characters(). I've never used progressive parsing, and there's no real standard, so you'll have to experiment with it to see how it works. Dave

RE: splits in character data using SAX

A temp buffer for every characters call, push the terminating null and then cat to a longer lived buffer. The text is complete when you hit the endElement and you get it out of the longer lived buffer, which is then ready for the next characters field. ... at least that has worked for me, but I