As shared above, that the document that you are viewing is on web. Could you confirm the web browser you are working on?
As Mac uses its own pdf viewer to view the pdf, make sure that that you have the Acrobat Reader plugin installed.
For testing purpose would you try opening the file in the desktop application? To see whether result is same or not
I'm viewing it on Chrome.
Like I said, I'm not interested in additional plugins. There obviously seems to be a way to make it work without them, as I can view other company's ebooks just fine on the same web browser, but not my own pdf, and my department isn't going to be satisfied with a plugin fix. And I of course cannot expect most people to have downloaded extraneous plugins. What I want to know is, what are these competitors doing right that I'm doing wrong?
The error doesn't seem to occur on the desktop app for Acrobat, using the latest version.
The Chrome browser (and FireFox and MS Edge) uses it's own PDF viewer. If you are running into problems with that viewer, with a file that renders correctly in Adobe Acrobat or the free Adobe Reader, the problem is in the browser software. You need to file a bug report about Chrome's PDF viewer with the Chrome development team. You can do this from within Chrome:
Why is it I can see other people's pdfs just fine then, with the same browser? It makes no sense...
Appreciate the replies though.
1 person found this helpful
Without knowing how exactly the Chrome PDF viewer works, it's impossible to say what exactly is triggering this particular problem. It could be due to the font you are using, or how the PDF file is organized internally. What it comes down to is that Chrome is not processing something in your PDF file correctly. It's very likely not the PDF file that is the problem (you can view it correctly in Acrobat), but how Chrome is rendering your specific file.
I see, thank you. I suppose then I'm looking for suggestions on how to export or optimize the file differently for testing purposes to help me root out the problem.
Key things to consider in testing
1. Don’t stroke fonts
2. Never outline fonts
3. Transparency will make a difference, anywhere on the page
4. Be sure you know how to check reliably whether fonts did embed, substitution makes a lot of difference
5. Take careful note of the browser versions involved and check for fixes.