On Lion the change is triggered by saving the file under a new name ( Duplicate => Save.).

But I'm on Mac OS X Lion 10.7.4, with Preview.app Version 552 (719.23). but you never know until you take a really really close look at the PDFs in question.īTW, for me the simple hit on + does not yet change the PDF. When saving a PDF the second time, chances are, that only the /ModDate metadata key is s updated (unless you're using a new version of Quartz on your Mac).

I've mis-spend quite some man days of work on 'analyzing' the wrong files before I discovered the problem about a year ago.Ī lot of True Believers of the Apple Cult are not aware of this behavior, and a lot of prepress Pros are also completely clueless about it. Therefor I always need to first establish a procedure with Apple customers which guarantees I get to analyze the original PDF files exhibiting a particular bug or problem, not the ones which where spoiled by Quartz/Preview. I earn (part of) my living with debugging PDFs.Īnd I made it a habit now to never-ever respond to a customer with suggestions how to fix any (even the most simple) reported problem as soon as I discover the provided sample PDF has been touched by Quartz (fortunately, Apple admits its involvement by updating the /Producer metadata key with Mac OS X 10.7.4 Quartz PDFContext or similar):īecause I never know if this PDF was the original PDF that exhibited the described problem, or if the customer was just trying to mail the original problem PDF via his MacBook and unintentionally re-saved + re-wrote the PDF when operating his mail app.

Indeed, Preview heavily re-writes any PDF that was initially created by any non-Quartz application upon saving it for the first time.

Latest version of preview mac os