User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101
            Thunderbird/24.5.0
MIME-Version: 1.0
References: <537E212E.2030607@morningstar2.co.uk> <537E5311.3020302@nag.co.uk> 
            <537E60D1.7010708@morningstar2.co.uk>           
            <C10CA70E-E313-4833-9574-4D5EAF76BC39@gmail.com>
            <srxei41dhyjy$.dlg@nililand.de>
Content-Type: text/plain; charset=Big5
Content-Transfer-Encoding: 7bit
Message-ID:  <537F5F74.9070008@morningstar2.co.uk>
Date:         Fri, 23 May 2014 15:47:16 +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: Reading from the system (pipe input)
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
In-Reply-To:  <srxei41dhyjy$.dlg@nililand.de>
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

On 23/05/2014 14:43, Ulrike Fischer wrote:
> (But I wouldn't like to bother Christian for something that it is
> only needed to handle file names with spaces. Imho when you start to
> quote file names there is soon either one quoting level too much or
> too few when people start to pass the file names around. There are
> better ways to spent ones time ;-)). 

Note that the space business here is a macro level thing. Currently
expl3 explicitly forbids any spaces in names, i.e. it's more restrictive
than the engines are. Piped input is not really linked to that except as
the pipe is a 'file name' of sorts, forbidding spaces leads to an
unexpected error with expl3. Nothing in that sense to worrk Christian about.
-- 
Joseph Wright