Is there a way to "push" a book to a Kobo reader wirelessly?

[rantanplan]

Originally Posted by salamanderjuice

Setup a Calibre-Web server (https://github.com/janeczku/calibre-web). Runs on top of a Calibre database and offers Kobo sync. Basically you change the Kobo store URL to the location of your Calibre-Web server and then when you sync the Kobo it syncs with your "store". You can set it up so that only certain shelves will sync and it can still sync to the real Kobo store if you or her do purchases there. I've been using it on my Libra Color and it's great. Only complaints are it doesn't sync reading progress, just the books nor does it do PDFs just ePub. Might be overkill for your purposes but for me, it's been the best way to manage my eBooks I've ever had.

While that works perfectly well, that also poses that danger of corruption as both apps are not aware of each other. So, please make sure to always stop the calibre-web Windows service / systemd service / docker container before running the Calibre proper application.

[salamanderjuice]

Originally Posted by rantanplan

While that works perfectly well, that also poses that danger of corruption as both apps are not aware of each other. So, please make sure to always stop the calibre-web Windows service / systemd service / docker container before running the Calibre proper application.

Yes, I do. It's very very rare I run Calibre proper anyways these days.

[berrrnard]

Originally Posted by salamanderjuice

Setup a Calibre-Web server (https://github.com/janeczku/calibre-web)..

Is there a way to make it so that KEPUB files are downloaded onto the device rather than regular EPUB files?

[salamanderjuice]

Originally Posted by berrrnard

Is there a way to make it so that KEPUB files are downloaded onto the device rather than regular EPUB files?

Yes, you can specify a path to a kebubify binary and it will convert books to kepub on sync.

[mramosch]

Does anybody know exactly what tools like kepubify do and how does it differ from simply renaming a file from .epub to .kepub.epub.

Do they perform this excessive <span business that KOBO uses for their internal navigation?

[PeterT]

Originally Posted by mramosch

Does anybody know exactly what tools like kepubify do and how does it differ from simply renaming a file from .epub to .kepub.epub.

Do they perform this excessive <span business that KOBO uses for their internal navigation?

Of course they do. Without those spans features like keeping track of location within the book will not work.

You could of course peruse the GitHub repository for kepubify and learn more. https://github.com/pgaskin/kepubify


Sent from my Pixel 7a using Tapatalk

[mramosch]

Yeah, I’ve already been to pgaskin’s GitHub page but haven’t had enough time yet to go through all his repositories. But thanks anyways for the link.

By the way: Is there a place where one could get in contact with developers of alternative eReaders like e.g. KOReader ?

I couldn’t manage yet to have KOReader on the KOBO device let fall through taps to reach my Javascript layer like AppleBooks, BookFusion or even the KOBO app on iOS do.

A workaround with links/footnotes/endnotes is not acceptable especially because of the buggy implementation by KOBO.

I really need to find a way to have taps interact with my JS code. It’s so amazing on iOS and I don’t wanna miss out having the same great experience on e-Ink.

[PeterT]

There is a koreader forum here in MobileRead. And a web site https://koreader.rocks/ and a GitHub repository https://github.com/koreader/koreader

Sent from my Pixel 7a using Tapatalk

[mramosch]

And that’s where KOReader developers lurk around?

Because I wanna eventually really know for sure whether this is (or likely will be) supported sometime in the near future. Not just guessing around with other people for probabilities ;-)

[PeterT]

I've no idea at all. Why don't you just go and check those resources out and see.

Sent from my Pixel 7a using Tapatalk

[mramosch]

I’ll definitely do that! Thanks for the hints…

[PeterT]

My limited research is that KoReader does NOT support JavaScript and is unlikely to do so.

Sent from my Pixel 7a using Tapatalk

[mramosch]

Thanks Peter! Do you know of any other KOBO compatible reader that supports tap interaction/propagation to JS.

Plato?

[PeterT]

No idea at all. However I seriously doubt that any exist.

From what I can tell many of the 3rd party reading apps play very loosely with their support for even the basic CSS in eBooks.

Sent from my Pixel 7a using Tapatalk

[Aleron Ives]

I suspect that security is also a factor. A bad actor could potentially do a lot more damage with a deliberately malformed e-book that has JavaScript in it compared to one that doesn't, so since most e-books don't need JavaScript, it's both easier and safer to leave it unsupported.