[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: [xsl] Problem with encoding UTF-8

---

---

which version of Acrobat?
I'm assuming Professional is that right?

regards DaveP 

    -----Original Message-----
    From: David at roamware [mailto:david@xxxxxxxxxxxxxx] 
    Sent: 15 December 2004 18:46
    To: Xsl-List
    Subject: Re: [xsl] Problem with encoding UTF-8
    
    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@xxxxxxxxxxxx]
    Sent: 15 December 2004 17:45
    To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
    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/
    
    

-- 
DISCLAIMER:

NOTICE: The information contained in this email and any attachments is 
confidential and may be privileged.  If you are not the intended 
recipient you should not use, disclose, distribute or copy any of the 
content of it or of any attachment; you are requested to notify the 
sender immediately of your receipt of the email and then to delete it 
and any attachments from your system.

RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants.  However, it 
cannot accept any responsibility for any  such which are transmitted.
We therefore recommend you scan all attachments.

Please note that the statements and views expressed in this email and 
any attachments are those of the author and do not necessarily represent
those of RNIB.

RNIB Registered Charity Number: 226227

Website: http://www.rnib.org.uk

---