« Oh for pete's sake | Main | Why I can't handle Wyland's artwork »

Here's the problem with the script.

In some cases, based on:

1. Acrobat Reader on your system


2. What is the default PDF application on your system

the script will attempt to open up Acrobat Reader instead of Acrobat Pro.

First, the scripts both most definitely state Acrobat Professional. I've triple-checked those. However, the problem is one of what happens the first time the script runs. Depending on how your OS is set up, I think that AppleScript is saying "Oh, use the default application that matches the File Type and Creator Code", which unfortunately, can mean Acrobat Reader.

The problem seems to be that both Acrobat Reader and Acrobat Professional look almost the same to the OS. Let me illustrate:

These are the pertinent results for AppleScript's "Info For" on Acrobat Professional version 8:

• file creator: CARO


• file type: APPL


• bundle identifier: com.adobe.Acrobat.Pro


• kind: Application


• name extension: app


• short name: Acrobat


• displayed name: Adobe Acrobat Professional


• type identifier: com.apple.application-bundle

Now, for Acrobat Pro version 7:

• file creator: CARO


• file type: APPL


• bundle identifier: com.adobe.Acrobat.Pro


• kind: Application


• name extension: app


• short name: Acrobat


• displayed name: Adobe Acrobat 7.0 Professional


• type identifier: com.apple.application-bundle

Now for Acrobat Reader 8:

• file creator: CARO


• file type: APPL


• bundle identifier: com.adobe.Reader


• kind: Application


• name extension: app


• short name: Adobe Reader


• displayed name: Adobe Reader


• type identifier: com.apple.application-bundle

The problem is, the only difference other than the name is the bundle identifier. Since the script is getting its tell target changed, I'm thinking that the bundle identifier isn't being used.

So now what to do? Well, I've filed a bug report with Apple and until I'm absolutely sure of what exactly is going on, I'm not going to change the code. For one, I'm not sure that there's much I can do to fix this. What I am not going to do though is rig up some fragile patch that may cause more problems than it solves.

There is however, a workaround that is reliable, and relatively easy. The line with the tell block that is getting repurposed is at line 233, and should read:

tell application "Adobe Acrobat Professional" for Acrobat 8 Professional or

tell application "Adobe Acrobat 7.0 Professional" for Acrobat 7 Professional.

IF you are getting this script trying to use Reader, open it up in Script Editor and look for that line. When you find it, change it so it lists the correct name for your version of Acrobat Pro. Save the script and quit Script Editor. As long as you have Acrobat Pro on your Mac, that will fix the script to only use the correct version of Acrobat Pro.

Once I come up with a proper fix, I'll post another article here letting you know.

Thanks for your patience, and I'm really sorry about this, especially because I'm not sure there's an easy fix.

Technorati Tags: Acrobat, Adobe, AppleScript, puppy

Comments

Post a comment

Thanks for signing in, . Now you can comment. (sign out)

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

URL:
Remember me? YesNo

Comments: