Closed fletchsod-developer closed 3 years ago
Snuffleupagus
commented
3 years ago Your PDF document uses non-standard fonts, but doesn't embed any of them, which means that the PDF document itself is violating the PDF specification and it simply cannot be guaranteed that the document will render as intended in all viewers.
fletchsod-developer
commented
3 years ago Segoe UI is a TTF file that come with Windows 10, in the "C:\Windows\Fonts" folder. The "Quick PDF" software doesnt have the embedding API object
Snuffleupagus
commented
3 years ago Segoe UI is a TTF file that come with Windows 10,
That means that anything which isn't Windows will be, more or less, guaranteed to not render the PDF document correctly. Note that the whole point of the "Portable Document Format" is that files should be portable, and by not embedding fonts you're basically guaranteeing that problems can/will occur.
The "Quick PDF" software doesnt have the embedding API object
If a particular PDF generator cannot embed fonts correctly, that's a bug in that software.
timvandermeij
commented
3 years ago Closing since this is a duplicate of some of the issues in https://github.com/mozilla/pdf.js/issues?q=is%3Aopen+is%3Aissue+label%3A4-non-standard-fonts.
BuyersGuide_4_26_2021 12_00_31 PM.pdf Attach (recommended) or Link to PDF file here:
Configuration:
Web browser and its version:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.85 Safari/537.36
Operating system and its version:
Windows 10
PDF.js version:
Unknown but latest version in Google Chrome
Is a browser extension:
Yes, in latest version Google Chrome
Steps to reproduce the problem: 1.PDF I'm attaching, open it in this JS PDF viewer (render wrong) 2.PDF I'm attaching, open it in Adobe Acrobat Reader DC (render correctly)
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):