You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-users@xalan.apache.org by Brian Minchau <mi...@ca.ibm.com> on 2005/08/04 21:44:24 UTC
Re: SAXException: Attempt to output character of integral value 231 that is
not represented in specified output encoding of cp860
Pedro,
Issue 1799 is a different problem, its error message is this:
>> Attempt to output character of integral value 235 that is not
represented in specified output encoding of .
If you look carefully you will see that the message does not specify which
encoding. I think that 1799 was an internal error to do with temporary
output trees which have no associated encoding.
I think your problem is already reported in issue 2084
in http://issues.apache.org/jira/browse/XALANJ-2084
you can see that the error message similar to the problem you see, with the
name of the encoding.
Issue 2084 points to 2087 as having the fix. That fix was applied to the
codebase yesterday by myself. It was a last minute patch going into the 2.7
release, which is expected to be released very soon (any day now). So you
can watch this mailing list for the announcement.
The fix in 2087 is about a bug in the code that figures out if a given
character is in the encoding or not. Of course if unicode code point 231 is
not in cp860 this problem won't go away.
- Brian
- - - - - - - - - - - - - - - - - - - -
Brian Minchau
XSLT Development, IBM Toronto
Pedro Alves
<pedro@neraka.no-
ip.org> To
xalan-dev@xml.apache.org
08/04/2005 11:51 cc
AM
Subject
Re: SAXException: Attempt to output
Please respond to character of integral value 231
xalan-dev that is not represented in
specified output encoding of cp860
On Thu, Aug 04, 2005 at 08:12:05AM -0700, david_n_bertoni@us.ibm.com wrote:
> > I got no answers at all. Should I fill this as a bug?
> >
> >
> > Thanks
>
> Since the bug is not fixed until Xalan-J 2.7, and you're using 2.6, why
> would you expect to have the fix?
>
> Dave
The first link you gave me was
http://issues.apache.org/jira/browse/XALANJ-1799
which is marked as closed and fixed. The last comment says:
Comment by Oleg Lyebyedyev [04/Mar/04 09:53 AM]
Update to 2.6.0 fixes this bug. Thank you.
So I thought it was the solution to my problem. I just followed the
duplicate references and got to 1710 (you already replied this to me but I
was not familiar with jira and didn't fully understand it).
Thanks for your time
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xalan-dev-help@xml.apache.org
--
Pedro Alves
pedro.alves@zmail.pt
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
Re: SAXException: Attempt to output character of integral value 231 that is not represented in specified output encoding of cp860
Posted by Pedro Alves <pe...@neraka.no-ip.org>.
On Thu, Aug 04, 2005 at 03:44:24PM -0400, Brian Minchau wrote:
> Pedro,
>
> Issue 1799 is a different problem, its error message is this:
> >> Attempt to output character of integral value 235 that is not
> represented in specified output encoding of .
>
> If you look carefully you will see that the message does not specify which
> encoding. I think that 1799 was an internal error to do with temporary
> output trees which have no associated encoding.
>
> I think your problem is already reported in issue 2084
> in http://issues.apache.org/jira/browse/XALANJ-2084
> you can see that the error message similar to the problem you see, with the
> name of the encoding.
>
> Issue 2084 points to 2087 as having the fix. That fix was applied to the
> codebase yesterday by myself. It was a last minute patch going into the 2.7
> release, which is expected to be released very soon (any day now). So you
> can watch this mailing list for the announcement.
>
> The fix in 2087 is about a bug in the code that figures out if a given
> character is in the encoding or not. Of course if unicode code point 231 is
> not in cp860 this problem won't go away.
>
Sorry, mate, I didn't understand one thing. 2084 points to 2087, and you
say its fixed.
I downloaded the cvs version this afternoon and tried it, and still have
problems (in fact, more problems than before). I attacted a test case and
a comment for 2087.
Sorry if I misunderstood you in some way
best regards
--
Pedro Alves
pedro.alves@zmail.pt
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org