3 ms·
> It really isn’t Apple’s fault if someone else is producing bad files that they happened to previously tolerate, especially if that somebody isn’t maintaining
by jfim 6y ago
> It really isn’t Apple’s fault if someone else is producing bad files that they happened to previously tolerate, especially if that somebody isn’t maintaining their software.
It's not clear if the issue is caused by the PDF files produced by ABBYY, or if the issue is also present in other OCR'ed PDF files.
In either case, Preview shouldn't silently corrupt the file. It could display an error saying that it was unable to save the file, or a warning that some data couldn't be saved, so that the user can check if the file still works for them after saving.
- zepto 6y agoPDF’s are essentially a stack machine based program. It’s not clear what’s causing the problem, but verifying correctness of programs is not a solved computer science problem.
- duskwuff 6y agoPDF is not a stack machine. This is a common misconception. PostScript was a stack machine with included operators which implemented a set of vector graphics commands. PDF has a similar rendering pipeline, but it renders a set of primitives described directly in the document -- there is no virtual machine involved.
- zepto 6y agoMy understating is that PDF still has a stack machine. Just one that is much simpler. Having said that, PDF is vastly more complex than it was originally. It can contain forms, JavaScript, audio, video, accessibility metadata, etc. It’s an extremely complex format.
- buckminster 6y agoYes, but it's easy to generate a valid pdf. You just include the features you need and ignore the rest. It's really hard to transform an arbitrary pdf because you need to handle all the features. Without further information this is more likely to be an Apple bug because they are doing the harder job.
- zepto 6y agoOne point: Transforming an already incorrect file into a correct one is the hardest job of all. Plus some further information: ABBY has had months to support Big Sur but still haven’t. That makes it seem like they either don’t care about supporting MacOS users, or they have a very low engineering budget. Either way, that makes it seem more likely to me that they have a bug, than Apple. But, regardless of the balance of probabilities, the point is that the original piece blames Apple entirely. And yet nobody here really seems to dispute the idea that ABBY, a professional PDF generator could be producing a buggy file.