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=24278>. 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=24278 Incorrect SAXException about bad integral value of a character to be written out. ------- Additional Comments From [EMAIL PROTECTED] 2004-06-08 15:23 ------- Anders, I haven't looked carefully at your patch, but bug 29234 mentions the specific problem that you do, about m_maxCharacter not being set on the serializer when created from XSLTC (thanks for your careful analysis). That fix is already in CVS, and is smaller (safer?) than your fix. Please see if it works for you and let us know in this bug report. You suggestion of one way of creating a serializer, rather than more ways with duplicate code is right. Initially XSLTC and Xalan-J interpretive each had their own serialiation mechanism. I merged the two a while ago but there are a number of internal methods on the serializer that are called either from XSLTC or from Xalan-J interpretive, but not both. ... Yes, some duplication. Regards, Brian Minchau --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
