top | item 24159891

(no title)

onyva | 5 years ago

Is it more than just an ePub reader? You really feel it’s justified to spin-up an electorn app (!!!) to read an ePub? I use Emacs’ nov.el or Foliate which are not only low on resources but also instantaneous to open files.

discuss

order

chocolatkey|5 years ago

I don't like it either, but the only way it is technically feasible to support the full potential styling/markup of an EPUB is to use a browser engine, and therefore electron is a logical choice. Can your specialized EPUB reader support MathML? Or vertical-ttb text?

Finnucane|5 years ago

Just this. Epub depends on the same tech stack as the web. So, either you use an engine that supports that in full, or you are going to be missing pieces of the standard. Which means that most other reading software opts for missing pieces of the standard.

ognarb|5 years ago

I have a bad news for you, recently I was interested in how could I write a good QML/Kirigami based ebook reader and looked at all the existing Linux epub reader and each one was using a webview for the epub rendering. But they usually try to integrate better with the rest of the app and your DE so you just don't see it.

EDIT: the only epub reader I know that doesn't use a webview is Okular and the rendering using QTextDocument basic html support is horrible.

hombre_fatal|5 years ago

I ran into a similar realization when I set out to build my own minimal RSS reader.

Your options are A) web view, B) crappy RSS reader.

popup21|5 years ago

It's irrelevant to me whether or not it's an electron app. I'm not running a Pentium 486 system. I've got more RAM than I know what to do with...I'll run a half-dozen instances of Thorium if I wanted to...no worries.

onyva|5 years ago

It’s not just resources. It’s usability. Electron apps look and feel out of place to me. I would personally never use one let alone for reading an ePub. I get the point about perfect rendering, but that’s a specific problem I’m personally not worried about.