plato VS The-Open-Book

Kobos[1] and Pocketbooks[2] are a lot more open than Kindles. AFAIK you can transfer .epub files into both devices and these epubs are perfectly readable via the stock OS. If for some reason you find the stock proprietary OS lacking, you can install an open source one like KOreader [3] or Plato[4]

Of course you want a good way of organizing epubs pdfs mobi, and like has already been mentioned Calibre[5] is a great option.

[1]https://www.kobo.com/

[2]https://pocketbookstore.com/en-ca

[3]https://github.com/koreader/koreader

[4]https://github.com/baskerville/plato

[5]https://calibre-ebook.com/

KOReader is nice. There's also Plato[0] for Kobo, which unlike the Kobo Libra 2 stock reader and KOReader didn't choke on an .epub with the entire Bible in one xhtml file.

[0]: https://github.com/baskerville/plato

Good luck! If you don't like it, there are a few other, similar projects, like Plato. That one is focused on speed and simplicity, so it might actually be better suited to your purposes. It was left unmentioned earlier because it's been incredibly buggy for me, but it's there.

plato

I noticed some similarities in the source code to https://github.com/baskerville/plato/

Is there some common source for Kobo-compatable rust code that you both drew from, or was plato the original source?

On the issues page of its github site. Create a new issue with [Feature request] tag in title.

I don’t really know much about Koreader’s reader (I use it mostly as a file manager/sftp server/OPDS client), but I heartily recommend Plato to read manga! It shows the pages full screen with no margins on the top or the bottom. I haven’t tried with kepubs though, I just read my cbz directly, without passing them though kcc.

Have you seen the "Open Book" project?

https://github.com/joeycastillo/The-Open-Book

Open book project https://github.com/joeycastillo/The-Open-Book

If you want to get all custom, you could build an e-reader https://github.com/joeycastillo/The-Open-Book https://www.tomshardware.com/news/raspberry-pi-pico-powered-open-source-ebook-reader

>I really wish I could have an e-reader, but again, I don't want to spend money on things that will lock me into a single vendor indefinitely and might just arbitrarily go away.

https://github.com/joeycastillo/The-Open-Book

This may be up your alley.

It's not a commercial off the shelf product, but the Open Book uses a 4.2" screen. There are other devices you can find on places like AliBaba that are kinda small. However, in general you won't find a name brand commercial ereader under 6" that isn't ina phone body. There were a couple at 5" back-when but the industry really settled on 6" as the common base size.

This is very useful to see examples of how people have used APIs that are either poorly documented or not at all. Or even that are well documented, really. Going from docs to code is not always straightforward.

To give you just one example, recently I've been using it to find how people have written code to interface with e-ink displays. I usually have the datasheet which lists all the commands the protocol support, but building it all into a valid startup sequence of ~20 commands to activate the display is left as an exercise for the reader.

So the docs will look like this: https://www.waveshare.com/w/upload/6/6a/4.2inch-e-paper-spec...

And what I need is a sequence like this: https://github.com/joeycastillo/The-Open-Book/blob/5c5054c58...

There is a link to the project early in the article: https://github.com/joeycastillo/The-Open-Book