3 ms·

Wow, just wow. The PDF works fine before saving in Preview. As in, Preview itself will render the file perfectly fine with OCR. By all accounts, the PDF is com

Wow, just wow. The PDF works fine before saving in Preview. As in, Preview itself will render the file perfectly fine with OCR. By all accounts, the PDF is completely valid and uncorrupted at this point. Making a change to the file and saving it in Preview is what causes the corruption. So how the hell could you possibly excuse Preview and call this a ABBYY issue when Preview is the one that causes the issue? That's absurd to the highest level.

zepto 6y ago
“By all accounts, the PDF is completely valid and uncorrupted at this point.” Is it? I don’t see any accounts showing this to be a fact.
dkonofalski 6y ago
>The PDF works fine before saving in Preview. I think the disagreement here is that there's no evidence of this. Preview's error handling could very well be interpreting bad data and allowing the file to be opened. The question becomes, then, should Preview continue to propagate that bad data on save or should it try to correct it with the possibility that it corrupts just that data. If the PDF was not in-spec prior to Preview touching it but it is in-spec after Preview saves it, is it a good thing that Preview "fixed" the PDF file and made it "proper" or is it bad because it technically lost/corrupted data? In other words, what is the "right" thing for a software to do in this case? Keep bad data and leave the file as "bad" or fix the issue to make a valid PDF and, as a side effect, remove the "bad" data?