Skip to main content

A fail: Okular PDF Reader (an alternative to Foxit PDF Reader for Linux)

The project is to build a Linux Mint machine to have the identical functionality and ergonomics as the existing Windows 10 machine. This stage relates to reading and annotating PDF files.  It is a test of a secondary piece of software following a fail of Foxit PDF Reader for Linux.

Environment & required functionality

Reading and annotating PDF files need to happen on the following machines:
  • The Linux Mint Xfce 18.3 laptop "Gandalf";
  • The Windows 10 laptop "Legolas".
The synchronisation agent is Google Drive in Windows 10, and grive2 in Linux Mint.

Alternatives

From the fail of Foxit PDF Reader, alternatives are required.

Sources:

Software selection

From the above sources (especially Linux.Com of 2014), it looks like Okular might the best candidate for a test.

Evince failed to qualify because it seems unlikely to meet the minimum requirement of annotating PDFs.

Installation experience

Easy, but not necessarily the desired outcome.

In Gandalf's admin account, used Software Manager to find Okular.  Selected and installed Okular 4.15 (so it said) via Software Manager (part of KDE flathub).

Took a very long time, >30 seconds for <300Mb of disk space consumption.

In the CLI, top revealed no particular problems, Gandalf was working all the time.  Bounced Software Manager to kick the process.  Found out that Okular had indeed been installed and clicked to launch it, to prove installed.  Okular launched.

Oddly, Okular was not immediately available from the Xfce start menu, but ran from CLI as okular.  App "Application Finder" also found Okular, but didn't run it.

However, logged out of admin, logged into non-admin user, Okular now appears in and runs from the start menu, as it should.

User experience

Immediately presented with normal-looking window, menus are accessible by keyboard, and the standard keyboard shortcuts are available.  Good start.  CTRL+O opened the file open dialogue box in ~/documents.  So it should be simple enough to type ../grive/PRIV/Project[...] to navigate to the folder in which the test PDF file is located?

Nope!  Okular's file open decided it couldn't cope with this and presented a false error message about being unable to open a file that it hadn't been told to open yet.  Accompanying the false error message was an undesired piano-like sound effect.  (Had Gandalf's apps got a general permission to make any noises?)  Had to revert to using the keyboard (or the mouse) to use the GUI objects to navigate to the test PDF file.  The alternative would have been to use the CLI out the outset.

(A minor irritation, but one that demonstrates that, once again, a different Linux app uses a different set of libraries that re-invent the triangular wheel... there appears to be too little standardisation in the Linuxverse, too many forks, too much false choices.  This can happen in the Windowsverse, but Windows developers just seem less keen to re-invent wheels!)

Opened a known good test file and the file is all present & correct, complete with annotations saved previously on Legolas and grived to Gandalf.  However, there is no ability to annotate from within this instance of Okular.

Okular's About reveals that it is 0.24.2 on KDE platform 4.14.16.  This is nothing like as advertised in the Software Manager.

There might be a different way to find the appropriate version of Okular, but this will then turn into a wild goose chase.  At this rate, the Windows user will be constantly testing software instead of actually using it to be productive, and should therefore stick with Windows.

Conclusion

Okular did not meet the minimum requirements, so counts as a FAIL on this project.

Test completed May 2018.

Comments

Popular posts from this blog

Scanning & OCRring to PDF: Simple Scan, gimagereader and gscan2pdf v NAPS2 for Windows

The project is to build a Linux Mint machine to have the identical functionality and ergonomics as the existing Windows 10 machine. This stage relates to scanning paper documents to PDF and digitising the scanned text via optical character recognition. Environment & required functionality The scan-and-OCR function needs to run on the following machines: The Linux Mint Xfce 18.3 laptop " Gandalf "; A Linux Mint Xfce 18.3 virtual machine " Gimli "; The Windows 10 laptop " Legolas ". In any modern office - whether at home or at work - some transactional documents and documents from public authorities still arrive by snail-mail. This requires the ability to scan all documents, optionally with the digitisation of scanned text (typically via optical character recognition). The hardware is an old HP OfficeJet Pro 276dw, connected to the LAN instead of directly to a workstation. Alternatives There are two strategies: To use the software pr

An attempt at full-disk encryption: Vera Crypt

The project is to build a Linux Mint machine to have the identical functionality and ergonomics as the existing Windows 10 machine. This stage relates to testing full-disk encryption using VeraCrypt . Environment & required functionality Full-disk encryption needs to run on the following machines: The Linux Mint Xfce 18.3 laptop " Gandalf "; The Windows 10 laptop " Legolas ". The objective requirement is to protect user data from the physical theft of the physical machine, to provide an additional line of defence against data loss. This is probably more important for Windows than for Linux Mint.   Even so, in both cases, the operating system is likely to log activity which can reveal personal data and user (meta)data. Full-disk encryption does not mitigate against Microsoft’s sinister telemetry functionality, for which the main solutions seem to be: Either to use tools whose developers are constantly on the prowl, hunting for t

The Big Bang: Microsoft Windows goes for good, positive adaptations required

On 27Mar2021, Linux Mint ate Microsoft Windows 10 on Legolas. Three months on, I conclude beyond any doubt that wiping out Windows was the best decision I ever made. The second best decision I ever made was to test Linux Mint in Virtual Box five years ago. The third best decision I ever made was to take ownership of the learning curve that migrating in Windows really entails. A quick reminder: what’s Microsoft Windows like nowadays? I still need to use Windows at work. I cannot easily describe how painful it now is to use Windows. So I’ll try to describe it difficultly. My work machine is a powerful beast, but it exhibits constant latency. For a keyboard-orientated power user, this means that some keystrokes go walkabouts when other services on the Windows machine go to nuclear war with each other, scrambling to feed their narcissistic self-importance for besieged system resources wholly at the user’s expense. Something on Windows tends to clear the keyboard buffer randomly, resulting