View Single Post
Old 03-06-2017, 07:45 PM   #6
dwig
Wizard
dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.dwig ought to be getting tired of karma fortunes by now.
 
dwig's Avatar
 
Posts: 1,613
Karma: 6718541
Join Date: Dec 2004
Location: Paradise (Key West, FL)
Device: Current:Surface Go & Kindle 3 - Retired: DellV8p, Clie UX50, ...
Quote:
Originally Posted by gabaldini View Post
thanks a lot for your answer!
Now I know its not my kindle fault! I would try your suggestions.
Actually, it might be your Kindle's fault, though given the horrid PDFs that the Internet Archive distributes I'd say the odds were that the fault lies in the file.

That said, the Renderer vs PDF file coin has two sides. Tomsem describes one side well. On the flip side, though, there are a wide range of perfectly legitimate options in the construction of a PDF. Few PDF renderers support 100% of these. My old Kindle Keyboard doesn't support layer transparency in PDFs, something the IA is notorious for using in their PDFs. This can cause significant "missing" elements when displayed. For ages, Apple's Preview app, their default viewer for PDFs as well as images, failed to support a significant range of legitimate font encoding options making many PDFs generated on Windows fail to render readable text when viewed in Preview although Adobe Reader on Mac displayed the PDF perfectly. The list of such flaws in renderers is endless.
dwig is offline   Reply With Quote