Repository navigation
LumenPDF 0.3.0
Six things that made LumenPDF feel broken rather than unfinished.
Printing
There was none. A PDF application without printing is a strange thing to ship.
Page ranges, copies, greyscale, fit-to-page or actual size — and printing to a
PDF file keeps the document's own page size instead of reflowing it onto A4.
Pages are rasterised through PDFium at the printer's own resolution rather than
handing the printer a PDF, so what is on screen is what comes out: annotations,
filled form fields and OCR text layers included, instead of depending on how
complete the printer's own PDF interpreter is.
Links
They did nothing when clicked.
Internal jumps now follow. External links always show you the real target
first, because what a PDF prints on the page and where its link actually
points are two unrelated strings. Only http, https and mailto are ever
handed to the system, and a Launch action — one that names a program to run —
is not offered as a link at all.
Encrypted documents
A password-protected PDF was refused with a message. It now asks for the
password. It is used once and written nowhere: this application has no keystore
of its own, and storing someone else's document password without one is not a
trade worth making.
It remembers things now
Theme, window size, the last dozen files you opened, and where you stopped
reading in each of them. None of that survived a restart before — switching to
the light theme and finding it dark again next launch was the daily version of
this.
繁體中文・简体中文・日本語
The interface was English only. It now ships fully translated in three more
languages and follows your system locale by default.
Only complete translations are offered. A partial one falls back to English
string by string and produces a window in two languages with no error anywhere.
Adding a language is a single JSON file — see
translations/README.md.
Tests run on their own
Every push now builds and runs the full suite on GitHub Actions — 107
assertions, up from 65. Releases are built the same way and are not published
if they fail.
Two real bugs this found
CMakeLists.txt still said 0.1.0 after v0.1.0 and v0.2.0 had shipped, so
the v0.2.0 binary reported itself as 0.1.0. The new update checker would have
told those users an update was available forever. The release workflow now
refuses to publish a tag that does not match the declared version.
annotationAt() could close a page held by the form-fill environment.
PDFium caches page objects per document, so that would have destroyed the
widget state of whoever was editing that page — the same cause as an earlier
run of form bugs.
Please read before trusting it with something
The signature feature is an ink stamp, not a cryptographic digital
signature. It does not identify who signed and does not break if the document
is altered afterwards. If you need a legally recognised signature, this is not
it. The wording in the README and on the site has been corrected to say so.
The installer is not code-signed, so Windows SmartScreen will warn on first
run — More info → Run anyway. A certificate is issued to an identified legal
entity and costs a few hundred dollars a year; the support is implemented and
waiting for one. See
docs/CODE-SIGNING.md.
Verify your download against SHA256SUMS.txt:
(Get-FileHash .\LumenPDF-0.3.0-win64-setup.exe -Algorithm SHA256).Hash.ToLower()Still not built
Annotation review sidebar, sticky notes and shapes · tabs · cryptographic
signatures · page composition (insert blank, crop, watermark, split) ·
PDF↔Office conversion · more UI languages · macOS and Linux.