Note that mapping a Windows path to a 'file' URI is a matter of guesswork, the
succesful result of which is determined by the resolvers on the platform as
much as in the XSLT software itself (which is often just a shallow wrapper for
the platform's resolver or an XML parser's resolver).

In 4Suite for example you see a lot of 'failed' entries in David's chart
because we defer to the python language's core libraries' preference: the
arguably just-as-ubiquitous format where the ":" in the drivespec is replaced
with "|". A URI like file:///C|/foo will work nicely. We also supply functions
for generating an ideal (for python) 'file' URI from an OS-specific path and
vice-versa.


David.Pawson@xxxxxxxxxxx wrote:
> http://www.dpawson.co.uk/xsl/rfc2396/
> 
> Shows 4 processors and their reaction
> to various combinations.
> 
> HTH DaveP
> 
> 
> > > However, if I try to send a full path so I can incorporate a 
> > > file that is
> > > somewhere other than the same directory, it doesn't work.  
> > > I've tried to
> > > send the parameter as c:\foo and as file:\\\c:\foo and 
> > > nothing seems to
> > > work.  
> > > 
> >  I do not know about xsltproc, but neither of your examples 
> > are correct
> > syntax.  Try each of these -
> > 
> > file:///c:\foo
> > file:c:\foo
> > file:///c:/foo
> > 
> > One of these should work (file: URLs are notoriously hard to 
> > be sure of
> > the right syntax for, but the slashes right after the scheme must be
> > forward ones, not reverse)
> > 
> > I am assuming that you are on Windows because of the backslashes.  If
> > you are on *nix, use only forward slashes.
> > 
> > Cheers,
> > 
> > Tom P
> > 
> >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> > 
> 
> - 
> 
> NOTICE: The information contained in this email and any attachments is 
> confidential and may be legally privileged. If you are not the 
> intended recipient you are hereby notified that you must not use, 
> disclose, distribute, copy, print or rely on this email's content. If 
> you are not the intended recipient, please notify the sender 
> immediately and then delete the email and any attachments from your 
> system.
> 
> RNIB has made strenuous efforts to ensure that emails and any 
> attachments generated by its staff are free from viruses. However, it 
> cannot accept any responsibility for any viruses 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 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 

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