I can only make guesses as to why this might happen. My first guess
would be that the serialization was not actually done by Saxon.
Alternatively, you might have used Saxon to serialize to a character
stream, and then have used some other software to convert the characters
to bytes.
You're completely correct. It was the serialization of the document that
produced the error. It's fixed now.
Thanx for telling me where to look (and sorry to all since it wasn't
really XSLT related...)
/Marcus
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list