Skip to content
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

Closed
GerHobbelt opened this issue Jul 14, 2019 · 6 comments
Closed

PDF content not visible (white/empty view) #7

GerHobbelt opened this issue Jul 14, 2019 · 6 comments
Labels
🐛bug Something isn't working 🕵investigate Needs further analysis to find the root cause.

Comments

@GerHobbelt
Copy link
Collaborator

GerHobbelt commented Jul 14, 2019

As reported by Tiffany here: https://getsatisfaction.com/qiqqa/topics/pdf-content-not-visible

I am using v. 78. I have a large library. Many of my pdfs display perfectly but some do not. If I have over the document, I still get the quick view. However, when I open the document none of the pages display, nor are they visible in the preview tab. The documents open fine in an external viewer.

Related issue report: https://getsatisfaction.com/qiqqa/topics/pdfs_stop_displaying_blank_pages

@GerHobbelt
Copy link
Collaborator Author

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 PDF

One 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 qpdf helps: this does (of course) NOT resolve the issue itself but the deprotected PDF will show up all right in Qiqqa once that one has been imported as well, thus providing a reasonable work-around. (https://github.com/GerHobbelt/qiqqa-revengin/blob/master/mv_protected_pdf.sh)

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 Qiqqa

When 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?...)

@GerHobbelt
Copy link
Collaborator Author

Related to #34

@GerHobbelt
Copy link
Collaborator Author

An example PDF which exhibits this behaviour:
F7D042DAF56686EFEADFA1EDED8B5E9CCEE3C364.pdf

@GerHobbelt GerHobbelt added this to the Our Glorious Future milestone Oct 4, 2019
@GerHobbelt GerHobbelt added 🦸‍♀️enhancement🦸‍♂️ New feature or request 🤔question Further information is requested or this is a support question 🐛bug Something isn't working 🕵investigate Needs further analysis to find the root cause. and removed 🤔question Further information is requested or this is a support question 🦸‍♀️enhancement🦸‍♂️ New feature or request labels Oct 4, 2019
GerHobbelt added a commit that referenced this issue Apr 21, 2020
…new bits of technology to be integrated into Qiqqa as we upgrade the functional elements to modern standards (embedded browser, etc.): #2 #7 #34 #35
@GerHobbelt
Copy link
Collaborator Author

This is due to the Sorax library not handling certain PDFs.

See also #209

AFAICT this bug doesn't exit in MuPDF, at least not in the same form. Keeping this one open until #209 is done, as it's a known issue and a nauseating one.

GerHobbelt added a commit to GerHobbelt/qiqqa-open-source that referenced this issue Jan 18, 2021
…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
@GerHobbelt
Copy link
Collaborator Author

See #209. This was a SORAX-specific bug. As bleeding edge now has kicked out SORAX, this problem at least is gone.

@GerHobbelt
Copy link
Collaborator Author

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 qpdf before importing into Qiqqa is not needed any longer.

GerHobbelt added a commit to GerHobbelt/qiqqa-technology-tests that referenced this issue Sep 14, 2022
…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛bug Something isn't working 🕵investigate Needs further analysis to find the root cause.
Projects
None yet
Development

No branches or pull requests

1 participant