|
Wouldn't you know it: I restarted the computer and updated Acrobat to 8.1.1 and the problem is gone. Good thing, since I couldn't figure out how to identify the raw code. Smile's "Property & class to raw code" command doesn't seem to do anything.
Now if I could only figure out how to get Acrobat to enter comma-separated keyword lists into the Properties field via AppleScript, without the string-enclosing quote marks that defeat its whole keyword parsing routine. The idea is this:
tell app "Adobe Acrobat Professional" set info of active doc key "Keywords" value "some, string with, commas between, keywords" end tell
This leaves the document's Keywords property set to "some, string with, commas between, keywords", including the quote marks.
If, OTOH, you manually type the keywords in (with commas), they are nicely parsed and entered into the document's XML properties as separate keywords.
Script Debugger does. It's called "Manifest". In the File menu. But it needs the actual command, not just a property. If I type 'input volume' into a script in SD with no tell block, it does compile. 'input volume' is a property of 'volume settings' in Standard Additions, built into every Mac. When I check for its raw code, it shows «property invl».
I don't have Acrobat Pro. Can you check in Script Debugger or Smile (free) if it uses that same raw code «property invl» for 'value'?
|