Thread: Kobo Bug thread
View Single Post
Old 11-15-2020, 12:19 AM   #1315
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by bigwoof View Post
I'm having this same problem with fanfictions updated with calibre on my libra H2O and the latest firmware.
Um, no you are not. The problem that @JSWolf is talking about is with the page count while reading. Sometimes, it doesn't increase as you turn the page.
Quote:
The epub on the device is definitely updated. when I view it using other ebook-viewer directly from the Kobo mounted drive, the new chapters etc are there.

When viewing on the Kobo itself, the intro chapter shows the correct page count and number of chapters in the text but the new chapters are not accessible in the reader. It basically only allows access to the chapters it saw when it *first* opened the book. any new chapter added after that point are unaccessible.

The only solution I have found is to mark the book as unread and then reboot the Kobo. that clears whatever cache it has and it reads the full book just fine next time.

The books are all sent to the Kobo using calibre and the extended driver to convert them automatically to kepub btw. The metadata is being updated properly and collections are being created etc.
Unfortunately, that is working as designed. What happens when you add a book to the device is that it imports details of it into an internal database. This includes the ToC. If you replace the book, the behaviour of the device it to remove it from the internal database and import the book as a new book. This means that you lose the reading position and annotations from the book.

Because of those last two points, calibre cheats. When you resend a book, it will update the device in such a way that it will not remove the book. That will retain your reading status and annotations, but, it does not update the ToC or metadata. It means that if you make minor changes (spelling, styles, etc.) the book will load with no problems. But, if you make structural changes, such as to the ToC or the internal file structure, these will not be picked up.

You can turn this behaviour off in the driver. Uncheck the option "Do not treat replacements as new books". After that, any changed book will be treated as new and reimported.
davidfor is offline   Reply With Quote