|The stupid question is the question not asked|
Re^2: Mac Space in Pathby bettis (Initiate)
|on May 23, 2013 at 03:27 UTC||Need Help??|
Thank you so much for your responses. I implemented and tested different permutations of the suggestions listed here. I also added a line to print the path $metadata_file, so I could keep track of what the script was opening if it was able to open the file and not die:
First, I commented out the line that deletes the trailing space from the user input. I noticed that the chomp() was not working the same after OSX 10.4, so I had to implement the line (We're a small Mac typehouse and all of our machines have slightly different implementations of perl. The trailing space works on some machines and not on others, but no trailing space works on all.):$metadata_file =~ s/\s$//;
When I comment it out, you'll see that the trailing space is still there and the space between "vendor" and "instructions" has been escaped:
The script opens the file and reads it in perfectly if I simply delete the space in the path:
I also tried not using quotes around $metadata_file in the open command and it successfully commented out the space:
To answer your question, fishmonger, the metadata_file is simply being inserted at the top of every document the script produces, so I open it, join it, format it and insert it when I need to in the script.
This particular piece of code is my test to get it to work, then I can rewrite the other parts of the script that read and write files with space bands. Previously, I simply admonished all our comps to not use space bands in their paths. Unfortunately, the client's CMS inserts space bands at every level, so I need to figure this out. It seems so simple, but it's not working.
Again, thank you for your help.