Quark Forums

This is a user-to-user forum, where you meet experts; exchange ideas & discuss solutions with other users of QuarkXPress, App Studio etc. If you are looking for support, please go here: http://support.quark.com

Hi, I’ve been using Quark Xpress 2016 for some time now to automate with Applescript the production of PDFs with customized information. I recently upgraded to Quark Xpress 2017, and now some of my applescripts will no longer work. Specifically, when including the optional “page range” or “PDF output style” clauses. As an example; something like this used to work in Quark Xpress 2016:

I did try your script and entered the name of the output style by hand and it failed. I then duplicated a standard output style and copy & pasted the name into the script. This time the script worked. I then tried to remove the last part of the name (deleted " copy"). Now the script also works.

Thank you very much for taking the time to look at this. I tried replicating your process in my setup but the results were the same. I duplicated the output style and copied the name into the script, but the problem here seems to lie with the “PDF output style” clause not being recognized, because when I try to run it from the Script Editor, it fails with a Syntax Error stating that it “Expected end of line, etc. but found identifier.” While highlighting the “PDF” part of the “PDF output style” clause. It won’t even compile with the hammer tool. This is all a bit baffling to me, especially since these scripts used to run fine with QX2016. If I can’t get this to work as expected I’m thinking I could probably cobble something up by manipulating the UI with System Events to have the script choose a PDF style on the fly from the pop up menu, or maybe re-installing QX2016, which would pretty much defeat the purpose of purchasing the upgrade. Quick question though; Did you run your script on QX2017 with macOS High Sierra? Maybe my problem occurs only with this specific setup.

I did run the script with the same version of QuarkXpress 2017 as you, but on a different OS: El Capitan. Unfortunately I can't test on Sierra or High Sierra. So it's High Sierra specific. Maybe you could report this bug directly with Quark or otherwise in the Facebook group.

After editing my AppleScripts in order to work around the problems introduced by updating my software, I opened a support ticket (Ticket ID #79787), which was acknowledged on January 8.So far, the Product team has been unable to provide an answer as to why some of the functionality of AppleScript support appears to be broken under mac OS High Sierra.I've tried to test my AppleScripts under three additional configurations, installing Quark Xpress 2017 in a Mac Mini, a MacBook Pro and an iMac Pro, all of them running High Sierra. In every instance AppleScript commands that used to work flawlessly are now failing.I'd be very interested to know if full AppleScript support for High Sierra will be reinstated by upgrading to Quark Xpress 2018, or if the problems found in the current version are likely to remain.

After upgrading to High Sierra (now using 10.13.3), I'm having the same error when compiling my scripts written for QuarkXPress 2017 v13.2.1. It seems to be related to a command from the PDF Suite in the QXPScriptingAdditions.osax.--------------------------tell application "QuarkXPress 2017" export document 1 in WebPath as "PDF" PDF output style "Onofrio PDF MACH5 Output Style"end tell--------------------------"Syntax error: Expected end of line, etc. but found identifier."The text "PDF" in PDF output style is highlighted as the error.

This line used to work, and the scripts that were compiled before they were saved run just fine with the command, but I cannot edit and recompile the scripts without commenting out the "--PDF Output Style..." part of the line. It's still listed in the QuarkXPress 2017 dictionary:[PDF output style text] : Output style to be used: Default is Captured Settings

It acts like when you have two osaxen installed with conflicting syntax. I tried removing the other osaxen, with no effect to this problem. I also noticed that the QuarkXPress 2017 package in Applications folder contains a Library:ScriptingAdditions:QXPScriptingAdditions.osax. Is the one in Library:ScriptingAdditions no longer needed? I've compiling with and without, with no difference.