4:23 p.m.
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
6:56 p.m.
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
6:56 p.m.
Hi,
some explanation about the background first: pdfColorConvert used
OutputIntents instead of ICC profiles. An OutputIntent is pretty much
the same as an ICC profile, however it has some more information.
Advantage of an OutputIntent is, that if it is being used Acrobat
takes it into account when the PDF is being displayed.
The OutputIntentSourceSelector parameter of the Destination allows to
use the OutputIntent which is embedded in the settings file, from an
external file or to use an OutputIntent embedded in the PDF to be
processed.
If the OutputIntent is being taken from the settings file you may
either embedd the OutputIntent into the settings file or you embedd
the ICC profile into the settings file and add the additional
information by using the parameters starting with OI_ - e.g.
OI_OutputCondition. You may leave these parameters empty as they only
have to be present in order to mak an OutputIntent from an ICC profile.
So far for the background. Now to answer your questions:
All three ways are supported on a Mac too.
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.
There is a command line switch for doing this:
pdfColorConvert --makeprofiledata <iccfile> <configfile>
So you would need to type pdfColorConvert followed by the switch --
makeprofiledata followed by the ICC profile to embedd followed by the
settings file into which you would like to embedd the ICC profile.
Please note that it is usefull to open the settings file in any text
editor befor or after in order to remove all ICC profiles not being
required for the conversion. This makes the file smaller and makes
pdfColorConvert (even) faster when processing your files.
2) ICC profile saved next to the pdfColorConvert
executable. I
can't seem to get this to work either.
This would only work if pdfColorConvert is being invoked from the
program folder. The path to the ICC profile has to be defined either
relative to where pdfColorConvert is being invoked from or absolute.
3) ICC profile saved under C:\ . This works great,
but of course
only in Windows.
OK, indeed difficult to achieve this on a Mac. Same applies here as
for 2). This is an absoulte path which would work on a Mac too.
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.
Hope this helps,
Dietrich
--
Dietrich von Seggern | Director Product Management
callas software GmbH | Schoenhauser Allee 6/7 | 10119 Berlin | Germany
Tel +49.30.4439031-0 | Fax +49.30.4416402
Amtsgericht Charlottenburg, HRB 59615 | Geschaeftsfuehrung: Olaf
Druemmer, Ulrich Frotscher
6233
days inactive
6233
days old
callas_user_forum@lists.callassoftware.com
2 comments
3 participants
participants (3)
-
Dietrich von Seggern -
maillist_pk＠mac.com -
Nicholas