PakPlace

I was asked this question, and unfortunately I cannot find it in the iListen user manual (1.6 or the addendum) or on the web site knowledgebase. So, I will illustrate it here - fortunately it is not that difficult.

You must have iListen running. Switch to it - the running iListen application.

Under the File menu, select the first item "Commands..." (as of 1.6.8 there is a voice commands for this: Show Commands Window)

The commands window should appear:

Now, are you going to be importing a script for a particular application, or for global/everywhere use? If it is for global use then you are in the right place (see the drop down menu above that says "Type: Global".) If you are going to be importing a script for a particular application, you need to click on the drop down menu above "Type:" and select the only other entry, "Application Specific."

Click the "Import..." button at the bottom and select the text file with the script in it. If this is a global script, iListen will then import the scripts into a new pack with a new name, otherwise it will create a script pack with the same name as the application.

Hopefully it will import them with out any problems. Importing and exporting can be a little touchy. If iListen has problems importing the Applescript for particular commands, it will give you a cryptic (unless you understand Applescript and iListen scripting) error message and you must hit the okay button to continue importing. For each particular command that it had problems with, the type column will show "Applescript (uncompiled)". This means that iListen could not compile, or translate the Applescript text into working code. If you open that particular command (double click on it or press the "Edit..." button) sometimes you might see a missed return or a whole bunch of garbled characters. Fix it if you can, otherwise, you can always disable the command using the check box next to the name in the command listing window or in the command editing window itself.