As I mentioned I am using XercesImpl from 31st July 2003. Both files have
0xFF 0xFE at the start of them.
I compared them at byte level, apart from crappy formating (LF before every
'>') the PDF file had an extra pair of nulls on the end. When I changed my
code to strip them it all worked. i.e. Adobe Acrobat is putting a pair of
nulls after the closing tag. Just a case of a $1.2Bn company proving they
should maybe stick to Graphic Designers as clients ;)
Thx.
David
-----Original Message-----
From: Michael Kay [mailto:mike(_at_)saxonica(_dot_)com]
Sent: 15 December 2004 17:45
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: RE: [xsl] Problem with encoding UTF-8
If so, you have a
UTF-8 BOM in your file. You have to get rid of it, or switch
to Saxon (or something else?)..
Whether or not Saxon accepts a BOM depends on the XML parser you are using.
Xerces accepts the BOM, Crimson does not.
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>
--~--
--~------------------------------------------------------------------
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>
--~--