Close ad

MacOS Sierra is one of the more reliable versions of Apple's computer operating system, as it introduced fewer major innovations and often focused on improving performance and stability. However, it is far from perfect and some flaws are too obvious.

One of them has been showing up for quite some time – problems with PDF documents. On the day of the official release of macOS Sierra, the first problems associated with PDF files were discovered by users of Fujitsu's ScanSnap scanning applications. The documents created by this software contained many errors and its users were advised to wait before switching to a new version of macOS. Fortunately, ScanSnap's malfunction on the Mac was preventable, and Apple fixed its compatibility with macOS with the release of macOS 10.12.1.

Since then, however, there have been more problems with reading and editing PDF files on the Mac. All seem to be related to Apple's decision to rewrite PDFKit, which handles macOS's handling of PDF files. Apple did this in order to unify PDF handling in macOS and iOS, but in the process inadvertently affected macOS's backward compatibility with pre-existing software and created many bugs.

DEVONthink-affiliated developer Christian Grunenberg says of the modified PDFKit that it's "a work in progress, (…) it was released too soon, and for the first time (at least as far as I know) Apple has removed several features without considering compatibility."

In the latest version of macOS, marked 10.12.2, there is a new bug in the Preview application, which removes the OCR layer for many PDF documents after editing them in the application, which enables text recognition and work with it (marking, rewriting, etc.).

TidBITS Developer and Editor Adam C. Engst he wrote: “As a co-author of the manual Take Control of Preview I'm sorry to say this, but I must advise Sierra users to avoid using Preview to edit PDF documents until Apple fixes these bugs. If you can't avoid editing the PDF in Preview, make sure you work with a copy of the file and keep the original in case the edits somehow damage the file."

Many developers reported the observed bugs to Apple, but in many cases Apple either did not respond at all or stated that it was not a bug. Jon Ashwell, developer of Bookends, said: “I sent Apple several bug reports, two of which were closed as duplicates. On another occasion, I was asked to provide our app, which I did, but received no further response.”

Source: MacRumors, TidBITS, Apple Insider
.