DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27807>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27807 SAXParser beheading some strings [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2004-03-19 22:53 ------- SAX parsers are free to split character data [1] into as any much chunks as they please and they can split the text at whatever boundaries they want. This is allowed for reasons having to do with parser efficiency and input buffering. In order to handle this properly, your handler needs to accumulate the text returned in each call until you recieve a callback that isn't characters. Xerces will split calls to characters at the end of an internal buffer, at a new line and also at a few other boundaries. You can never rely on contiguous text to be passed in a single characters callback. [1] http://www.saxproject.org/apidoc/org/xml/sax/ContentHandler.html#characters (char[],%20int,%20int) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
