The FDK has not been tested at Adobe under Mac OSX 10.3, but undoubtedly can be made to work. The next release that will be tested and configured for Mac OSX 10.3 will be out in late summer, early fall.<br /><br />In your e-mails, I have seen three problems.<br /><br />1) tk/Tkinter not installed.<br /><br />The built-in Python does not come with the tk/tKinter graphical user interface modules. Without these, the FDK tools can only be run in command-line mode. This means opening the Terminal windows, and typing commands in the Terminal window. It will work in this mode.<br /><br />You can get the GUI version working, but you'll be on your own for this, for the next few months. I'm pretty sure that all you need to do is to go the Python web site, and get the Acqua Tk download.<br /><br />2) FDK modules not found.<br /><br />The Python interpreter has a couple standard paths where it looks for modules. You can see these by starting it up by itself, and typing:<br />import sys<br />print sys.path<br /><br />sys.path is a list of file paths where Python looks to find modules. The location of all the FDK modules needs to be on this list.<br /><br />There are a couple ways to add to this list. The FDK uses the mechanism whereby you put the each additional file path in a simple text file, and put that fie in Python 'site-packages' directory. On my system, this is in:<br />/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages<br /><br />You can also look in the sys.path list to find where it is. <br /><br />Making these files is the one critical function of the FinishInstall.py script. You can also make them by hand. The list of needed extra file paths is:<br />/adobe/FDK/Tools/SharedData<br />/adobe/FDK/Tools/Programs/OTFProof/exe/osx<br />/adobe/FDK/Tools/Programs/tx/exe<br />/adobe/FDK/Tools/Programs/tx/exe/osx<br /><br />However, it is alot easier to run FinishInstall.py. I suggest that you simply run it using the 'tcsh', from your home directory<br />1) open a new "Terminal" window<br />2) say "tcsh". This switches you to using the 'tcsh' command shell.<br />3) Say " python <path to FDK>/FinishInstall.py"<br />4) say 'exit' when done, to return to the regular bash shell.<br /><br />Note that we do currently have a bug in that the '<path to FDK>' cannot contain spaces. <br /><br />This will accomplish the critical function of the FinishInstall.py script: the command lines for teh FDK will then work. However, it will not help you avoid typing by putting 'alias' commands in your home directory login file. The 'alias' command allows you to specify that a long command string should be substituted whenever you type a word at the beginning of a command line. For example. if you say:<br />alias makeotf="python /Users/will/Typesetting/Font/AdobeFDK/FDK1.6-OSX/Tools/Programs/makeotf/exe/MakeOTF.py "<br /><br />then thereafter you will need to type only 'makeotf', and the command interpreter will think you typed the whole thing.<br /><br />However, an alias lasts only until you close the Terminal window. To always have an 'alias' definition, available, you need to put it in your login file. For bash, this file is '.bash_login', in yoru home directory. (Note that the file name starts with a period, so it will be invisible in the Finder, and the Terminal command '"ls" will show it only if you specify the path). An easy way to get your alias commands into your bash login file is to copy the alias commands from the file made by FinishInit.py. This file is called 'FDK.init'. You will need to edit these commands, as the 'bash' syntax differs from the 'tcsh' syntax. <br />Changes:<br />Instead of saying:<br />setenv FDK_PROGRAM_ROOT '"<path to top level FDK directory>"'<br />you must say:<br />FDK_PROGRAM_ROOT='"<path to top level FDK directory>"'<br />with no spaces on either side of the equals sign.<br /><br />You must edit all the alias commands to change from:<br />alias makeotf python $FDK_PROGRAM_ROOT/makeotf/exe/MakeOTF.py<br />to<br />alias makeotf="python $FDK_PROGRAM_ROOT/makeotf/exe/MakeOTF.py"<br />with no spaces on either side of the equals sign.<br /><br />Hope this helps!
8
Replies
AdChoices