from my investigations over the weekend, the only time i could see that you
were likely to get a UTF-8 BOM is if you are transcoding to UTF-8 from
UTF-16.

After I fixed my encoding problems, both expat and xerces-c handled it fine.
(both UTF-8 & UTF-16 BOM's)

Cheers
Simon

-----Original Message-----
From: Eric Kidd [mailto:eric.kidd@[...]..]
Sent: Monday, April 02, 2001 6:03 PM
To: soapbuilders@[...].com
Subject: Re: UTF-8 BOM (was RE: [soapbuilders] Follow-up UTF-8 test)


On Mon, Apr 02, 2001 at 03:06:35PM -0700, Michael Brennan wrote:
>  Thanks for the reference. I've overlooked that (and thought that UTF-8
>  never includes a BOM).

UTF-8 generally shouldn't include a BOM, IIRC.  But if you see one, you
should recognize it.  UTF-16, according to the XML standard, must include a
BOM.

>  I wonder how many other XML parsers have problems with this.

This is probably a good reason not to send a UTF-8 BOM if you can avoid
doing so. :-)

Cheers,
Eric

--
XML-RPC HOWTO:
http://www.linuxdoc.org/HOWTO/XML-RPC-HOWTO/index.html
XML-RPC for C and C++:  http://xmlrpc-c.sourceforge.net/


To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@[...].com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/