Hi Graeme,
Thanks for the help. I’m a little Unix-rusty lately. I had removed the slash
from the file name, but had left dashes in there. I thought dashes were
acceptable. My Unix has been “corrupted” by speaking Mac OS X too long.
Now I have to figure out why the icc profile i’m creating is not doing what i
want it to do, but that’s an entirely other issue. To paraphrase the Mad Hatter
when he realized his watch was wrong, “I can’t understand what’s the matter, I
used the best mayonnaise in it."
Rich
On Aug 17, 2017, at 6:36 PM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote:
Richard Rose (Redacted sender rsrosemdva for DMARC) wrote:
Hi,
It’s pretty unbelievable, but I had never run up against that problem with
Unix commands
before. I thought the $PATH pertained to any file, not just executables.
There's no such function built into the native file open API's, apart from
looking in the current directory.
I put a copy of it8.cht in the directory with the image file and the it8
text reference file.
Error - CGATS file 'Q60Q60E1-IT8.7/1-1998-02.txt' read error : Unable to
open file
'Q60Q60E1-IT8.7/1-1998-02.txt' for reading
Right - you have a forward slash in the name, indicating that the file
1-1998-02.txt is within the Q60Q60E1-IT8.7 directory below your current
directory.
Either quote the filename using double quotes, or rename it to something
more Unix friendly. Generally spaces, dashes or slashes of either sort
are not good choices for file or directory names.
Cheers,
Graeme Gill.
