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
Update: Quark tech support has reproduced this problem and acknowledged it as a defect in the software. Six weeks ago they promised a patch to fix it. But they have failed to respond to several requests for an approximate time frame. The recent February 2016 patch did not fix it.
I'm glad Quark has acknowledged the problem but disappointed they won't give users some guidance on how long we'll have to wait for a fix. I don't think Quark 2015 is usable for professional work until that fix arrives since, by Quark's own admission, it ruins a substantial percentage of placed PDF files upon output. Considering all this I feel I should warn the wider design and production community about this severe defect and about Quark's unwillingness, so far at least, to provide any kind of timeline for fixing it.
I'm the original poster. Unfortunately, it's not fixed.
It outputs OK when Quark 2015 is set to ignore or flatten transparency. But it outputs incorrectly when Quark is set to export transparency natively (the Quark default and necessary for many common workflows). This is exactly the earlier behavior.
Quark, what is the status of this? It's been a long time since you acknowledged this problem as a defect in the software.
Is it actually fixed in Quark 2016?
This is a really bad bug. A very large job of ours got ruined by it. With all respect, it needs to be fixed quickly.
To Quark: unfortunately this problem is not in fact fixed in Quark 2016. You can easily verify this for yourselves using my test files. Some of the pages now output correct, but others still output incorrectly when Quark is set to output transparency natively (the default).
This is disappointing. We have now purchased two Quark upgrades (2015 and 2016), and neither one is usable. Both corrupt output. We are still forced to continue using Quark 9 to get correct PDF output for our large publications.
Can Quark please prioritize a fix for this awful bug, which I first reported to you back on November 24, 2015?