EXPath File - whitespace in relative file paths
From Hans-Juergen Rennau:
extension functions file:xxx throw an error if a file name contains whitespace. The EXPath spec , however, lists examples with such file names  which supposedly should be processed without error, e.g.
my file.xml: A relative path, pointing to a file in the current working directory.
I know that the spec is still in progress, but I think it makes sense for the file module to be as robust as possible - the idea is to work with the file system as it is, and file names are not URIs - at least in my opinion..
Needs a little attention in
#3 Updated by John Lumley over 6 years ago
- Status changed from New to Resolved
Corrected to accomodate spaces and backslashes. Additional tests (@EXPath-file-exists-009->012@) added to EXPath Github test suite (https://github.com/expath/expath-cg/tree/master/tests/qt3/file). Tested on Windows machines, but will require others to test on Macs or Unixen.
Note - Hans-Jurgen raised an issue about;
file:exists('/projects/infospace/pcol/h.txt'), file:exists('file:/projects/infospace/pcol/h.txt') => false true
This has not been addressed, as I am somewhat unclear what on a Windows machine '/projects' means - on Unix derivatives it is an absolute path. Looking at http://en.wikipedia.org/wiki/Path_%28computing%29 shows that only
cmd.exe seems to support it. Enlightenment needed. Alternatively we could mandate that if you mean absolute use
file: and if relative don't start with '/'.
Please register to edit this issue