I get the same result. It appears that the Crimson parser doesn't support byte order marks in UTF-8 files.
Michael Kay
-----Original Message-----
From: Bill Keese [mailto:billk@tech.beacon-it.co.jp]
Sent: 05 November 2002 01:28
To: michael.h.kay@ntlworld.com; saxon-help@lists.sourceforge.net
Subject: Re: [saxon] BOM for UTF-8 broken in v7

Yes, it makes that that's an issue with the XML parser.
But I'm using the default parser for the command line Transform class (on the command line I just call "java  net.sf.saxon.Transform input.xml style.xsl").  Thus, I must be using the Crimson parser included in JDK 1.4.
----- Original Message -----
From: Michael Kay
To: 'Bill Keese' ; saxon-help@lists.sourceforge.net
Sent: Saturday, November 02, 2002 2:55 AM
Subject: RE: [saxon] BOM for UTF-8 broken in v7

This was a bug in AElfred (well, not a bug actually, a change in the spec that happened after the code was written). It's a problem in the XML parser, not the XSLT processor.
Saxon 7.2 no longer uses AElfred. Which XML parser are you using? Because the spec has changed, it may well be a problem that affects other parsers too.
Michael Kay
-----Original Message-----
From: saxon-help-admin@lists.sourceforge.net [mailto:saxon-help-admin@lists.sourceforge.net] On Behalf Of Bill Keese
Sent: 01 November 2002 08:52
To: saxon-help@lists.sourceforge.net
Subject: [saxon] BOM for UTF-8 broken in v7

Looks like bug 472844 (Byte order mark from UTF-8 files not handled) has resurfaced in the new (experimental) Saxon V7.  The error message is something to the effect that the root node is undefined