-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PDF content not visible (white/empty view) #7
Comments
This is still an issue in v79 (last non-open-sourced release). It is unclear to me if it's all due to a single cause or multiple causes. Some of the (possible) reasons why№ 1: protected PDFOne of the reasons Qiqqa will show a blank slate for an otherwise correctly imported PDF is when that PDF is flagged as protected. Many datasheets published in PDF format exhibit this behaviour once imported in Qiqqa. As part of the Qiqqa reverse engineering work done in the years past (https://github.com/GerHobbelt/qiqqa-revengin), it turned out that taking those PDFs and deprotecting them using an external tool such as Examples of protected PDFs which cause this: On-Semi/Fairchild datasheets. (It's been long since I had this problem myself, so no ready example available straight away at the time of this writing, alas) № 2: bad or broken PDF imported into QiqqaWhen you use the Qiqqa Sniffer to find and download additional publications, once in a while a download MAY fail in such a way that Qiqqa believes a file has been obtained, but only part of the data has actually arrived (or even nothing at all): this will cause a bad/broken PDF file to be imported into Qiqqa, which will not be reported as broken or damaged, but instead will show up a a document with 1 or many utterly blank pages. № 3: ...(Anything else from the discussion board?...) |
Related to #34 |
An example PDF which exhibits this behaviour: |
…le updated: -q quiet mode patches, ...) Going to use binary PNG transmission over stdout as working with a temporary file would quickly wear out any SSD serving as temp disk: one image rendered for every page, thumbnail of a page, etc.etc.: that's a lot of images rendered and saved to temp disk space if we used that as intermediate storage. :-( - adding width next to height as a render criterium: this should ultimately fix a long-standing problem I have with Qiqqa rendering 'PowerPoint presentation PDFs' in a crazy way: those pages SHOULD be fitted to the screen as well as all other pages. That's about jimmejardine#7, jimmejardine#9, jimmejardine#209, jimmejardine#280 and a part of the work towards jimmejardine#289
See #209. This was a SORAX-specific bug. As bleeding edge now has kicked out SORAX, this problem at least is gone. |
Afterparty Note: this bug is SORAX barfing a hairball ona whole slew of PDFs, particularly ones that are "protected" against printing, etc. OnSemi IC datasheets are a prime example: they failed all of them. MuPDF has no problem with them, so preprocessing these PDFs with |
…new bits of technology to be integrated into Qiqqa as we upgrade the functional elements to modern standards (embedded browser, etc.): jimmejardine/qiqqa-open-source#2 jimmejardine/qiqqa-open-source#7 jimmejardine/qiqqa-open-source#34 jimmejardine/qiqqa-open-source#35
As reported by Tiffany here: https://getsatisfaction.com/qiqqa/topics/pdf-content-not-visible
Related issue report: https://getsatisfaction.com/qiqqa/topics/pdfs_stop_displaying_blank_pages
The text was updated successfully, but these errors were encountered: