unsubscribe me too...way too much traffic!

 

DO NOT REPLY [Bug 4472] New: - "01" shouldn't be a valid xs:Year

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

unsubscribe me

unsubscribe me email ==> [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 4456] - Not all correct encoding is supported

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

unsubscribe me please

unsubscribe me pleaseJ('R—è¬×­eêè>V­Š{¦N‡ZÈéåËßy¥êæ¢{a†Ûiÿù²ëszº'zßìþÈ žêk¦V­Š{¦­çÜtôý

Re: SAXParser question

Carl Christianson wrote: > Hi all, > this might be a dumb question but I'm wondering if something I'm seeing is > "normal". it is normal as specified in http://sax.sourceforge.net/apidoc/org/xml/sax/ContentHandler.html#characters(char[], int, int) i think that the reason for this behavior is t

Re: SAXParser question

Carl, It is frequently the case that XML processors read documents using buffered I/O. This leads to occasions where character data crosses buffer boundaries. To avoid costly data copying and memory allocation, SAX permits the parser to generate multiple character data "events". If you conside