Either a bug in Xerces or the underlying transcoder, whatever that is... while it would be best to fix Xerces, assuming that is the problem, there may also be a workaround.
-----Original Message----- From: Giulio Troccoli [mailto:[email protected]] Sent: Friday, August 14, 2009 5:47 AM To: [email protected] Subject: RE: Invalid byte 1 (£) of a 1-byte sequence It won't be easy but I'll give it a go and report back. In any case, that would be a bug in Xerces, wouldn't it? So the "approrpiate corrective action" would be to change my application to work around this bug, wouldn't it? Giulio
