[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
Manuel Geißer
bugzilla_noreply at kde.org
Sat Sep 11 11:42:18 BST 2021
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #16 from Manuel Geißer <geisserml at gmail.com> ---
> I think you should report at PDFium, pdf.js, Poppler, and pikepdf.
Be careful - there are considerable differences between these libraries. I
don't really know about pdf.js and PDFium, but pikepdf is quite low-level and
does not provide a function to obtain page size on its own - this needs to be
done downstream using CropBox/MediaBox, UserUnit, and Rotate.
> There is also a muPDF backend for Okular. Did you try that? `mutool info userunit_10.pdf` reports `[ 0 0 17856 17856 ]`.
Yes, I am aware that MuPDF directly takes /UserUnit into account. I noticed
this during the tests for my lib (which also has a (Py)MuPDF rendering
backend).
How do I obtain the MuPDF backend for Okular, though? Is it possible that KDE
Neon does not provide it? (I already have the okular-extra-backends package
installed...)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Okular-devel
mailing list