FBReader premium is free for Onyx devices

[pazos]

Congratulations if you have one.

https://fbreader.org/content/fbreade...-e-ink-readers


WARNING: The program is not recommended for CSS Warriors and was labeled as rubbish by JSWolf himself. Please don't try it if you suffer from strong bias or other conditions. Opening the program might hurt your eyes

[pazos]

Do notice that the app is a bit spyware-like, but at least they announce it and it is not mandatory.

Since version 3.0.18 FBReader wants to collect some anonymous info about users. “Anonymous” means FBReader does not send any personal details that allow to identify you. No name, no email address, nothing. On the other hand, we want to collect info about books you read, the frequency of the app usage, your typical actions, etc. Why?

There are two reasons. The first is that we want to do the app more convenient. And we need to know typical behavior patterns and problems. The second reason is curiosity. We are interested to know what do our users read and how. Maybe we will publish statistics like “The popular book of the month”.

If you select “Allow” below, we start to send the data, not more than 1Kb per day. The data will be sent over a secure (https) connection. If you prefer “Do not allow”, we send one message “A user does not allow to collect statistics”. Please note that if you have several devices, FBReader shows this message on all of them, as we do not detect if the user is the same. If you change your mind in the future, change the answer in “Statistics” section of the settings dialog.

Thank you if you decide to select “Allow”, and we wish you a pleasant reading, anyway.

[JSWolf]

I cannot say about the premium version, but the regular version of FBReader is rubbish for ePub.

[pazos]

Okay: I'm going to add a big warning to OP.

[Hrafn]

Features available in this premium version:
* Reading aloud (via Android text-to-speech)
* Google/Yandex Translate integration
* Built-in support for PDF and comic book formats
* Thumbnail library view

Not really a lot of use to me (and I moved away from FBReader to AlReader and then AlReader X some time ago), but may be of interest to some people.

[citytrader]

FBreader is my daily driver, I tested all of them and some are slow, others have pagination issues like Neoreader where the pagination is wrong, you read the first page number 1 and you move two pages ahead and it still shows page 1 (is an example), in FBreader the pagination counter advance as you move ahead in the pages like a normal book, the same issue of bad pagination has AIReaderX. The one I could like is Moon Reader but there is % of pages (no numbering), I wonder if the developers have ever read a book that shows only percentage instead of page numbers

[norweger]

Originally Posted by JSWolf

the regular version of FBReader is rubbish for ePub.

How come?

[JSWolf]

Originally Posted by norweger

How come?

Because it doesn't respect the CSS properly.

[norweger]

Originally Posted by JSWolf

Because it doesn't respect the CSS properly.

It doesn't respect the CSS that comes with the epub you are reading, or the CSS you have set as your general preference in the settings tab?

I've had a hard time getting the setup to look right in FBReader. That is my only gripe with the app, though.

[JSWolf]

The ePub CSS.

[Hrafn]

Originally Posted by citytrader

... others have pagination issues like Neoreader where the pagination is wrong, you read the first page number 1 and you move two pages ahead and it still shows page 1 (is an example), in FBreader the pagination counter advance as you move ahead in the pages like a normal book, the same issue of bad pagination has AIReaderX. The one I could like is Moon Reader but there is % of pages (no numbering), I wonder if the developers have ever read a book that shows only percentage instead of page numbers

I always assumed that the former problem was due to some reader apps using 'page' as defined by page-breaks in the ebook (probably to maintain consistency with the dead-tree version) -- with the potential for (particularly on smaller screens and/or with larger fonts) for multiple screen 'pages' per ebook-defined-pages.

I'm largely indifferent between either definition or percentage -- all I really need to know is how far through the book I am.

(And I actually prefer my reading app to ignore CSS -- as a more consistent reading experience is more important to me than following the vagaries of how the publisher defines the font.)

YMMV, of course.