Hello Nicholas
I recommend embedding the ICC profile into the cfg file
For this you have to use the "Terminal" and the following command:
/Applications/pdfColorConvert_CLI/pdfColorConvert --makeprofiledata
<iccfile> <configfile>
The easiest way to enter the long path the the icc file and the
config file is to enter the line:
/Applications/pdfColorConvert_CLI/pdfColorConvert --makeprofiledata
in the terminal.
Then drag and drop first the icc profile and then the cfg file onto
the terminal and launch the command.
This will embed the ICC profile in your cfg. In the cfg you just need
to specify the name of the ICC profile as it can be found at the
beginning of the last line in the newly created cfg file.
best regards
Peter Kleinheider
Am 05.04.2007 um 16:23 schrieb Nicholas:
Hello everyone,
I've been using the Windows Demo of pdfColorConvert CLI for about
two weeks. I'm very impressed with it. However, I can't seem to
make the Mac Demo function correctly (I'm using 10.4.9). I can get
it to run with the default, demo destination profile. But, I'm
unable to get it to recognize our own destination profile.
The manual describes three way of adding a destination profile:
1) Embed the destination profile in the config file. I don't know
how to do this on either platform. If someone could explain this
process I'd be grateful.
2) ICC profile saved next to the pdfColorConvert executable. I
can't seem to get this to work either.
3) ICC profile saved under C:\ . This works great, but of course
only in Windows.
I'm open to any method that allows me to specify our own
destination profile while using OS X. Thanks for any and all help.
Kind regards,
Nicholas
_______________________________________________
callas_user_forum mailing list
callas_user_forum(a)lists.callassoftware.com
http://lists.callassoftware.com/mailman/listinfo/callas_user_forum