71–80 of 326 posts
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.
However, there are exceptions, for example the first ‘b’ on line 10. It becomes an ‘ä’ on line 21. I guess that’s because that is bold text, and thus a different font.
Earlier quoted context omitted.
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 main…
> 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.
Earlier quoted context omitted.
What device do you use to read PDF's?
I've really been enjoying a remarkable tablet since I got it a few weeks ago. Great for taking notes, great for reading pdf's (and scribbling on them - which is surprisingly useful!), terrible for literally anything else.
I hope it will soon be the best e-reader on the market, thanks to KOReader[1].
[1] https://old.reddit.com/r/RemarkableTablet/comments/jsb3r7/ko...
Why anyone treats PDF as anything but a write-once format is beyond me. It's so finicky that I'm not shocked bugs like this happen. The only programs I'd be reasonable sure wouldn't screw it up are Acrobat itself, and pdflatex and friends. I think we need a multi-image container format. It could be something that's literally a bunch of jpgs/pngs/pick your poison in a tar container, and given a new extension. OSes wou…
If you don't want to break something, just don't try to edit it. That can't be enforced anywhere but at the individual user level.
Even proprietary formats in first-party software have this problem. Hell, plain-text editors have this problem.
Let's be real. Every single macOS release, until it reaches x.y.4 or x.y.5 is just in beta and you are the tester. I upgraded to Catalina when it hit 10.15.6, and I watched for the year since the release all the comments and posts about the horrible things it was doing to their computer, files, apps, etc. Apple supports the latest 2 versions of macOS. Always be on the "previous" one is my advice. Since my family and…
I don't know very many pieces of widely used / actively developed software that stayed static on X.0.0 for more than a couple weeks after release or so.
Earlier quoted context omitted.
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?
You’re a victim of ABBYY’s poor PDF generation, that’s what. Nothing excuses ABBYY if their PDFs are corrupt.
Earlier quoted context omitted.
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 main…
> 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 unabl…
It’s not clear what’s causing the problem, but verifying correctness of programs is not a solved computer science problem.
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…
That said, the author of this article is clearly an ass, and i have a hard time being sympathetic.
Assuming the pdf is actually in spec, which it's probably not, this shouldn't be happening. That said, if the 3rd party app vendor says the pdfs they generate are broken in big sur, that should tell you, they may be broken other places as well, and it's probably not apple's issue.