Re: Saxon and XT both exhibit unexpected document() be

> Thus, it is not related to the extent Java Runtime follows RFC 2396, but is caused
> by the way SAXON computes systemId of a file, namely, by forcing reslashing the path
> to the UNIX way, which leads to non-conformant behaviour.

This sounds like the right thing to do. By default saxon command line
arguments are specified as being file names rather than URIs (so should
use \ (although / also works, as is normally the case with command line
tools on windows) but then that file name must be converted to a uri
which means more or less changing \ to / and sticking file:// at the
front.

David


-- 
http://www.dcarlisle.demon.co.uk/matthew

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list