Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting actual path to file from pxf:info on case-insensitive filesystems #292

Open
dwcramer opened this issue Jun 16, 2019 · 0 comments
Open

Comments

@dwcramer
Copy link

I'm using pxf:info to see if images that a document refers to are available. Local builds happen on MacOS, which is typically case insensitive, but remote builds happen on a case-sensitive filesystem.

If I refer to an image file, Alice.jpg, three times, as alice.jpg, Alice.jpg, and aLice.jpg, in the case-insensitive environment pxf:info tells me each time that the file is there, but doesn't tell me what the case of the file on the filesystem actually is:

<?xml version="1.0" encoding="UTF-8"?>
<results xmlns="http://www.w3.org/ns/xproc-step">
   <c:file xmlns:c="http://www.w3.org/ns/xproc-step"
           href="file:/Users/dcramer/diff-test/diff-test1/images/alice.jpg"
           readable="true"
           size="117494"
           last-modified="2018-03-28T14:58:13Z"/>
   <c:file xmlns:c="http://www.w3.org/ns/xproc-step"
           href="file:/Users/dcramer/diff-test1/images/Alice.jpg"
           readable="true"
           size="117494"
           last-modified="2018-03-28T14:58:13Z"/>
   <c:file xmlns:c="http://www.w3.org/ns/xproc-step"
           href="file:/Users/dcramer/diff-test1/images/aLice.jpg"
           readable="true"
           size="117494"
           last-modified="2018-03-28T14:58:13Z"/>
</results>

It would be great if there were a way to get the actual spelling of the path to the file, even in a case-insensitive environment so I could compare that with the path to the file in the document and warn the user that this doc will not build on the build machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant