Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 41266 invoked from network); 7 Nov 2003 23:49:39 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Nov 2003 23:49:39 -0000 Received: (qmail 57981 invoked by uid 500); 7 Nov 2003 23:49:21 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 57842 invoked by uid 500); 7 Nov 2003 23:49:21 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 57829 invoked from network); 7 Nov 2003 23:49:21 -0000 Received: from unknown (HELO exchange.sun.com) (192.18.33.10) by daedalus.apache.org with SMTP; 7 Nov 2003 23:49:21 -0000 Received: (qmail 26852 invoked by uid 50); 7 Nov 2003 23:49:28 -0000 Date: 7 Nov 2003 23:49:28 -0000 Message-ID: <20031107234928.26851.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: dev@cocoon.apache.org Cc: Subject: DO NOT REPLY [Bug 24457] - Xalan/XSLT using UTF-8: Incorrect SAXException: Attempt to output character of integral value... X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N 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_bug.cgi?id=24457 Xalan/XSLT using UTF-8: Incorrect SAXException: Attempt to output character of integral value... agallardo@agsoftware.dnsalias.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER | ------- Additional Comments From agallardo@agsoftware.dnsalias.com 2003-11-07 23:49 ------- This is not a good example for "resolved later". This bugs cleary depends on a Xalan bug that is in discussion right now. For me this bug is open. If we leave this bug as "resolved later", then when you see the bug on Xalan Bug 24278 it looks like our bug was solved. This is not a good idea since this status would suggest Xalan people, that the bug is not a internal Xalan issue.