contador web Saltar al contenido

Developers are suffering from problems related to PDFKit on macOS Sierra 10.12.2

If you manage and edit a lot of files PDF on macOS, we have pretty bad news if you?re using the latest version of Apple?s desktop operating system, the macOS Sierra 10.12.2.

Adam Engst, from the website TidBITS and co-author of the book Take Control of Preview , recalled some problems that users have been facing since the launch of Sierra (more specifically with PDFs created by Fujitsu's ScanSnap scanner; something that was corrected in the 10.12.1 update). Now, however, the problems have increased.

Summing up the technical part: apparently (according to developer Craig Landrum), Apple decided to rewrite the framework PDFKit in macOS 10.12, which broke a lot of PDF-related things used by developers. Software that uses third-party PDF libraries is probably immune to the problems; but developers who use PDFKit (like the creators of DEVONthink and EagleFiler) are not only suffering, they can do absolutely nothing to solve things once and for all.

Apple's plans, according to developer Christian Grunenberg (from DEVONtechnologies), involve creating the same foundation for both iOS and macOS. Only, for him, everything was released a little too soon, depreciating several resources without worrying about compatibility. With the 10.12.2 update, many new incompatibility issues have appeared and almost none of the old ones have been fixed.

In macOS 10.12.2, if you edit in Preview (Preview) a PDF document containing layers of text inserted by the ScanSnap scanner's OCR feature, all of these layers will be deleted. The Bookends app is closing every time when showing a PDF with annotations. Interestingly, the Pr-Visualization app itself doesn't seem to be suffering so much from PDFKit's problems.

While none of this is corrected, the solution for those who work a lot with PDFs (either in Pr-Preview or third-party apps) is to guarantee and always work on a copy of the original document, in order not to miss anything.

Let's hope that in macOS 10.12.3 (which is already in the testing phase) these problems are properly and completely solved.

(via Daring Fireball)