References: <55C15708.1090708@clear.net.nz>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
            Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Message-ID:  <55C05505.3000906@morningstar2.co.uk>
Date:         Tue, 4 Aug 2015 07:00:37 +0100
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: Joseph Wright <joseph.wright@MORNINGSTAR2.CO.UK>
Subject: Re: Spaces in path names
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <55C15708.1090708@clear.net.nz>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 05/08/2015 01:21, aparsloe wrote:
> On reading interface3.pdf (July 15, 2015) I see that spaces are not
> allowed in paths for \file_path_include:n and \file_path_remove:n. To my
> (mild) surprise I found that \file_if_exist:nTF functioned happily with
> paths that included spaces, or at least if the current *.tex document
> was in a directory at the end of a path with spaces, \file_if_exist:nTF
> was perfectly capable of finding other files in the same directory. I
> don't doubt there are underlying reasons for the different behaviours,
> but to someone not steeped in TeX lore, this feels confusing. The
> \file_path_ functions should also be indifferent to spaces in paths.
> 
> Andrew Parsloe

We revised the behaviour in this area some time ago: spaces are now
allowed and there is some internal logic to quote names correctly. All
of the \file_... functions use the same internals, but this statement in
the docs was missed as part of the update. It will be corrected in the
next release.
--
Joseph Wright