\pdffilesize and spaces

Joseph Wright joseph.wright at morningstar2.co.uk
Sat Oct 19 08:44:40 CEST 2019

On 18/10/2019 22:45, Joseph Wright wrote:
> On 18/10/2019 22:26, Karl Berry wrote:
>> And the quotes are a whole problem in themselves, since now you can't
>> find filenames containing quotes. For example,
>> \pdffilesize{"file_1.tex"} should arguably fail unless the filename has
>> quotes. (I am not sure where the quotes are read in this case.)
> As a 'Windows person', quotes around file names are just 'part of 
> filenames' and are equivalent: "<filename>" = <filename>. It's 
> more-or-less impossible to create a file name containing double quote 
> mark (See 
> https://docs.microsoft.com/en-gb/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN 
> - there are quite a few reserved chars.)
> Joseph

David points out off-list that various Windows functions ignore trailing 
spaces in the extension of a file name: certainly this happens at the 
Command Prompt. Probably we are seeing that behaviour via API calls: 
probably best is for the macro layer to remove trailing spaces.


More information about the tex-live mailing list