Bug #2269: EXPath File - whitespace in relative file paths - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #2269

closed

EXPath File - whitespace in relative file paths

Added by John Lumley over 9 years ago. Updated over 8 years ago.

Status:

Closed

Priority:

Low

Assignee:

John Lumley

Category:

EXSLT extensions

Sprint/Milestone:

9.6.0.4

Start date:

2014-12-18

Due date:

% Done:

100%

Estimated time:

Legacy ID:

Applies to branch:

9.6

Fix Committed on Branch:

9.6

Fixed in Maintenance Release:

9.6.0.4

Platforms:

Description

From Hans-Juergen Rennau:

extension functions file:xxx throw an error if a file name contains whitespace. The EXPath spec [1], however, lists examples with such file names [2] 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 EXPathFile.toString()

Actions

Copy link

Updated by John Lumley over 9 years ago

This 'bug' is a consequence of the fix for https://saxonica.plan.io/issues/2037 which corrected problems on Macs and Unixen, but introduced 'no spaces' errors for relative file path names.

Actions

Copy link

Updated by O'Neil Delpratt over 9 years ago

Found in version changed from 9.6.0.1 to 9.6

Actions

Copy link

Updated by John Lumley over 9 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 '/'.

Actions

Copy link