[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] UnknownHostException
Subject: Re: [xsl] UnknownHostException From: "Thomas B. Passin" <tpassin@xxxxxxxxxxxx> Date: Tue, 30 Oct 2001 10:41:49 -0500 |
[<bernwardhanssen@xxxxxx>] > > > file:///usr/docs/x.xml > > David > > That works for UNIX. > But file://D:\test.xml do not work for windows. > There works > file:///D:\test.xml and file:/D:\test.xsm > It depends on the processor (and sometimes on how it is invoked). Theoretically there are supposed to be three slashes for a file on the local machine, or "file://localhost/" - they are equivalent according to the RFC. A single slash is not legal but many processors allow it because it is a common error. Whether the path separators should be changed from backslaches to forward slashes is not made clear in the RFC. If the path part of the URL is considered to be "opaque", then they should remain backslashes. If the path is considered to be parsable, they should be changed. How does your processor consider them? You have to try and see. Furthermore, some processors erroneously insist on just a single slash after the "file:". Some act differently depending on whether you are invoking a file on the command line or from within a stylesheet. Cheers, Tom P XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] UnknownHostException, David Carlisle | Thread | RE: [xsl] UnknownHostException, DPawson |
Re: [xsl] Xalan Encoding Problems, Raul Rodriguez | Date | Re: [xsl] Xalan Encoding Problems, David_N_Bertoni |
Month |