Software that uses third-party PDF libraries probably runs fine, but those of us in the development community who relied upon Apple’s PDFKit library were really slammed - and we have no way to fix the problems ourselves. The primary problem with Sierra with respect to PDFs is that Apple chose to rewrite the PDFKit framework in macOS 10.12 and it broke a number of things that PDF-related developers relied upon (I write scan-to-PDF software and know other developers who were impacted). Developer Craig Landrum, who founded the document management system company Mindwrap, said: The first I heard that Sierra’s PDF-related problems might affect more than ScanSnap scanners came in a comment left on one of those articles on 26 October 2016.
Now, however, it seems Sierra’s PDF-related problems go deeper, and you should exercise caution when editing PDFs with Preview. Those problems turned out to be less severe than initially feared (see “ ScanSnap Conflicts with Sierra Easily Avoided,” 3 October 2016), and Apple resolved them in macOS 10.12.1 (see “ macOS 10.12.1 Sierra, watchOS 3.1, and tvOS 10.0.1 Mostly Fix Bugs,” 24 October 2016).
One of the first problems with macOS 10.12 Sierra revolved around PDFs created by Fujitsu’s ScanSnap scanners (see “ ScanSnap Users Should Delay Sierra Upgrades,” 20 September 2016).
0 kommentar(er)
