If you use a hex editor at every stage of the process to find
out when the bytes for the character ? are x3F (meaning the ?
really is a ? and its not just your viewer) then you'll know
that the last stage was the culprit.
Actually, I no longer trust a hex editor. UltraEdit in hex mode doesn't
display the bytes that it found on the disk, it displays the result of
decoding those bytes and translating into UTF-16. So I'm now using my own
Java program that displays what a Java FileInputStream gives me, which I
think is reasonably close to what's actually there on the disk. It's as
close as I can get, anyway.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--