You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Quba-Viewer-1.4.0 on Linux, opening the application including a PDF file name will not render the PDF content, but produce a content warning instead.
If the PDF contains structured content, the PDF display on the left reports the error, while the structured content pane is displayed with proper content from the PDF's structured data.
Opening the same PDFs via d&d or Ctrl-O works properly
The detailed error message reveals that Quba-Viewer is trying to render the PDF using a container-based path, instead of the host file system:
PDF.js Version 2.9.359 (build: e667c8cbc)
Nachricht: Missing PDF "file:///tmp/.mount_Quba-1zAq2sf/resources/app.asar/dist/lib/pdfjs/web/somedir/somefile.pdf".
The text was updated successfully, but these errors were encountered:
assuming that AppImage packaging is only used on Linux, it is expected that the error won't show on Windows :)
Additional info: This only happens with relative file names - which is likely the reason why other methods of opening the file do work. AFAIR, even opening files via "Desktop" operations will hand the absolute file name (with leading "/") to the application.
assuming that AppImage packaging is only used on Linux, it is expected that the error won't show on Windows :)
the code is the same for win , mac and linux and in that particular part of the functionality there is not distinction
Additional info: This only happens with relative file names - which is likely the reason why other methods of opening the file do work. AFAIR, even opening files via "Desktop" operations will hand the absolute file name (with leading "/") to the application.
And that I actually could reproduce on windows if there is a manual we will include it #58 . Background is probably that it had been requested to be able to be the default software assigned with file types and the OS
Using Quba-Viewer-1.4.0 on Linux, opening the application including a PDF file name will not render the PDF content, but produce a content warning instead.
If the PDF contains structured content, the PDF display on the left reports the error, while the structured content pane is displayed with proper content from the PDF's structured data.
Opening the same PDFs via d&d or Ctrl-O works properly
The detailed error message reveals that Quba-Viewer is trying to render the PDF using a container-based path, instead of the host file system:
user@host:~> bin/Quba-1.4.0.AppImage somedir/somefile.pdf
PDF.js Version 2.9.359 (build: e667c8cbc)
Nachricht: Missing PDF "file:///tmp/.mount_Quba-1zAq2sf/resources/app.asar/dist/lib/pdfjs/web/somedir/somefile.pdf".
The text was updated successfully, but these errors were encountered: