One of the simplest and most useful applications that all Mac computer users have is "Preview". With it, we can easily edit PDF documents, among others. It is not an application in the style of PDF Expert, with a much more professional style and full of advanced features and functions, however, for day to day, for editing, simple annotations, as I said, it is very useful.
Now, however, those users of Mac computers that already have macOS Sierra 10.12.2 installed and running on our computers, we are being urged to stop using Preview for editing PDF documents, at least until Apple corrects various errors contained in the application that could cause serious problems in the original document.
Preview glitches could damage your PDF documents
All macOS Sierra 10.12.2 users should stop using the native Preview application for editing PDF files otherwise, the original file could suffer irreversible alterations. At least this is the recommendation made public by the editor of TidBITS, Adam Engst.
With this statement, Engst supports the position of developer Craig Landrup who previously stated that Apple's decision to rewrite the PDFKit framework for macOS 10.12 has broken essential functionality on which PDF-related developers rely, such as support for ScanSnap and Doxie scanners.
Adam Engst, co-author of "Take Control of Preview", urges users to stop using the Preview app in macOS Sierra 10.12.2 because the new version of the PDFKit is a "work in progress" that could lead to serious problems in edited documents
At the same time, Adam Engst points out that, if we have no other option at that time but to work on a PDF document through the Preview app, let's do it using a copy of the document, keeping the original PDF file safe. .
It pains me to say this, speaking as the co-author of "Take Control of Preview," but I have to recommend that Sierra users avoid using preview to edit PDF documents until Apple fixes these errors. If editing a PDF in preview is unavoidable, be sure to only work on one copy of the file and keep the original if editing introduces corruption of any kind.
The Preview application, as a "work in progress"
Regarding the cause or causes of these serious problems in Apple's Preview application, Adam Engst quotes DEVONthink developer Christian Grunenberg, who has defined the new rewritten version of PDFKit in macOS Sierra as a "work in progress":
Apple wants to use a common foundation for iOS and macOS. However, it was released too early, and for the first time (at least in my experience) Apple disapproved of several features without worrying about compatibility. And to make matters worse, many of the above features are now broken or not implemented at all, which means we had to add a lot of solutions or implement things on our own. And there is still work to do.
[macOS Sierra] 10.12.2 introduces new issues (it seems Apple wants to at least fix the now broken compatibility) and of course it fixed almost none of the other issues. Not only DEVONthink - many other applications (such as EndNote, Skim, Bookends, and EagleFiler) are affected as well.
As specified by MacRumors, previously "Apple removed the functionality of its iWork suite for Mac" in order to make it compatible with iOS, however, it reintroduced the lost features in a later version. Whether Apple plans to do the same with an upcoming update to "Preview" is still unclear. In the meantime, Until Apple resolves the issues with the native Mac application, Engst recommends Smile's PDFpen app as an alternative for PDF editing of all kinds, or Adobe Acrobat DC as a more expensive option.
This has been going on for a long time ...
"Broken" does not translate to "broken" (broken or broken, as you used the word both times). It should be translated as "(which) does not work" or "(which) is not working".