I find posts like this completely pointless when they include no details at all. This is just "there's an incompatibility between third-party software and a version of macOS that the third-party software says they don't support yet, so I'm going to publicly criticize Apple".
If you're not going to do the work to figure out what the corruption is, at least include the two PDFs so other people can look at them and see what happened.
There’s a list of blog posts about the same problem linked in the article including a radar from 2016 (https://openradar.appspot.com/29786282) on Apple’s bug tracker. It’s not exactly an obscure bug that nobody knows how to reproduce.
A radar from 2016 is not useful, that describes an old bug. Just because the symptoms look like something we’ve seen before doesn’t mean it’s the same underlying issue.
There might be newer Radars too, I can only see that 2016 one because some kind soul set up a public interface to show a subset of submitted Radars. With Apple's opaque and in-transparent bug reporting process there's no way of knowing if someone already reported it. I've submitted numerous feedbacks already but I can't do that for everything or do the homework for a trillion dollar company.
> If you're not going to do the work to figure out what the corruption is …
I'm sorry, but last time I checked neither Apple nor ABBYY pay my salary. I really don't understand these takes. If Apple or ABBYY want my PDFs, they should be able to find my email address rather easily. Your tl;dr version of the post is completely unfair. I publicly criticize Apple because they are breaking something that potentially affects a lot of people who are unlikely to even know about it, and they are doing it for at least the second time now. If you don't think that's worthy of criticism, I don't know what is.
I also love how so many people assume I didn't already talk to support and file radars. I guess you had better luck in the past than me, but I can assure you, these options aren't always as useful as you might think they are.
Fair enough, though I'd still argue that a public write-up that might warn a few people and save them the trouble is well worth writing on its own. As this blog is just a hobby, my time for it is limited and it's not like a write-up like this doesn't already take up some time. I did provide plenty of resources in the links, to which I don't think sample PDFs from me would add much value. But point taken, I'll try to attach sample data where applicable in the future.
If you're not going to do the work to figure out what the corruption is, at least include the two PDFs so other people can look at them and see what happened.