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 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
