Will try that. What worries me though is that the document used to work on
the same setup that I am using now. I added something and then it stopped
working... Is there any way to know exactly where the offending character is
Once upon a time, "Trevor Nash" was seen writting:
>> Suddenly I get the following error when trying to transform an XML document
>> Error on line -1 column 95144 of
>> Error reported by XML parser: bad continuation of multi-byte UTF-8 sequence
>> (character code: 0x20)
>> Transformation failed: run-time errors were reported
>> What is the problem? How can I correct it?
> The usual cause is that your input document is not really UTF-8.
> Usually this does not matter since the 'common' characters (i.e.
> ASCII) happen to have the same encoding. Things go wrong when you
> have accented characters or special symbols like 'copyright'. Try
> <?xml version="1.0" encoding="iso-8859-1"?>
> at the start of your input document. I am guessing of course (this is
> the normal encoding for Windows platforms) you should really find out
> what the encoding really is.
> If you are convinced the input document should be in UTF-8, you will
> find the offending character at offset 95144 of the input file. The
> error message isn't in terms of line and column because the parser is
> unsure what the encoding is, and therefore doesn't know what a line
> ending looks like.
> Trevor Nash
> Melvaig Software Engineering Limited
> voice: +44 (0) 1445 771 271
> email: tcn@... web: http://www.melvaig.co.uk
> saxon-help mailing list
P |Carlos Araya
_ |WebCT Administrator/Trainer
G |California Virtual Campus, Region 1
---- C/O De Anza College
10650 Bubb Road
Cupertino, CA 95014
web: http://www.cvc1.org (work)
PGP Fingerprint: E629 5DFD 7EAE 4995 E9D7 3D2F 5A9F 0CE7 DFE7 1756
A man said to the universe: "Sir, I exist." "However," replied the
universe, "that fact has not created in me
a sense of obligation."
-- Stephen Crane