News for hackers. Stuff that matters.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @03:19PM (#25448004)
They are using software unsupported by the vendor and blaming Apple for the outcome.

“ABBYY says they don’t support Big Sur yet, that’s fine. But Apple didn’t tell me that I can’t upgrade to Big Sur when I use ABBYY. I’d be a lot less angry if there was a changelog or release notes from Apple where it says there is a known problem with OCR’ed PDFs in Preview. Their software is broken, they need to tell me. I don’t care if it only worked because they had workarounds for super shitty PDFs that ABBYY possibly produces, I just need my OS to keep working for me.”

Re:Preview in macOS Big Sur is destroying PDFs by jcrawfordor on Wednesday December 16, 2020 @03:40PM (#25448286)
So Preview opens a file, which is apparently valid per Preview (Preview handles and displays it correctly). After changes, preview then saves a file that is not valid per Preview (OCR text layer is corrupted).

It is very difficult for me construe a situation in which this would not be considered errata in Preview. Even if ABBYY is writing unusual PDFs, it's popular enough software that this issue will be encountered in the real world multiple times. Having to deal with unusually formed PDFs is just a general trait of writing PDF software. If you consider it a non-issue that your software writes corrupt PDFs when the same situation is handled correctly by Acrobat, no matter how unjust you feel the cruel world to be, you should not be in the PDF business. There's a reason most PDF viewers only present a highly constrained feature set, and it's because writing a capable PDF editor is very difficult. Apple has decided they are up to the challenge, and in this case has failed.

As a general rule, if your software package opens a file fine, then writes a broken version of it, seems to all the world like a bug in your software package.

The idea that this behavior in a PDF reader can be excused because the software that generated the PDF was not approved for the operating system the viewer is running on per the vendor... kind of stretches credulity. I don't usually inquire as the OS used to generate the PDF when I receive one.

Re:Preview in macOS Big Sur is destroying PDFs by dkonofalski on Wednesday December 16, 2020 @04:45PM (#25449194)
If this is a bug with Preview, then that's really, really bad since Preview is a bedrock of macOS and has been for years.

However... it sounds like the issue is that FineReader is storing the OCR'd text in the metadata in a way that's not part of the official PDF spec. So, it sounds like Preview is able to open the file by ignoring that metadata and then, upon save, is storing the metadata back, as normal, which then corrupts the OCR data. This reminds me a lot of when people would store metadata like this in MP3 files to include things like album art and booklets. Normal mp3 players would ignore it as just metadata or bogus data but opening it in an audio editor would do this same thing.

I'm not sure who the "blame" lies with in this case because Abby FineReader probably is writing this stuff in a non-supported way but Preview really should just ignore it rather than trying to correct it. It's very likely that the OCR text, post-save, is actually bits from the document itself rather than from the metadata.

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @03:56PM (#25448511)
“The idea that this behavior in a PDF reader can be excused because the software that generated the PDF was not approved for the operating system the viewer is running on per the vendor.”

Nobody is saying that. The suggestion is that the software that generates the PDF produces corrupt documents.

The fact that the vendor of that software doesn’t approve it for Big Sur suggests that they might be aware that there are problems.

Re:Preview in macOS Big Sur is destroying PDFs by jcrawfordor on Wednesday December 16, 2020 @04:10PM (#25448704)
I worded it that way for two reasons, one of which is admittedly speculative:

1) It seems highly unlikely that ABBYY relies on some changed OS behavior in generating PDFs that leads to it producing PDFs that are malformed in such a way that is only revealed when they are rewritten by Preview. Behavior in Preview is by far a more likely cause of the problem. Generally the thing that changed is what broke...

2) To the user, this looks 100% like a problem in Preview no matter what's happening, and it's Apple's responsibility to not do this kind of thing to users. The PDF opens properly the first time, so de facto it is "valid" as determined by the product that later corrupts it. As I said, handling questionably valid PDFs is part and parcel of writing PDF software, and failure to handle a PDF that otherwise renders correctly looks like a bug on your part... especially when it otherwise renders correctly in your own software.

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:30PM (#25448980)
I don’t really see why #1 is highly unlikely. PDF is very complex, and it’s easily possible that a generator could have a bug.

‘Generally the thing that changed is what broke’

This has been never been true in software engineering. Changed code reveals bugs which need to be fixed elsewhere all the time.

2. Yes, to the end user it looks like a problem with preview.

No, the fact that it opens at all doesn’t make it de facto “valid”.

Yes, handling questionable PDFs is part of writing PDFs handling software.

No, that doesn’t mean that all PDF handling software must or can feasibly handle any and all corruption.

The very fact that there are many kinds of questionably valid PDFs out there proves the point. Handling the the intersection of all the invalid PDFs is impossible.

Rendering correctly has nothing to do with this. PDFs have many attributes which are not rendered.

It really is on the document creator to produce a valid document in the first place.

It’s certainly on ABBYY to have tested this months ago and either fixed it, or publicized it.

Re:Preview in macOS Big Sur is destroying PDFs by dkonofalski on Wednesday December 16, 2020 @04:53PM (#25449296)
>The PDF opens properly the first time, so de facto it is "valid" as determined by the product that later corrupts it.

While I agree with your main point that, to the user, this looks like a problem with Preview, I think it's actually because Preview is doing something beneficial to open the file which is to ignore "bogus" data. Preview, from what I can tell, ignores additional data that it doesn't expect specifically to allow for opening PDF files where the document data is fine but the metadata is corrupted. The fact that it opens it means nothing since the file would not be able to be opened at all otherwise and Preview is actually doing the user a favor by salvaging it. Once Preview "fixes" it, though, it looks like the OCR pointer is still there but the metadata that contains the plain-text content is not so it's pointing to binary document data instead. Another option is that Preview has "fixed" a font and the mapping is no longer correct which, while I can't really see the text in the image, would be obvious as you'd see words that map to the same corruptions. In either case, Preview's behavior is "correct" and the fact that it was less strict before does not mean that it's now broken - the source PDF is still what was "broken".

Re:Preview in macOS Big Sur is destroying PDFs by interestica on Wednesday December 16, 2020 @11:34PM (#25452495)
I think a big issue is that 'preview' is used as just a pre-view. The metaphor is that you haven't actually opened/viewed the file yet 'for real'. Yet, preview has morphed into a program that makes changes to files even without any kind of save dialogue.
Re:Preview in macOS Big Sur is destroying PDFs by dkonofalski on Thursday December 17, 2020 @11:36AM (#25457154)
Are you confusing Quick Look with Preview? Preview is not just for PDFs and allows you to view, annotate, and edit lots of document types...
Re:Preview in macOS Big Sur is destroying PDFs by interestica on Friday December 18, 2020 @11:24AM (#25468569)
No, really. Preview. Yes, it can open everything (I don't know where I suggested that it is only for PDFs?)

But it doesn't act like other editors. There's no save dialogue when you, for instance, rotate a PDF. The term 'Preview' in other programs, like when using a scanner or other text editors, is a non destructive type of viewer. Just a viewer. "preview before you make changes"

But preview on OSX changes that.

Re:Preview in macOS Big Sur is destroying PDFs by smarx007 on Wednesday December 16, 2020 @05:58PM (#25449947)
This is ridiculous. When I read that FineReader is not supported on Big Sur, I understand it as I cannot run FineReader to _produce_ PDFs on Big Sur. But I expect Big Sur not to trash PDF files that were produced on Catalina, for example.

By the way, I was forced to purchase PDF Expert since a few years ago because of all kinds of problems with Preview (blurry text, wierd bugs with annotations, removed ability to print PDF with annotations and the list goes on).

Re:Preview in macOS Big Sur is destroying PDFs by arvindamirtaa on Wednesday December 16, 2020 @03:28PM (#25448148)
Here's the rest of the statement that you left out that answers your point.

"...I just need my OS to keep working for me. This bug could hit me without even owning a scanner at all – someone sending me a PDF that I then unknowingly break before archiving it. That’s the part I’m mad about."

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @03:34PM (#25448219)
It doesn’t really. Firstly, that’s not what they are mad about, since that hasn’t actually happened to them. They are mad that the pdf’s their scanner produces don’t work properly.

And secondly, that hypothetical could well be using broken software too. We really don’t know how bad the PDF’s ABBY produces are, but as someone who owned this scanner and the software, it’s fairly obvious that the software is barely maintained.

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.

Re:Preview in macOS Big Sur is destroying PDFs by arvindamirtaa on Wednesday December 16, 2020 @03:40PM (#25448281)
> "They are using software unsupported by the vendor and blaming Apple for the outcome."

But by this logic, no software other than those that Apple sells you directly (their own or through the MAS) is "supported software". If Apple makes a change and all of them break rendering it useless of anyone using software not bought from them, would you still be making this same apology?

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @03:42PM (#25448308)
No this is not correct.

ABBY hasn’t updated their software for Big Sur, i.e. ABBY themselves say it hasn’t been updated yet and is not supported by them on Big Sur.

That’s what unsupported means. It has nothing to do with whether Apple supports it.

Re:Preview in macOS Big Sur is destroying PDFs by arvindamirtaa on Wednesday December 16, 2020 @03:45PM (#25448350)
I receive that PDF file that looks like any other PDF file.

I open it with preview. It opens fine. I close it and open it again. It opens fine.

I open it a third time and make a small arrow pointing to something and save it (as I would with ANY OTHER PDF).

It breaks.

I'm not using ABBYY. I've never heard of it. It's not on my system. It's just a PDF file that I got sent.

Now what?

Re:Preview in macOS Big Sur is destroying PDFs by dayjobpork on Wednesday December 16, 2020 @03:52PM (#25448466)
You are opening it wrong /s
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @03:58PM (#25448542)
You’re a victim of ABBYY’s poor PDF generation, that’s what.

Nothing excuses ABBYY if their PDFs are corrupt.

Re:Preview in macOS Big Sur is destroying PDFs by mynameisvlad on Wednesday December 16, 2020 @04:10PM (#25448703)
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.

Re:Preview in macOS Big Sur is destroying PDFs by dkonofalski on Wednesday December 16, 2020 @04:59PM (#25449364)
>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?

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:32PM (#25449013)
“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.

Re:Preview in macOS Big Sur is destroying PDFs by arvindamirtaa on Wednesday December 16, 2020 @04:00PM (#25448579)
Hahaha this is just brilliant.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:05PM (#25448642)
It’s not brilliant. It’s just correct if ABBYY is producing corrupt PDFs, which is a possible cause of this problem.
Re:Preview in macOS Big Sur is destroying PDFs by arvindamirtaa on Wednesday December 16, 2020 @04:10PM (#25448717)
If "Corrupt" = works fine until you make an edit and save using Preview, yes. You're 100% correct.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:33PM (#25449028)
Works fine until you make an edit really doesn’t mean anything at all. PDF is much more complex than just a static image.
Re:Preview in macOS Big Sur is destroying PDFs by ehutch79 on Wednesday December 16, 2020 @07:20PM (#25450659)
Someone buys a bottle coke

They shake it up a lot

They hand me said bottle of coke

I open it, and get sprayed by fizz

THAT IS CLEARLY THE COCA-COLA COMPANIES FAULT!

Re:Preview in macOS Big Sur is destroying PDFs by ehutch79 on Wednesday December 16, 2020 @07:25PM (#25450714)
To be clear, my point here is that just because something is handed off, does not mean it's existence is reset or something.
Re:Preview in macOS Big Sur is destroying PDFs by function_seven on Wednesday December 16, 2020 @03:42PM (#25448306)
> 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.

I think it is. Preview used to correctly handle the thing, and now it doesn't. Users cannot be expected to inspect the raw PS code of their PDFs to determine standards compliance. What they can do is assume that something that works yesterday, and appears to work today, is in fact working.

The PDFs didn't change, the application did. It's the application's fault.

If you have compatible behavior that you remove, it's on you to alert the user of the reduced functionality.

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @03:52PM (#25448464)
Yes, it is in principle possible that Apple was doing something special to support bad PDFs produced by ABBY which they then removed. If this is what happened, I would agree with you.

But, there is no evidence yet that they removed anything.

It’s quite possible (I’d say likely) that ABBY’s PDFs were corrupt all along.

Preview may have tolerated them not because of a special feature which was then removed, but because it happened not to depend on correctness before.

In this case, Apple wouldn’t have been in a position to even know about the problem.

You know who would? ABBY, who have had free access to Big Sur for months. You’d think that even cursory testing at their end would have shown this problem.

They have had months to fix it, months to work with Apple on the issue, any months to publicize it it really is Apple’s fault.

Re:Preview in macOS Big Sur is destroying PDFs by tonyedgecombe on Wednesday December 16, 2020 @04:32PM (#25449018)
The trouble is the PDF specification is vague and ambiguous in a number of areas. This has resulted in a lot of ill formed documents. If you are going to write a PDF reader then you are going to have to accept those documents and not corrupt them.

Even if ABBY does have a bug and fixes it then people will still have a bunch of older documents they will want to read.

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:41PM (#25449139)
This is mostly accurate, however it is an idealization to suggest that you can accept and not corrupt all of the ill-formed documents.

This is in principle impossible.

If it turns out that there is a widespread problem with many kinds of document that no longer work properly, I’ll be more inclined to say Apple is at fault.

But as it stands, it just seems like ABBY has been producing bad PDFs.

Re:Preview in macOS Big Sur is destroying PDFs by saagarjha on Thursday December 17, 2020 @03:52PM (#25460260)
I’m sure Apple had much more time with ABBY than ABBY had with Big Sur ;)
Re:Preview in macOS Big Sur is destroying PDFs by jfim on Wednesday December 16, 2020 @03:51PM (#25448451)
> 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.

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:00PM (#25448583)
PDF’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.

Re:Preview in macOS Big Sur is destroying PDFs by duskwuff on Wednesday December 16, 2020 @04:26PM (#25448931)
PDF 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.

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:35PM (#25449069)
My 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.

Re:Preview in macOS Big Sur is destroying PDFs by buckminster on Wednesday December 16, 2020 @06:39PM (#25450287)
Yes, 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.

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @08:52PM (#25451384)
One 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.

Re:Preview in macOS Big Sur is destroying PDFs by ihuman on Wednesday December 16, 2020 @03:45PM (#25448358)
> They are mad that the pdf’s their scanner produces don’t work properly

The PDF that FineReader made worked properly. The one that Preview made didn't.

Re:Preview in macOS Big Sur is destroying PDFs by dkonofalski on Wednesday December 16, 2020 @05:01PM (#25449390)
That doesn't mean it's a valid PDF. Preview has error correction to try and recover document data when metadata is corrupt. It's entirely possible that the documents have always had corrupt metadata and that Preview now expects stricter PDF guidelines.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @03:58PM (#25448552)
How do you know it worked properly?
Re:Preview in macOS Big Sur is destroying PDFs by ihuman on Wednesday December 16, 2020 @04:23PM (#25448888)
The first paragraph and image in the article. When the author copied the text from FineReader's PDF and pasted it in TextEdit, it had the correct text. When the author tried that with preview's pdf, it pasted garbled data.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:43PM (#25449166)
That doesn’t mean there wasn’t file corruption.
Re:Preview in macOS Big Sur is destroying PDFs by ihuman on Wednesday December 16, 2020 @04:50PM (#25449256)
I never said anything about file corruption. You asked how I know FineReader worked properly, and I explained why the article showed it working properly, and that preview doesn't work properly anymore.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @05:16PM (#25449532)
File corruption would be a way it would not be working properly that wouldn’t be revealed by what you did.
Re:Preview in macOS Big Sur is destroying PDFs by matrixagent on Wednesday December 16, 2020 @03:25PM (#25448095)
Read it again. This bug could hit you without ever using ABBYY yourself. Apple broke Preview.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @03:37PM (#25448251)
I read it. It doesn’t show that Apple broke Preview. It says Preview stopped being compatible with PDF’s produced by ABBYY.

Those PDFs could have been buggy all along, and only now be showing up due to improvements in preview.

It’s possible that Apple broke preview, but having seen how poorly maintained ABBYY is, I wouldn’t be surprised if it was producing malformed PDFs that just happened to work on older version of preview.

Re:Preview in macOS Big Sur is destroying PDFs by matrixagent on Wednesday December 16, 2020 @04:21PM (#25448865)
I honestly don't care who is exactly at fault. I definitely blame Apple for destroying the PDF. There might be plenty of blame left for ABBYY for creating a bad PDF in the first place. That does not change how utterly unacceptable Preview.app's behavior here is. If you honestly think there is no valid criticism for Apple here, I don't know what to tell you. In any case, the whole thing is annoying technology – and seeing some of the comments here, people should more often try to step out of their own mind bubble and try to look at these things form their grandparents' or similar perspective. I personally am very aware of plenty of ways to work around this issue. But Apple used to be the company you could use if you either are not or don't want to be concerned about things like that.

And a quick edit: I really dislike people who discuss like you do – all of what I just wrote is already stated in the post itself. Another commenter even called you out for ignoring that part when quoting me. I should not have wasted five minutes spelling it out for you again, your mind won't be changed anyway.

Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:53PM (#25449292)
With all due respect, if you had led with your “footnote”, you wouldn’t have even been able to write such an angry sounding piece. Also, you say that you don’t care who is at fault, but that isn’t how the piece came off. It’s odd you’d say that now.

I quoted you because you hadn’t incorporated this key information into the main text.

What I think is that there are many ill-formed PDFs out there and that supporting the intersection of all of them is essentially impossible.

I also think that it’s every bit the responsibility of a company like ABBY to generate good PDFs. How can it not be? Relying on Preview to be forgiving when you are a maker of PDF generation software is obviously irresponsible.

Why do you think ABBY didn’t announce that this problem existed when the Big Sur betas were available for them to test with?

For what it’s worth, I stopped recommending Fujitsu scanners years ago. For a while I loved mine, but none of the software was well maintained.

Re:Preview in macOS Big Sur is destroying PDFs by masswerk on Wednesday December 16, 2020 @09:22PM (#25451606)
"Broke" may be a bit harsh. What appears to be happening is that Preview somehow loses or corrupts the toUnicode map, which is apparently located in the metadata, when saving the PDF. Mind that every application will have to reassemble/reflow the metadata when saving a reflowed document (like after cropping and/or discarding pages). To do so, the application has to interpret and to reassemble the metadata before wiriting it back.

Now, some algorithms and routines may be more robust and allowing than others. Maybe, an innocent refactoring attempt just lost that critical bit of robustness, required to deal with that particular format produced by this particular application.

For example, consider an XML-based format, where a particular application delivered a malformed document, like a missing closing quote for some attribute. Most XML interpreters will churn happily along with this, but, after a rewrite of some routine, an application just ignores the malformed tag with the runaway string. Did it break XML? Or did it just fail to interpret a malformed document, it had somehow been able to deal with thanks to some extra robustness present in the previous version?

Considering this hypothetical case: Should that application be improved by an update to regain its previous robustness? Yes, absolutely. Is it a bug and is the vendor to blame? Probably not. Mind that this might be quite well what is happening here, as well.

Re:Preview in macOS Big Sur is destroying PDFs by matrixagent on Thursday December 17, 2020 @07:01AM (#25454794)
I think you might interpret the word more harshly than I intend it to be. Something that worked before Big Sur is not working in Big Sur. It's broken. That's all there is to it for me as an end user. Of course there is a difference in reasons for things breaking, and I'm not denying that Apple might have "improved" Preview.app when you judge it by how well it adheres to a PDF spec. But it still "broke" a very common and normal workflow by doing so, and I would at least expect them to acknowledge that. If they decide breaking this is worth it, that's absolutely fine with me. But I don't think they are even aware of it, and that is not something I'm willing accept from a company with the reach and resources of Apple.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Thursday December 17, 2020 @12:13PM (#25457578)
Are you happy to accept corrupt PDFs being generated by ABBYY, a company that does nothing but write software to produce PDFs and yet hasn’t even commented, let alone maintained their software?

Do you think ABBYY is even aware if the issue?

It seems like you expect Apple to test everyone else’s software, and make workarounds for their bugs.

Regardless of Apple’s scale and resources, this is obivously unreasonable.

Also you say: “That's all there is to it for me as an end user” as if you didn’t understand anything about the complexities of software development, but reading your comments on other topics, you are obviously skilled in the art. You are not ‘just an end user’ who doesn’t understand the complexities.

Re:Preview in macOS Big Sur is destroying PDFs by r00fus on Wednesday December 16, 2020 @03:33PM (#25448206)
So is there an active Preview corruption example that doesn't involve ABBYY? I've used FineReader before for a commercial effort, I do remember it being very finicky.
Re:Preview in macOS Big Sur is destroying PDFs by apocalyptic0n3 on Wednesday December 16, 2020 @03:42PM (#25448297)
It's unrelated to OCR, but there have been other Preview issues. We ran into an issue a few years ago where saving a PDF with forms in Preview would set some style setting so that in most other readers, the form fields would have no background color and use white text, making them unreadable. They were still perfectly readable in Preview, but had the style issues in Chrome, Firefox, Acrobat (and Reader), and Foxit. We have a project where we programatically fill in PDF forms using PDFtk and one day, our editor just starting spitting out empty PDFs. After troubleshooting, we traced it back to the style changes Preview was making after another dev had accidentally done a CMD+S on the template file and committed the template.

In short: NEVER save a PDF with Preview. You should probably just avoid opening it in Preview period, frankly.

Re:Preview in macOS Big Sur is destroying PDFs by matrixagent on Wednesday December 16, 2020 @04:27PM (#25448936)
I personally don't use anything else, but when the problem first occured a few years ago, it was not limited to PDFs from ABBYY. (Which is not to say that it's purely Preview.app's fault. Maybe all of these PDFs were created in a bad way, would not surprise me at all. Could very well be that Preview.app is actually "improving" and fixing old bugs/cruft, breaking things that worked before but never should have in the first place. As the end user that doesn't really matter for me though, as I said in the post itself.)
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @05:27PM (#25449651)
> Could very well be that Preview.app is actually "improving" and fixing old bugs/cruft, breaking things that worked before but never should have in the first place.

Exactly this.

So the question is, whose responsibility is it? Apple’s to magically support the intersection of all the broken sofware?

You essentially have argued that ABBY is popular enough that Apple should have tested it.

Maybe it is popular, but the implication is that Apple would need to regression test against all this popular PDF generating software for any change to the preview engine, since they wouldn’t be able to know for sure what software’s PDFs would be broken by conforming changes.

What we know they did, was to make a copy of Big Sur available for ABBY to use to test their own software. That’s pretty standard practice in a case like this and is them behaving responsibly.

If Preview really was at fault, ABBY could have raised the issue with Apple, and or put a warning in their own software. If it’s that popular, you’d think they would have an incentive to do this.

What isn’t obvious is that Apple should somehow introduce workarounds every time a third party doesn’t fix a bug.

Re:Preview in macOS Big Sur is destroying PDFs by ehutch79 on Wednesday December 16, 2020 @07:21PM (#25450668)
but the file was stuff generated with abbyy, even if you give it to someone else.
Re:Preview in macOS Big Sur is destroying PDFs by AlexandrB on Wednesday December 16, 2020 @03:25PM (#25448085)
Would be interesting to see if Preview is stripping OCRd text from PDFs not created by ABBYY FineReader.
Re:Preview in macOS Big Sur is destroying PDFs by db48x on Wednesday December 16, 2020 @03:43PM (#25448323)
Are you arguing that ABBYY Finereader is going to produce different PDF files once they support the new OS? Possibly they will, if only to work around this obvious bug in Preview.
Re:Preview in macOS Big Sur is destroying PDFs by zepto on Wednesday December 16, 2020 @04:07PM (#25448662)
I’m arguing that yes, they will produce different PDF files.

It’s not obvious the bug is in preview. The bug could easily be in in ABBYY’s PDF generation code.

To be fair, I’m not arguing that this is the case. I’m arguing that it just as easily could be as there being a bug in Preview, which is also possible.

Re:Preview in macOS Big Sur is destroying PDFs by db48x on Wednesday December 16, 2020 @11:10PM (#25452359)
It's entirely obvious that the bug is in Preview.